Cookie Policy
The short version. CreonAI keeps what it needs to sign you in and to remember your settings. It asks before keeping anything that only exists to measure, it uses Meta's advertising cookies only if you choose "Allow all" on our website, and it uses no Google Analytics.
This page lists every cookie CreonAI sets and everything it keeps in your browser's storage (localStorage and sessionStorage), what each one is for and how long it lasts. We treat browser storage exactly as we treat cookies.
1. Needed for the service
These make the service work, so they do not need your permission.
| Name | Kept in | What it does | How long |
|---|---|---|---|
authToken, access_token |
Browser storage | Your sign-in token, kept when you sign in so you stay signed in. | Until you sign out |
creonai_token |
Cookie (httpOnly, so scripts on the page cannot read it) | Keeps you signed in on some sign-in paths. | 30 minutes |
creon_terms |
Cookie | Set when you create an account with Google, GitHub or Apple after ticking the Terms box, so the sign-in can record that you accepted the Terms. | 10 minutes |
creon:consent, and the older creon_cookie_consent |
Browser storage | Your answer to our cookie question, so we do not ask again. | Until you clear site data |
creon:ads_consent |
Browser storage | Your answer about Meta's advertising cookies, so we do not ask again. | Until you clear site data or change your answer |
2. Preferences you set
Kept only in your browser, because you chose them:
- your theme
- the AI model you chose
- your voice settings
- your file manager favourites and recent files
- notices you have dismissed
They last until you change them or clear site data.
3. Measurement, only with your permission
We ask before keeping any of these. If you say no, they are never created, and any that already exist are deleted.
| Name | Kept in | What it does | How long |
|---|---|---|---|
creon:visitor |
Browser storage | A random visitor id, so we can count visitors. | Until you clear site data or say no |
creon:attr |
Browser storage | How you first found us: the source, the page that sent you (the referrer), the page you landed on, and any campaign tags in the link. | Until you clear site data or say no |
creon_anon_id |
Browser storage | An anonymous id the app uses to count how it is used. | Until you clear site data or say no |
creon:session |
Session storage | An id for a single visit. | Until you close the tab |
creon:consent:replay |
Browser storage | Your answer to the question about recording how you use the app. | Until you clear site data or change your answer |
creon:replay:day |
Browser storage | A count of how many recordings have started today, so we stop at three. | Reset each day |
One of these is about session recording. If you allow it, we record the screens you open, where you click and how you scroll, never what you type. The Privacy Policy explains what a recording holds.
4. Advertising, only if you choose "Allow all"
Only on our website, and only after "Allow all", the Meta Pixel loads and Meta sets these on creonai.io. "No thanks", "Count visits only", or Settings, then Account, then Ads measurement deletes them and stops the pixel. The iPhone and iPad app never sets them.
| Name | Kept in | What it does | How long |
|---|---|---|---|
_fbp |
Cookie (Meta) | Lets Meta recognise this browser, so it can tell us which visits and sign ups came from our adverts on Facebook and Instagram. | 90 days |
_fbc |
Cookie (Meta) | Set when you arrive from one of our Meta adverts, to connect the visit to that advert. | 90 days |
Meta uses this data under its own privacy policy. The Privacy Policy explains what Meta receives.
5. Other companies
- No other advertising cookies, and no Google Analytics.
- Session recordings are not sent to any other company. They are stored in our own storage with Amazon Web Services in London and deleted after 30 days.
- When you pay by card, Stripe sets its own cookies on its own checkout pages. See Stripe's privacy policy.
- Signing in with Google, GitHub or Apple happens on their sites, under their own policies.
- Connecting GitHub or Gmail from Settings, Connections also happens on GitHub's and Google's own pages, which set their own cookies there. Connecting Supabase is done by pasting two values here and sets no cookie.
- An app you build with sign-in on your own Supabase project keeps its visitors' sign-in in their browser storage on that app's address. That storage belongs to your app and your Supabase project, not to creonai.io.
5. Changing your answer
Clear this site's data in your browser settings (cookies and site data for creonai.io). The next time you open a page that asks, the question appears again. Clearing site data also signs you out.
If you have an account, you can also change it in the app: Settings, Account, Privacy, Usage analytics.
6. Questions
Email marco@creonai.io. Our Privacy Policy explains what we do with personal data.