Privacy Policy

Overview

This Privacy Policy explains how KeyHollow handles information in the current local-first iPhone application. KeyHollow protects selected photos inside independent encrypted vaults and supports encrypted vault export and restore without requiring a KeyHollow account or sending vault contents to a KeyHollow-operated server.

Information KeyHollow collects

KeyHollow does not require an account and is not designed to collect personal information. The current app contains no advertising or analytics SDKs and does not send vault contents, vault passcodes, encryption keys, usage history, or device identifiers to a KeyHollow-operated server.

If you contact support, KeyHollow receives the information you voluntarily include in your message, such as your email address, device model, app version, and problem description. Do not send private photos, vault passcodes, encryption keys, or other sensitive vault content to support.

Photos access and imports

KeyHollow uses Apple-provided photo selection and permission interfaces so you can select photos for import. Selected photos are processed on your device. KeyHollow re-encodes selected images to reduce embedded metadata, encrypts them locally, and stores encrypted files in the app's protected container.

• Copy to Vault keeps the original item in Apple Photos.
• Move to Vault encrypts and verifies the vault copy before asking iOS to delete the selected original. Apple controls the final deletion permission and confirmation.

If deletion is denied or cannot be completed for every eligible item, KeyHollow treats the operation as a copy. Apple may process photo permissions and library changes under Apple's own terms and privacy policy.

Local storage and security

Vault photos, thumbnails, and manifests are stored using authenticated encryption. Each vault has independent cryptographic key material. Vault passcodes and usable vault encryption keys are not stored as plaintext files. The current app does not use Face ID, Touch ID, or the iPhone device passcode as a substitute for a KeyHollow vault passcode.

No security measure can guarantee protection against every threat. A compromised, modified, maliciously controlled, or already-unlocked device may weaken these protections.

Encrypted vault exports and imports

KeyHollow can create a portable .khvault archive of the vault that is currently open. The archive is encrypted locally using a new random 32-character recovery code that is separate from the vault’s 8–20 digit local LowKey. KeyHollow does not send the archive or recovery code to a KeyHollow-operated server.

You choose where to save or share the encrypted archive through Apple’s document picker and any Files provider you select. A recovery code may be copied only when you deliberately use the Copy control. KeyHollow requests local-only clipboard handling with a short expiration, but iOS or third-party clipboard and storage tools may retain or process information under their own terms. Keep the archive and its recovery code separate.

During restore, you select a .khvault archive and enter its recovery code. After authenticated validation succeeds, KeyHollow creates a new local LowKey for the restored vault. KeyHollow cannot recover a lost local LowKey or export recovery code.

Backups and cloud services

KeyHollow does not provide KeyHollow-operated cloud storage or synchronization. Its protected vault-data directory is designed to be excluded from ordinary device backup. You may choose to store an encrypted .khvault archive with a third-party Files provider; that provider's privacy and retention practices apply. A usable archive still requires its separate recovery code.

Sharing, sale, and advertising

Because the current app is not designed to collect personal information, KeyHollow does not sell personal information, share it for cross-context behavioral advertising, or use vault content for advertising or artificial-intelligence training.

Children's privacy

KeyHollow is not directed to children under 13 and is not designed to knowingly collect personal information from children.

Changes to this policy

This policy may be updated when KeyHollow's features, data practices, or legal obligations change. The effective date above identifies the current version. Materially different features, including any future optional cloud service, will require corresponding policy updates before launch.

Contact

Privacy or support questions may be sent to keyhollow.app.support@gmail.com.