Your data
You control what leaves. You control what lasts.
Your AI history can contain some of your most personal and valuable work. You should be able to understand where it is stored, what is shared and who decides what becomes part of the record. Continuums Server keeps that record on your own computer; reaching it from an AI is a separate, deliberate decision.
Control of your data
Where your history is stored, which material is examined, what is shared with an AI or service, and how you take your work out again.
- Your Continuums live on Continuums Server, running on your own computer
- No hosted Continuums account, and no cloud tier standing in for your machine
- No silent sharing
- No training by Continuums on your work content
- No content telemetry
- Export, backup and deletion without a paid upgrade
Control of the record
What counts as your decision, what remains an AI proposal, where each item came from and what is still open.
- Source and status visible on every item
- AI proposals kept separate from accepted state
- Accepting records your position, not a verified truth
- Permission to retrieve context is not permission to accept a decision or activate a rule
- Rejected and superseded material stays in history, not in the current record
Four separate data flows.
They are different decisions with different boundaries. Before you join a beta workflow, we’ll explain which controls exist for each one and which are still design direction. Local storage is not a promise that no information ever leaves the computer.
- Website registration
Sends your contact and optional signup details to our registration service. It never asks for AI history, account credentials or access to a server.
- Your server’s local storage
The durable record lives on your own computer. Discovery may inspect a substantial amount of the material you select, and what it finds stays on the server unless you authorise something else.
- AI access to authorised context
A separate decision from where the work is stored. If you connect a cloud AI, the context you authorise for it can be processed by its provider. Local storage does not by itself mean local-only processing.
- The connection between them
The route your server and an AI use to reach each other. Any relay or other intermediary is described according to the actual route, and the context can include real source excerpts. Review the context before sharing.
We choose words to match the evidence.
- Prepared
- A briefing is ready for you to review. Nothing has left yet.
- Copied
- You copied the text. This does not show that a provider received or processed it.
- Delivery confirmed
- Used only when a supported route has acknowledged receipt.
- Accepted as your decision
- You approved a proposal. It records your position, not that the claim is verified true.
- Deleted
- Removes what we hold. Derived records, backups and copies already sent to another provider are explained separately.
The details, per release.
- How the local server works
- Storage and processing details
- Supported sharing routes
- Our no-training policy
- Export and deletion behaviour
- Contact us about your data
- These describe the implemented release you are offered. Statements here that are design direction are marked as such. Running a server on your own computer is not by itself a tested backup or disaster-recovery solution, and we do not offer a hosted one in its place.