1. Who we are and how to contact us
NOLO is an independently operated AI assistant, built and maintained by one person. It is available as a web app at nolo-app.com, a website at landing.nolo-app.com, an Android app distributed through Google Play (package app.nolo.ai), and a directly downloadable Android APK.
For the purposes of the EU General Data Protection Regulation (GDPR) and the UK GDPR, the operator of NOLO is the data controller for the processing described here.
For privacy questions, data access or deletion requests, complaints or security reports, write to nolo.ai.app@gmail.com. That is the fastest route and it reaches a real person. If you contact us, we process your email address and the content of your message in order to answer you. We have not appointed a Data Protection Officer, because NOLO's scale and processing do not meet the conditions in GDPR Art. 37.
The controller's full name and postal address are set out in section 21, at the foot of this page.
2. What this policy covers
This policy covers the NOLO website, the web app, the Android app on Google Play, the standalone APK, subscriptions, AI chat, file and image processing, voice dictation, reading answers aloud, web search, live-data widgets, exports and the optional Google Drive sync.
It does not govern the independent processing carried out by the companies named in section 7 when they act as controllers in their own right (for example Google for your Google account, Stripe for payment fraud prevention, Google Play for your purchase). Their own policies apply to that processing, and we link to each of them.
3. How NOLO is built, in one paragraph
There is no sign-up. When you first open NOLO, your browser generates a random identifier: nolo_ followed by 40 random letters and digits. That string is your entire identity: it is not derived from your device, your email or your IP address, and it means nothing outside NOLO. Your conversations are written to your browser's own storage (localStorage and IndexedDB) and stay there. When you send a message, your browser posts it to NOLO's own API, and NOLO's server, not your browser, forwards the part needed to answer to an AI provider. That relay is deliberate: it means the AI provider sees a request from NOLO's server, with no user identifier and no IP address of yours. There are three exceptions to that rule, and they are listed in section 8 rather than buried.
4. Data categories NOLO processes
| Category | What it actually is | Why |
|---|---|---|
| Anonymous app identifier | A random string, nolo_ followed by 40 random letters and digits, generated in your browser. Not linked to a name, email, phone number or device identifier. | Daily usage limits, plan entitlement, abuse prevention, and linking a subscription to the device that bought it. |
| Conversation content | Your messages, the recent conversation context, files and images you attach, image prompts, URLs you paste, and voice clips you record. | Producing the answer or performing the task you asked for. Relayed to AI providers in real time; never written to a NOLO database. |
| Your location (optional) | Only if you tap "Use my location" when NOLO asks where you are: your device's position: to four decimal places (about 10 metres) when you ask for places near you, so that the nearest one really is the nearest, and rounded to two decimal places (about a kilometre) for the weather and the name of your area. The app keeps it in memory for 30 minutes, for that chat only, and sends it with your messages there. | Answering "near me" and "here" questions, such as the weather or what is nearby. Never written to a NOLO database. |
| Local app data | Chat history, projects, spaces, saved memories, generated-image gallery metadata, settings and preferences. | Kept in your browser storage so your workspace survives a reload. Never uploaded to NOLO. |
| Usage counters | Per anonymous ID: credits consumed and images generated each day, and credits consumed in each short time window. | Enforcing daily allowances and detecting cost abuse. Contains no message text. |
| Subscription state | Your plan (free / plus / pro), subscription status, Stripe customer ID (web) or Google Play purchase token and product ID (Android). | Giving you what you paid for and removing access when a subscription ends. |
| Hashed IP counters | A SHA-256 hash of your IP address, truncated to 14–16 hexadecimal characters, with a daily request count. Stored per feature: chat, chat titles, transcription, feedback, account creation, account restore, checkout and the billing portal, and sign-in attempts to the owner's panel. | Rate limiting and abuse prevention without keeping IP addresses. See the honest caveat in section 18. |
| Feedback you send | The text you type into the feedback box, an optional 1–5 star rating, what kind of report it is (a bug, an idea, billing or something else), where in the app you opened it from, your plan tier, your interface language, the model that was answering, the app version and platform (web or Android), and a random reference code that your device keeps so it can show you our reply. Only if you tick "Attach the last exchange", after seeing it: your last message and NOLO's answer, up to 4,000 characters. | Improving NOLO. Stored with no identifier attached: not your anonymous ID, not your IP, not an email. |
| Scheduled tasks and routines | Only if you create one: what you ask NOLO to do and when, its settings, and, if you turn on notifications, your browser's push subscription. | Running the task at the time you chose, even with NOLO closed, and telling you when it is ready. Stored encrypted on our server; see section 6. |
| Price alerts | Only if you set one: the market symbol, whether to tell you when it rises above or falls below a price, that price, the name of the asset and the text of the notification. | Watching the price and telling you when it crosses your line, even with NOLO closed. The name and the notification text are stored encrypted; see section 6. |
| Optional Google account identifier | Google's opaque account identifier (the OpenID sub, a numeric string) if, and only if, you switch on Drive sync. Not your email, name or profile picture. | Deriving, in your browser, the key that obfuscates your sync files (not used for that if you turn on end-to-end encryption; see section 10). If you keep the Google session, NOLO's server also reads it from Google's sign-in token and keeps it, encrypted, in a cookie on your device; it is never stored in NOLO's database. See section 10. |
| Technical data | Seen by NOLO's own server while it answers a request: IP address, requested path and user agent. No general access log keeps them. Only runtime error output is kept, without conversation content, and a short security log of probing requests (section 9). | Serving the request, security, debugging and abuse prevention. See Contabo in section 7. |
| Payment data | Card details, billing address and tax data, handled entirely by Stripe or Google Play. NOLO's servers never see or store a card number. | Taking payment, preventing fraud, and meeting tax and accounting obligations. |
| Support email | Your email address and whatever you write to us. | Answering you. |
5. What stays on your device
Your conversation archive lives in your browser's localStorage and IndexedDB: chat history, projects, spaces, memories, gallery entries and settings. NOLO has no server-side copy of any of it and no way to reconstruct it.
- Incognito chats are not written to storage at all. They exist only in memory and disappear when the chat is closed.
- App lock can put NOLO behind a password of your own (at least 4 characters), with fingerprint or face unlock as an option. With it on, every conversation is stored encrypted on your device (AES-256-GCM), with a key that only your password or your fingerprint opens (WebAuthn PRF), and the app asks for one before reading any of them. A longer password protects them better. The lock does not yet encrypt your memory, settings, projects, skills, drafts or files, and an answer that arrives in the background waits unencrypted until the app collects it. A lock set up with an earlier version of the app only covers the screen until you tap "Encrypt my chats" in Settings > Privacy.
- If you clear browser data, switch browser or device, reset the app, or uninstall it, local history is gone. We cannot recover it, because we never had it.
- Without the app lock, local storage is not encrypted by NOLO. Anyone with access to your unlocked device or browser profile, and software with access to your browser storage, can read it.
6. What NOLO's own servers store
This is the complete list. Everything below lives in one PostgreSQL database on NOLO's own server and is keyed on your anonymous ID or on a hashed IP, never on a name, email or IP address in the clear.
| Table | Every field it holds | Deleted after |
|---|---|---|
nolo_users | Anonymous ID, when it was created, plan, subscription status and when the subscription ends, Stripe customer and subscription IDs (web subscribers only), Google Play purchase token and product ID (Play subscribers only). | Kept while you use NOLO; deleted on request. See section 15. |
nolo_daily_usage | Anonymous ID, date, credits consumed. | 30 days, by an automated nightly job. |
nolo_daily_images | Anonymous ID, date, images generated. | 30 days, by the same job. |
nolo_window_usage | Anonymous ID, time window, credits consumed. | 7 days. |
nolo_ip_limits | Truncated salted hash of an IP address, date, request count. No IP address in the clear. | 7 days. |
nolo_processed_webhooks | Payment event IDs already handled, so a repeated webhook cannot double-charge or double-grant. | Retained for billing integrity. |
| Feedback | Your message, optional star rating, the kind of report, where it was opened from, plan tier, interface language, the model that was answering, app version and platform, the random reference code, the last exchange only if you attached it, a timestamp, our reply if we write one, and when we archived it. No identifier of any kind: not your anonymous ID, not an IP, not a hash. The reference code only lets your device fetch our reply; it never returns your message. | Kept until we delete it by hand. Answering or archiving a message does not delete it, and nothing deletes them automatically. |
nolo_agenda | Only if you schedule something: one row per task or routine you save, by hand or by confirming one that NOLO proposes. Your anonymous ID; the task's title and text, encrypted; its settings, encrypted (which mode runs it, reasoning and image options, and a copy of up to 30 of your saved memories, only if you switch on "Include my memory"); the texts of its notifications, encrypted. In the clear: when it runs, your time zone and interface language, the random ID of the chat it answers in, your plan, its state (active, paused, running or done) and why it is paused, when it last ran and when it runs next, how many times it has run, retries, how many results in a row nobody opened, whether to notify you, and when you created it. | When you delete it, or with "Delete all my data". A one-off task goes once it has run and your device has collected the answer, and at the latest 30 days after it ran, by the nightly job. A routine stays until you delete it: one whose results nobody opens pauses itself, but is not deleted. |
nolo_agenda_entregas | One row per run of a task: which task, your anonymous ID, when it was due and when it started, its status (running, ready or error) with a short error reason, and the ticket your device uses to collect the answer (job ID, mailbox address and read token, the token encrypted). The answer itself is not stored here: it waits in the mailbox on NOLO's server (section 7). | As soon as your device collects the answer. Uncollected ones after 8 days, by the nightly job, or with "Delete all my data". |
nolo_push | Only if you turn on notifications: your anonymous ID, a hash of your browser's push address (to avoid duplicates), the subscription itself (that push address and the public keys your browser created for it), encrypted, and when it was saved. At most five devices per ID. | When you turn notifications off on that device, when the browser's push service reports the subscription is gone, when a sixth device replaces the oldest, when the same browser is used with another NOLO ID, or with "Delete all my data". |
nolo_alertas | Only if you set a price alert: your anonymous ID; the market symbol (for example AAPL or BTC-USD), the direction (rises above or falls below) and the price, in the clear, because the database compares them with the market price itself; the name of the asset, the text of the notification, its currency and language, encrypted; and when you created it, when its price was last checked, and when and at what price it went off and you were told. | When you delete it, 30 days after it goes off, by the nightly job, or with "Delete all my data". |
nolo_alertas_peticiones | The price requests in flight: a request number and the symbol. No anonymous ID. | As soon as the answer is read, and at the latest after 10 minutes. |
nolo_insignias | Your anonymous ID and your account number, given in order of arrival, with a title and a colour if NOLO gave that number one. | Kept while you use NOLO; deleted on request. |
nolo_credit_reservas | Credits set aside while an answer is being written: your anonymous ID, the date, the amount. | Released when the answer ends, and they expire on their own within minutes if it never does. |
nolo_consumed_tokens | Only if you buy a credit pack on Google Play: the purchase token, your anonymous ID, the product and the date, so a purchase cannot be redeemed twice. | Retained for billing integrity. |
nolo_webhook_events | Payment event IDs already handled, like nolo_processed_webhooks. | Retained for billing integrity. |
nolo_metricas | Daily totals of how many times each event on a closed list happened (the app opened, a message sent with each model, the plans page opened), per plan and platform. No identifier of any kind, and nothing you typed. | Kept as totals. |
nolo_refs | Monthly totals of subscriptions per referral code and plan. No identifier of any kind. | Kept as totals. |
nolo_agenda_cfg | Internal settings of the clock that runs scheduled tasks. Nothing about you. | Kept while the feature exists. |
nolo_usage_events, nolo_visitors | Left over from NOLO's former analytics: your anonymous ID with the date, event, model, token counts and plan; and your anonymous ID with the date last seen. Nothing has written to them since those analytics were retired. | Deleted from NOLO's own server on 7 November 2026. What is left of them in its backups goes within 14 days, and in the old database 30 days after the move. |
Shared chats are not in that list, because they are not in the database. When you share a chat with a link, your device encrypts it (AES-GCM, with a random key) before it leaves, and the encrypted file waits in the mailbox on NOLO's server until the deadline or the number of openings you chose, at most 30 days. The key travels only in the link, after the "#", which browsers never send to a server, so NOLO holds bytes it cannot read. Whoever opens the link gets their own copy in their chats.
The encrypted fields use AES-256-GCM with a key that only NOLO's server holds, outside the database, so a copy of the database on its own does not reveal them. NOLO's server can decrypt them, because it has to read a task to run it and an alert to send it: this is encryption at rest, not end-to-end encryption.
What is not in that list, and never will be: the text of your conversations, the answers, your files, your images, your voice clips, your email address, your name, your IP address in readable form, or any advertising or cross-site identifier. The only text of yours it holds is what you put into a scheduled task, a routine (its text and, if you choose, a copy of your saved memories) or a price alert, because you asked NOLO to act on it later, and it is stored encrypted; and the feedback you choose to send, with the last exchange only if you attach it, which carries no identifier. NOLO's code has an internal rule against logging user content; console output records lengths, hashed IDs, counters and timings only.
7. Every company that receives your data
These are NOLO's processors and sub-processors. The list is exhaustive as of the date at the top of this page. "Sees your IP" means the provider receives your device's IP address rather than our server's.
AI models
| Provider | What it receives | What it keeps | Sees your IP |
|---|---|---|---|
| Groq, Inc. (United States) Privacy policy |
Your message plus the part of the conversation needed to answer, and any web-search results attached to it. Also your voice recordings when you use dictation, and short internal classification requests. Runs the open-weights models used by the Fast and Plus tiers and the Whisper speech-to-text model. | Nothing. NOLO's Groq account has Zero Data Retention enabled globally, which overrides every per-API setting, so inputs and outputs are not logged at all. Without that setting Groq would be entitled to keep them for up to 30 days for reliability and compliance, which is why we switched it on. | No |
| OpenRouter (United States) Privacy policy |
The same conversation content, when you use the Pro tier, and any image you upload on the Fast and Plus tiers for the assistant to look at. On the Pro plan, when NOLO uses its web browser for a task, also the task and the content of the pages the browser opens, with a screenshot of the page when the helper needs to look at it. On every plan, when NOLO reads web pages to answer you, the text of each page and a few words on what NOLO is looking for in it, for the reading model. On the Pro plan, and only if you choose the natural voice for reading answers aloud, the text of the answer as it is read, the name of the voice you picked and, if you wrote one, your instruction on how it should be read. OpenRouter does not run the models itself: it passes each request to one of the three companies below and returns the answer. | Every NOLO request carries OpenRouter's zero data retention and no data collection settings, so it can only be routed to endpoints that keep nothing and do not train on it. OpenRouter states that it does not store prompts or responses unless the account opts in to logging; it keeps request metadata such as token counts and timing. | No |
| Wafer, Inc. (United States) Privacy policy |
The Pro tier's conversation content, passed on by OpenRouter. Wafer runs the Pro model, DeepSeek V4.1 Flash. | Reached only through OpenRouter's zero-data-retention routing, which admits only endpoints that do not retain prompts or train on them. | No |
| Morph (AutoInfra, Inc., United States) Privacy policy |
The same as Wafer, but only when Wafer is unavailable: Morph is the fallback for the Pro model. | The same zero-data-retention routing as Wafer. | No |
| Google Cloud (Vertex AI) (United States) Privacy notice |
Images you upload on the Fast and Plus tiers, passed on by OpenRouter, so the shared vision model (Gemini 2.5 Flash Lite) can describe them for the assistant. The Pro model reads images itself and does not use this. On every plan, the same model also reads the web pages NOLO opens to answer you: it gets the text of each page and a few words on what NOLO is looking for, written by the assistant, not your messages, and returns only the part that answers. On the Pro plan, and only if you choose the natural voice for reading answers aloud (it is off unless you switch it on in Settings), the text of the answer as it is read, the name of the voice you picked and, if you wrote one, your instruction on how it should be read, passed on by OpenRouter, so Google's text-to-speech model (Gemini 3.8 Flash Lite TTS) can turn the text into audio. The audio goes back to your device; NOLO does not store the text, the instruction or the audio. The short samples you can play to compare voices are a fixed sentence written by NOLO, not your content. The default read-aloud voice is your device's own: NOLO's servers and these companies take no part in it, and how the device produces it is up to the device and its browser. | The same zero-data-retention routing: of the companies that serve this model, only Google's Vertex AI endpoints meet it, so they are the only ones used. | No |
| OpenAI (United States), through OpenRouter Privacy policy |
The text prompt when you generate an image, and the source image when you ask for an edit. OpenAI runs the proprietary image model (GPT Image 2.5); OpenRouter passes the request on from NOLO's server. | This endpoint is not zero-retention: OpenRouter lists it as keeping the prompts it receives and not training on them. The finished image comes back to NOLO, which keeps it for 30 days (see Contabo below). | No |
The honest version of "zero data retention". Zero retention is a setting somebody has to switch on, not a law of physics, so here is the state of each one rather than an average. Groq: NOLO has Zero Data Retention enabled at account level, so nothing is logged. OpenRouter: every chat and photo-reading request carries its zero-data-retention setting, so it can only reach endpoints that keep nothing (Wafer and Morph for Pro, Google's Vertex AI for photos). OpenAI, for images: this endpoint does not offer it, and OpenRouter lists it as keeping the prompts it receives, without training on them. So for chat, web search and voice dictation the content really is discarded once the answer is delivered. For image generation it is not, and we would rather point at that single exception than let the others carry it.
Search and live data
| Provider | What it receives | What it keeps | Sees your IP |
|---|---|---|---|
| Tavily (United States) Privacy policy |
Only the search keywords NOLO derives from your request, not your conversation. Used when you ask something that needs current information. | Tavily states it may use portions of query data to improve its own responses, and that when its index cannot answer, it may pass the query to third-party search index providers. | No |
| Open-Meteo (Germany); Yahoo Finance, Finnhub (United States) and Binance, for prices, charts and headlines; CoinGecko; ESPN and TheSportsDB, for sports; Photon / Komoot, Nominatim & Overpass (OpenStreetMap); Wikimedia Commons | Only the specific lookup: a city name for weather, a ticker symbol, a coin, a team, a place name, or an image filename; and, only if you tap "Use my location", your position: to about 10 metres to find places near you, and rounded to about a kilometre for the weather and the name of your area. Requested by NOLO's server, not your browser. For price alerts, NOLO's database asks Yahoo Finance every five minutes for the price of each symbol that has an active alert, with nothing but the symbol. | Ordinary API request logs on their side, attributable to NOLO's server and not to you. | No |
| OpenAlex, Crossref, Europe PMC and arXiv, for scientific papers | Only the search for a paper: the words, title, authors or DOI that NOLO looks for, or a reference you asked it to check. Requested by NOLO's server, never with anything about who asks. | Ordinary API request logs on their side, attributable to NOLO's server and not to you. | No |
| BOE (Spain's official gazette), the Publications Office of the European Union (which runs EUR-Lex) and Romania's Portal Legislativ, for laws and EU court rulings | Only the lookup: the name, number or words of the law, the article, the case number of an EU ruling, and the language you want it in. Requested by NOLO's server, never with anything about who asks. Romania's Portal Legislativ is queried over plain HTTP, because its interface does not accept HTTPS, so that lookup travels unencrypted between NOLO's server and the portal: the law being looked for, not who is asking. | Ordinary API request logs on their side, attributable to NOLO's server and not to you. | No |
| Google (favicon service) and DuckDuckGo (icon fallback) | The domain name of a site cited in a search answer, so a small icon can be shown next to it. Fetched by NOLO's server on purpose, because loading these directly would tell Google every site you read about. | Ordinary request logs, attributable to our server. | No |
| The websites you or NOLO open | When you paste a link, or when NOLO opens a web page to answer you (a search result, the results page of a site's own search, or a link on a page it read), NOLO's server downloads that page. The site gets a request from our server, with the address of the page and nothing about you. On the Pro plan, a page that only shows its content to a real web browser is opened with the browser described next, without clicking or typing anything. NOLO can also use that web browser on its server to do a task you ask for on a site: the site gets ordinary visits from our server, identified as NOLOBot, and whatever you asked NOLO to type into it. A form (a contact form, a booking request) reaches the site only if you tap Send on it in the chat. The browser never logs in and never types passwords or card details. The screenshots of what it sees are shown to you and saved only in your chat, on your device. | Whatever that site logs about a visit, attributable to our server. | No |
Infrastructure
| Provider | Role | What it sees | Sees your IP |
|---|---|---|---|
| Contabo GmbH (Germany; the machine is in France) Privacy policy |
Rents NOLO the server everything runs on: the website, every API call, the PostgreSQL database holding exactly the tables listed in section 6, the clock that checks your scheduled tasks and price alerts, the code that lets a long answer finish after you close the app ("Keep answering when you leave", in Settings), your scheduled tasks and routines, the images NOLO generates for you, the sandbox where NOLO runs the Python code it writes, and, on the Pro plan, the web browser NOLO uses for a task on a website. For ordinary chats that background code is only used while that setting is on, and never in anonymous mode. That sandbox is a throwaway gVisor container with no internet access: it receives the code and the files attached to that chat, and it is destroyed, with everything in it, when the run ends. Nothing from it is kept. The web browser is another throwaway gVisor container, one per task: it can reach public websites only through a guard on our server, and it is destroyed, with its cookies and everything it saw, when the task ends (or 3 minutes after, if a form is waiting for you to tap Send). Each task gets a new one, so nothing from one task carries over to the next. | Contabo provides the machine and its network, as our processor, and NOLO operates everything on it. Its network carries your IP address with every request; NOLO's server uses it to answer and keeps no general access log (the security log in section 9 is the only exception). Like any company that owns the hardware, Contabo could physically reach what is on the machine: what is in those tables (no conversation content, except the last exchange you attach to a feedback report yourself; the other text of yours is your scheduled tasks, routines and price alerts, encrypted, see section 6); the images you generate, for 30 days; the code and files of a Python run, only while it runs; and the content of that one chat, in the clear, for as long as the answer is being written: your message, the context sent with it, and the reply. The answer is produced on the server side, so there is no key we could keep from it. It is erased the moment your device confirms it has the answer, and self-destructs after 12 hours if nobody collects it (7 days for the answer of a scheduled task, because nobody is watching when it runs). Turn the setting off and nothing from your chats is sent there; only the scheduled tasks you create still run there. | Yes |
| Cloudflare, Inc. (United States) Privacy policy |
Answers the question "where is nolo-app.com?" (DNS). No traffic passes through it. | Only that lookup, usually from your internet provider rather than from you. It holds no data of yours, apart from what the next row says about the first 30 days after the move. | No |
| Vercel, Cloudflare and Supabase (United States), for 30 days after the move | Where NOLO ran until it moved to its own server in November 2026. They stay switched on but unused for 30 days, in case the move has to be undone, and are then shut down. | Nothing new. Supabase keeps the database as it stood on the day of the move; Cloudflare keeps the images generated and the chats shared before it, until they expire, and sees the IP address of whoever opens one of those older links. | Only for those older links |
| Your browser's push service (optional) Google for Chrome and Android, Mozilla for Firefox, Apple for Safari |
Delivering the notifications you switch on: a reply that finished while you were away, a scheduled routine that ran, or a price alert that went off. | An encrypted notification it cannot read, addressed to your browser. Switch notifications off and nothing is sent here. | Yes (it is your browser's own service) |
Payments, distribution and optional sync
| Provider | Role | What it receives | Sees your IP |
|---|---|---|---|
| Stripe Privacy policy |
Payments for subscriptions bought on the web. | Your card details, billing information and payment history, directly. They never pass through NOLO. Stripe acts as an independent controller for fraud prevention and its legal obligations. NOLO stores only the resulting customer ID. | Yes (on Stripe's own checkout page) |
| Google Play Billing Google privacy policy |
Payments for subscriptions bought inside the Android app. | The entire purchase is handled by Google under your own Google account. NOLO receives only a purchase token and a product ID, and asks Google's servers once a day whether that subscription is still active. NOLO never sees your Google account, name, email or payment method. | Yes (Google handles the purchase) |
| Google Play (distribution) | Distributing the Android app. | Google collects its own data about the download, install and any crash reports under its own policy, and gives us aggregate, non-identifying statistics in the Play Console. We cannot see who you are from those. | Yes |
| Google Drive & Google Sign-In (optional) | The opt-in cross-device sync. | Files placed in your own Drive: obfuscated by default (not end-to-end encrypted), or end-to-end encrypted if you turn that on. See section 10 for the full detail. | Yes (your own Google account) |
We do not sell personal data, do not share it for cross-context behavioural advertising, and do not use it to build advertising profiles. There are no advertising SDKs, attribution SDKs or third-party trackers in NOLO.
8. What your browser loads directly from third parties
Almost everything is relayed through NOLO's own server so that third parties never see you. These are the exceptions, where your browser talks to another company directly and that company therefore receives your IP address and user agent. We list them because they are real, not because we are comfortable with them.
| Who | When | Why it is direct |
|---|---|---|
Google Fonts (fonts.googleapis.com, fonts.gstatic.com) | On every page load of the website and the app. | The interface typefaces are served from Google's font CDN. Google receives your IP address and user agent as a result. |
| Cloudflare cdnjs, jsDelivr and SheetJS (cdn.sheetjs.com) | Only when you use a feature that needs a library: PDF reading, Word and Excel handling, maths rendering, charts, diagrams, maps, code highlighting, QR codes, file export. SheetJS's own CDN serves only the Excel library, with cdnjs as the fallback. | These libraries are loaded on demand from public CDNs rather than bundled. The CDN sees your IP and which library you fetched, which loosely reveals which feature you used, though not its content. |
fal media CDN (*.fal.media) | Only when you open an image generated before 3 November 2026, when NOLO used fal. | Those older images are rendered straight from fal's CDN link, so fal sees your IP address at that moment. |
| Frankfurter (currency), Open-Meteo (sunrise and sunset), Nager.Date (public holidays), OpenStreetMap tiles (maps) | Only when one of those interactive widgets appears in a conversation and you interact with it. | These widgets refresh their own data in the browser. Each of those services sees your IP and the specific lookup: a currency pair, a coordinate, a country code, a map tile. |
You can verify all of this yourself in about thirty seconds: open NOLO, press F12, open the Network tab, and watch. Everything on this page is observable.
9. Analytics
NOLO runs no third-party analytics on the website or in the app. Until it moved to its own server in November 2026 it used Vercel Web Analytics and Speed Insights (cookieless, aggregated, no visitor identifier). They ended with the move and their scripts have been removed. Visits and speed are now counted by NOLO's own server, as described below.
Visit statistics
A small script of NOLO's own (/js/nv.js) runs in the app and on the website pages. It uses no cookies, stores nothing on your device and assigns no identifier. When a page opens it sends: the page path (without query or fragment); the name of the referring site (host only); a campaign tag, if the link had utm_source, ref or source; your browser language and screen width; whether the device has a touch screen; and whether NOLO is opened installed or in a browser. When you leave the page it sends five load and response timings (LCP, INP, CLS, FCP and TTFB), measured with Google's open-source web-vitals library, which is served from NOLO's own server.
On the server, the IP address and the User-Agent of that request are used only in memory. The IP gives the country, through DB-IP's free country database kept on the server (DB-IP receives nothing). The User-Agent gives the device type, the browser and the operating system family. Then both are discarded. IP Geolocation by DB-IP.
Unique visitors per day are counted with a hash of IP, User-Agent and site, and a second hash of IP and User-Agent alone, so that someone who uses both the website and the app counts once in the combined figure. Both are salted with a random key that exists only in memory and changes every day, so visits cannot be linked across days or to anyone, and the hashes are never written to disk. So that a restart of the counting program does not count the same visitors twice, the key and the hashes seen that day are kept in a memory-only folder of the server that only that program can read; they are erased when the day ends, when the program is stopped and when the server restarts. The same hash tells, in memory, whether a visitor opens a second page that day; only how many did is stored. What is stored is totals only: per day, page views and visitors, broken down by page, referring site, campaign, country, device type, browser, operating system, language and installed or browser, and by each pair of those (for example, country and page), so that the owner's panel can filter one by another; per hour, the same kind of totals for the last 40 days; and speed as anonymous histograms per page and device type. Daily totals are kept 800 days, totals by pairs 200 days, hourly totals 40 days (3 days when broken down) and speed histograms 400 days. Robots that announce themselves are not counted. Only the owner of NOLO sees these figures, in an owner-only panel; no third party receives them.
NOLO's own former usage and visitor analytics have been retired and the code that wrote them has been removed. What NOLO also counts is how many times certain things happen each day, as totals with no identifier of any kind: the nolo_metricas table in section 6.
How long each message takes
When an answer ends, NOLO's server records how its time was spent, to find where the waiting goes: how long the request took to prepare and to reach the model, when the model's first piece arrived, when the first word went out and when it ended; whether it ran in the background; the model and the provider that served it; how many rounds and tools it used; and the size of the request. The app adds its own half: how long sending took, when the first word appeared on the screen, the total time and the size. The two halves are joined by a random ID made for that one message. No anonymous ID, no IP address, no text. These records are kept for 14 days and only the owner sees them. Anonymous chats and scheduled tasks never send them.
Switching all of it off
Settings → Privacy → "Don't send usage statistics" stops the app on that device from sending the visit statistics, the timings of each message and the daily counts in nolo_metricas. It is a setting of the app, so it does not reach the pages of this website. Nothing else in NOLO changes.
Security on the server
Requests to paths no real visitor uses, such as /.env, /.git/, /wp-login.php or any *.php, get a 404. They are written to a log on the server, kept at most 48 hours and at most 2 MB, with the IP address, path, user agent and time, so that whoever keeps probing can be blocked. No other request is logged.
An address that requests 3 such paths within 10 minutes is blocked for 4 hours. One that fails to log in to the server by SSH 6 times within 10 minutes is blocked for 24 hours. A blocked address is kept only while its block lasts, and the owner's panel shows only how many were blocked and their countries. Failed SSH logins are attempts to break into the server, not uses of the app; the operating system's journal records them for 7 days.
Networks on Spamhaus's DROP list (networks hijacked or run by criminals), downloaded daily, are refused at the firewall; nothing is sent to Spamhaus. Per-IP limits on requests and connections keep a single address from flooding the service; their counters live in memory, for at most a minute after an address’s last request, and are never written. Error logs are kept for 7 days without conversation content, and there is no general access log of requests.
10. Google Sign-In and Drive sync (optional)
NOLO offers an optional Google Sign-In so your chats can follow you between devices. It is entirely optional and NOLO is fully functional without it. If you never sign in, this section does not apply to you.
What NOLO asks Google for
openid, which returns Google's opaque account identifier (thesub). NOLO does not request your email, name or profile picture. If Google's standard response includes them, NOLO discards them immediately and never stores them.https://www.googleapis.com/auth/drive.appdata, which grants access restricted to NOLO's own hidden folder inside your Drive. This scope cannot read, list or modify any other file in your Drive. It is technically incapable of it.
What is stored in your Drive
Files in that hidden folder: one per conversation, and one with your settings, memory, projects, skills and your anonymous ID (so your paid plan follows you across devices). A manual backup, if you save one, is one more file there.
By default, each file is scrambled in your browser with AES-GCM 256 before it is uploaded, but the key is derived from your Google account identifier (with PBKDF2 at 100,000 iterations and a fixed salt), not from a secret only you know, so this is obfuscation, not end-to-end encryption. The key is regenerated locally each session and never transmitted to or stored on NOLO's servers. NOLO's servers never see the key, the plaintext, or even the fact that sync files exist.
End-to-end encryption (optional)
In Settings > Account, on the Drive card, you can turn on end-to-end encryption with your fingerprint (or with a recovery code only). Then:
- Your device creates a random 256-bit key. Every file is encrypted with it (AES-GCM 256) before it leaves your device. Files already in your Drive are rewritten encrypted in the same place.
- That key is stored in your Drive only wrapped: by a passkey (your fingerprint, face or screen lock, kept and synced by your password manager, such as Google's or Apple's) through the WebAuthn PRF extension, and by a 24-character recovery code shown once on your screen. NOLO never receives the key, the passkey's secret or the code. On your device the key is kept wrapped by a non-extractable device key.
- On another device you open the backup with that passkey or with the code. A device that has neither does not sync until you open it there.
- You can turn it off again on the same card. Your files are uploaded again in the obfuscated format, in the same place, and only then is the wrapped key deleted from your Drive.
- If you lose all your devices, the passkey and the recovery code, nobody can open your Drive backup, not even NOLO. That is the price of nobody else being able to read it. Your chats on your devices are not affected.
- What stays visible to Google: how many files there are, their names (which include a random conversation ID), their sizes, when they change, and a short fingerprint of each conversation used to avoid needless uploads. Not their content.
Google's Limited Use commitment
NOLO's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, NOLO does not transfer information received from Google APIs to third parties; does not use it for advertising, profiling or training AI models; and does not allow humans to read it, except with your explicit consent, to comply with applicable law, or as strictly necessary for security operations.
The honest caveat. Without end-to-end encryption, the key comes from your Google account identifier rather than a password only you know, so this is obfuscation, not end-to-end encryption. If someone held both your sync files and your Google account identifier, they could derive the key, and Google holds both, so Google could read them. NOLO stores neither: the files stay in your Drive and our servers never download them. To be exact, while you are signed in our server does see your Google identifier and a Drive access token, so this rests on what our code does, not on mathematics. That is why we do not call it encrypted.
With end-to-end encryption on, neither Google nor NOLO's server has the key, so neither can read your files, even with that token. As with any web app, this relies on the code NOLO serves to your browser doing what this page says: the code is the same for everyone and can be inspected in your browser.
How to disconnect or delete it
- Sign out on this device: Settings → Account → Sign out. The token is revoked and syncing stops. Your sync files stay in your Drive so you can come back.
- Delete everything: Settings → Data & storage → "Delete all my data". This deletes every sync file from your Drive, revokes the token and wipes local data on the device.
- Revoke from Google: at any time, at myaccount.google.com/permissions. This works independently of NOLO.
11. Payments and subscriptions
On the web, payments go through Stripe. You are redirected to Stripe's own checkout; your card details are entered on Stripe's page and never reach NOLO's servers. NOLO stores the resulting Stripe customer ID against your anonymous ID so your plan can be recognised, and receives webhook events about the state of the subscription.
In the Android app from Google Play, payments go through Google Play Billing under your own Google account. NOLO receives a purchase token and a product ID and nothing else: no name, no email, no payment method. NOLO asks Google once a day whether that subscription is still active, and removes paid access when it is not. Google also sends NOLO real-time notifications when a subscription changes state.
In both cases the payment provider retains transaction and invoice records for as long as its own tax, accounting and anti-fraud obligations require. NOLO cannot delete those records on your behalf.
12. International transfers
NOLO is operated from the European Union, but most of its providers are established in the United States: Groq, OpenRouter, Wafer, Morph, OpenAI, Tavily, Stripe and Google (and Mozilla or Apple, if you turn on notifications in their browsers). Using NOLO therefore involves transferring data outside the European Economic Area.
These transfers rely on the European Commission's Standard Contractual Clauses and, where the provider is certified, on the EU–US Data Privacy Framework, together with the technical measures described throughout this policy, principally that your identity is not transferred at all, because there is none to transfer.
If you would rather not have your data processed in the United States, the honest answer is that NOLO is not the right tool for you today, and we would rather say so than bury it.
13. Legal bases for processing
| What we do | Legal basis (GDPR Art. 6) |
|---|---|
| Running chat, search, file and image features, the tasks you schedule, and relaying your requests to AI providers | Performance of a contract, Art. 6(1)(b). |
| Usage counters, hashed-IP rate limits, abuse and fraud prevention | Legitimate interests, Art. 6(1)(f): keeping a free-to-start service financially viable and available. |
| Anonymous daily counters | Legitimate interests, Art. 6(1)(f). |
| Optional Google Drive sync | Consent, Art. 6(1)(a), given by choosing to sign in. Withdrawable at any time. |
| Subscriptions, invoices, tax and accounting records | Contract, Art. 6(1)(b), and legal obligation, Art. 6(1)(c). |
| Answering support emails | Legitimate interests, Art. 6(1)(f), or contract where it concerns a paid plan. |
Where we rely on legitimate interests, you have the right to object. See section 15.
14. How long anything is kept
| Data | Retention |
|---|---|
| Your conversations | Never stored by NOLO. They live on your device until you delete them. |
| Message content at an AI provider | Not retained at Groq (Zero Data Retention is enabled on the account), nor at the companies OpenRouter passes chat and photo requests to (zero data retention is required on each of them). The exception is image generation at OpenAI, which keeps the prompts it receives. See section 7. |
| Daily usage and image counters | 30 days, deleted by an automated nightly job. |
| Rolling-window usage counters | 7 days. |
| Hashed-IP rate-limit counters | 7 days. |
| Your row in the users table (ID, plan, subscription state) | For as long as you use NOLO, then until you ask us to delete it. |
| Generated images on NOLO's server | 30 days, then deleted automatically. Anyone with the link can open the image during that time; the link cannot be guessed. Your own copy stays in your local gallery. |
| Feedback messages | Until we delete them by hand: answering or archiving one does not delete it, and there is no automatic deletion. They carry no identifier, so they cannot be traced back to you, which also means we cannot delete "yours" on request. |
| Scheduled tasks and routines (encrypted) | A routine: until you delete it. A one-off task: until it has run and your device has collected the answer, and at most 30 days after it ran. All of them at once with "Delete all my data". |
| Runs of a scheduled task | Until your device collects the answer, and at most 8 days. The answer itself waits on NOLO's server for up to 7 days. |
| Push subscriptions (encrypted) | Until you turn notifications off on that device, the browser's push service retires the subscription, or you delete all your data. |
| Price alerts (name and notification encrypted) | Until you delete the alert, and at most 30 days after it goes off. All of them at once with "Delete all my data". |
| Shared chats (encrypted on your device) | Until the time you chose when sharing (30 days at most) or the number of openings you chose, whichever comes first; earlier if you stop sharing or use "Delete all my data". NOLO cannot read them: the key is in the link, after the "#", and never reaches a server. |
| Your location | Never stored. The app keeps it in memory for 30 minutes, for the chat where you shared it. |
| Sync files in your Drive (obfuscated, or end-to-end encrypted if you turned it on) | In your Drive, under your control, until you delete it. We have no copy and could not read one. |
| Error logs on NOLO's server | 7 days, then automatically discarded. They hold error types and codes, with no conversation content. The only request log is the security log of probing requests: at most 48 hours and 2 MB (section 9). There is no general access log of requests. |
| Timings of each message (no identifier, no text) | 14 days (section 9). |
| Encrypted backups | The database every 6 hours, and the images, the shared chats and the owner's statistics (section 9) once a day, encrypted with a key that is not on the server. Never the answers being written. Kept for at most 14 days, so something you delete can remain in a backup until that backup expires. |
| Payment and invoice records | As long as Stripe's or Google's legal, tax and accounting obligations require, typically several years, and outside our control. |
| Support emails | As long as needed to resolve the issue and keep a record of it. |
15. Your rights, and how to actually use them
Under the GDPR and comparable laws you have the right of access, rectification, erasure, restriction, objection, portability, withdrawal of consent, and the right to lodge a complaint with a supervisory authority. If you are in the EU you can complain to your national data protection authority; a list is at edpb.europa.eu.
Because NOLO holds almost nothing about you, most of these you can exercise yourself, immediately, without asking us:
- Erase your conversations, projects, memories and settings: Settings → Data & storage → "Delete all my data". Instant, and it also removes the Drive sync files if you use sync, and your scheduled tasks, their pending results, your price alerts and your push subscriptions from our server.
- Export your data: the export controls in the app produce a file from your local storage. That file is your data. There is no server copy to request. You can protect it with a password: it is then encrypted on your device, and without that password nobody can open it, not even you.
- Erase your server record: email nolo.ai.app@gmail.com with your anonymous ID (Settings → Account shows it) and ask us to delete it. We respond within 30 days and usually within a few days. If you have a paid subscription, cancel it first, because deleting the record ends your access.
- Object to legitimate-interest processing: write to us. In practice, opting out of usage counters means opting out of NOLO, because they are what makes daily limits possible. We will say so plainly rather than pretend otherwise.
- Withdraw sync consent: sign out in Settings, or revoke NOLO at myaccount.google.com/permissions.
There is a dedicated data-deletion page at nolo-app.com/delete-account.
The trade-off in being anonymous. Because we hold no email or name, we cannot verify that a data request comes from you. If you ask us to delete or disclose a server record, we can only act on the anonymous ID you supply. We will not hand over or delete a record belonging to an ID you cannot demonstrate is yours. That protection cuts both ways, and it is the price of not asking who you are.
If you are in California or another US state with a comparable law: NOLO does not sell or share personal information as those terms are defined, does not use it for cross-context behavioural advertising, and does not offer financial incentives for data. The rights described above apply equally, and we do not discriminate against anyone who exercises them.
16. Children
NOLO is not directed at children. You must be at least 16, or the minimum age for consent to data processing in your country if that is lower, and at least 18 to buy a subscription. We do not knowingly process data from anyone below that age. Because there is no account, we have no age verification beyond this statement and Google Play's own content rating, another limit we would rather state than imply away. If you believe a child has used NOLO and you want the associated server record removed, email us with the anonymous ID.
17. Security
- HTTPS everywhere, with HSTS and preloading.
- A strict Content Security Policy that limits which hosts the app may contact at all. It is enforced by your browser, and every host in section 8, like every company in section 7 that your browser reaches directly, is listed there; the rest of section 7 is reached by NOLO's server, never by your browser.
- Provider API keys live only in server environment variables and are never exposed to the browser.
- Cross-origin requests are restricted to NOLO's own domains.
- Rate limits on every expensive endpoint, keyed on a hashed IP.
- Sync payloads are obfuscated client-side before they leave the device, or end-to-end encrypted if you turn that on (see section 10).
- With the app lock on, conversations are stored encrypted on the device with a key that only your password or fingerprint opens (section 5). A backup you export can be protected with a password: it is then encrypted on your device (AES-GCM 256, PBKDF2 with 600,000 iterations) and cannot be opened without it.
- A design rule against logging user content, applied throughout the codebase.
No internet service can promise perfect security. You remain responsible for your device, your browser profile, your exported files and any content you choose to submit. If you find a vulnerability, email nolo.ai.app@gmail.com. Reports made in good faith are welcome and will not be met with legal threats.
18. The honest limits
Every claim above has an edge. Here they are, collected in one place so you do not have to find them yourself.
- NOLO is not "zero logs". We keep pseudonymous usage counters for 30 days, and our server keeps a short security log (48 hours) of probing requests, with the IP address. Without either, daily limits and abuse prevention would not work. "No content logs and no identity" is accurate; "zero logs" would be a lie.
- Hashing an IP is pseudonymisation, not anonymisation. Our rate-limit hashes use a fixed salt, so the same IP always produces the same hash. It cannot be reversed to an address by inspection, but someone who guessed an IP could confirm it. Those rows hold only a counter and a date, and are deleted after 7 days.
- Your IP and your anonymous ID are in the same request. When you send a message, our infrastructure necessarily sees both at once. We do not store them together and nothing writes that pairing to a database, but we cannot claim the pairing never exists.
- Drive sync is end-to-end encrypted only if you turn it on. By default it is obfuscated with a key derived from your Google account, so Google could read it. With end-to-end encryption on, Google still sees the files' names, sizes and dates, and losing every device, the passkey and the recovery code means losing the Drive backup. See section 10.
- Scheduled tasks and price alerts are encrypted at rest, not end-to-end. NOLO's server holds the key, because it has to read a task to run it and an alert to send it. A stolen copy of the database would not show them; NOLO itself can read them. An alert's symbol, direction and price are in the clear, because the database compares them with the market itself. See section 6.
- Local storage is encrypted only with the app lock on, and only the conversations. Without the lock, anyone with your unlocked device can read your chats. With it, your memory, settings, drafts and files are still not encrypted, and the encryption is as strong as your password.
- Your messages are not end-to-end encrypted with the AI. To answer, the model has to read what you write: it travels encrypted (HTTPS) and is not kept, but NOLO's server and the AI provider read it while the answer is written. What is end-to-end encrypted is the Drive backup (if you turn it on), shared links and password-protected exports.
- Some third parties do see your IP directly. Google Fonts on every load; the library CDNs when you use those features; and the few services behind interactive widgets (currency, sunrise, holidays, map tiles) when you use one. Section 8 lists exactly when.
- We cannot audit our providers' internals. What section 7 reports is what each provider publicly commits to. We can prove what NOLO sends and to whom; we cannot prove what happens inside another company.
19. Professional, regulated and sensitive use
NOLO is useful for legal, compliance, business, medical-adjacent and research work, but it is not a law firm, lawyer, accountant, doctor, financial adviser or any regulated professional service. Using it creates no attorney-client relationship, no professional privilege and no duty of confidentiality equivalent to one owed by your own adviser.
If you intend to put client data, personal data of others, health data, trade secrets, privileged material or regulated information into NOLO, you are the controller of that data and you are responsible for confirming that doing so is lawful, authorised and compatible with your professional duties. Read section 7, decide whether that chain of providers is acceptable for your obligations, and do not paste anything you are not entitled to share with them. NOLO does not currently offer a data processing agreement or a business associate agreement; if you need one, email us before using NOLO for that work.
20. Changes to this policy
If we add, remove or replace a provider, this page changes and the date at the top changes with it. That is the commitment: the list in section 7 is meant to be complete at all times, not aspirational. Material changes will also be surfaced in the app or on the website. If you want to know what changed and when, ask us and we will tell you.
21. Legal identity
Operator of NOLO and data controller for the processing described above:
Vasile Eduardo PușcașuStr. Cireșar 14, Bragadiru
Județul Ilfov, Romania
nolo.ai.app@gmail.com
Published to satisfy the identification requirements of GDPR Art. 13, the EU Digital Services Act and EU consumer law. It is the same operator address registered with Google Play. For anything to do with NOLO, email is the right channel and will always get a faster answer than post.