Security & custody
Local-first is an obligation, not a slogan.
If Nolocron is going to hold your memory of record, it takes on what comes with custody: control, provenance, scoped access, and audit. The claims on this page stay tied to what is actually true today — and name plainly what is still a launch step.
Local custody
Where your data lives
- Your archive lives on your own disk, not in a required Nolocron cloud account.
- It is stored in standard, inspectable formats — SQLite databases, content-addressed files, and Markdown or CSV exports — so it stays readable with everyday tools.
- You can back it up, move it, copy it, or delete it like any other set of files.
Provenance
Knowing where everything came from
- Every item traces back to where it came from: which source and import produced it, and what the original record looked like.
- Imported source material is treated as canonical; machine-generated additions such as summaries and embeddings are labeled derived and never conflated with it.
- An append-only event store records what happened — imports, exports, deletes, agent queries — so operations can be reviewed after the fact.
Scoped access
Who can act, on what, within which scope
- Nolocron tracks who is behind every action, not just a single user: each one runs through an execution context that records who is acting, what they may do, and in which scope.
- AI access is scoped by default — an assistant sees a chosen archive or project, not your whole memory — with least-privilege defaults and a default-deny policy engine.
- Answers are designed to cite the items they drew from, and each run is designed to leave a receipt of what context was assembled and used.
- You grant access, and you can tighten or revoke it; external clients connect through an open protocol (MCP) under the same limits.
Preview limits
What is still a launch step, not a guarantee
- This is a private preview, not a public launch. It is shared for product review while Nolocron is still pre-public.
- A public domain, DNS, TLS, access controls, and analytics are launch operations — configured and verified at release, not claimed here in advance.
- There is no public download, account, or signup flow yet. The waitlist is a way to follow progress, not a production capture system.
- Public copy deliberately avoids asserting any security control that has not been configured and verified in production.