Keepwick

Privacy Policy

Keepwick · Developer and operator: Sudarev Daniil · Last updated: October 28, 2026

Keepwick keeps your passwords and keys and makes encrypted backups of your files. Encryption happens on your device; the developer runs no servers that your files, passwords or keys pass through, and there are no accounts.

1. Passwords and keys

The password vault is an encrypted file on the device (AES‑256‑GCM). The encryption key lives only in this device’s Keychain and never leaves it. On Mac the vault opens after Touch ID or your Mac password; on the phone, with Face ID, fingerprint or passcode. You enter passwords yourself; the app does not send them anywhere.

2. Encrypted backups

Files are encrypted on the device (AES‑256, restic format) before upload to storage you connect yourself (for example Cloudflare R2, Backblaze B2, iCloud Drive, Google Drive, your own server). The storage only sees encrypted data. The backup password and storage keys are kept only in the Keychain (iOS/macOS) or Android Keystore.

3. Sync

There is no sync through our servers. Passwords are not transferred between devices automatically; backups go only to the storage you chose.

4. Pro subscription

On iPhone there is an optional Pro subscription through the App Store. Apple handles purchase and payment; we only get an entitlement check on the device and never see your payment details. You can restore purchases in the app.

5. Notifications

Telegram notifications are sent only to a bot you configure; they never contain file contents, passwords or keys.

6. No ads or tracking

The app has no advertising, analytics, crash reporting, trackers, in-app purchases or third-party SDKs that collect data, and does not use the advertising ID.

7. Deleting data

There is no account, so there is nothing to delete on our side: remove the app and, if you wish, the backup folder in your storage.

8. Children

The app collects no data from anyone, including children.

9. Changes and contact

If this policy changes, the new version will be published on this page. Contact: [email protected].