What this site knows about you

• There are no accounts. You are never asked for a name, an email address, or a password, and there is nothing here to sign up for.
• There is no advertising, and no advertising network is given anything.
• There is no counting of visits, no invisible markers, no recording of what you do on the page, and nothing embedded from another site. This site loads nothing from anyone else at all.
• There is no profiling. Nothing here tries to work out who you are or connect one visit to another.
• Your data is never sold, rented, or traded. Not now, not later, not as part of anything.

When a run is created, the following is written down and kept:

• the question you asked, and the short title the engine gave it;
• every statement the engine produced, the links between them, which ones merged, and how much weight each one gathered;
• the run’s own record of what happened while it grew, in order, and the final verdict;
• the time of the run, and of each statement.

The ask line takes words alone — there are no uploads of any kind, and no upload storage behind this site. Your typed question and what the engine grew from it are the entire record.

No profile of you is kept anywhere, and there are no contact records and no mailing lists, because there is nothing here that would create one.

Runs are kept in the United States, in professionally run storage this site rents. This site reaches that storage directly and writes only to its own records. If you are reading from outside the United States, that is where your question goes.

The engine cannot run without sending text to the minds that grow and read the web. Your question, and the statements the engine generates from it, are handled by two outside minds — established companies acting as this site’s processors — one grows the web, the other reads it once and writes the verdict.

Both are used on their paid, business-grade terms, and under the published data policies for those terms, what is sent to them and what comes back are not used to train them. Those are their policies, not ours; we can point at them, and we can choose not to send more than the engine needs, which is what we do. Nothing beyond the question and the statements derived from it is sent — nothing about where you are, nothing that names you, nothing about where else you have been. If you need the processors by name — for a deletion request that has to travel, say — ask through the contact below and you will get the current list.

Running the engine costs real money, so requests are counted per connection. What they are counted against is a one-way scramble of the number your connection arrives from — never that number itself. It is scrambled together with a secret of this site’s own, so it cannot be matched against anything outside here; the number is never kept, this site never writes it down, and it cannot be worked back out of the scramble.

Each scramble is kept with a counter and a date so a daily limit can be enforced, and it is deleted about a week later. It is not linked to your runs, and it is used for nothing else. The company that keeps this site online keeps its own brief record of requests, as every such company does.

A visitor gets no cookies at all. Reading the site, opening a run, and watching one grow set nothing on your device.

One cookie exists, and only the keeper of this instrument ever receives it: unlocking private mode with the keeper’s key leaves a single cookie behind, and it holds that key and nothing else. It belongs to this site alone — no other site can read it, nothing running inside the page can read it either, and it has nothing to do with measuring anyone. It lasts a year unless you clear it. It is a door key, not a name.

This matters more than anything else on this page: a run is not private. Anyone with a run’s link can read it in full — the question, every statement, the verdict. Runs are unlisted: there is no public feed of other people’s questions, and the library on the home page shows only the runs your own browser started (it remembers them locally, on your device). The operator can see everything that is stored. Search engines are asked not to list individual runs, which is a courtesy rather than a wall: a link is a link — share it and you have shared the run.

So: ask the engine real questions, but do not type anything into it you would not want read — no names of people who did not agree to be here, no medical details, no secrets, nothing that identifies you unless you mean it.

Write and a run will be deleted — the question, its statements, its events, and its verdict, all of it, no reason required. You can also ask for a copy of what is stored for a run. Include the run’s link, or the question text, so it can be found.

Requests go to Devello Studios: devellostudios.com/contact. Because there are no accounts, a run link is the only handle on a run — keep it if you think you may want it removed.

If this policy changes in a way that matters, the effective date at the top changes with it and the change is described here rather than quietly swapped in. If the change is significant, a note stays on this page for a while.

14 August 2026: this page was rewritten in plainer words. Nothing about what is kept, sent, or deleted changed; the one addition is that the door cookie’s year-long life is now stated above.

The Why Engine is operated by Devello Studios (Devello Inc.). Privacy questions, deletion requests, and anything else: devellostudios.com/contact. The companion document is the terms of use, and the about page explains what the engine is doing with all of this.