LOKR

Privacy policy

Effective 14 October 2026

LOKR is a password manager for KeePass databases. It is built so that nobody but you can read your data, including the developer. LOKR has no servers and no user accounts, and the developer receives no data from the app.

What LOKR stores, and where

• Your password database (a KeePass .kdbx file), encrypted with your master password. It is stored on your device and in your own Google Drive, in files you pick or create in LOKR.
• App data on your device: settings, sync status and backup copies of your database, encrypted with a key kept in your device's secure storage.
• Quick unlock and autofill data, if you turn them on: an encrypted copy of what is needed to unlock or fill, protected by your device's biometric or screen-lock check. LOKR never receives fingerprint, face or other biometric data; your device's operating system performs the check.
• Your Google sign-in: the access tokens Google issues to LOKR, encrypted on your device.

Google Drive and Google user data

LOKR asks Google only for the drive.file permission: access to files you choose in Google's file picker or create with LOKR. It cannot see any other files in your Drive. LOKR uses this access only to read and write your database files and, for shared databases, to share them with the people you invite. It does not read your Google profile, email or contacts.

LOKR's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not transferred to anyone, not used for advertising, and not read by humans.

Shared databases

When you share a database, LOKR shares its Google Drive file with the Google accounts you invite and stores each member's public key and name in the file. The database content stays encrypted; each member unlocks it with their own credentials.

What LOKR does not do

• No analytics, tracking, advertising or crash-reporting services.
• No data is sold or shared with third parties.
• No data is sent anywhere except to Google Drive, at your request, encrypted.

Device permissions

• Internet: to sync with Google Drive.
• Biometrics / device credential: for quick unlock and autofill, if you turn them on.
• Notifications (Android): to remind you when autofill saved a new login that LOKR still needs to add to your database.
• Installed apps (Android): to show which app you are filling a password into and to check that app's signature, so passwords are only filled into the genuine app.

Deleting your data

In LOKR, Settings > Forget this device deletes everything LOKR stores on that device; uninstalling the app does the same. Your database files in Google Drive remain yours: delete them in Google Drive if you no longer need them. You can revoke LOKR's access to your Google account at any time at myaccount.google.com/permissions.

Children

LOKR is not directed at children under 16.

Changes

If this policy changes, the new version is published on this page with a new effective date.

Contact

oneaxis, dev.oneaxis@gmail.com