KeyWise Privacy Policy
This policy explains what KeyWise stores, what it does not collect, and how your data is handled in current production builds.
1. Core Principle
KeyWise is designed as a local-first credential manager. Your vault data is encrypted and stored on your device. Current production builds do not provide cloud sync, Google Drive sync, family sharing, or member-invite workflows.
2. Data Stored On Device
2.1 Vault and Credential Data
- Encrypted vault metadata and encrypted credential entries.
- Lock-method configuration and local app settings.
- Optional local backup files you explicitly create.
2.2 Security State
- PIN hash/salt and lockout counters (when PIN lock is used).
- Session activity markers used for auto-lock behavior.
- Local crash log entries used only for device-side diagnostics.
3. Data Not Collected
- No cloud credential sync payloads.
- No Google Drive backup integration.
- No RevenueCat integration.
- No account profile or social graph collection.
- No advertising ID usage and no ad network SDK integration.
4. Limited Network Interactions
Some features may use network access when available. These are feature-specific and not used to upload your encrypted vault data for cloud sync.
- Google Play Billing for one-time Premium purchase and restore checks.
- Optional update-check metadata from WiselyRise endpoints.
- Optional breach-check requests for user-triggered checks.
5. Encryption and Security
KeyWise uses device-side key derivation and authenticated encryption for vault content. Security also depends on your lock credentials and device security posture.
- Use a strong lock method and keep recovery code safe.
- Do not share decrypted credential exports publicly.
- Keep your OS and app version updated.
6. Third-Party Services Summary
| Service | Purpose | Credential Data Shared |
|---|---|---|
| Google Play Billing | Premium purchase and restore entitlement flow | No vault credential plaintext |
| WiselyRise Update Endpoint | Version/update notice metadata | No credential payload |
| Breach Check Endpoint (if used) | User-triggered leak checks | No full credential export stream |
7. Retention and Deletion
- Local app data stays on your device until you delete it or uninstall.
- Backup files remain where you save them and are controlled by you.
- Crash log files remain local and can be removed by clearing app data.
8. Children
KeyWise is not directed to children under 13. If a parent or guardian uses KeyWise to store household credentials, they are responsible for managing that data.
9. Changes To This Policy
We may update this policy when product behavior changes. Material updates will be reflected by updating the effective date on this page.
10. Contact
For privacy questions or requests: contact@wiselyrise.in
Website: wiselyrise.in/keywise