App Access & Reviewer Instructions
UNRESTRICTED ACCESSThis document serves as testing guidance for Google Play Console App Reviewers and independent security auditors evaluating btw vault.
Play Console App Access Declaration
The app operates with zero required external credentials, paywalls, pre-registered test accounts, VPN requirements, or geographic restrictions. Any reviewer can launch the app and perform full end-to-end verification immediately.
Standard Reviewer Testing Protocol
Reviewers may execute this verification sequence to test the entire client cryptographic lifecycle:
Launch the application. Enter any master password of at least 8 characters (e.g., GoogleReview123!). Toggle biometric unlock if testing on physical hardware. Tap "Create Secure Vault". The encrypted SQLCipher database is initialized locally in the device sandbox.
Tap the "+" button to add a Login, Credit Card, or Secure Note. Verify field masking, password visibility toggling, and clipboard copying with automated clipboard clearance.
Open "Vault Customization" from the drawer. Create custom field definitions, toggle category visibility, and pin categories to the primary vault dashboard.
Under Settings, tap "Lock Vault Now" or background the application. Confirm the vault immediately locks, master keys are evacuated from memory, and the unlock screen is required to re-authenticate.
In Settings, tap "Export Backup" to generate an encrypted .btw-vault file. Then scroll to Danger Zone and tap "Wipe Vault" to verify complete cryptographic eradication of local database records. On the setup screen, tap "Restore .btw-vault Backup" to test full recovery using the master password.
Google Drive Cloud Backup Verification
Under Settings → Google Drive Backup, tapping "Link Account & Back Up" initiates official Google OAuth 2.0. Reviewers may sign in with any standard consumer Google account to audit the integration.
STORAGE PATH: Hidden app-data container (no read access to root drive or user files)