Privacy policy
Este documento ainda não está disponível no seu idioma: está a ler a versão inglesa. A ClearCloud é uma empresa francesa e estas condições regem-se pela lei francesa: em caso de divergência, prevalece a versão francesa.
Article 1 — Data controller
ClearCloud — SIRET 53993273100034
21000 Dijon, France
GDPR contact: contact@clearcloud.fr · Security contact: contact@clearcloud.fr
Article 2 — Data collected
Account data: email, name (if provided), role within the organisation. If you choose to sign in with Google, GitHub or GitLab, the provider passes us your email and your name; we receive neither a password nor access to your repositories.
Monitoring data: monitored URLs and targets, monitor settings (including, if you enter them, HTTP credentials or authentication headers), check results (status, HTTP code, latency, timestamp, region), incidents and maintenance windows.
Alert configurations: recipient email addresses, webhooks and tokens for the tools you connect (Slack, Discord, PagerDuty…).
Phone numbers (SMS alerts): the mobile number a member of your organization enters in an SMS channel. We never collect it on our own: it is not taken from your account or asked for at sign-up. It is encrypted at rest with the channel's configuration and used only to send that channel's alerts (down, recovery, test) and the code that checks its holder agreed to receive them. The SMS log only keeps a masked version of the number (+336•••••78). Only enter someone's number with their consent.
Billing data: processed by Stripe — OKStatus never stores card numbers, only a Stripe customer identifier and the invoice history.
Technical data: IP address and user agent of connections to the dashboard and the API, an audit log of actions (who changed what, when, from which IP). Aggregated audience statistics via Matomo, self-hosted by ClearCloud in France, on public pages only: no cookie, no individual identifier, IP address anonymised (last two octets removed) before being recorded.
Status page subscribers and visitors: email address of notification subscribers (double opt-in); for a problem report, the optional email, the message and the IP address.
Article 3 — Purposes, legal bases and retention periods
| Data / purpose | Legal basis | Retention |
|---|---|---|
| Account and organisation | Performance of the contract | Until the account is deleted (immediate on request) |
| Check results | Performance of the contract | 90 days (Free) · 180 days (Pro) · 365 days (Max) · 730 days (Enterprise), then automatic daily deletion |
| Resolved incidents, ended maintenances, status page announcements, deployment markers | Performance of the contract | Same duration as check results |
| Status pages, monitors, alert channels and other settings | Performance of the contract | For the duration of the subscription |
| Support requests sent from the dashboard | Performance of the contract | 24 months after handling |
| Delivery events of the e-mails we send (receipts, bounces) | Legitimate interest (deliverability) | 90 days |
| History of alerts sent | Performance of the contract | Same period as check results |
| Phone number of an SMS channel | Performance of the contract | As long as the channel exists; deleted with it |
| SMS log (masked number, credits used, status) | Performance of the contract (record of the credits used) | 13 months |
| Audit log | Legitimate interest (traceability, security) | For the duration of the plan, with a minimum of 12 months |
| Visitor reports | Legitimate interest | 12 months after archiving |
| Billing | Legal obligation | 10 years (Stripe) |
| Technical logs (access, application) | Legitimate interest (security) | 30 days |
| Database backups | Legitimate interest (continuity) | Rolling 30 days — deleted data disappears from backups within 30 days |
| Aggregated audience statistics | Legitimate interest | No individual identifier |
No plan has unlimited retention. An Enterprise customer may request a shorter period than their plan's ceiling.
Article 4 — Sub-processors
The list below is exhaustive for the operation of the service. It is dated; any change is announced to Enterprise customers with 30 days' notice (see the DPA).
Reference list, dated, with history and RSS feed: okstatus.eu/legal/sous-traitants.
| Sub-processor | Role | Location | Data |
|---|---|---|---|
| OVHcloud | Object storage (database backups, PDF reports, logos), hosting of the monitoring probes, and hosting of OKStatus's own status page (status.okstatus.eu) and its probes, outside the monitored platform | France — object storage and OKStatus's status page in Gravelines (GRA). United Kingdom — public probes, OVHcloud site in London (Erith): the London region, plus the regions that do not yet have a probe on site (all except Paris, Frankfurt, Madrid, Amsterdam and Warsaw), which run from this same site until they are deployed United Kingdom: European Commission adequacy decision | Database backups (all service data), reports and logos; for the probes, check requests to your targets, with the monitor's credentials if it has any |
| Scaleway | Hosting of the platform (applications, database, identities) since 26 September 2026, and of the Paris region probe since 10 October 2026; transactional email delivery (alerts, notifications, reports, address verification) and the associated message queue | France (Paris, PAR2 datacentre) | All service data (accounts, monitors, results, incidents, status pages, logs); recipient email addresses and notification content |
| Stripe | Subscription payment and invoicing | Ireland (EU); Stripe, Inc. group (United States) for payment processing Standard contractual clauses (module 2) and Stripe's DPA | Billing identity, address, payment method (never stored by OKStatus), invoice history |
| Google · GitHub · GitLab | Social sign-in (OAuth), only when you choose that sign-in method | United States Each provider's own transfer framework (EU-US Data Privacy Framework / standard contractual clauses) | Email address, display name |
| Cloudflare | DNS and proxy for OKStatus's own status page (status.okstatus.eu) only; the rest of the service does not go through it | Global network, point of presence closest to the visitor EU-US Data Privacy Framework and standard contractual clauses (Cloudflare's DPA) | IP address and HTTP headers of status.okstatus.eu visitors |
| Browser push services | Delivering push notifications to the device, only if you enable the push channel; the service used depends on your browser or the app | United States Each provider's own transfer framework (EU-US Data Privacy Framework / standard contractual clauses); content end-to-end encrypted (Web Push, RFC 8291) | Device subscription identifier, encrypted notification content (monitor name, status) |
| UpCloud | Hosting of the monitoring probes for the Frankfurt, Madrid, Amsterdam and Warsaw regions (one machine per region, on site) | European Union — Germany (Frankfurt), Spain (Madrid), Netherlands (Amsterdam), Poland (Warsaw) | Check requests to your targets, with the monitor's credentials if it has any, and their results (no account data) |
| OVHcloud SMS | Sending SMS alerts and number verification codes, only if you create an SMS channel | France; the SMS is then delivered by the recipient's mobile operator (European Union, European Economic Area, United Kingdom or Switzerland) United Kingdom and Switzerland: European Commission adequacy decisions | Recipient's mobile number, SMS text (monitor name and address, status, region) or verification code |
The following are operated by ClearCloud on its own infrastructure and are not sub-processors: authentication (Keycloak), audience measurement (self-hosted Matomo), monitoring, logs and the secrets vault. No third-party support, CRM or error-tracking tool receives your data.
The probes that run your checks are hosted by Scaleway (Paris region), UpCloud (Frankfurt, Madrid, Amsterdam and Warsaw regions) and OVHcloud (London region, and the regions that do not yet have a probe on site, which run from London); their exact location is given in the table above (European Union, and the United Kingdom, a country covered by an adequacy decision). A probe only receives what the check needs: your target's address and, if the monitor uses them, its credentials (basic auth, token, headers). Your account data and the results stay in the European Union.
Article 5 — Your GDPR rights
- Access and portability: Settings → "Export my data" (JSON/CSV archive, link valid for 48 h). Monitoring credentials and alert tokens are never included.
- Rectification: from your account settings.
- Erasure: Settings → "Delete my account". The organisation, its monitors, results, status pages, alert channels, history and the authentication account are deleted immediately; backups containing them expire within 30 days. Invoices are kept for 10 years (legal obligation).
- Objection and restriction: contact@clearcloud.fr
Response within 30 days at the latest. You have the right to lodge a complaint with the CNIL (cnil.fr), the French data protection authority.
Article 6 — Security
- Encryption in transit (TLS) on all exchanges, including between the probes and the platform.
- Monitoring credentials, authentication headers, LLM API keys and alert channel configurations are encrypted at application level (AES-256-GCM, with the key held in a vault separate from the database); they are never returned in clear text to the dashboard nor included in exports.
- Logical isolation per organisation, verified on every request; owner / admin / member / read-only roles.
- Two-factor authentication (TOTP) available on every account, enforceable across a whole organisation (Enterprise plan) and mandatory for platform administrators.
- Audit log of sensitive actions, exportable, kept for at least 12 months.
- Daily backups and continuous transaction logging, kept for 30 days in France.
- Automated scanning of dependencies and images; an external security audit is planned before opening to large accounts. No certification has been obtained to date.
- Reporting a vulnerability: contact@clearcloud.fr (see /.well-known/security.txt). We acknowledge receipt within 3 working days and will take no legal action against research carried out in good faith.
Article 7 — Cookies
Cookies used (strictly necessary — no consent required):
| Cookie | Lifetime | Purpose |
|---|---|---|
| okstatus_session | 30 days | Authentication |
| okstatus_id_token | 30 days | Identity token (sign-out) |
| oauth_state, oauth_code_verifier, oauth_idp_hint | 10 minutes | Securing the sign-in flow |
| PARAGLIDE_LOCALE | 1 year | Interface language |
| sp_unlock_<organisation>_<page> | 12 hours | Access to a password-protected status page |
Statistics via Matomo, self-hosted by ClearCloud (matomo.clearcloud.fr, France): no cookie, anonymised IP, raw data purged after 180 days. Two consent exemptions under CNIL decision no. 2020-091 apply here at once — strictly necessary cookies, and audience measurement limited to our own site. An exemption from consent removes neither the duty to inform nor the right to object: you can refuse audience measurement in one click from the cookie policy, which also details the local storage used for your display preferences.
Article 8 — AI assistants (MCP connector)
OKStatus does not send your data to any artificial intelligence provider on its own initiative, and does not use it to train a model.
If you wish, you can link your account to the AI assistant of your choice through the MCP connector (mcp.okstatus.eu). The assistant only gains access after you sign in and give your explicit agreement on a consent screen that names its publisher. It can then read, for the organisations you are a member of: the name, target and state of your monitors, check results (including error messages), uptime, incidents and their updates, maintenance windows and the list of status pages. It never receives monitoring credentials, authentication headers, API keys or the configuration of alert channels.
By default, this access is read-only. For organisations on the Max and Enterprise plans, the assistant can also create or change monitors, open and update incidents, and schedule or cancel a maintenance window — only after a second, separate agreement, requested the first time it attempts a change, and never for a read-only member. It cannot delete anything. These changes are recorded in the audit log under your name, with a mention of the assistant used; opening or updating an incident in this way notifies your alert channels and the subscribers of your status page, as it does from the dashboard.
The data consulted in this way is transmitted to the publisher of the assistant, which processes it under its own terms and its own privacy policy. That publisher is not a sub-processor of OKStatus: we control neither how long it keeps this data nor where it processes it.
We recommend Mistral AI (Mistral Vibe, formerly Le Chat), a publisher established in France that states it hosts its service in the European Union. If you choose another assistant — for example Claude (Anthropic, United States) — your data may be processed outside the European Union: the consent screen warns you of this before any access. It is up to you to check that this choice is compatible with your own commitments, in particular if this data concerns your customers.
You can withdraw this access at any time, by removing the connector in the assistant or by asking us to revoke it (contact@clearcloud.fr). Withdrawal prevents any further access; it does not erase what the publisher of the assistant has already received. Each call made through the connector (tool used, account, organisation, application) is recorded in our technical logs, kept for 30 days.
Article 9 — International transfers
Monitoring data and technical data are hosted and processed in France and in the European Union. Three limited exceptions: billing through Stripe Payments Europe Ltd (Ireland, US group, standard contractual clauses), social sign-in through Google, GitHub or GitLab if you choose it, and the consultation of your data by an AI assistant that you have linked to your account yourself (Article 8).
Article 10 — Contact
contact@clearcloud.fr — Response within 30 days.
CNIL: 3 Place de Fontenoy, 75007 Paris, France — www.cnil.fr