Help

Sync encryption

How Fovea protects synced passwords and other sensitive data.

Fovea sync uses Chromium’s Nigori keystore model to protect your most sensitive data types.

Opaque payloads

Saved passwords and encrypted autofill data are stored as opaque, encrypted bytes. The Fovea service stores and relays these payloads without decrypting, logging, or inspecting their plaintext.

How keys are handled

Encryption key material is coordinated through the Nigori keystore and delivered to your signed-in browsers when they need it, so a newly signed-in device can read your existing encrypted entries.

Fovea sync does not currently use a separate, user-set sync passphrase. Your account credentials are the gate to your synced data.

Good practices

• Use a strong, unique password for your Fovea Account.
• Sign out of devices you no longer use from the Account page.

Common questions

• Can Fovea read my passwords? No — saved passwords are stored as ciphertext the service never decrypts.
• Is there a separate sync passphrase? Not currently; your account credentials are the gate to your data.
• What happens on a new device? Once signed in, it receives the key material it needs to read your existing encrypted entries.