01Documentation plugin
ChatGPT, Codex and Claude Code documentation plugin
The public documentation plugin at bot-creator.fr/api/mcp does not require a Bot Creator account and does not access bots, Discord tokens, payments or private account data. It receives the arguments sent in documentation tool calls (for example a search query, command intent or proposed Blocks action list), along with technical request data processed by Cloudflare, including IP address, requested URL and user agent. Do not submit secrets or sensitive personal data.
Tool arguments are processed to search, read or validate public documentation. The MCP implementation does not save conversations or tool-call arguments in a Bot Creator application database. Cloudflare processes technical logs under its own hosting policy; no additional fixed retention period for these provider logs is promised here. Public documentation may be cached; this is not a cache of your private account or bot state.
These operations provide the requested documentation service; technical security processing protects its availability. ChatGPT and Codex separately process your conversations under OpenAI’s own terms and privacy policies, and Claude Code under Anthropic’s. This plugin does not retrieve your OpenAI or Anthropic account or entire conversation history. In Claude Code, the plugin’s optional validation hook sends only the Blocks action list of the *.botcmd.json files it checks to the same endpoint. Sending a support email shares the information you include with the publisher for handling your request.
Jeremy SOLER is the publisher and contact for requests concerning Bot Creator processing: [email protected]. The controller details, service providers, international transfer information and available privacy rights are described elsewhere on this page. See also plugin support and plugin terms of use.
02Who we are
The data controller is Jeremy SOLER, sole trader in France.
Bot Creator (website bot-creator.fr, mobile and desktop apps, the Docker runner, the Manager API at api.bot-creator.fr, the web console at app.bot-creator.fr and the dashboards hosted at dash-<id>.bot-creator.fr) is published by Jeremy SOLER, Entrepreneur Individuel, 9 rue Gagnée, 94200 Ivry-sur-Seine, France (SIRET 883 556 128 00014). Contact for any privacy request: [email protected].
No separate data protection officer is designated: privacy requests are handled directly by the publisher, Jeremy SOLER.
03In short
What is stored where, honestly.
- If you only use the app with your own bot and local features: bot configuration and your bot token stay on your device (token in the system secure storage). The app still sends usage analytics and crash reports to third parties (see “Analytics and crash reporting”) and shows ads unless you subscribe.
- If you sign in with Discord, use cloud hosting, the Copilot (AI) or the web console: your account, your bots’ configuration and, when you save it to the cloud, your bot token are stored on our servers (the token is encrypted at rest). Earlier versions of this policy said tokens were never stored in a database. That was not accurate for cloud features and is corrected here.
- AI Copilot messages are sent to a third-party AI provider (DeepSeek).
- There is currently no self-service “delete my account” or “export my data” button. You exercise your rights by email (see “Your rights”).
- We do not sell your data. Discord data is used only to run the service you asked for, and is not sold or licensed to anyone.
04This website (bot-creator.fr)
What the website itself does when you visit it.
Fonts. The website loads fonts from Google Fonts (fonts.googleapis.com, fonts.gstatic.com), which transmits your IP address and browser details to Google when a page is displayed.
Hosting. The website is a static site hosted on Cloudflare Pages (Cloudflare, Inc., United States), which receives technical logs (IP address, requested URL, user agent). Cloudflare keeps these logs according to its own policy.
Public MCP server. bot-creator.fr/api/mcp serves public documentation to AI tools. It requires no account; requests are processed by the hosting platform and are subject to its technical logs.
Content editors. The /admin editor, reserved for site editors, loads a script from unpkg.com and signs in through GitHub via an OAuth proxy. It is not used by visitors.
The website itself does not use analytics cookies and sets no cookie or browser storage of its own. It displays no advertising.
05Data we process
Categories, purposes and retention.
Retention periods below are those configured in the software today. Where we write “until deletion”, no automatic purge exists yet; the data is removed when your account is deleted at your request.
| Data | Where / who | Purpose | Retention |
|---|
Discord account: user ID, username, display name, avatar. Discord sign-in requests the identify scope only (not your email address or your server list). | Manager database (PostgreSQL) | Sign-in, ownership of bots, support | Until account deletion |
| Discord OAuth access and refresh tokens | Manager database, encrypted (AES-GCM) | Keep you signed in with Discord | Until account deletion |
| Email and password hash, only if you register with email and password (bcrypt hash; we never store the password itself) | Manager database | Sign-in | Until account deletion |
| Session refresh tokens (hashed), push notification device tokens (FCM) and platform / language | Manager database | Sessions, notifications | Until expiry / revocation / deletion |
| Discord bot tokens, when you save a bot to the cloud, use the cloud runner or the web console; bot OAuth client secret and bot database credentials when you provide them | Manager database, encrypted (AES-GCM). Decrypted in memory by our servers and runners to connect your bot. The owner can retrieve their token from the app. | Run your bot | Until you remove the bot or your account is deleted |
| Bot configuration: commands, workflows, scripts, variables and values that your commands store (these may contain Discord user IDs, server IDs or anything your own commands save), versions, statistics (command name, server ID, locale, latency) | Manager database and Cloudflare R2 object storage (bucket located in Europe); runner volumes | Run and edit your bot, history and rollback | Configuration and variables: until deletion. Execution sessions and hourly statistics: 30 days. Runner logs (technical messages, no message content): 7 days. Command execution records: until deletion. |
| Activity log of your account actions: action, request path, status, IP address, user agent, filtered request payloads (secrets masked) | Manager database and object storage | Security, abuse prevention, support | 90 days |
| Team and collaborator data: bot team members, collaborator permissions, in-bot team chat messages | Manager database | Collaboration features | Until deletion |
| AI Copilot: your messages, the answers, and the context sent with them (bot configuration, commands, runtime state, tool results); request and result records | Manager database; sent to DeepSeek (see below) | Provide the Copilot | Conversations: until you delete them; 90 days after you delete a conversation. Requests without a conversation: 90 days. Usage counters: kept. |
| Shared AI command library: commands you contribute, with contributor links (you can opt out) | Manager database | Improve Copilot suggestions | Until you withdraw / account deletion |
| Purchases: store transaction IDs, product IDs and the raw notifications received from Apple, Google and Ko-fi; Stripe identifiers (none yet, as Stripe payments are not open); AI credit ledger | Manager database; Apple, Google, Stripe; Google Play purchase logs are also exported to ChartMogul (analytics provider) | Entitlements, accounting, fraud prevention | Until account deletion; accounting records as long as law requires |
| Dashboard (web) visitors: Discord user ID, username and server list of members who sign in on a dashboard; session cookie (see below). We do not collect page-view statistics on dashboards. | Manager database / dashboard service | Run the dashboard, statistics for its owner | Until deletion; no automatic purge |
| Backups you create with Google Drive | Your own Google Drive, hidden application data folder only (drive.appdata scope) | Backup and restore | Until you delete them |
06Analytics and crash reporting
Used inside the apps; there is no opt-out setting yet.
The apps use Google Analytics for Firebase, Firebase Crashlytics and Firebase Performance Monitoring (Android, iOS and web builds; not the desktop builds) and PostHog (all platforms, EU-hosted at eu.i.posthog.com). They collect events (screens, app open, creating a bot or a command, subscription steps), device type, operating system, language, performance traces, crash stack traces, IP address and installation identifiers.
When you are signed in, your Discord user ID is sent as is (not hashed) to Firebase Analytics, Crashlytics and PostHog, together with properties such as platform, premium tier, number of bots (bucketed) and language.
For about 20 % of installations, PostHog also records session replays of the app screen. At the moment text and images displayed on screen are not masked, so a replay can show what you see in the app, including bot names and command contents. Replays are not masked.
PostHog is used internally only, to group user journeys and build heatmaps in order to improve the product, not for advertising. There is currently no setting in the app to switch analytics off. You can object to this processing by writing to [email protected]. Retention is set by the providers (Crashlytics crash reports are kept for up to 90 days); we do not control a shorter period.
07Advertising in the apps
Google AdMob, with consent prompts.
The free version of the apps shows ads from Google AdMob, which collects advertising identifiers (IDFA on iOS, AAID on Android), IP address and interaction data. A consent dialog based on Google UMP is shown on launch (and Apple’s App Tracking Transparency prompt on iOS). You can reopen your choices at any time from “Manage ad privacy choices” in the app settings. We do not use any ad mediation partner: ads come from AdMob only. Earlier versions of this policy named IronSource; it is not used.
Watching a rewarded ad can grant Copilot credits; the credit is attributed on our server. A paid subscription removes ads.
08AI Copilot
Your messages leave our servers for DeepSeek.
The Copilot is provided by our Manager, not by the app directly. Your messages and the context needed to answer (bot configuration, commands, runtime state and tool results) are sent to the DeepSeek API (api.deepseek.com) using our own account key. DeepSeek (Hangzhou DeepSeek Artificial Intelligence Co., Ltd.) processes them in China, as our processor under its standard online API terms and privacy policy, which we accepted when creating the API account. Data is encrypted in transit (HTTPS). The European Commission has not adopted an adequacy decision for China. The legal basis is performance of the contract (you ask for the Copilot, art. 6(1)(b) GDPR). We have no standard contractual clauses or other art. 46 GDPR safeguard in place with DeepSeek: its standard API terms are governed by Chinese law. The transfer is made because it is necessary to deliver what you ask the Copilot to do. Do not send personal data about other people in Copilot messages.
The context is sent as is: nothing is automatically removed or masked before it is sent. The Copilot is instructed never to ask for or repeat tokens or secrets, but that is an instruction to the model, not a technical filter: do not write tokens or personal data of third parties in Copilot messages.
09Discord data and bot tokens
How we handle data that comes from Discord.
- We use Discord data (your identity, your applications and their team, and the events your bots receive) only to provide the features you use. We do not sell it, license it to data brokers, or use it to build advertising profiles. The Discord user ID is, however, sent to the analytics providers listed above.
- Bots run on your device, on our runners or on a runner you host. A bot’s gateway intents are those you enable in the bot configuration and the Discord developer portal (for example Guild Members, Presences or Message Content). Runners process events in memory to execute your commands. Our logs and statistics do not record message content; data that your own commands save into variables or into a database you connect is stored as you configured it.
- If you run a bot in a Discord server, you are responsible for informing and obtaining rights from the members of that server. For the data your bots save through Bot Creator, you are the controller and we act as your processor, storing it on your instruction.
- Bot tokens are credentials governed by Discord’s Developer Terms of Service and Developer Policy. You can revoke a token at any time in the Discord developer portal; Bot Creator will then be unable to connect your bot.
- On request we delete the Discord data associated with your account (see “Data deletion”). Bot Creator is an independent service and is not affiliated with or endorsed by Discord.
10Web console and dashboards
Cookies, storage and who is responsible.
Cookies. The console and the dashboards set one strictly necessary session cookie each: bcm_creator_app (console, app.bot-creator.fr) and bcm_cms_dash (member sign-in on a dashboard). They contain your session tokens, are signed but not encrypted, HttpOnly, SameSite=Lax, Secure, bound to the host, and expire with the session. The console also stores two “tutorial already seen” flags and a panel width in your browser’s localStorage. We set no advertising or tracking cookie there.
Third-party content. The console and dashboards load fonts from Google Fonts and, on the console, a script from jsDelivr (GSAP); Discord CDN avatars are displayed; dashboard owners can embed YouTube or Vimeo videos. Each of these receives your IP address when displayed.
Dashboards hosted for bot owners. A dashboard at dash-<id>.bot-creator.fr or on a custom domain is operated by the owner of the bot. The owner decides its content and is responsible towards its visitors; Bot Creator hosts it and processes sign-in data for the owner. Default “Terms” and “Privacy” pages are generated for each dashboard as placeholders that the owner must replace with their own.
11Payments
Stores and Ko-fi today; Stripe is planned.
App stores (Apple, Google, Steam) process payments for subscriptions bought there; we receive transaction identifiers and status notifications. Stripe is not yet used for payments: web plans and creator sales are planned. When they open, Checkout will be hosted by Stripe (we will not see your card number) and this policy will be updated before the first sale. Ko-fi notifies us of donations or purchases made there. We keep identifiers and status, not card data.
Apple refund review (updated October 22, 2026). When the iOS app offers the separate, optional consent for this purpose, you may allow us to send Apple information about delivery and use of a specific purchase, whether a trial or product information was provided before purchase, and our refund preference. We associate the response with Apple's transaction identifier. Apple uses this information to assess a refund request and makes the final decision. We do not send Discord messages, bot tokens or AI conversation contents in this response.
Accepting these terms or this privacy policy alone is not this consent. We record your explicit choice, its version, date, language and source against your Bot Creator account. A missing or declined consent prevents this transmission. Declining does not prevent purchases or refund requests. In app versions offering this control, you can change or withdraw consent in Settings → Privacy → Apple refund data sharing. Withdrawal prevents future transmissions and does not undo information already sent to Apple. These rules do not create consent for earlier users.
12Hosting and service providers
The providers that receive data from us.
- Infrastructure: our servers (API, databases, runners) are hosted by OVHcloud in Gravelines, France (OpenStack region GRA), on a Kubernetes cluster fronted by Cloudflare (proxy and custom-domain service); container images are stored on GitHub Container Registry. The database volume is not encrypted at disk level (sensitive fields such as bot tokens are encrypted by the application). There is no separate database backup; a full backup of the whole server is taken every day.
- Google (Firebase Analytics, Crashlytics, Performance, Cloud Messaging for notifications, AdMob (apps only), Google Drive when you connect it, Google Play billing, Google Fonts).
- PostHog (product analytics, EU region). DeepSeek (AI Copilot). Apple, Ko-fi, ChartMogul (payments and subscription analytics); Stripe is planned, not yet in use.
- Discord (sign-in and the bot platform).
- Cloudflare R2 (S3-compatible object storage) for configuration and log payloads.
Some of these providers are located outside the European Economic Area (notably the United States). For Google and Cloudflare (United States, and Stripe once it is used), transfers rely on the EU–US Data Privacy Framework and/or standard contractual clauses. PostHog is used on its EU region. Apple, Ko-fi and ChartMogul act under their own terms. For DeepSeek (China), see the AI Copilot section.
13Legal bases
Why we are allowed to process this data.
- Contract: account, bots, hosting, subscriptions, support.
- Consent: personalized advertising (AdMob UMP / ATT, in the apps).
- Legitimate interest: security and abuse prevention (activity log), diagnostics, crash reporting and product analytics.
- Legal obligation: accounting and tax records.
The apps are not directed to children. A Discord account is required to use most features, and Discord sets its own minimum age. We do not verify age. If you believe a child under 15 has given us personal data, contact us and we will delete it.
14Data deletion
Request deletion of your Bot Creator account and data.
How to request deletion
There is no self-service deletion yet. Send an email to [email protected] with the subject “Data deletion request”, from the address linked to your account or mentioning your Discord user ID so that we can identify you. We reply without undue delay and, in any case, within one month.
What is deleted
- Your account and Discord / email identity, OAuth tokens and sessions.
- Your bots, their configuration, variables, versions, statistics, and the stored bot tokens and credentials (also from object storage and Redis).
- Your activity log and its stored payloads.
- Your AI Copilot conversations, requests and results, and your contributions to the shared command library (an entry shared with another contributor stays for them).
- Purchase links, collaborator links and team messages tied to your account.
What may remain
- Aggregated AI usage and cost counters, which are kept without the content of your conversations.
- Purchase and invoice records that we must keep for accounting and tax purposes.
- Administrative audit entries and technical logs held by our infrastructure providers, until they expire. Server backups and administrative audit entries are kept for at most 90 days, sometimes less.
- Data held by third parties under their own policies: Google (Firebase, AdMob), PostHog, Stripe, Apple, Google Play, Discord. Write to them directly to exercise your rights on data they hold as independent controllers.
- Data stored on your own device (including your token in secure storage) and in your own Google Drive, which you delete yourself.
15Your rights
GDPR and other privacy laws.
If you are in the European Economic Area, the United Kingdom or California, you have the right to access, rectify, erase, restrict, object to processing and port your personal data, and to withdraw consent at any time. There is no self-service export yet: on request we send you your data in a structured, commonly used format, within one month. Write to [email protected]. You may also lodge a complaint with your data protection authority (in France, the CNIL).
16Third-party policies
Privacy policies of services we use.
17Changes and contact
Questions about privacy.
We update this page when processing changes. The date below is the date of the last review. For questions, contact [email protected].
