1. Scope and roles
This agreement covers the personal data that you, the customer, put on Bot-Hosting.net or that your deployments collect: the files, databases, environment variables and traffic of your applications, bots and websites. For that data you are the controller and we are your processor. You decide what is collected and why, and you are responsible for having a legal basis for it.
Your own account data (your identity, email, payments) is not covered here: for that data we are the controller, as described in section 6 of our legal page.
This agreement forms part of our Terms of Service and lasts as long as we process your data. Where it conflicts with the Terms on a data protection matter, this agreement prevails.
2. Instructions and confidentiality
- We process your data only on your documented instructions. Those instructions are this agreement, our Terms, and what you do on the service: deploying, editing, restoring, moving or deleting through the dashboard, the API, the CLI or Ask AI.
- If EU or French law requires us to process your data otherwise, for example under a court order, we tell you first, unless that law forbids it.
- If we believe one of your instructions breaks the GDPR, we tell you.
- We never use your data for our own purposes and never sell it.
- Everyone we authorise to access your data is bound by confidentiality. We look at your content only to run the service, when you ask us for help, or to investigate abuse as described in section 1.5 of our Terms.
3. Security measures
3.1 What is in place
- Each deployment runs in its own container, with its own filesystem and its own CPU, memory and disk limits.
- Your deployment's domains are served over HTTPS, with certificates issued and renewed automatically by our edge proxy.
- Backups are encrypted on the node before they leave it (restic, AES-256), and stored with OVHcloud in Gravelines, France.
- Our edge proxy keeps no access logs. The console output of a deployment is kept on its node as a rolling buffer of at most 5 MB, and deleted with the deployment. Anything your own application logs is under your control.
- Anti-abuse monitoring sees resource use, process names and the number and destinations of network connections, never their contents. A person reviews every case before any action.
- Administrative access to the servers and to your deployments is limited to the people who run the platform.
- Our servers sit in third-party data centres that are physically secured and audited by their operators. OVHcloud and Hetzner hold ISO/IEC 27001 certification.
3.2 What is not in place, today
- Files, volumes and databases are not encrypted at rest. If you store sensitive data, encrypt it in your application.
- HTTPS ends at our edge proxy. The hop from the edge proxy to the node is plain HTTP. If you need end-to-end encryption, serve TLS from your own application on its port.
4. Subprocessors and transfers
You authorise us to use the subprocessors below. Each is bound by data protection terms that protect your data as this agreement does, and we remain responsible to you for them. Payment, email and sign-in providers only see your account data, so they are listed on our legal page instead.
| Subprocessor | What it does | Where |
|---|---|---|
| Hetzner Online GmbH | Servers running part of the deployment nodes, and the edge proxy that serves HTTPS traffic to your deployments | Germany and Finland (EU) |
| OVH SAS | Hosting of the dashboard and of part of the deployment nodes, and storage of the encrypted backups (Gravelines) | France (EU) |
| DataWagon LLC | Dedicated servers running part of the deployment nodes | United States |
| Cloudflare, Inc. | CDN and DDoS protection in front of the dashboard, and the Turnstile anti-bot check | United States |
| OpenRouter, Inc. and the AI model providers it routes to | Ask AI and Studio, only when you use them: your prompts and the files the assistant reads go to the model you pick | United States, China or other countries, depending on the model |
4.1 Changes to this list
We publish a new or replacement subprocessor in this table, with the date it starts, at least 14 days before it processes your data. The only exception is an urgent change needed to keep the service running or secure, such as replacing a failing provider, which we publish as soon as it happens. This page is how we inform you: check it, or its date at the top. If you object to a change, write to [email protected]. If we cannot resolve your objection, you may cancel and we refund the unused part of your current billing period.
4.2 Transfers outside the European Union
Where a subprocessor is in a country without an EU adequacy decision, the transfer relies on the EU-US Data Privacy Framework when that provider is certified, and otherwise on the Standard Contractual Clauses of the European Commission included in that provider's terms. Ask AI and Studio only send data to an AI provider when you use them, and the model you pick decides which one.
5. Personal data breaches
If we become aware of a breach affecting your data, we notify you without undue delay, by email to your account address. We tell you what we know: what happened, which data and roughly how many people are concerned, the likely consequences, and what we have done about it. We complete the notice as we learn more, so that you can meet your own obligations toward your supervisory authority and the people concerned.
6. Assistance and audits
- Requests from the people whose data you host. You can handle most of them yourself, since you have full access to your files and databases to find, export, correct or delete data. If you need more, we help. If one of those people contacts us directly, we forward the request to you and do not answer it ourselves.
- Your own compliance work. We give you the information you need for your records of processing, a data protection impact assessment or a consultation with your authority. This page answers most of it.
- Audits. You can check our compliance first through this page and by sending us your written questions or questionnaire, which we answer. If that is not enough, or a supervisory authority requires it, you or an auditor bound by confidentiality may audit us once a year at most, more often if there are signs of a breach, with 30 days' notice and at your cost.
7. Deletion
You can download your data at any time, through the file manager, SFTP or your database. When you delete a deployment or your account, its files and databases are destroyed on the node at once, and its encrypted backups are erased within 30 days. If your plan lapses, deletion follows section 3.6 of our Terms. We keep no copy afterwards, unless the law requires it.
8. Description of the processing
| Subject matter | Hosting the applications, bots, websites and databases you deploy |
|---|---|
| Duration | As long as you use the service, then until deletion as described in section 7 |
| Nature | Storage, running your code, network transmission, backup and restore, deletion, and reading by the AI assistant when you use Ask AI or Studio |
| Purpose | Providing the service you signed up for |
| Types of data | Whatever your deployments process, which you decide. Typically names, usernames and user ids, contact details, IP addresses, messages and form submissions |
| People concerned | Users and visitors of your applications and websites, members of the Discord servers your bots are in, and your own staff |
| Special categories | None required by the service. If you process health or other sensitive data, the additional safeguards are yours to apply, starting with section 3.2 |
9. Parties and signature
This step is optional: the agreement already binds both of us through the Terms. If your records need a signed copy, fill in your details, save the page as a PDF and sign it. What you type stays in your browser.
Processor
Leo Andert, entrepreneur individuel, trading as Bot-Hosting.net
9 rue du Clos Poulain, 41350 Huisseau-sur-Cosson, France
SIREN 894 885 003, VAT FR86894885003
[email protected]
Signed for the processor
Leo Andert, operator, on 20 November 2026
Controller (the customer)
________________________
________________________
Signed for the controller
________________________, on 20 November 2026
Signature
French law applies, as for our Terms, and the limitation of liability in section 1.7 of the Terms applies to this agreement to the extent the law allows. We may update this agreement: the date at the top shows the version in force, and a change that reduces your protection is published here at least 14 days before it applies.