Privacy Policy

• No ads, no tracking, no selling. No advertising or analytics trackers, and we never sell, rent or share personal data for marketing.
• Secret values stay encrypted. They are encrypted before they are stored, never shown in the dashboard, and never given to AI tools. Not even we read them.
• Few providers, all named below. Each one only gets what it needs to do its part.
• You can leave. Delete a workspace yourself at any time, or ask us to delete your account and everything in it.

Nionx Cloud is run by Benjamin Juhasz, based in Sweden, who is the data controller for the personal data described here. Contact: privacy@nionx.cloud. For a workspace, the person or organization that owns it decides what goes into it; for that content we act on their behalf.

Account details: your name, email address and whether it is verified. Your password is stored only as a one-way hash, never in a form anyone can read.

Google or GitHub sign-in: if you sign in with or connect one of them, we receive your name, email address, profile picture and the account's ID at that provider. We ask only for that: the basic profile on Google, and read:user and user:email on GitHub, nothing about your repositories, files or mail. Any access token the provider gives us is stored encrypted and used for nothing else.

Security data: active sessions with their IP address, browser and sign-in time (so you can see and end them); your two-factor secret and backup codes, stored encrypted; the time you last confirmed your identity for sensitive actions; and short-lived rate-limit counters that protect sign-in and the API from abuse.

What you put in a workspace: workspace, project and environment names, secret names and descriptions, encrypted secret values and their version history, members, roles and invitations, and API tokens with their name, expiry, last use and IP allowlist. We store only a fingerprint (hash) of each token, never the token itself.

Connected AI tools: when you connect a tool such as Claude Code or the Nionx command-line tool, we store the name and return address the tool gave itself, the workspace and permissions you approved, when you connected it and when it was last used, and its sign-in tokens. When a tool asks you for a secret value, we store a fingerprint of the one-time link, which secret it was for and when it was used.

Audit log: who changed what and when, including reads made with API tokens and changes made by connected tools. It records names and version numbers, never secret values.

Usage counts: how many API calls each workspace makes per month, to apply plan limits.

Waitlist: your email address and when you agreed to be contacted.

Email you send us: messages to any @nionx.cloud address, with your email address and anything you include, and what you send with Send feedback in the dashboard (with the page you sent it from).

Technical logs: for each request, the time, path, response status, duration and a request ID, to keep the service running and investigate problems. Request and response bodies, secret values and tokens are never logged.

• No analytics, advertising or social-media trackers, and no fingerprinting.
• No reading of secret values: not by us, not by AI tools, not for training anything.
• No payment details. The beta is free; if paid plans arrive, a payment provider will handle cards and be named here first.
• The status page stores no personal data. Its "From your location" measurement runs in your browser and is never sent to us.

Each value is encrypted with AES-256-GCM under its own data key, and that key is encrypted again with a key-encryption key kept apart from the database. The dashboard never shows stored values, to you or anyone else.

Values leave Nionx only in answer to a request made with an API token you created for that environment, from an allowed IP address if you set an allowlist, and every such read is recorded in the audit log. Connected AI tools can see secret names and whether each has a value, never the values themselves; when a value is needed, you type it into Nionx yourself.

We don't look at, analyse or use secret values for anything other than giving them to your API tokens.

• To run the service: sign you in, store your workspaces, answer API requests and let the tools you connect do what you allowed.
• To keep it secure: verify your email, require two-factor and identity confirmation for sensitive actions, limit attempts, enforce IP allowlists and keep the audit log.
• To apply plan limits.
• To email you about your account: verification, password resets, invitations and security notices.
• To email you about the beta if you joined the waitlist, and only for that.
• To answer and act on email, feedback and security reports you send.
• We don't make automated decisions about you that have legal or similarly significant effects.

• Contract: running your account, workspaces, API tokens and connected tools.
• Legitimate interests: security, preventing fraud and abuse, technical logs, the audit log and answering your messages. We have weighed these against your rights; you can object (see below).
• Consent: waitlist emails. You can withdraw it at any time.
• Legal obligation: when the law requires us to keep or disclose something.

