If you scanned a code in a magazine and landed here: we do not know who you are. There is no account for you, we never asked for your name or email, and we have no way to recognise you on a second visit. What follows is the whole of it.
What we record. When you open a page like this we note that a visit happened, which panels you opened and how far you went. Those actions are tied together by a random key made fresh for that one visit, so the publisher can see how many people explored and how deeply. The key identifies the visit, not you, and a later visit gets a different one.
Questions you type. If you ask the page something, your question and its answer are stored so the publisher can see what readers wanted to know. The text is deleted automatically after 180 days, whether or not anyone asks. The count remains; the words do not.
Notes to the publisher. A private note reaches them carrying no indication of who wrote it, and is deleted after 180 days.
Your network address. We need to count requests to stop flooding, but we do not need to know where they came from, so your address is never stored. What is stored is a one-way code derived from it that cannot be turned back into an address and changes every day. Those rate-limit counters are erased after about two days.
Pages written for children. Where a publisher has marked an article as written for children, that page records nothing whatsoever, and offers neither the question box nor the note box.
Cookies. A small cookie stops a page counting you twice and remembers which reaction you chose, and it lasts a year. Nothing is used for advertising, and nothing follows you to other sites.
What we count. We count how many people visit nascentbloom.com on a given day, and that includes this page. No cookie is involved and no account exists. Your address is not stored: what is kept is the same one-way code described above, which changes every day and cannot be turned back into an address.
What that shows us, and what it does not. Because the code changes daily, we can see how many different visitors arrived on one day and nothing beyond that. We cannot tell whether you came back the next day, what you read before, or who you are. One row is kept per visitor per day, and those rows are deleted after 400 days.
We collect the name, email address and password you provide, and the articles you add. Where you start an article from a document, the file is read in memory and its words taken out; the file itself is never written to disk or to our database, and is gone the moment the text reaches your screen. Passwords are stored as irreversible hashes and cannot be read by us. Your articles, analytics, drafts and assistant history are reachable by no other publisher — every query that touches them is scoped to the account that owns them. They are reachable by us, because they sit in our database and we hold its credentials; what we do with that is set out in our terms. We send account-related email — verification and password resets — and no marketing.
We do not sell your information and never share it with another publisher. Producing a reading experience means sending the article text, and any question a reader types, to a language-model provider. We keep a list naming every one of them and what reaches each, send it on request, and tell you before it changes. We do not train any model on your content.
Under the Digital Personal Data Protection Act, 2023 you may ask what we hold about you, ask us to correct or erase it, and complain if our answer does not satisfy you.
Readers: because no account exists for you, we usually cannot connect you to your own records. If you want something you typed removed, tell us the publication and roughly when, and we will look. Question text expires after 180 days regardless.
Publishers: delete any article, or your whole account, from your dashboard at any time. Deleting an article also removes everything generated from it; deleting an account removes all of that together with your analytics.
If a breach affects your data we tell the publication, promptly and in writing, with what we know: what happened, when, and which pages are involved. We cannot tell you ourselves — we hold no name, address or account for any reader, so there is no way for us to reach you. Telling readers is the publication's responsibility under the Act, and the publication is also the one that can actually do it. We give them the facts and, if they want it, the wording. We will also notify the Data Protection Board of India where the Act requires it.
Write to [email protected], which reaches a person rather than a queue. We answer within seven days. If you are not satisfied, the Act gives you the right to complain to the Data Protection Board of India.
We may update this page. Material changes are reflected in the date at the top.