Privacy Policy

Secure sync for every browser you use.

Relay keeps bookmarks current by storing an end-to-end encrypted vault, not a behavioral profile. Useful by design, quiet by default.

Last updated: April 29, 2026

The short version

Name or emailNot required
Analytics SDKNo
Bookmark contentsEncrypted
Password resetNo
Data collection

What we collect

Relay stores the minimum data needed to operate secure bookmark sync:

DataWhat it isReadable by Relay?
End-to-end encrypted vault Your bookmarks, encrypted on your device before upload. No
Vault lookup key A derived identifier used to find your vault without storing your username in plain text. Operational only
Browser UUID A random install identifier used for browser limits and service protection. Yes, random
Optional passkey records A credential public key, credential metadata, browser UUID, and one server-side share of an encrypted local unlock wrapper. Verification only
Short-lived sync metadata Minimal technical metadata used for rate limits and reliability. Limited
Data minimization

What we do not collect

Relay does not collect, store, or transmit your name, email address, plaintext password, biometric data, device PIN, browsing history, location data, ad-tracking events, tracking identifiers, or readable bookmark contents.

Vault protection

How encryption works

Your bookmarks are encrypted on your device before they leave the browser.

  1. Your password derives the local encryption key.
  2. Relay encrypts bookmark data before upload.
  3. The server stores only the encrypted result and required operational metadata.
  4. Relay does not store your decryption key or a readable copy of your bookmarks.
In practice: database access alone is not enough to read bookmark contents. Unlocking requires the password or a verified passkey together with the approved browser's local key share.
Service providers

Third-party services

Supabase

Stores encrypted vault data and operational metadata for sync.

Stripe

Handles Relay Pro payments. Relay does not receive card details.

Browser store and hosting

May process standard request metadata when you install Relay, visit Relay web pages, or download a manual release.

No tracking stack

Relay does not include advertising networks, tracking pixels, analytics SDKs, or remote scripts. Sync requests contribute only aggregate service-health counts, while the extension's activity timeline stays local.

Retention and control

Data retention

Your encrypted vault is retained until you delete your account. Bookmark profiles and Context Capsules live inside that encrypted vault. Pro Time Machine keeps full encrypted vault snapshots for a limited restore window, then they expire. Account deletion removes the server-side vault and related sync records. Payment records are handled by Stripe according to Stripe's retention requirements.

Your rights

You can delete your account at any time from Relay settings. Because Relay does not require email or name collection, support requests may require you to provide non-sensitive context such as your Relay version and visible error message.

Review and contact

Security review

Relay limits source access to reduce cloning and repackaging risk. The trust boundary is documented at relayextension.com/trust, the security model is documented at relayextension.com/security, and approved independent reviewers may receive source access under written terms.

Changes to this policy

If this policy changes materially, we will update the date on this page.

Contact

Questions or concerns? Visit relayextension.com/support.