Privacy

The database and attachments are encrypted on your device. A master passphrase unlocks them. While unlocked, data is processed in memory; this does not protect against malware in an active session.

Each user stores encrypted files on their own Google Drive, without a shared database on the developer’s server. Google OAuth and Drive API use drive.file: files created by or shared with the app, not the entire Drive. permissionId checks account binding. Google handles sign-in, requests and storage under its terms; file sizes and timestamps are not hidden.

Copying uses the system clipboard. Opening an attachment gives an external app a decrypted temporary copy. Exports may create unencrypted files. External editor history and autosave are outside Key-X’s control. Cleanup does not guarantee physical erasure.

Revoking Google access does not delete stored cloud files. Delete them in your Drive; local files and backups require separate deletion.

Support and data enquiries: keyx.help@gmail.com