Privacy Policy
What n3os collects, why, who else sees it, and what you can require us to do about it. Written to be read rather than to be survived.
Last updated 15 November 2026
Who we are
N3O Studios operates n3os.com and the tool directory at tools.n3os.com. For the purposes of the Digital Personal Data Protection Act, 2023 we are the Data Fiduciary, and for the purposes of the UK and EU GDPR we are the data controller.
We are based in India. If you are reading this from the EU, the UK, or anywhere else, the rights described below still apply to you, and we do not make you argue about which law you are covered by: where two of them differ, we apply whichever gives you more.
N3O StudiosSalt Lake, Bidhannagar, Kolkata, West Bengal 700106, IndiaEmail: support@n3os.comGrievance Officer, N3O StudiosGrievances: grievance@n3os.comPlease email before sending post: we answer email far faster, and a letter that arrives without one may take considerably longer to reach the right person.The short version
You can browse the entire directory and read everything we publish without an account, without giving us an email address, and without us storing anything that identifies you.
We ask for personal data in exactly three places: if you create an account, if you subscribe to the newsletter, and if you send us a message, which includes suggesting a tool for the directory. Each is optional, each is described below, and none of them is a condition of using the site.
We do not sell personal data. We do not share it for advertising. We do not run advertising, and the one thing that records how a visit moves from page to page - Google Analytics - runs only if you accept it.
If we ever add affiliate links or sponsored placements, we will update this policy before the first one goes live, saying what, if anything, they record about you.
What we collect, and why
Accounts. If you create one, we store the email address you sign in with, a username if you set one, and an identifier from the sign-in provider you chose. We never receive or store a password: sign-in is either a one-time email link or an OAuth provider, so there is no password on our side to lose. The purpose is to let you sign in and to keep anything you save associated with you. The lawful basis is performance of the contract of providing you an account; under the DPDP Act it is the consent you give when you create one.
Which version of the Terms you accepted. When you tick the box on the sign-in page, we record the version of the Terms you agreed to and the time, against your account. The purpose is being able to show what was agreed; the basis is our legitimate interest in that, and it is deleted with the account.
Saved tools. If you press Save on a tool in the directory, it goes on a list at tools.n3os.com/saved. Without an account that list is kept in your own browser and is never sent to us. If you are signed in, it is also stored against your account, so that it follows you to another device: which tool, when you saved it, and the price model the listing showed at the time, which is how the page can tell you that a tool's pricing has changed since. Only you can read your list. We do not publish it, count it per tool, or use it to rank anything, and opening a tool's page without pressing Save records nothing about you. Removing a tool from the list deletes it, and the whole list is deleted with the account. The basis is performance of the contract of providing you an account.
Newsletter. If you subscribe, your email address goes to Buttondown, who send the emails. The purpose is sending you the newsletter; the basis is your consent, which you can withdraw with the unsubscribe link in every email or by emailing us.
Messages you send us. If you use the contact form, suggest a tool at tools.n3os.com/submit, or email us, we receive what you wrote, your name if you give it, and your email address, so we can answer and, for a suggested tool, check who is asking. A suggested tool is also put in our review queue, so suggestions are dealt with in the order they arrive, and you get one automatic email saying it has arrived. The basis is our legitimate interest in replying to you, and your consent in sending it.
Assistant questions. If you use the assistant, the question you type is sent to a third-party model provider to be answered. The same goes for the prompt builder at tools.n3os.com/use/prompt-builder, but only if you press Improve with AI: then the four fields you filled in are sent to be rewritten, and nothing is sent otherwise. Do not put anything confidential into either. We do not store the conversation or the draft, and the provider's own retention is theirs rather than ours.
Page views. We count how many times each page is opened, per day, and which site referred the visit. That is the whole record: no cookie, no identifier, no profile, and no record of which pages any individual looked at. Two people visiting once and one person visiting twice are indistinguishable to us by construction. Visits by search-engine crawlers and other automated tools are not counted. The basis is our legitimate interest in knowing which pages are worth writing.
Objecting to being counted. If your browser sends a Global Privacy Control or Do Not Track signal, neither the page-view counter nor the error report runs for you at all: your browser does not send them, and if a request arrives anyway, our server discards it before anything is recorded. That is free, needs no account, and is the simple way to object that the law asks for. Firefox, Brave and DuckDuckGo can send the signal, and extensions add it to other browsers.
Errors. If a page breaks in your browser, it tells us the error message, one line of the technical trace, and which page it happened on. It is counted the same way as a page view - no cookie, no identifier, no profile, and the counter cannot tell two people hitting a fault once from one person hitting it twice. We do not receive anything you typed, and the address of the page is recorded without its query string. Before a report is stored, anything in it that looks like an email address, a sign-in token, an access key or a long account or card number is replaced with a placeholder, and web addresses inside it lose their query strings too. The basis is our legitimate interest in finding out that something is broken without waiting for someone to tell us.
Security. When you use the assistant or load a page, your IP address is passed through a one-way keyed hash so we can rate-limit abuse. The hash is what the rate limiter sees; the address itself is never written to storage. In the same way, when you suggest a tool, a keyed hash of the email address you gave is kept for a day, so that our automatic acknowledgement cannot be used to flood someone's inbox; the address in it is never stored. Each hash is deleted when the limit it counts towards resets: within minutes for the per-minute limits, and by the end of the day (UTC) for the daily ones. The basis is our legitimate interest in keeping the service available.
Cookies and local storage
We use no advertising cookies. We do use Google Analytics, and only if you accept it - nothing from Google is loaded until you do. What follows is the complete list of what is stored on your device, and it is short.
Strictly necessary, set without asking because the site cannot do what you asked without them: a session cookie, set only if you sign in, scoped to n3os.com and its subdomains so one sign-in works on both sites - it holds your session and nothing else and is removed when you sign out; a cookie recording your answer to the banner below, which holds one word; and, during sign-in, a short-lived value your browser stores so the sign-in can be completed securely.
Set at your request: your light or dark theme preference. It is a cookie holding one word, scoped to n3os.com and its subdomains so that choosing dark on one of our sites does not leave you on a white page when you reach the other. It is set only when you click the toggle, and nothing on our side reads it. The same goes for your list of saved tools on tools.n3os.com: it is kept in your browser's own storage, written only when you press Save, and removed when you take the last tool off it.
Not set by us at all: the page-view counter. It records that a page was opened, on a date, and nothing else - no cookie, no identifier, no profile.
Needing your consent, and the reason there is a banner: one thing, Google Analytics, which sets its own cookies and tells us which pages are read and roughly where in the world from. It is not necessary for the sites to work, so it does not happen unless you say yes. If you decline, or simply ignore the banner, no Google script loads at all and nothing else changes - our own page counting carries on either way, because it stores nothing on your device and identifies nobody. The one exception is a browser that sends Global Privacy Control or Do Not Track, which we do not count at all.
You can change your mind whenever you like by declining or accepting again - the banner returns if you clear your cookies, and the choice covers both sites. We treat no answer as a refusal.
Two things used to need your consent and no longer do, both for the same reason. Our fonts were loaded from Google and are now served by us. The icon beside each tool in the directory was fetched by your browser from Google, and is now fetched by our own server instead and passed on to you - so your browser never contacts Google for it, and Google never sees that it was you looking. Where we can remove a third-party dependency rather than ask permission for it, we would rather do that.
Signing in with Google or GitHub
If you choose to sign in with Google or GitHub, you are sent to them to approve it, and they tell us only that the sign-in succeeded plus the email address on the account. That redirect is something you asked for by clicking the button, so it does not need separate consent - but it does mean Google or GitHub knows you signed in here, under their privacy policy rather than ours.
If you would rather they did not, use the email link instead. It does the same thing and involves nobody but us.
Who else processes your data
We use a small number of service providers, each for one job, and each bound to process data only on our instructions:
- Supabase - database, authentication, the account system, and the review queue of suggested tools. Data is held in their Singapore region.
- Cloudflare - hosting and delivery of tools.n3os.com.
- Google - analytics only, and only if you accept the banner; if you do not, we send them nothing. Google processes this under their own terms and may transfer it outside the UK, EU and India. The tool icons are no longer part of this: our server requests those, so what reaches Google is a website address and our server, never you.
- BigRock - hosting of n3os.com, and delivery of contact and tool-suggestion messages to our inbox, by our own mail server.
- Buttondown - newsletter delivery, for subscribers only.
- Groq and other model providers - answering assistant questions, and rewriting a draft when you press Improve with AI in the prompt builder, for the duration of the answer.
- Google - the favicon images shown beside each listing, which our server fetches rather than your browser, and Search Console verification.
This list is exhaustive at the date above. If we add a processor that handles personal data, this list changes before it goes live, not afterwards.
Where your data goes
We are in India and our providers are largely outside it, so personal data is transferred internationally. For transfers out of the UK or EU we rely on the European Commission's Standard Contractual Clauses, or on the provider's own adequacy arrangements where one applies.
The DPDP Act permits transfer outside India except to territories the Government restricts. We do not transfer personal data to any restricted territory.
How long we keep it
Account data: for as long as the account exists, and deleted when you delete the account.
Newsletter subscription: until you unsubscribe.
Messages: for as long as we need to deal with what you wrote, and routinely cleared afterwards.
Tool suggestions in the review queue: 12 months from when you send them, then deleted automatically.
Page view counts: indefinitely, because they contain nothing about any person.
Error reports: 90 days, then deleted automatically.
Rate-limit hashes: until the limit they count towards resets, which is at most a day.
Your rights
Whatever law applies to you, you can ask us to: tell you what we hold about you and give you a copy; correct anything wrong; complete anything incomplete; delete it; or stop processing it. Under the GDPR you may also object to processing carried out on the basis of legitimate interests, and ask for your data in a portable form.
Under the DPDP Act you additionally have the right to nominate another person to exercise these rights if you die or become incapable of exercising them yourself, and the right to a grievance redressal process - which is below, and which you must use before approaching the Data Protection Board.
Where we rely on consent, you can withdraw it at any time, and withdrawing it is as easy as giving it was. Withdrawing consent does not undo what was lawfully done before you withdrew it.
Write to support@n3os.com to exercise any of this, or to grievance@n3os.com if it is a complaint rather than a request. We answer within 30 days, and sooner in practice. We do not charge for it.
Complaints
If we get this wrong, tell us first, because it is faster and we would rather know. Our grievance process is in the Terms, along with the timescales we hold ourselves to.
If we do not resolve it, you can complain to the Data Protection Board of India. If you are in the UK you can complain to the Information Commissioner's Office, and if you are in the EU, to your national supervisory authority. You do not need our permission and you do not have to tell us first.
Children
The site is not directed at children, and accounts are for people aged 18 or over. Under the DPDP Act, processing the personal data of a child requires verifiable parental consent, and we do not have a mechanism for obtaining it - which is why we do not knowingly collect data from anyone under 18. If you believe a child has given us personal data, write to us and we will delete it.
Changes
If we change this policy in a way that affects you, we will say so on the site before the change takes effect, and the date at the top will move. We will not quietly broaden what we do with data you already gave us.
If a change is material - to what we collect, why we collect it, or who else processes it - we will also email account holders and newsletter subscribers at least 14 days before it takes effect, saying what is changing.