Privacy policy

QoBot is a local-first product: the security workspace you build with the desktop app stays on your computer. This policy covers what does reach us: your visit to qobot.io, your place on the waitlist, and the little the desktop app sends when you use it. It exists in French and English; the French version prevails in case of difference.

Who is responsible

Articule SAS (trade names Qontrol and QoBot), 231 rue Saint-Honoré, 75001 Paris, France, RCS Paris 843 409 954, is the controller of the processing described here. For anything about your data, write to privacy@qobot.io. We have not appointed a data protection officer; that address reaches the people who handle your request.

What we collect, why, and for how long

Purpose	Data	Legal basis	Kept for
Your waitlist signup and the emails about it (confirmation, news about access, your invitation)	Email address; your answers, all optional (type and size of organization, role, country, sector, what prompted you, who handles security today, how you’d use QoBot, the first question you’d ask); language; the page and variant you signed up from; campaign tags (UTM) and ad click IDs from the link you followed; referring site; confirmation date	Your consent, given when you join and confirm by email	Until you leave the list, or 3 years after our last contact with you
Referral (“move up the list”)	Your referral code, who referred you, how many people you referred confirmed their signup	Your consent (the waitlist terms)	Same as your signup
Audience measurement of the site	Pages viewed, the events listed in our code (button clicks, waitlist steps, language switch…), page address, referring site, campaign tags, language. A random ID that lives in memory for one page. No cookie, IP discarded	Our legitimate interest in knowing which pages work. This measurement is set up to need no consent under the CNIL’s rules (see Cookie policy); you can turn it off	25 months at most
Ad conversion measurement, only if you accept advertising cookies	What each ad platform’s tag collects (see Cookie policy); when we turn on server-side conversions, the fact that you confirmed your signup, with your email hashed (SHA-256) and the ad click ID	Your consent	Set by each platform; we keep nothing beyond your signup
Proof of your cookie choice	A random consent ID, your choices, the cookie policy version, the date. No IP	Our legal obligation to prove consent	13 months
Replying to you	Your email and what you write to us	Our legitimate interest in answering	3 years after our last exchange
Protecting our services from abuse	A hash of your IP address, to count requests per network	Our legitimate interest in keeping the service available	24 hours

We don’t sell personal data, we don’t build advertising profiles, and the free-text answer of the waitlist never leaves our database.

The desktop app

The app runs on your computer and keeps your security workspace (documents, answers, history) in a folder there. It reaches us only in these cases:

• Your AI provider. With your own API key (Anthropic, OpenAI or Mistral) or your Claude subscription, requests go from your computer to that provider, under your contract with them. We don’t see them.
• QoBot credits, if you use them instead. You sign in with your email (we send a one-time code), and your requests go through our server to Anthropic. We keep your email, your devices, and for each request the model, the tokens used and the cost, to manage your credits. We don’t store the content of your requests.
• Telemetry, in three levels you choose: Essential (app health and product events, tied to a random install ID, never to you; on by default, and you can turn it off in Settings → Privacy, then nothing is sent), Request insights (a label and category of each request, computed on your computer, with your organization’s size band, country and role; never the text; off unless you turn it on), and Design partner (a conversation you choose to share with us). Crash reports follow the Essential setting and go through our server.
• Feedback you send from the app becomes an issue in our GitHub project, quoting your words. If you’re signed in, it carries your account ID, never your email.

Who receives your data

Our team, and the providers that process data on our behalf, listed with their location and safeguards in Subprocessors. If you accept advertising cookies, the ad platforms named in the Cookie policy receive what their tags collect, under their own privacy policies.

Transfers outside the European Union

Most of our processing happens in the EU: our servers are in Paris (OVHcloud), and audience measurement is hosted in Frankfurt. Some providers are US companies or store data in the US: Resend (our email sender) stores emails in the US, and Anthropic receives QoBot credits requests. These transfers rely on the European Commission’s Standard Contractual Clauses and, where the provider is certified, the EU-US Data Privacy Framework. The Subprocessors page says which applies to whom. Ad platforms may also transfer data to the US under the Data Privacy Framework.

Your rights

You can ask to access, correct or delete your data, to restrict or object to its processing, to receive it in a portable format, and you can withdraw a consent at any time (unsubscribe link in every email, or “Cookies (manage)” on the site). Under French law you can also leave instructions about your data after your death.

Write to privacy@qobot.io from the address concerned. We answer within one month. If you think we haven’t respected your rights, you can complain to the CNIL, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, or at cnil.fr.

Security

How we protect our services and your data is described on our Security page.

Children

QoBot is for organizations and the people who work in them. It isn’t aimed at children, and we don’t knowingly collect data about anyone under 15.

Changes

When this policy changes, we publish the new version here with its date and version number. If a change affects how we use the data you already gave us, we tell you by email before it applies.