Provable, not just promised

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.

Data flow

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.

Action
What leaves your device
Who receives it
What they keep
Chat message
Your message, the parts of the conversation needed to answer and, if "Use memory" is on, your saved memories. No name, no email, no account.
Groq on Fast and Plus. On Pro, OpenRouter, which passes it to Wafer (or to Morph if Wafer is down). Always through NOLO's server, so your raw IP never reaches them.
Nothing. None of them trains on your messages, and all are on zero data retention: we switched it on at account level with Groq, and every request through OpenRouter can only reach endpoints that keep nothing. Full detail.
A long answer, when you close the app
The same message and context as above, plus the answer as it is written. Sent so a long reply can finish without your phone being awake.
NOLO's own server, the machine it rents from Contabo. It holds that one chat in the clear while the answer is being written, because the answer is produced on the server side and there is no key we could withhold from it.
Nothing once it reaches you. The copy is erased the moment your device confirms it has the answer, and self-destructs after 12 hours if nobody collects it. You can switch this off in Settings ("Keep answering when you leave") and it is always off in anonymous mode. Scheduled tasks are the exception: they always run here (next row).
A scheduled task or routine (only if you create one)
What you ask NOLO to do and when, its settings and, only if you switch on "Include my memory", a copy of up to 30 of your saved memories. When it runs, that text goes to the model as a new message: not your chat history.
NOLO's own server, which stores it encrypted. When it is due it always runs there, even with "Keep answering when you leave" switched off, because nobody is there to wait for it: the server holds the task and its answer in the clear until your device collects it. The model is the one of the mode you chose, as for a chat message, and if you allowed notifications your browser's push service gets an encrypted notice it cannot read.
The server erases the run the moment your device collects the answer, and after 7 days if nobody does. Our server keeps a routine until you delete it, and a one-off task until it has run and your device has the answer (30 days after it ran at the latest). "Delete all my data" removes them all. Not available in anonymous mode.
Web search
Only the search keywords NOLO builds from your request, not your whole chat.
Tavily, through NOLO's server.
A query log, with no link to who you are. Tavily may use queries to improve its own service and may pass one to another search index if its own can't answer.
Reading web pages
The address of each page NOLO needs to answer you (a search result, a site's own search with the details you gave, a link on a page it read), and, for the reading model, the text of that page with a few words on what NOLO is looking for in it. Not your messages.
The websites, from NOLO's own server, which identifies itself as NOLOBot and follows each site's robots.txt; on Pro, a page that needs a real browser is opened in the sealed browser described below. The reading model is Gemini 2.5 Flash Lite on Google's Vertex AI, through OpenRouter.
NOLO keeps nothing: the page goes into one answer and is forgotten. OpenRouter and Google, under the same zero-retention setting as chat. The websites, whatever they log about a visit.
Image generation
The text prompt for the image and, for an edit, the picture being edited.
OpenAI, running its proprietary image model, through OpenRouter and NOLO's server, so it does not see your IP. Your browser then loads the finished image from NOLO's own server.
OpenAI keeps the prompts it receives, without training on them. NOLO keeps the image for 30 days behind a link nobody can guess, then deletes it; your copy stays in your local gallery.
Python (when NOLO runs code to work something out)
The code NOLO wrote, and the files attached to that chat so the code can read them. Not the rest of your history.
NOLO's own server, in a sealed container with no internet access, made for that one run. Code you run yourself with the Run button runs on your device instead.
Nothing. The container and everything in it are destroyed when the run ends. Not used in anonymous mode, nor with "Keep answering when you leave" switched off.
Browsing the web (Pro, when NOLO uses a browser for a task)
The task, written by NOLO from your request (what to find or do, on which site, the details you gave), and the pages the browser opens, including a screenshot when it needs to look at one. The websites get ordinary visits, and whatever you asked NOLO to type into their search boxes; a form only if you tap Send.
NOLO's own server runs the browser in a sealed container that can only reach public websites, through a guard. The helper that drives it is the Pro model, through OpenRouter. Websites see NOLO's server, not your IP; it identifies itself as NOLOBot and follows each site's robots.txt.
NOLO keeps nothing about your browsing sessions, not even how many you ran. Each session runs in a fresh browser in its own container, and its cookies, site data and everything it saw are deleted when it ends: nothing carries over to the next session. The screenshots are saved only in your chat, on your device. OpenRouter, under the same zero-retention setting as chat. The websites, whatever they log about a visit and whatever a form you chose to send contains.
Voice dictation
The audio clip you record (up to 60 seconds on Free, 3 minutes on paid plans), only while the mic is on.
Groq (Whisper), through NOLO's server.
Nothing, under the same zero-retention setting as chat. NOLO never stores the audio either.
Live data
The symbol, place or query (a stock ticker, a city for weather, the title of a law). Only if you tap "Use my location": your position, to about 10 metres for places near you and rounded to about a kilometre for the weather.
Open-Meteo, Yahoo Finance, Finnhub, Binance, CoinGecko, ESPN, TheSportsDB, OpenStreetMap, Photon (Komoot) and Wikimedia; for scientific papers OpenAlex, Crossref, Europe PMC and arXiv; for laws the official databases of Spain (BOE), the EU (Publications Office) and Romania (Portal Legislativ). All through NOLO's server. Four widgets refresh in your browser instead (currency, sunrise, holidays, map tiles) and those four do see your IP.
A normal API request; no profile of you. Your location is never stored: the app forgets it after 30 minutes.
A price alert (only if you set one)
The symbol, whether it should rise above or fall below a price, that price, and the text of the notification.
NOLO's own server, which stores the name and the notification encrypted. Every five minutes the database asks Yahoo Finance for the price, with nothing but the symbol, and when it crosses your line your browser's push service gets an encrypted notice it cannot read.
The alert stays until you delete it, and at most 30 days after it goes off. "Delete all my data" removes them all.
Just opening the app
Nothing you typed. But the page pulls its typefaces from Google Fonts, and features like PDF reading or charts pull their library from a public CDN. NOLO's own visit counter sends the page, the site you came from, your language, screen width, whether NOLO is installed and load times to NOLO's server, with no cookie and no identifier; the server works out the country from the IP address and keeps only totals.
Google Fonts, and Cloudflare cdnjs / jsDelivr (and SheetJS's own CDN for Excel files), directly from your browser, so they see your IP.
Standard CDN request logs. No content, nothing you typed. We'd rather name it than let you find it in the network tab.
Drive sync (opt-in)
A copy of your chats, only if you turn sync on: obfuscated by default (not end-to-end encrypted), or end-to-end encrypted if you turn that on with your fingerprint.
Your own Google Drive (a private app folder). NOLO doesn't download it or keep a copy.
It lives in your Drive until you delete it. See the honest limit below.
Feedback (only if you send it)
What you write, the kind of report, the model that was answering, the app version and platform. Your last message and its answer only if you tick "Attach the last exchange", after seeing them.
NOLO's own server, with no identifier: not your ID, not your IP.
Until we delete it by hand: reading, answering or archiving it does not. Because nothing ties it to you, we cannot find "yours" to delete it later.

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).

On our side

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.

Daily usage & image counters30 days
Rolling-window counters7 days
Rate-limit buckets (hashed IP)7 days
Timings of each message (no ID, no text)14 days
Your ID, plan & subscription stateuntil you ask us to delete it
Scheduled tasks you create (encrypted)until done or deleted
Price alerts you set (encrypted)until deleted, 30 days after they go off at most
Your IP address, in the clear, in our databasenever
The content of your chatsnever, unless you attach it to feedback

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.

The honest part

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.

Don't trust, verify

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.

FAQ

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.