Security

Security you can understand.

Here's how SuNodes protects your account, your team's work and the actions taken on your behalf: what each protection does, what it guards against, and where its limits are. No certifications we don't have, and no promises nobody can keep.

Your account

Signing in

Strong password storage

Passwords are hashed with argon2id, a slow hash designed for passwords, and never stored as written.

Protects against: Your password being read from a copy of the database.

Two-step sign-in and passkeys

Add an authenticator app (with one-time recovery codes) or a passkey. Once you raise your account's protection, it never drops back without you.

Protects against: Someone signing in with a stolen or guessed password.

New-browser check

A password-only sign-in from a browser your account hasn't used must also enter a code sent to your email. Trusted browsers are remembered for 90 days.

Protects against: A leaked password being used from a new place.

Limits: Applies to password-only sign-ins; passkeys are already stronger.

Confirm it's you

Sensitive changes, like your security settings, signing out a phone or deleting your account, need a confirmation from the last 15 minutes. With two-step sign-in, a password alone isn't enough.

Protects against: Someone at an unlocked computer changing your security.

Rate limits

Sign-in attempts are limited per address, per account and per network.

Protects against: Password guessing at scale.

Sessions and devices

Staying signed in, and signing out

Server-side sessions

Your browser holds a random session token in a secure, HTTP-only cookie; only a hash of it is stored. Sessions expire: 30 days if you choose to stay signed in, after 12 idle hours otherwise, and never later than 90 days.

Protects against: Stolen session tokens being usable forever.

Sign out everywhere

Sign out one session or every other device from Account → Security. Changing or resetting your password signs out every session and phone.

Protects against: A forgotten or lost device staying signed in.

Phones you can revoke

Each signed-in phone appears in Account → Security. Signing one out ends its tokens and notifications at once. Phone access tokens last 10 minutes, and a reused refresh token signs the phone out.

Protects against: A lost phone, or a copied token.

Origin-checked requests

Every request that changes something must come from SuNodes itself.

Protects against: Another website making your browser act on your account.

Your workspace

Who can see and do what

Roles

Owners and admins manage the workspace; editors build and publish but can't touch billing, domains, AI keys or members; viewers can only look. A guest sees only the projects shared with them.

Protects against: Teammates doing more than their job needs.

Workspace isolation

Every request is checked against the workspace it acts in. Something in another workspace answers as if it doesn't exist.

Protects against: One customer seeing another's data.

Limits: For most data this is enforced by SuNodes's application checks; customer apps add database-level isolation between their own tenants.

Team sign-in strength

Members must sign in at least as securely as the workspace owner requires.

Protects against: A weakly protected member account becoming the way in.

Mailbox access is the owner's

Being a workspace admin gives no access to someone's mailbox. Owners share it with exactly the capabilities they choose, and only they can disconnect it.

Protects against: Admins or AI agents reading mail they weren't given.

AI and connected services

What AI sees, and what it can't be talked into

This section is about protecting data when AI does work for you. What an AI is allowed to do, and when it must ask you first, is AI governance: it has its own page.

Anonymized mail for agents

Before an AI model sees mail an agent was given, names and contact details are replaced with placeholders; card, ID and bank numbers, keys and codes are never revealed.

Protects against: Personal data in your mail reaching an AI provider.

Limits: This applies to mail given to agents. Content you give the website builder (your business details, site text, images) is sent to the AI provider as it is.

Untrusted content stays data

Text from emails, websites, form messages and connected services is passed to AI models marked as data, not instructions.

Protects against: Instructions hidden in content (prompt injection).

Limits: Labeling reduces the risk; the real safeguard is that permissions and approvals don't change whatever an AI is told.

Connected-service credentials

Credentials for services you connect are stored encrypted, used only by SuNodes's servers, and never shown again; you choose which actions are turned on.

Protects against: Keys leaking through the browser or to an AI.

Your data

Protecting what's stored and sent

Encrypted in transit

SuNodes, and every site it hosts, is served over HTTPS with certificates issued and renewed automatically, HTTP redirected to HTTPS, and HSTS.

Protects against: Traffic being read or changed on the way.

Secrets encrypted individually

Stored secrets such as your AI provider keys and authenticator secrets and connected mailbox passwords are encrypted with AES-256-GCM, each with its own data key, wrapped by a master key kept outside the database.

Protects against: Secrets being readable from a copy of the database.

Keys checked, then hidden

An AI key is verified with its provider before it's saved, and it's never shown again.

Protects against: Keys being exposed in the dashboard.

Privacy-friendly analytics

Site analytics don't use cookies or store visitors' IP addresses. Unique visitors are counted with an anonymous ID that changes every day, and visitors whose browser sends Do Not Track aren't counted.

Protects against: Tracking your site's visitors more than needed.

Limits: IP addresses are recorded elsewhere where security needs them, for example in sign-in records.

Encrypted backups

Backups of the database and site files are encrypted before they're written; the backup job refuses to write an unencrypted one.

Protects against: Data loss, without creating readable copies.

Accountability

A record of what happened

Activity log

Sign-ins, security changes, publishing, domain and DNS changes, team changes and AI key changes are recorded. Records are kept for a year; actions by SuNodes staff on customer accounts are kept for two and must state a reason.

Protects against: Changes nobody can account for.

Staff access is limited and logged

SuNodes's admin area needs an admin role and a passkey confirmation; viewing a customer's account is read-only and recorded from start to finish.

Protects against: Unaccountable access by staff.

Abuse handling

Anyone can report a site; suspected phishing is flagged for review, and takedowns are recorded with a reason.

Protects against: SuNodes-hosted sites being used against people.

Honest limits

What we don't claim

  • Email and files aren't end-to-end encrypted: SuNodes's servers process them to provide the service.
  • No system is perfectly secure. We describe what's in place, not a guarantee.

Found a security problem? Email support@sunodes.com. To report abuse on a site hosted by SuNodes, use the abuse form.

Protect your account.

Sign in and turn on two-step sign-in or a passkey in Account → Security.