What's actually private, and what isn't.
Most apps say "we respect your privacy" and stop there. Here is the whole picture: what leaves your device, who receives it, what we keep, and where the honest limits are. No marketing words you can't check.
What leaves your device, per action.
Your history stays on your device, but an AI still has to send some things somewhere to answer you. Here is exactly what, and to whom, for each thing NOLO can do.
If you never turn on sync, never schedule a task and never use a tool, what leaves your device is the message you send to get an answer, plus the requests listed under "Just opening the app" (typefaces, libraries and the cookieless visit count).
What NOLO's own servers store.
We do keep a little, and we'd rather tell you exactly what than pretend it's zero. It's pseudonymous: tied to your anonymous ID, never to a name, email or raw IP, and never the content of your chats.
Daily usage counters
We store a daily counter per anonymous ID: credits consumed, images generated, and your plan. This is how daily limits and billing work. We never store the text of your messages or the answers. An automated job deletes the old rows every night.
Scheduled tasks and price alerts, only if you create one
The text of your own we hold, apart from feedback you choose to send: what you asked NOLO to do later, its title and settings, a copy of up to 30 saved memories only if you switched on "Include my memory", and the name and notification of a price alert. All of it is encrypted (AES-256-GCM) with a key that only our server holds. Our server can decrypt it, because it has to read a task to run it and an alert to send it, so this is encryption at rest, not end-to-end. An alert's symbol, direction and price are in the clear, because the database compares them with the market itself. The answer to a task is not stored here: it waits in the server's mailbox until your device collects it.
Your IP only ever reaches our database as a salted one-way hash, and that bucket is deleted within a week. The honest footnote: your IP address does reach our server with every request, and the network of the company we rent it from carries it, because that is how the internet works. Our server uses it to answer and keeps no general access log; only requests for paths no visitor uses, such as /.env, are logged for 48 hours so that probing can be blocked. We would rather write it here than let "we never store your IP" quietly do more work than it should.
Where the limits actually are.
Anyone can claim "fully private". These are the places where NOLO is not, stated plainly so you can decide for yourself.
Your history is on your device, encrypted only with the app lock
Without the app lock, chats are stored in your browser's local storage in plain form. That keeps them off our servers, but it also means anyone with access to your unlocked device could open them. Turn on the app lock (Settings > Privacy) and every chat is stored encrypted, with a key only your password or fingerprint opens. It does not yet cover your memory, settings, drafts or files, and it is as strong as your password.
Drive sync is end-to-end encrypted only if you turn it on
By default your chats are scrambled on your device before they reach your Google Drive, but the key is derived from your Google account identifier, not from a secret only you have, so it's obfuscation, not end-to-end encryption: Google, which holds both the file and that identifier, could read it. One tap with your fingerprint (Settings > Account) makes it end-to-end encrypted: a random key that only your passkey or your recovery code opens. Then neither Google nor NOLO can read it, and if you lose every device, the passkey and the code, nobody can.
Scheduled tasks are encrypted at rest, not end-to-end
A task has to run while NOLO is closed, so our server holds the key to read it. A stolen copy of our database would not show your tasks; NOLO itself can read them. And while a run waits to be collected, our server holds the task and its answer in the clear, for up to 7 days, even if "Keep answering when you leave" is off.
Image generation uses a third-party, proprietary model
The chat models are open-weights and we name them. Image generation is the exception: it runs on OpenAI's proprietary model, through OpenRouter. The prompt still goes through our server without your identity, but it's fair to know that one capability isn't open-weights and isn't zero-retention.
We do run analytics. Cookieless, but real
NOLO runs no third-party analytics. Until it moved to its own server in November 2026 it used Vercel Web Analytics and Speed Insights: page visited, referrer, rough country, device type, load timings, with no cookies and no visitor ID. They ended with the move. NOLO now counts visits and speed with its own script on its own server: the same kind of data, no cookies, nothing stored on your device and no identifier. The IP address and User-Agent are used only in memory to get the country and device type, then discarded; only totals are kept, and only the owner sees them. After each answer the app also reports how long it took, to find where the waiting goes: times, the model and provider that answered and the size of the request, under a random ID for that message, with no account, no address and no text, kept for 14 days. Anonymous chats never send it, and "Don't send usage statistics" (Settings → Privacy) turns all of this off in the app on that device. Details are in section 9 of the privacy policy. An earlier version of this page said "no analytics" while they were running. That was wrong, and we keep the correction here rather than quietly deleting it.
A handful of third parties do see your IP
Your messages never reach a provider with your IP attached, because our server stands in the middle for that. But your browser loads typefaces from Google Fonts, feature libraries from a public CDN, and four live widgets refresh themselves directly. Each of those sees an IP address. The privacy policy lists every one and exactly when it happens.
Check it yourself in two minutes.
You don't have to take our word for any of this. The browser already gives you the tools to watch what NOLO does.
Open the network panel
In NOLO, press F12 and open the Network tab, then send a message. Your message goes to NOLO's own API and nowhere else. No ad networks, no third-party profilers, no advertising SDKs. What you will see: Google Fonts, a library CDN, and NOLO's own cookieless analytics, all listed above and in the privacy policy.
Clear the storage
In the same panel, open Application → Storage and clear it. Your chats vanish, because that's the only place they live. There's no server copy to delete.
Check what was sent
Click any request to /api/chat and read the payload. There's no email, no name, no login token: just your anonymous ID, your settings and the conversation you chose to send.
Name the model
Ask NOLO which model is answering. It will tell you, the chat models are open-weights, so you can look up exactly what's running and judge it for yourself. See the comparison.
Straight answers.
No, and we won't claim it. We keep pseudonymous daily counters (your anonymous ID, credits used, your plan) for 30 days so limits and billing work, and our server keeps a short security log (48 hours) of requests for probing paths such as /.env, with the IP, so that whoever keeps probing can be blocked. We never log the content of your messages and never write your IP to our database in readable form. "No content logs, no identity" is accurate; "zero logs" would be a lie.
We don't. Sync stores a copy in your own Google Drive app folder, and NOLO never downloads it or keeps a copy. By default it is obfuscated: the key is derived from your Google identifier rather than a private secret, so it's not end-to-end encryption, Google could read it, and while you are signed in our server sees that identifier and a Drive access token, so this rests on what our code does, not on mathematics. Turn on end-to-end encryption on the Drive card in Settings > Account and it rests on mathematics: the key is opened only by your passkey or your recovery code, which never reach us or Google.
No, and for chat they don't keep them either. Chat and photo requests through OpenRouter (the Pro model, served by Wafer or, if Wafer is down, Morph, and photo reading on Fast and Plus) can only reach endpoints that store nothing. Groq would be entitled to hold data for 30 days for abuse monitoring, so we switched Zero Data Retention on at account level and it stores nothing at all. The one exception, and we'd rather name it than average it away, is image generation: OpenAI keeps the prompts sent to it, without training on them. None of them can tie any of it to a person anyway, because there is no account and no IP of yours for them to tie it to. Provider by provider, it's all in the privacy policy.
To enforce daily limits, process payments and stop abuse, the bare minimum to run a service without an account. It's pseudonymous and short-lived, and you can see precisely what it is above.
Not the privacy model. The Android app is the same web app running inside a secure Android container, so there is still no account and your chats still live on your device. Two things are different: Google Play handles the download and gives us aggregate install and crash statistics under its own policy, and if you subscribe inside the app, Google Play Billing takes the payment. In that case we receive only a purchase token and a product ID, not your name, email or payment method, and you cancel or request a refund through Google Play rather than through us.
Not across the web, and not as a person. There are no advertising SDKs, no attribution SDKs, no third-party trackers and no cookies for tracking. What exists is NOLO's own cookieless visit statistics, counted on our own server and described in the limits above, and pseudonymous usage counters so daily limits work. Nothing profiles you, nothing follows you elsewhere, and nothing is sold.
Every single company, by name, with what each one receives and keeps, is listed in section 7 of the privacy policy. If that list ever changes, that page changes. It is meant to be complete at all times, not aspirational.
Private by design. Honest about the rest.
Open it, watch the network, read the payload. Then decide.