Your vault lives on your machine.
That is not a policy setting, it is the architecture.
Only a hash, a public key and a name you opted in ever leave the machine. Content leaves only when you mark it public and sign it.
Every atom, node and sealed record you keep. Stored in open formats in a folder you can see, back up, and move.
Questions you put to ARK, the councils it sits, and the answers it proposes. With a local model, nothing is sent anywhere to be answered. If you connect an online model with your own key, your question and the notes ARK reads to answer it go to that provider, and nothing else.
Fingerprints are computed on your machine as the record is made. Publishing a seal shares a fingerprint, never the contents.
If you buy a paid build, we hold the key and the invoice. That is the commercial record and nothing more.
Letters you send to the three desks, kept until the thread is closed or you ask us to delete it.
One email address, used once, to tell you the build is ready. Never sold, never mailed for anything else.
A tool that keeps a copy of your thinking is not your tool.
No analytics, no advertising pixels, no session recording, no cookie banner because there are no tracking cookies to consent to. On ship, the two typefaces are served from our own machine rather than a font network, so reading this page tells nobody anything.
Tell us to show you every line we hold about you, to correct it, or to delete the lot. There is little to show, which is the point. UK GDPR applies and we answer as the data controller, Third ARK Limited.