Your data
What is stored where
Section titled “What is stored where”| Data | Where |
|---|---|
| Notes in a cloud notebook | With Kyra, synced to your signed-in devices |
| Notes in a local notebook | Only in the browser that made it |
| Memories and transcripts | With Kyra, in your account |
| Attachments | With Kyra, against your plan’s storage |
| Calendar, reminders, contacts | On your device. Read and written in the moment, not uploaded and kept |
| Your code | On your machine. See below |
| Billing details | With Stripe, our payment processor |
Personal and organisation are separate
Section titled “Personal and organisation are separate”Work you do in your personal workspace and work you do in an organisation are separate: separate notebooks, separate memory, separate transcripts, separate credits. Nothing crosses.
Check which workspace is active before asking Kyra to search or save. “My notes have vanished” is nearly always the wrong workspace.
What leaves your machine when you use computer control
Section titled “What leaves your machine when you use computer control”If you have connected a computer, this is the part worth being precise about.
Stays on your machine: your code, your diffs, what coding agents say to each other, file contents, and command output.
Reaches Kyra: a coarse view of each session — working, blocked on a question, or finished — plus whatever the session explicitly reports as a question or a result, and whatever you ask Kyra to read or do.
Coding agents run on your accounts and subscriptions. Kyra orchestrates and summarises; it is not a proxy for them.
Whatever a coding agent produces is treated as untrusted data. Kyra summarises it; it never follows it as instructions. That matters because text a model wrote — or text a web page or a document contains — must not be able to steer your assistant.
Taking your notes with you
Section titled “Taking your notes with you”This is the whole reason notebooks are Git repositories.
- Clone it. Git access →
- Notes are Markdown. Open them in VS Code, Obsidian, or anything else.
- History comes too. A clone carries every commit.
There is no export button because there does not need to be one — the export format is the storage format.
Encryption
Section titled “Encryption”Content is encrypted at rest, with keys managed by a cloud key service rather than stored beside the data. Traffic between your devices and Kyra is encrypted in transit.
What not to put in Kyra
Section titled “What not to put in Kyra”The reasons are ordinary rather than dramatic: notes get shared, published, cloned to laptops, and read aloud; transcripts persist; and search surfaces things at moments you did not plan for. Secrets belong somewhere designed to hold them.
Deleting your account
Section titled “Deleting your account”Request deletion from Portal → Settings → Account.
- Immediately — your account is suspended. Sessions stop, connected machines lose access, sharing and publishing stop working. Nothing is being processed on your behalf any more.
- After a grace period of about a week — everything personal is destroyed: notes, notebooks, memories, transcripts, attachments, profile, and connections.
The grace window is deliberate, so a deletion made in anger or by accident can be undone. After it, it cannot.
Deleting less than everything
Section titled “Deleting less than everything”You do not have to delete the account to delete data.
| To remove | Where |
|---|---|
| One memory | “Forget that”, or Settings → Memory |
| One transcript | Transcripts |
| A note | Delete it in the notebook — the history keeps the record of it existing |
| An entire notebook | Notebook Settings → Danger. Permanent, including history |
| An attachment | Settings → Attachments |
| A machine’s access | Settings → Coding agents |
| A share link | Members & Sharing |
Terms, privacy policy, and the data processing agreement are at kyra-hi.com/legal. Kyra is for adults — you must be 18 or over to have an account.