Legal
Privacy Policy
What NitzAI stores, who it sends your messages to, and how to get any of it removed.
Last updated
What this covers
NitzAI is a private AI chat app. This policy covers what the app itself stores about you, what it sends to the services it depends on, and how to get any of it removed. It applies to this deployment only — not to the model providers, search provider or sign-in provider behind it, each of which has its own policy.
The short version: your account and your conversations are stored so the app can show them back to you, your messages go to a model provider to generate replies, and nothing is sold, shared for advertising, or used to train a model.
What we store
Held in the app's own database, all of it keyed to your account:
- Account — your name, email address, whether that address is verified, your avatar URL if you signed in with Google, and which daily allowance your account is on. Email and password accounts store a hash of your password, never the password itself.
- Sign-in sessions — a session token plus the IP address and browser user agent that created it, so you stay signed in and so an unexpected session is identifiable.
- Conversations — the thread title, every message in full as you and the model wrote it, any images you attached or generated, which model answered, whether the reply came from Image mode, and the timestamps. Long threads also get a running summary of their earlier turns, written by the server so the conversation stays inside the model's context window.
- Usage counters — how many requests you made on each UTC day, and the token totals those requests reported. These enforce the daily allowance and let the operator see what the deployment costs. They count requests and tokens, not content.
There is no advertising identifier, no device fingerprint, and no cross-site tracking. An earlier version of the app let you save your own model endpoint; those rows (a label, a base URL, a default model, and the last four characters of the key) are no longer created or read, and any left over will be purged on request.
What stays on your device
Your preferences are device preferences, not account data, so they live in your browser's local storage and are never sent to the server as a profile: chosen model, reasoning effort, temperature, reply length, your custom system prompt, image model and size, the Save chat history switch, accent colour, text size, message density, send key, light or dark theme, and which conversation you had open last.
That means they don't follow you to another browser — and clearing site data for this domain removes them outright, without touching your account or your conversations.
Who else sees your messages
- The model provider — to generate a reply, the app sends the thread the reply belongs to: your messages, the model's earlier ones, any images attached, your system prompt, the running summary, and the sampling settings. Which provider receives it is set per deployment; this one is configured for an OpenAI-compatible gateway.
- The search provider — only on a message you explicitly sent with web search turned on, and only the search query derived from that message. The rest of the conversation is not sent.
- Google — only if you choose to sign in with Google, which tells us your name, email address, whether it is verified, and your avatar URL. We receive no other Google data and never post anything on your behalf.
- Our hosting and database providers — the app runs on Vercel and stores data in a managed Postgres database, so both necessarily process it on our behalf. Vercel Analytics records aggregate page views without cookies and without identifying you.
No one else. We do not hand conversations to any other third party, except where a valid legal demand leaves us no choice.
What we never do
- Sell or rent your data, or share it with advertisers or data brokers.
- Use your conversations to train a model. We don't train models.
- Build an advertising or interest profile from what you chat about.
- Read your conversations for any purpose other than the one below.
To be straight with you about the limits of that last one: your conversations are stored unencrypted at the row level, so whoever operates this deployment is technically able to read them in the database. That access is used only to investigate a fault you've reported, to respond to abuse or a security incident, or where the law requires it — never to browse.
How long we keep it
- Conversations — until you delete them. Deleting a conversation deletes its messages with it, immediately and for good; there is no recoverable trash.
- Nothing at all, if you turn off Save chat history in Settings. Replies still stream to your screen, but no conversation or message row is written. The model provider still receives the message in order to answer it.
- Sessions — a session lasts a week, extended while you keep using the app. Signing out ends it at once.
- Account — until you ask us to delete it. Everything else hangs off your account and is deleted along with it.
- Usage counters — kept as a per-day tally. They're the one thing retained after a conversation is deleted, because they record that a request happened, not what was in it.
Your controls
In the app today:
- Turn off Save chat history in Settings → Memory & data to stop anything being written.
- Delete any conversation from the sidebar, at any time.
- Sign out from the account menu at the bottom of the sidebar, which ends that session immediately.
Export, bulk deletion, account deletion and editing your profile don't have a button yet — they're listed in Settings as coming soon. Until they ship, email privacy@nitzai.com and we will export, correct or erase your data by hand. Say which you want; we'll confirm when it's done, within 30 days and normally much sooner.
Depending on where you live you may also have the right to correct your data, object to or restrict how it's processed, or complain to your data protection authority. The same address covers all of those.
How it's protected
- Everything is served over HTTPS, with HSTS set so browsers refuse to downgrade.
- Passwords are stored as Argon2 hashes. A password you set cannot be read back out, by us or by anyone with the database.
- Session cookies are signed, HTTP-only, and marked secure in production, so page scripts can't read them.
- Every query that touches a conversation is filtered by your own account id, so one account cannot reach another's messages even through a crafted request.
- The app sends a content security policy and refuses to be framed, which blocks the clickjacking route to your session.
- Camera, microphone, geolocation, payment and ad-topics access are switched off at the browser level for every page.
No system is perfectly secure, and we won't pretend otherwise. If you find a vulnerability, please report it to privacy@nitzai.com before disclosing it publicly.
Children
NitzAI isn't intended for children. Don't create an account if you are under 13, or under the minimum age for digital consent where you live if that is higher — 16 in much of the EEA and the UK. If we learn that an account belongs to a child below that age, we will delete it.
Where it's processed
The app and its database run on infrastructure in the United States, and the model and search providers may process a request in another country again. If you are in the EEA or the UK, that means your data leaves it. Transfers rely on the providers' own safeguards, including standard contractual clauses where those apply.
Changes to this policy
If what the app does with your data changes, this page changes with it and the date at the top moves. For a change that materially affects you we'll say so in the app rather than leave you to notice the date. Your use of NitzAI after a change means you accept the updated policy — and if you don't, the controls above let you take your data and go.