Privacy policy
What we keep, and why.
NorseOS is in a closed, free beta. This policy covers the norseos.com website, the request-access form on it, the NorseOS control plane and its web app Valhalla, and the runner and desktop software you install. It is written to be read, not skimmed past. If anything here is unclear, write to us.
1. Who we are
NorseOS is run by [Legal entity], a Norwegian company (org. no. [Org. no.], [Registered address], Norway). [Legal entity] is the controller of the personal data described here. Contact: [Contact email].
2. What we collect
If you join the waitlist
- Your email address and, if you write one, your message (up to 500 characters). The form has no name or company field.
If you are invited and sign in
- Account: email address, an optional display name, your role and the workspace you belong to, and when the account was created or disabled.
- Invitations and sign-in links: the invited email address and expiry times. Links are stored only as a hash, never as the working link.
- Passkeys: a credential id, the passkey's public key, a usage counter and an optional label. Your fingerprint, face or device PIN never leave your device and never reach us.
- Enterprise sign-in (only if your organisation sets it up): the identity your identity provider returns for you.
What you and your agents do in your workspace
- Tasks, runs and conversations: the tasks you give, messages between you and agents, agent replies, tool calls and their arguments, approvals you grant or refuse, rooms and their mandates, boards, schedules, skills and documents you create.
- Memory and agent profiles: facts and notes stored as workspace memory or as part of an agent's profile, so agents can pick up where they left off. These can contain personal data if you or your agents write it there.
- Audit chain: a tamper-evident, signed record of what happened in each run and who did it. It is how you can prove afterwards what an agent did.
- Usage and budgets: token counts, costs where known, and the budget limits you set.
- Feedback you send with the in-app button, with the page and run it was sent from. Secrets are redacted before it is stored.
- Notifications: if you turn on browser notifications, the push address your browser gives us.
Your runner and devices
- Runner name and id, which agent tools and versions it offers, its capacity and state, pairing records, and the tokens that let it connect (stored only as hashes).
Credentials you choose to store with us
- API keys for model providers, and tokens for services you connect (for example GitHub, Render or Linear). They are stored encrypted and used only for your workspace.
- Logins to subscription tools such as Claude Code or Codex stay on your own runner. We do not receive them.
Technical data
- Your IP address, used for a few minutes to rate-limit sign-in and the waitlist form, and in our hosting provider's ordinary request logs.
- The website itself uses no analytics, no tracking pixels, no advertising and no third-party scripts or fonts.
3. Your AI providers and what reaches us
You bring your own AI access, either a subscription you are logged in to on your runner or your own API key. Which of your data passes through NorseOS depends on which:
- Subscription tools on your runner (Claude Code, Codex and similar). The tool runs on your machine and talks to its provider directly. That call does not go through NorseOS, and we do not receive your login. What does reach our control plane: the task text you give through NorseOS; a redacted copy of the conversation (what you said and what the agent answered, plus a short marker for each tool it used, but not its internal reasoning, tool inputs or tool results), so you can read it in Valhalla; and agent status. When you watch or type into a terminal in Valhalla, the screen output and your keystrokes pass through the control plane on their way; keystrokes are not stored, only that an input was delivered and how many bytes it had.
- API keys (Anthropic, OpenAI, xAI, Google, or an OpenAI-compatible endpoint you configure). Here the control plane makes the call for you, with your key. The prompt, conversation, any code the agent selected and tool results are sent to that provider and are stored in your workspace.
- Local models (for example Ollama or LM Studio) reached through your runner. The conversation goes from the control plane to your runner and the answer comes back; both are stored in your workspace. Nothing goes to an outside provider.
Your code and files stay on your runner, except what an agent sends to a provider as part of its work, what appears in the conversation, and what you push to services you connect. Each AI provider handles what it receives under your own agreement with that provider, not under this policy.
4. Why we use it
- To run the service you signed up for: sign-in, your workspace, dispatching work to your runner, showing you what your agents did, enforcing your budgets and approvals. (GDPR legal basis: performance of our agreement with you.)
- To keep it secure and honest: rate limits, abuse prevention, the audit chain, and fixing what breaks. (Legitimate interests: protecting you, other testers and the service.)
- To answer waitlist requests and run the beta: writing to you about access, and reading your feedback to improve NorseOS. (Legitimate interests, and steps you asked for before an agreement.)
- Browser notifications, only if you turn them on. (Consent, which you can withdraw in your browser at any time.)
- Legal obligations, such as bookkeeping or responding to lawful requests.
We do not sell your data, we do not use it for advertising, and we do not use your workspace content to train AI models.
5. Where it is stored
The control plane and its database run on Render in Frankfurt, Germany (EU). If you use NorseOS from the United States or elsewhere outside the EU, your data is transferred to and stored in the EU. Render, Inc. is a US company; where its staff can access the systems, that is covered by Render's data processing terms. Your runner, and everything that stays on it, is on your own machine.
6. Who else receives it
Our service provider: Render (hosting, database, logs). That is the only service provider that processes NorseOS data on our behalf today. The website is also served by Render. We will update this list before adding another.
Services you choose: when you connect or use them, the following receive data from your workspace under their own terms, because you directed it:
- the AI providers you configure (section 3);
- GitHub, Render, Linear and other services you connect, for the actions you or your agents take there;
- your browser's push service (for example Google, Mozilla or Apple) if you turn on notifications; the message itself is encrypted for your browser.
Others: people you invite into your workspace see what their role allows. We may disclose data if the law requires it, or to a successor if the business is sold, under this policy. Nobody else.
7. How long we keep it
- Waitlist: until we have answered you and the beta round you asked about is over, or until you ask us to delete it.
- Account and workspace data, including conversations, memory and the audit chain: for as long as your account is active. When the beta ends, or your account is closed, we delete it within 90 days unless you ask us to keep it for a move to a later version.
- Deletion on request: we delete your account and workspace within 30 days of a verified request. Database backups at our hosting provider expire on their own schedule after that.
- Rate-limit records: minutes. Hosting request logs: as kept by Render.
- We may keep a minimal record longer where the law requires it.
8. Your rights (EU/EEA and UK)
You can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or hand it over in a portable format. Where we rely on consent, you can withdraw it. Write to [Contact email]; we answer within one month. You can also complain to the Norwegian Data Protection Authority (Datatilsynet) or the authority where you live.
9. US and California notice
This applies to US residents, including California residents under the CCPA as amended by the CPRA.
- Categories we collect: identifiers (email, account id, IP address); account and authentication records; internet or network activity within the service (runs, logs, audit records); and whatever personal information you or your agents put into workspace content. Sources and purposes are as described in sections 2 to 4.
- No sale, no sharing. We do not sell personal information and do not share it for cross-context behavioral advertising, and have not done so in the past 12 months.
- Sensitive information: account credentials are used only to sign you in and run the service, never to infer anything about you.
- Your rights: to know what we collect and how we use it, to get a copy, to correct it, and to have it deleted, without being treated differently for asking. You can use an authorized agent. We will verify a request by confirming it from the email address on the account.
- Retention: as in section 7.
To make a request, write to [Contact email].
10. Cookies and browser storage
norseos.com sets no cookies and stores nothing in your browser.
Valhalla (the web app) sets only cookies it needs to work, all first-party and unreadable by scripts:
ravn_session: keeps you signed in, for up to 8 hours.ravn_passkey_challenge: lasts a few minutes while you sign in or register a passkey.ravn_oidc_browser: lasts 10 minutes, only during enterprise sign-in.
Valhalla also keeps a few display preferences in your browser's local storage (theme, language, pinned items, panel layout, which room messages you have seen), and the command bar remembers its last result for the current tab in session storage. These are conveniences, not tracking. There are no analytics, advertising or tracking cookies, so there is nothing to opt out of.
11. Security
Workspaces are isolated from each other in the database, stored credentials are encrypted, sign-in tokens and links are stored only as hashes, all traffic is encrypted in transit, and the audit chain is signed so changes to it can be detected. No system is perfectly secure; if a breach affects your personal data we will tell you and the authorities as the law requires.
12. Children
NorseOS is a professional tool and is not for anyone under 18. We do not knowingly collect data from children. If you believe a child has given us data, write to us and we will delete it.
13. Changes
We will update this page as NorseOS changes, and change the date at the top. If a change materially affects how we use your data, we will tell signed-up testers by email before it takes effect.
14. Contact
[Legal entity], [Registered address], Norway.
Email: [Contact email].