VERSION 1.0.4On-device AES-256 encryption with private Google Drive backup. Zero servers.
DryVault Logo
DRYVAULTZero-Knowledge
Back to DryVault Overview
OFFICIAL PRIVACY POLICY · EFFECTIVE OCTOBER 2026

Privacy Policy: We Don't Control Your Data.

DryVault is built on strict zero-knowledge principles. Your credentials, files, and notes are encrypted locally on your hardware. We do not operate remote databases, user accounts, or tracking services.

Executive Privacy Summary

1. Zero Data Custody: We do not control, view, collect, or store any of your passwords, secure notes, private files, or Master PINs.

2. 100% Local Device Storage: By default, all your data is stored exclusively on your physical device’s internal flash storage within an isolated, hardware-encrypted SQLite sandbox.

3. Optional Google Drive Persistence: If you choose persistent backup for disaster recovery or multi-device sync, your device encrypts the vault locally before uploading directly to your personal Google Drive AppData folder (drive.appdata scope). We do NOT operate any intermediate servers or proxy relays.

4. Direct Support: For all inquiries or security reports, contact our team directly at support@choresnest.com.

1. Information We Do NOT Collect

Unlike traditional cloud password managers, DryVault requires zero account registration. When using DryVault:

  • We do not collect your name, email address, phone number, or identity documents.
  • We never receive or log your Master PIN, passwords, notes, or uploaded files.
  • We do not embed third-party advertising SDKs, tracking pixels, or commercial telemetry beacons.
  • We do not record your IP addresses, device identifiers, or GPS location coordinates.

2. Data Storage Topology & Cryptographic Isolation

A. On-Device Local Flash Storage (Primary)

Your passwords, sensitive files, metadata, and secret notes are compiled into an encrypted database stored solely inside your mobile device’s protected private application storage.

All vault records are encrypted using AES-256-GCM (Galois/Counter Mode with 128-bit authentication tags). The encryption key is derived locally from your Master PIN using PBKDF2-HMAC-SHA-256 with a locally generated cryptographic salt.

B. Persistent Google Drive Synchronization (Optional)

If you activate cloud synchronization within DryVault, the application connects directly to your personal Google Drive account using Google’s official OAuth2 client.

  • Strictly Isolated Scope: DryVault requests only the https://www.googleapis.com/auth/drive.appdata permission scope. This scope grants the application access exclusively to its own hidden, application-specific data folder in your Google Drive. DryVault cannot view, read, modify, or delete any of your personal Google Drive documents, spreadsheets, photos, or personal folders.
  • Client-Side Ciphertext Only: Before any backup file or snapshot is sent to Google Drive, it is fully encrypted on your device. Google receives only ciphertext binary blobs (.enc).
  • Zero Relay Servers: Transmission occurs via direct HTTPS from your phone to Google APIs. Choresnest and DryVault do not host intermediate servers, reverse proxies, or cloud routers.

3. Device Permissions & How They Are Used

DryVault requests only the minimum operating system permissions strictly necessary to function:

Android Autofill Service

Used exclusively to display save/fill dialogs when you interact with login fields in Chrome or native apps. Autofill queries remain local to your device.

Biometric Authentication

Allows fingerprint or face unlock using Android BiometricPrompt. Biometric verification is handled by your device's hardware Secure Enclave. DryVault never accesses raw biometric scans.

Network Access (android.permission.INTERNET)

Used strictly when you initiate Google Drive backup or restoration, or when checking for app updates. DryVault never sends vault content to any other domain.

Storage / File Picker

Used via system document picker when you deliberately choose a file or image to encrypt into your Private Files Locker.

4. In-Memory Key Hygiene & RAM Zeroing

DryVault defends against memory inspection and cold-boot vulnerabilities:

Whenever the vault auto-locks, when you press "Lock Vault Now", or when the application is minimized past your auto-lock timeout duration, all in-memory cryptographic keys and decrypted plaintext secrets are immediately overwritten with zeros and dereferenced from system RAM.

5. User Data Retention & Deletion Rights

Because DryVault maintains no centralized customer database:

  • Local Deletion: You may permanently delete your data at any time by selecting "Clear Storage" or uninstalling the application from your Android device. This immediately and irreversibly destroys the local encrypted database.
  • Cloud Deletion: If you enabled Google Drive sync, you can revoke access at any time from DryVault’s Cloud Drive settings or directly in your Google Account security settings. You can delete the hidden AppData folder from Google Drive with a single click.
  • Zero Residual Backups: Because we have no servers, there are no company database backups where your deleted data could linger.

6. Changes to this Policy

We will never alter our zero-knowledge architecture to compromise your sovereignty. If we update this Privacy Policy to reflect new regulatory guidelines or features, updates will be reflected on this page with an updated version number.

Privacy Support & Inquiries

Have a question about our zero-knowledge implementation or need assistance with your data sovereignty? Our security team responds promptly.

DIRECT SUPPORT: support@choresnest.com · CHORESNEST CRYPTOGRAPHIC INITIATIVE