Privacy
There is nothing to collect it with
Most privacy pages are a promise. This one is an architecture: the product has no account, no server and no network code, so the interesting question is not what we would do with your data but where it could possibly go.
What is collected
Nothing. Not anonymised usage, not crash reports, not a count of installs. The app contains no analytics library and makes no outbound requests; the engine makes none either, beyond whatever a source you explicitly connect requires in order to be read.
You do not have to take that from us. Two commands settle it in a way reading source code never could — one asks the operating system what the program has open, the other opens your whole identity in a tool nobody here wrote.
Where your identity lives
One file, in your home directory
~/.karaca/brain.db — a plain SQLite database. It never leaves the machine unless you move it.
Read-only in the app
The viewer opens that file with a read-only handle. It cannot change what it shows you, and that is a property of the file descriptor rather than a policy.
Yours to delete
Delete the file and the identity is gone. There is no copy anywhere else, because there is nowhere else.
Checking it yourself
You do not have to believe any of the above. While the app is running, ask the operating system what it has open — it should be the database and nothing across a network.
The first should print nothing at all — not a filtered list, nothing. The second prints every table in your identity. Neither depends on trusting a word on this page.
This website
The site is static. It sets no cookies, runs no analytics and embeds nothing from a third party — which is also why there is no cookie banner to dismiss. The graph you see is generated at build time from invented data; it is not anybody’s identity.
If the site is hosted somewhere that keeps standard server logs, those logs exist. We do not read them for anything and there is no identifier in them that ties a request to a person using the app, because the app never contacts this site.
If that ever changes
Any future feature that needs a server — syncing an identity between two of your own machines, for instance — would be optional, off by default, and described here before it shipped. The local product would keep working without it. Nothing that reads your work will ever require an account.