Accounts and data
Accounts (coming)
A free OpenIntern account is planned for the store add-in, so your key and settings follow you to every device. It will be optional: you will still be able to use OpenIntern without one.
Accounts are not available yet. Nothing on this page works today. The store add-in has no sign-in, and the local software will never need one. This page describes the plan, which can still change before release.
What an account will add
| No account (today) | Free account (planned) | |
|---|---|---|
| Getting started | Paste a key and go | The same, plus signing in |
| Who pays for the AI | You, on your own key | You, on your own key |
| Where your key lives | This device's add-in storage | Saved to your account, encrypted, unless you choose this device only |
| Settings and instructions | This device | Synced to every device you sign in on |
| Conversations | This device | Saved to your account, unless you opt out |
| If Office clears the add-in's storage | Key and history are gone | Sign in again and they come back |
The free account will cost nothing and have no credits, quota or card. You will still bring your own provider key and your provider will still bill you. A paid plan that runs on OpenIntern's own provider keys may come later; it is not designed yet.
Signing in
Planned sign-in methods are Microsoft, Google, GitHub and a one-time code sent to your email address. Signing in is your choice: after your first task the pane will offer it once, and you can say "Not now".
A sign-in lasts until it has gone 30 days unused, or for at most 90 days. The Account panel will list where you are signed in and let you sign out one session or all of them.
Saved keys
- Encrypted. A saved key is encrypted in our service with AES-256-GCM, using an encryption key held only as a secret of the service. Our database holds the encrypted key, the provider and the last four characters, never the key itself.
- Never sent back. No part of the service returns a saved key. The pane shows the provider and the last four characters, with Replace and Remove.
- Used per request. On each request from a signed-in pane, our service decrypts your key and passes it with that request to the agent, which holds it only while the request or task runs, as it does today. A key you keep on this device only takes precedence over a saved one.
- Protected changes. Adding or replacing a saved key, and deleting your account, will need a recent sign-in, so someone who got hold of a session alone could not do either.
- Never logged. Account requests are not logged with their headers or contents.
What is saved, and opting out
When you sign in, the pane will show what it will save: your key, your settings and instructions, and your conversations, each with its own checkbox, ticked by default. Untick one to keep it on this device only. You can change this at any time under Account, and turning a category off deletes what was saved for it straight away.
- Settings: model choice, preferences and saved instructions.
- Conversations: the text of your messages and OpenIntern's replies for each document, kept for 30 days from last use. Replies can quote figures from your documents, which is why conversations have their own checkbox.
- Never saved on our servers: your document contents, sheet snapshots, attachments, checkpoints and records of changes. These stay in your session and are deleted when it ends, as they are today.
Downloading and deleting your data
- Download everything saved to your account as a JSON file, with keys shown only by their last four characters.
- Delete your account and every saved row is deleted at once. Our database provider's point-in-time recovery keeps a backup copy for up to 30 days, after which it is gone.
- You can always remove a saved key and revoke it in your provider's console.
Before accounts launch
The Privacy Policy and Terms will be updated to cover accounts, the data they save and how long it is kept, before sign-in is turned on. The account service is part of the open-source code, so anyone can check how keys are stored, and anyone running the service themselves can leave accounts off.