🔐 PassForge

Last updated: March 9, 2026

1. Overview

PassForge ("the App") is committed to protecting your privacy. This policy explains how the App handles your data.

2. Data Collection

The App does NOT collect, transmit, or share any personal data. It operates entirely offline with no internet access - no network permission is requested or used.

3. Data Storage

All data you create (vault credentials, password history, password hints, settings) is stored exclusively on your device using:

• Android Keystore - hardware-backed cryptographic key management; keys cannot be exported even with root access
• AES-256-GCM encryption - for vault passwords, password history entries, and password hints
• EncryptedSharedPreferences - the entire storage file is encrypted on disk using AES256-SIV (keys) and AES256-GCM (values)
• PBKDF2WithHmacSHA256 - master password is never stored; a 256-bit key is derived using 100,000 iterations with a 32-byte random salt

Vault credentials are double-encrypted: each password is individually encrypted with the master-password-derived AES-256-GCM key, and the entire storage file is encrypted via EncryptedSharedPreferences backed by the Android Keystore.

No data is stored on external servers, cloud services, or third-party systems.

4. Screen Protection

All screens that display or handle sensitive data (password vault, credential editor, master password entry, password history) are protected with Android's FLAG_SECURE. This prevents:

• Screenshots and screen recordings
• Content appearing in the recent apps overview
• Screen mirroring or casting from exposing passwords

5. Authentication & Access Control

The App uses multiple layers of authentication to protect your data:

• Master password - Required to access the password vault (minimum 8 characters). The password itself is never stored.
• Biometric / device credential - Viewing or copying any password requires device authentication (fingerprint, face unlock, PIN, pattern, or device password) via Android's BiometricPrompt.
• Brute-force protection - After 5 consecutive failed master password attempts, a 30-second lockout is enforced before further attempts are allowed.
• Auto-lock - The vault automatically locks when returning from the background, requiring re-authentication.

6. Clipboard Protection

Passwords copied to the clipboard are automatically cleared after 30 seconds to prevent leakage through clipboard history or other apps.

7. Backup & Export Security

• Backup prevention - Android auto-backup and ADB backup are disabled to prevent data extraction.
• Encrypted export - Vault exports are encrypted with a user-chosen password (minimum 8 characters) via PBKDF2 + AES-256-GCM. The export file (.spg) contains a 32-byte salt followed by the ciphertext. The export password is independent of the master password and is never stored.

8. Third-Party Services

The App does not integrate with any third-party services, analytics platforms, advertising networks, or tracking systems. There are no SDKs, no telemetry, and no crash reporting services.

9. Permissions

The App requests no special permissions:

• No internet access
• No camera or microphone
• No contacts or phone
• No location services
• No external storage access (only its own private app directory)

Import/export uses Android's Storage Access Framework (SAF) file picker, which requires no permission declaration.

10. Data Deletion

You can delete all App data at any time by:

• Clearing password history from Settings → Clear History
• Deleting individual vault credentials within the app
• Deleting individual password hints
• Uninstalling the App (completely removes all data from your device)

11. Children's Privacy

The App does not knowingly collect data from anyone, including children under 13, because it collects no data whatsoever.

12. Changes to This Policy

Any changes to this privacy policy will be reflected in an app update with an updated "Last updated" date. This page will also be updated accordingly.

13. Contact

If you have questions about this privacy policy, please open an issue on the app's GitHub repository.