Last updated: October 8, 2026
Private.ai does not set cookies — not on the marketing site, not during signup, and not in the app. We load no third-party advertising or analytics scripts.
You do not have to take our word for any of this. Open your browser's developer tools, look at the Cookies panel for this domain, and check the Network tab for requests to hosts that are not ours. That check takes about a minute, and it is the reason this page is written in specifics rather than reassurances.
1. What we removed, and when
Until September 2026 our marketing and signup pages loaded advertising and analytics tags from Google (Analytics, Google Ads and DoubleClick), Meta, X and Dstillery. Those tags set cookies, tracked visitors across other websites, and sent data about visits to those companies. They never ran inside the authenticated app, but they did run on public pages, including the login page.
We removed all of them. We did not replace them with a consent banner, and we did not replace them with server-side equivalents that would send the same data from our own servers instead of your browser. They are simply gone.
2. What is stored in your browser
We use your browser's local or session storage for the items listed below. Some support the operation of the Services; others support marketing measurement. Your sign-in token is sent to authenticate requests, and campaign attribution is sent with your signup to measure campaign effectiveness. The entries below explain what is stored and how it is used:
- Your sign-in session. A token and its expiry, so you are not asked to log in on every page. Cleared when you sign out.
- Your settings. Preferences such as theme, app-lock timeout and which features you have switched on.
- Your conversations. Chat history is held on your device, not on our servers.
- Free usage. If you chat without an account, one number: how many of the free replies this browser has used, so that reloading the page does not reset them. It is never sent to us and says nothing about what you wrote.
- The welcome screen. One word noting whether this browser has already gone past the welcome screen that opens the free chat, so that it is not shown again. It is never sent to us and says nothing about you.
- Signup in progress. While you sign up, the choices you make along the way (plan, payment method, a promo code you arrived with, and the state of your payment) are kept for that tab so the flow survives the trip to the payment page. If you subscribe from a free chat, it also notes which button opened checkout and how many free replies and chats you had (counts only), and checkout opens in a new tab, and that tab keeps a random reference to the free chat’s tab so your chats can move into your new account; it holds none of their content. Gone when the signup completes or the tab closes.
- Campaign attribution. If you arrived from an advertisement, a hand-out promo link or one of our landing pages, we keep the campaign tags in that link (the “utm” parameters and, if present, the ad network’s click id), the promo code, and which landing page you saw first and most recently, for 30 days from the arrival that created the record; a later arrival from an advertisement starts a fresh 30 days. It is sent to us with your signup so that we can tell which campaign led to it, and if you pay by card or cryptocurrency it travels with the order as a note to the payment processor and back to us with the receipt. This is a label about an advert, not a profile of you, and it is never shared with advertisers.
- Two random per-tab identifiers for our own measurement, described below, plus a note of which landing page you saw and of the page that linked you here. All four are discarded when you close the tab, and the moment you sign in. If you sign up or sign in from the tab, the first identifier is sent to us with that request, so that what the tab recorded is linked to your account.
- A five-minute cache of which of our landing pages are currently live, so those pages render without waiting for us. It says nothing about you and is gone when the tab closes.
- When we last mentioned our apps. Dismissing a “get the app” banner, or following one through to a store, records a date 30 days ahead, and until then no part of the site raises the apps again. A second entry notes that the one-time card above the chat composer has appeared on this device, so that it cannot appear twice; that one is written when the card is shown rather than when you act on it. Neither records anything about you.
Clearing site data in your browser signs you out, resets your preferences, and removes your locally stored conversations and the other browser storage listed above. It does not delete your account or information already sent to us.
3. How we measure the site
We count page visits using self-hosted analytics running on our own infrastructure. It sets no cookies, and instead uses two random identifiers that exist only for the current browser tab and are discarded when you close it or sign in. It records which pages were visited, which of our own buttons and store badges were pressed, and the steps of a signup, tagged with the campaign attribution above — not who did any of it, unless you go on to sign up or sign in from that tab, which links what the tab recorded to your account — and the data is never shared with anyone. Page addresses are recorded without their query strings, apart from the campaign tags above, and the page that shows a new account number is never recorded as a visit. It also records the address of the page that linked you here, which your browser sends to every site it visits; we keep it so that we can tell a link from a search result from someone typing our name, and we never record the address of a page on this site as a source. When you create an account, our server notes the country your network address belongs to, using a database it holds locally (IP Geolocation by DB-IP); the network address itself is not retained in the signup event.
This page counting stops when you sign in. The signup steps that finish at that moment (that the account was created or paid for) are still sent as you sign in, under the same per-tab identifiers, for up to 10 seconds, and then nothing more.
The page that opens a chat invite is not counted as a visit. It sends one event and nothing else: that an invite page was shown, which of its two buttons was pressed (getting the app or opening it), if either, and whether you are on an iPhone, an Android phone, a Mac or something else. That event carries no identifier of any kind — not the per-tab identifiers, not a sign-in token — and not the invite link or the name that may follow it, and nothing is stored in your browser for it, so it cannot be linked to you, to the invite or to anything else you do. On an iPhone, an Android phone or a Mac, “Get Private.ai” also copies the invite link to your clipboard so that the app can continue your invite after it is installed; it stays there until you copy something else.
Separately, the app reports what happens in it as short events, each a name from a fixed list with values from fixed lists or small counts: in a free chat, that a reply arrived and roughly how long it took, that the free replies ran out, that a locked feature was chosen; at checkout and signup, which step you reached, which plan you picked, that payment started or was cancelled, and, if you signed up from a free chat, which button opened checkout and how many free replies and chats you had; once you are signed in, that you opened the app and roughly how long it took to appear, that you used a feature (for example started a new chat, sent an attachment, exported a chat, created a folder, searched your chats — never what you searched for — or had an answer read aloud), which action you used on an answer (copy, share, react, bookmark, regenerate, report, read aloud), how you answered our notification prompt, when a visit to the app ended with roughly how long it lasted (under a minute, 1 to 5 minutes, 5 to 15, 15 to 60, or longer — never the exact time or when it started) and whether you did anything in it, and whether app lock, memory and custom instructions are switched on (not what the instructions say) with a rough count of your folders (none, one to five, or six or more); and, for a request to us that failed, which part of the service it was for, its status code and the kind of failure. Never anything you wrote or read, no page address, no file name, no email address and no account number. These events go to our own servers, the same ones the app already talks to, and not from your browser to any analytics service. Before you sign in they carry the first per-tab identifier above. While you are signed in they carry your sign-in token instead and are linked to your account, and nothing at all is stored in your browser for them: they are held in the open page’s memory until they are sent, and lost if the tab closes first. None of these events is sent from the pages that open a chat invite or reset a password.
A few things are only ever counted, never linked to anyone: that a page hit an error it could not handle, or failed to load part of the site; that something stored on this device, such as a saved chat, could not be decrypted or opened; how a chat export went (opened, finished, or which step failed); and how quickly each page loaded, responded to a tap or click, and stayed still while loading, measured by your browser itself and sent only as a verdict (good, needs improvement or poor) for each measure — never the timing, the page or anything on it. Each is sent as a name and a kind from a fixed list with a number, and we keep only a total per day. They carry no identifier of any kind — not the per-tab identifier, not your sign-in token — and no error message, page address or detail of what failed, so they cannot be linked to you or to each other. Nothing is stored in your browser for them; they are held in the open page’s memory for up to a minute and lost if the tab closes first.
We also collect account-linked service usage metadata and account events, as described in Section 3 of our Privacy Policy. These records do not contain your prompts or responses.
4. Third parties
Two services are involved in running the site, and none is used for advertising or analytics. Everything else, typefaces included, is served from our own servers:
- Cloudflare Turnstile appears on one signup page to block automated abuse. It is a security control, not a tracker.
- Stripe and Coinbase handle payment when you subscribe, and only at that point. They receive what is needed to take the payment.
We do not send data to advertising platforms. There are no advertising cookies to refuse, no vendor list to review, and no tracking preferences to manage.
5. Your rights
Because nothing here is used for advertising or profiling, there is no advertising consent to withdraw. Rights you hold under laws such as the UK GDPR and the EU GDPR — including access, correction, deletion and objection — apply to the personal information we hold about you and are described in our Privacy Policy.
6. Contact
Questions about this policy, or a discrepancy you found while checking:
- Email: legal@private.ai