We use only what the service needs to work and what remembers your own settings. There are no advertising or analytics cookies.

• Sign-in cookies (names start with nionx.): keep you signed in, complete two-factor sign-in, protect sign-in with Google or GitHub against forgery, and remember a trusted device if you choose to.
• Preference cookies: your time zone, the last workspace you opened, beta features you switched on and how projects are shown.
• Local storage: light or dark mode (on the website, dashboard and status page), and your recent and pinned pages in the sidebar. They stay in your browser.

We share personal data only with providers that run parts of the service for us, under agreements that require them to protect it:

• Cloudflare (United States, with servers worldwide): hosting, databases, network, request logs, the anti-bot check (Turnstile) on the waitlist form, and Email Routing, which receives email sent to @nionx.cloud addresses.
• Resend (United States): sends account emails such as verification, password reset and invitations, and email we send from @nionx.cloud addresses.
• Google (United States): the mailbox that email sent to @nionx.cloud addresses is forwarded to; and sign-in, if you choose to sign in with Google.
• GitHub (United States): sign-in, only if you choose to sign in with GitHub.

We'll update this list before adding a provider that handles personal data. We may disclose data when the law requires it, and we'll tell you unless we're not allowed to. If Nionx is ever sold or merged, personal data would move only under this policy, and we'd tell you first.

Our main database is in Europe. Our providers run global networks, so data may also be processed in other countries, including the United States. Where the law requires it, these transfers rely on the EU-US Data Privacy Framework or the European Commission's Standard Contractual Clauses.

• Account data: while your account exists. When we delete your account at your request, your personal data goes with it, along with workspaces only you belong to.
• Workspace data: while the workspace exists. Deleting a workspace permanently deletes its projects, secrets, every version, tokens, invitations and audit log straight away.
• Audit log: kept while the workspace exists; your plan sets how far back you can view it.
• Sessions: end after 7 days without use, or when you sign out or end them on the Active sessions page.
• Connected tools: until you disconnect them under Account → Connections; their sign-in tokens expire by themselves.
• One-time value links: they stop working after 15 minutes or one use.
• Rate-limit counters: minutes to hours. Technical logs: a few days.
• Waitlist entries: until the beta ends or you ask us to remove yours.
• Email and feedback: until dealt with, then deleted when no longer needed. Ask us any time to delete yours.
• Backups: our database provider keeps point-in-time copies for up to 30 days, so deleted data disappears from them within that time.

You can see and change your name, password, two-factor settings, sign-in methods, sessions and connected tools in your profile, and delete workspaces you own. You can also ask us to:

• give you a copy of your personal data, in a common machine-readable format,
• correct it,
• delete your account and everything in it,
• restrict certain uses, or object to uses based on legitimate interests,
• remove you from the waitlist.

Email privacy@nionx.cloud from the address on your account, so we can confirm it's you. We reply within 30 days, free of charge. You can also complain to a data protection authority: in Sweden, that's Integritetsskyddsmyndigheten (IMY), or the authority where you live.

Besides encrypting secret values, we use HTTPS everywhere, a strict Content Security Policy, two-factor authentication, identity confirmation for sensitive actions, read-only, expiring and optionally IP-restricted API tokens, approval screens for connected tools, and an audit log. Our status and incidents are public at status.nionx.cloud.

No system is perfectly secure. If a breach affects your personal data, we'll tell the authorities within 72 hours where the law requires it, and tell you without undue delay. To report a vulnerability, email security@nionx.cloud.

Nionx Cloud is for developers and isn't meant for anyone under 16. We don't knowingly collect data from children; if you think we have, tell us and we'll delete it.

We don't sell or share personal information for targeted advertising, and we don't use sensitive personal information to infer anything about you. You have the same rights to access and delete described above.

When we change this policy, we update the date at the top. For important changes, we email account holders before they take effect.

Privacy questions and requests: privacy@nionx.cloud. Security reports: security@nionx.cloud.