Skip to content

Security & encryption ​

Aurora combines local-first storage, AuroraCloud account security, role-based workspace access, and optional per-workspace end-to-end encryption.

End-To-End Encryption ​

E2EE is set per workspace. You can turn it on when you create the workspace — the create dialog has an encryption checkbox — or later from Settings → Workspace → Encryption. When enabled, supported workspace content is encrypted on the device before it is synced. AuroraCloud stores encrypted payloads and encrypted key material, not readable workspace content.

Choosing it at creation is the cheaper moment: turning it on later has to re-encrypt what is already there, and anything written before then existed unencrypted. The box is off by default and stays a deliberate choice, because losing your recovery phrase loses the data with it.

Ticking it creates the workspace first and then opens the same setup flow the settings page opens, so the recovery phrase is keyed to a workspace that exists. If creation fails, no setup runs, and the choice does not carry over to the next workspace you create.

Unlock is independent of your login password. Changing, resetting, or replacing your password — including switching to OAuth sign-in — never affects encrypted content. Your account key (which wraps every workspace key) is protected by one or more recovery methods, managed from Settings → Workspace → Encryption.

Recovery & unlock methods ​

You can hold several recovery methods at once:

  • Device — every device you trust stores its own copy of the account key, wrapped by a non-extractable key held only by that device. Once trusted, that device unlocks silently. Device slots are created automatically the first time you unlock on a device. You can revoke one under Settings → Account → Security → Trusted unlock devices when a device is lost or sold.
  • Recovery phrase — a 12-word phrase generated when you enable E2EE. It is the guaranteed fallback for your first device or when every trusted device is gone. Aurora keeps no copy.
  • Key file — an optional offline method: Aurora generates a random 256-bit key, offers it as a one-time download, and you store the file somewhere safe. The material is generated on your device and is never sent to the server. Treat it like a password.

WARNING

Keep at least two recovery methods in separate places — for example a written recovery phrase and a key file on an encrypted drive. If you lose every method (all trusted devices, the recovery phrase, and every key file), your encrypted content is permanently unrecoverable by design — Aurora has no copy of these secrets and cannot decrypt for you.

Adding a new device ​

On a new or untrusted device you can:

  1. Approve from a trusted device — the new device shows a QR code and a short pairing code; an already-trusted device scans or enters it, and the account key is handed over through an end-to-end-encrypted exchange. The new device then unlocks silently, with no recovery-phrase entry.
  2. Enter your recovery phrase — the always-available fallback. It also provisions a device slot so future unlocks on that device are silent.
  3. Use a key file — unlock with a stored key file directly from the lock screen.

Managing recovery methods ​

The Recovery methods list in Settings → Workspace → Encryption (visible only when E2EE is enabled and your account is unlocked) lets you:

  • Rotate the recovery phrase — generate a new phrase; the old one is invalidated only after the new one is verified, so you never lose access mid-rotation.
  • Add a backup phrase or key file — extra recovery methods alongside the phrase.
  • Remove a recovery method — you cannot remove your last recovery-capable method (phrase or key file); add another one first.

Trusted devices are listed and revoked separately, under Settings → Account → Security → Trusted unlock devices. That page is also where you approve a new device with its pairing code.

What the server can and cannot do ​

AuroraCloud stores only encrypted key blobs and the non-secret parameters needed to use them. It never stores your recovery-phrase words, your key-file material, or your device key. Someone with full access to the AuroraCloud database can see that you have recovery methods and when they were last used, but cannot read your content or unlock your account. The How your encryption works panel in Settings → Workspace → Encryption sums this up.

Key rotation (for example after removing a member, below) is a client-side re-wrap: the server receives a new encrypted blob and discards the old one without ever seeing the plaintext key.

Forward-looking encryption (advanced)

Aurora can wrap keys with a hybrid post-quantum scheme (X25519 + ML-KEM) for protection against future "harvest-now, decrypt-later" attacks. It is off by default while mobile support lands; existing workspaces keep working unchanged.

