Cookie Policy Statement
Last updated: 7 September 2026
This Cookie Policy explains what cookies divin.ai actually uses on this website, why, and how you can control them. We've tried to write it in plain language rather than boilerplate, and we only describe what this site really does, not a generic list of things a website could theoretically do.
Who we are
divin.ai is operated as a French sole proprietorship (entreprise individuelle), registered under SIREN 752 754 192, with its registered address at 2 chemin du midi, 63960 Veyre-Monton, France. For any question about this policy or your data, contact us at [email protected].
What is a cookie?
A cookie is a small text file that a website asks your browser to store, so the website can recognize your browser on a later request, for example to keep you signed in, or to remember a setting. Cookies can be "session" cookies, which are deleted when you close your browser, or "persistent" cookies, which stay until they expire or you delete them yourself.
The cookies we currently use
Every cookie divin.ai sets today is strictly necessary for the site to function: signing in, staying signed in, and protecting your session from forgery. We do not currently use any analytics, advertising, or social-media tracking cookie of our own.
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
| divinai-session | Keeps you logged in and remembers short-lived information (like a confirmation message) between page loads. | Strictly necessary · first-party | 2 hours, or until you sign out |
| XSRF-TOKEN | Protects you from cross-site request forgery — confirms a form submission actually came from this site's own pages. | Strictly necessary · first-party | 2 hours |
| remember_web_... | Keeps you signed in across browser restarts after you sign in via a magic link, so you don't have to request a new one every visit. | Strictly necessary · first-party | Up to ~400 days, or until you sign out |
The session and "remember me" cookies are set with the Secure and HttpOnly flags (not readable by page scripts, only sent over HTTPS). The XSRF-TOKEN cookie is deliberately readable by this site's own scripts, which is what lets it do its job.
Cookies we don't use, today
We don't currently run Google Analytics, a Facebook/Meta Pixel, or any other analytics or advertising cookie on this site. If we introduce one in the future, we'll ask for your consent first, using the cookie banner shown on your first visit, before any such cookie is set, not after.
Payment: Stripe
When you choose a plan, you're taken to a payment page hosted at
checkout.stripe.com,
operated by Stripe. Stripe sets its own cookies on its own domain to process your
payment securely; divin.ai does not set or read those cookies. See
Stripe's own Cookies Policy
for details.
Why we don't ask for consent for these cookies
Under the ePrivacy Directive as applied in France (CNIL guidance) and the GDPR, cookies that are strictly necessary to provide a service you've actually asked for, such as staying signed in after you log in, are exempt from the requirement to obtain prior consent. You still have the right to know about them, which is exactly what this page is for.
Your choices
You can change your cookie preference at any time. Since every cookie we use today is strictly necessary, this choice doesn't currently change what's set, but it's the mechanism that will matter the moment that's no longer true.
You can also block or delete cookies directly in your browser's settings, though doing so for the strictly necessary cookies above will likely sign you out or break sign-in. allaboutcookies.org has instructions for every major browser.
Your rights
Under the GDPR, you have the right to access, correct, or request deletion of your personal data, to object to or restrict certain processing, and to data portability. To exercise any of these rights, contact us at [email protected]. You also have the right to lodge a complaint with France's data protection authority, the CNIL.
Changes to this policy
We'll update this page whenever what we actually do changes, most likely the day we introduce our first optional cookie, and update the "Last updated" date above when we do.