Privacy Policy for Keepass2Android / Keepass2Android Offline
1. Data Controller
Philipp Crocoll
Wallonenstr. 4
76297 Stutensee
Germany
For any questions regarding privacy, please contact: crocoapps@gmail.com
2. Overview
This app is a file-based password manager. All data you store in the app remains under your control. No password database or personal information is transmitted to the developer or any third party without your explicit action.
3. What data does the app process?
3.1 Password database and user-entered information
- All entries you create (e.g., passwords, usernames, notes, attachments) are stored only inside an encrypted KeePass database file.
- You choose where this encrypted file is stored (local device storage or third-party cloud services such as Dropbox, Google Drive, pCloud, WebDAV, FTP, etc.).
- The developer has no access to your database file or its contents.
- If you choose a cloud service, your data will be stored according to the terms and policies of that service provider. The app does not send unencrypted data.
3.2 No collection of personal data
The app does not collect, log, or transmit personal identifiable information (PII).
4. External storage providers
If you choose to store your encrypted database on services such as Dropbox, Google Drive, pCloud, or other WebDAV/FTP servers:
- The app only uploads/downloads the encrypted database file.
- The encryption is part of the KeePass approach and prevents these providers from accessing your data.
- Use of any cloud provider is voluntary and subject to their respective privacy policies.
5. Debug logs (optional)
- Debug logging is disabled by default.
- If manually enabled, logs remain stored locally on your device.
- Logs are not accessible to the developer unless you explicitly choose to send them.
- Logs typically do not contain personal data, except possibly filenames or folder paths depending on your device's configuration.
- Debug logs are never shared with third parties unless you explicitly authorize it.
6. Permissions
The app requests only the permissions necessary to provide its functionality:
Internet (Keepass2Android regular only): Required to allow the user to read/store password databases or key files on remote locations, e.g. Dropbox or via WebDav.
Contacts/Accounts (Keepass2Android regular only): Required by the Google Drive SDK. If you want to access files on Google Drive, you are prompted to select one of the Google Accounts on your phone to use. The permission is required to query the list of Google accounts on the device. Keepass2Android does not access your personal contacts.
Storage: Required to allow the user to read/store password databases or key files on the device locally.
Fingerprint/Biometric: Required if you want to use biometric unlock.
Vibrate: Required by the built-in keyboard (vibrate on key press).
Camera: Required for scanning OTP QR Codes.
Foreground service: Required to keep the app alive for QuickUnlock (so you don't need to enter your full master password repeatedly).
7. Legal basis (EU/DSGVO)
- The app processes data only at your request and only locally or in files owned by you, which constitutes processing for the performance of a contract (Art. 6(1)(b) GDPR).
- No personal data is transmitted to the developer.
- Use of optional cloud storage services is based on your consent.
8. Data retention
All data is stored only by you, for as long as you choose. If you delete your database file, the data is removed from your device or chosen storage provider.
9. Third-party services
The app does not integrate analytics, advertising, or tracking SDKs. Connections to third-party cloud services occur only when you explicitly configure them.
10. Changes to this Privacy Policy
Updates to this Privacy Policy will be published within the app or on the related project page. Continued use of the app after changes indicates acceptance of the updated terms.