Document Vault

Privacy Policy

Document Vault is a local-first document scanner and private vault. This privacy policy explains what the app stores, what DeadStick Digital does not collect, and how optional providers fit into the product.

Effective date: June 12, 2026

Short version. Document Vault does not use a proprietary DeadStick-operated document backend, does not sell personal data, and does not include advertising SDKs, third-party analytics SDKs, or cross-app tracking.

Local vault data

Document Vault stores vault content in the local app sandbox by default. That may include scanned document images, imported files, generated PDFs, packet exports, document titles, folders, tags, page order, scan source, timestamps, sync state, OCR text, translation text, crop information, filter choices, app-lock settings, local safety snapshots, and deletion tombstones used for sync reconciliation.

Data DeadStick does not collect

DeadStick Digital does not collect vault documents, scan images, imported files, generated PDFs, packet contents, OCR text, translations, titles, filenames, tags, folders, document hashes, search indexes, PINs, Google OAuth tokens, iCloud account details, or provider file identifiers to a developer-operated server.

Document Vault does not collect location, contacts, browsing history, advertising identifiers, or health data.

Subscription services

Paid or trial builds may use App Store or Google Play purchases, RevenueCat entitlement validation, and Supabase Auth account linking. Those services may process purchase history, entitlement state, product identifiers, app-user identifiers, sign-in identifiers, and account-deletion records needed for billing, Premium access, restore purchases, cross-platform entitlement linking, and account management. They must not receive vault documents, scan images, OCR text, translations, filenames, folders, tags, packet contents, generated PDFs, PINs, biometric settings, Google OAuth tokens, or provider file identifiers.

Permissions and providers

Camera access is used when the user scans documents. Face ID or Touch ID access is used only when the user enables biometric app unlock. File, share, import, and export surfaces are used only when the user chooses documents or destinations. Network access is used for user-selected cloud sync, OAuth sign-in, provider file upload or download, and subscription account features.

When a user enables iCloud or Google Drive sync, vault metadata and selected assets may be uploaded to that provider under the user's account. Document Vault does not operate an intermediate sync server. Cloud providers process account, file, diagnostic, security, or usage data under their own policies.

Sharing, export, and diagnostics

Users can export PDFs, protected PDFs, and Document Vault packet backups. Exported files leave the app sandbox when the user shares or saves them outside Document Vault.

Document Vault does not include developer-operated analytics or crash reporting in the current beta. Local diagnostic events are designed to remain privacy-safe, avoid automatic upload, and redact emails, tokens, keys, paths, hashes, ids, and one-time-code-like values.

Retention, deletion, and security

Local vault content remains on the user's device until the user deletes documents, removes local app data, resets the device, or uninstalls the app. Documents deleted in Document Vault are hidden from active vault views and may create tombstones so deletions can sync safely. See data deletion for more detail.

Document Vault uses AES-256-GCM for default local vault storage on Apple platforms when the Keychain-held vault key is available. The optional app PIN controls app access. It does not encrypt the local vault database by itself.

Contact

Use the Document Vault support page or the DeadStick Digital message form for privacy questions.