How OTPilot protects your data — in plain language.
We store
We never see
Every item in your vault is encrypted on your device with AES-256-GCM, each with its own key, before it leaves it. Those keys are protected by your vault key (your recovery key) — generated locally, it never leaves your devices, and on each device it is itself locked by your master password. The server only ever holds ciphertext it cannot read. If our database were stolen, your data would be unreadable.
A collection's items are encrypted with a collection key that only its members hold: each member receives it wrapped to their own device key, and the server stores only those wrapped copies, the encrypted items and the encrypted name. Removing someone stops their access to future changes; anything they could already see may have been copied, so OTPilot suggests changing those passwords.
When you share just a 2FA code (not a collection) with a teammate, the secret is encrypted with a key split in two halves: one is wrapped to your teammate's device key, the other stays on our server. Neither half can decrypt the secret alone, so a leak of our database doesn't reveal it. To make each code, your teammate's app sends its half and the server rebuilds the secret briefly, generates the 6-digit code and discards it: teammates get the code, never the secret. Because the server sees the secret while it makes a code, shared codes are not end-to-end encrypted against a live server. Stop sharing at any time; remove a teammate and their access ends at once.
No passwords to leak — we use magic links and Google sign-in via Supabase. Payments are handled by Stripe; we never receive card data, only a customer ID to identify your plan. All traffic is HTTPS/TLS. Among others, the extension talks to api.otpilot.app, to Supabase Auth to sign you in, to Gmail's feed with your browser's own Gmail session (to fill codes sent by email), to the icon storage bucket, and to images on the page you're on (to read a QR code).
See also our Privacy Policy.