We typically respond within 1–2 business days. All inquiries go to a single inbox: [email protected].
iOS and macOS are available now on the App Store and Mac App Store. Android and Windows builds are in active development and will land on Google Play and Microsoft Store shortly. Check back, or follow updates from inside the app.
No — we cannot reset it. Your master password is never transmitted to us; it exists only on your device and in your memory. Without it, the encrypted vault cannot be decrypted by anyone, including us.
You do, however, have two ways to regain access if you set them up in advance. First, if you exported a Recovery Kit (Settings → Security → Export Recovery Kit), that file contains a code beginning with RKRK- that restores your vault without the master password — store it somewhere safe, because anyone holding it can unlock your vault. Second, if you enabled biometric unlock, you may still reach the vault via Face ID or Touch ID, provided the biometric binding is intact. If you have neither, the vault cannot be recovered.
Go to Settings → Sync and configure your preferred cloud storage provider. RabbitKey supports iCloud Drive, Google Drive, and WebDAV. Your vault is encrypted before it leaves the device — your cloud provider only ever sees the encrypted file.
RabbitKey detects conflicts non-destructively and surfaces them in the UI. Go to Settings → Sync → Conflicts to review and resolve them manually. No data is deleted automatically during conflict resolution.
Enable sync to keep an encrypted copy in your cloud storage. You can also export from the app directly, but the two export formats differ in protection: an encrypted vault backup (.qpbk) stays encrypted and needs your master password to restore, while a CSV export is written as plain, unencrypted text so it can be imported elsewhere. Treat a CSV export as sensitive — anyone who opens the file can read every entry — and delete it securely once you are done. For long-term backups, prefer the encrypted .qpbk backup or sync.
Yes. All vault operations are fully local. An internet connection is only needed when you initiate a sync to your configured cloud endpoint.
Go to your device's Settings → Passwords → AutoFill Passwords and enable RabbitKey. The app will then appear as an autofill source in Safari and other apps.
Pro users can transfer the vault directly device-to-device with an in-app QR code. Alternatively, enable sync on both devices using the same cloud provider, or restore from an encrypted backup file.
Uninstalling the app removes the local database and clears the keychain entry. If you configured sync, delete the vault file from your cloud storage separately. We hold no data on our servers, so there is nothing to request from us.
No. RabbitKey is closed source. The app is distributed only as a compiled binary through the official platform stores.
Open RabbitKey and go to Settings → Upgrade to Pro. Pro is a one-time in-app purchase through the Apple App Store — no subscription required.
Go to Settings → Restore Purchases. Your purchase is linked to your Apple ID and can be restored on any device signed in with the same account.
Refunds are managed by Apple. Visit reportaproblem.apple.com or contact Apple Support to request a refund. We do not process payments directly and cannot issue refunds.
Free includes full encryption, biometric unlock, and up to 100 entries. Pro adds unlimited entries, cloud sync, password health reports, multiple vaults, tags, device transfer, and CSV import.
Yes. Pro is a one-time purchase that includes all future updates to Pro features at no additional cost.
Include your device model, OS version, and app version to help us respond faster. The same address handles general questions, privacy concerns, billing issues, legal requests, press inquiries, and security disclosures.
For coordinated disclosure of security vulnerabilities, email [email protected] with full reproduction details. We will acknowledge receipt within 48 hours and work with you on a fix before any public disclosure. Our security policy is also published at /.well-known/security.txt.