Locked Workspaces ​

When an encrypted workspace is locked:

  • page content and protected metadata stay unavailable
  • readable Markdown/HTML export is blocked
  • AuroraAI, server retrieval, and MCP cannot read locked content
  • local folder watchers are restricted so encrypted files are not auto-imported or overwritten in the background

Unlocking happens on the device. The unlocked plaintext is available to the app session so you can read, edit, export, or intentionally send selected context to a BYOK provider.

Backups And Exports ​

AuroraBak backups (.aurorabak and .aurorabak-bundle) keep encrypted page content as encrypted data, but images and attachments in them are saved unencrypted. A password-protected backup (.enc) encrypts the whole file. See Version history & backups.

Readable exports such as Markdown or HTML are different. Aurora can create them only after the encrypted workspace is unlocked, and it warns because the downloaded files are plaintext outside Aurora's encryption boundary.

Multi-Member E2EE ​

Encrypted shared workspaces use per-member wrapped workspace keys so collaborators can be granted access without storing plaintext content on the server. Members still need valid workspace membership and an unlock path on their device.

Removed members

Removing a member triggers workspace key rotation: a new key generation is created and re-wrapped only for the remaining members, all new content uses it immediately, and existing content is re-encrypted in the background. A removed member who saved the old key can at most read content that already existed while they were a member.

Authentication ​

Signing in ​

You can sign up and sign in with your email address and a password. Signup is open.

Aurora also supports Continue with Apple, GitHub, Google, and Microsoft. A button appears only for the providers that are available in the app you are using, so you may see fewer of them, especially in the desktop app. If an Aurora account already uses the same email address, Aurora asks for that account's password, or emails you a link, before it connects the provider.

How you sign in has no effect on encrypted workspaces: unlocking them always uses the recovery methods above, never your password or provider.

Account protection ​

AuroraCloud account security includes:

  • salted, slow password hashing
  • short-lived sign-in tokens that are refreshed in the background, with detection of reused refresh tokens
  • server-side session revocation
  • optional multi-factor sign-in with an authenticator app (TOTP) or email codes
  • required multi-factor sign-in for administrator accounts
  • recent security activity history
  • alert emails for sign-ins from a new device or an unusual network area

Manage all of this in Settings → Account → Security.

Trusted devices ​

When you enter a sign-in code, you can tick Trust this device so that device skips the code for a while (30 days by default). High-risk account changes still ask you to verify. Settings → Account → Security → Trusted devices lists your trusted devices; click Remove trust to make one ask for a code again. Changing your password, or changing or turning off your sign-in code method, removes trust from all your devices.

These sign-in trusted devices are separate from Trusted unlock devices, which hold the keys for encrypted workspaces.

Workspace Access ​

Workspace roles are enforced by AuroraCloud:

RoleReadEditManage membersDelete workspace
Owneryesyesyesyes
Editoryesyesnono
Vieweryesnonono

Direct page shares, guest links, and published pages have their own access rules. Password-protected links require the visitor to enter the link password before content is shown.

Desktop Secret Storage ​

Desktop provider keys and similar device-only secrets are session-only unless you explicitly enable secure storage. When secure storage is enabled, Aurora stores them in the OS keychain: Keychain Access on macOS, Credential Manager on Windows, or Secret Service/libsecret on Linux.

Aurora does not silently downgrade desktop secrets into plaintext files if the keychain is unavailable.

Data Residency ​

AuroraCloud runs on servers in Norway (EEA). Uploaded files and encrypted offsite backups are stored in Finland (EU). Files use private storage and are delivered through AuroraCloud-controlled access paths. The Privacy Policy lists every processor and location.

Reporting A Vulnerability ​

Email contact@aurora.ink with the details. Please avoid public disclosure until there has been time to respond.

Aurora is in public beta and free while beta.