Effective date: September 17, 2026
GuptVault is designed as a private, zero-knowledge credential manager for iPhone, iPad, and Mac. This policy explains what data the app stores, how it is protected, and when network services are used.
This policy is written for the current production design of GuptVault. It should be reviewed by qualified legal counsel before App Store submission or public launch.
GuptVault stores the credential information you choose to add, including:
GuptVault treats this information as sensitive. Credential values, notes, custom fields, and developer secrets are encrypted before persistence and before CloudKit sync.
GuptVault uses a zero-knowledge design, and there is no master password to choose, remember, or steal:
Because there is no master password and no account to reset, your recovery kit is the only way back in if every approved device is lost or erased.
If iCloud sync is enabled, GuptVault syncs encrypted vault records through Apple CloudKit so your data can be available across your Apple devices.
Important details:
You can manage iCloud access from Apple system settings and GuptVault app settings.
GuptVault may use network access for these app functions:
For breach checks, GuptVault sends only the first five characters of a SHA-1 hash of a password, never the password itself. The service returns padded lists of matching hash suffixes, and comparison is completed locally on your device. You can turn breach checks off in Settings or Password Health.
When you turn on GuptVault in AutoFill settings, GuptVault prepares an encrypted copy of eligible logins, verification-code setup keys, and passkeys for its AutoFill extension. This copy stays on your device and can be opened only after device authentication (Face ID, Touch ID, Optic ID, or passcode). The system AutoFill suggestion list receives only website names, user names, and opaque identifiers — never passwords, codes, or passkey private keys.
Smart Paste and the Security Coach use Apple’s on-device language model when Apple Intelligence is available. Text you paste into Smart Paste is analyzed on your device, and passwords and keys are extracted by GuptVault’s own on-device rules rather than the model. The Security Coach sends the model only counts and task titles — not item names, passwords, or other secrets. GuptVault does not send this data to GuptVault servers or third parties. Both features work without Apple Intelligence using on-device rules.
GuptVault does not use network access for advertising, behavioral tracking, or third-party analytics.
Scope note (2026-10-27): the guptvault command-line tool is not part of GuptVault 1.0, so the
command-line behaviour described in this section does not occur in the shipping release. It is kept
here because the in-app developer items do exist and because the tool may return in a later version.
Counsel should confirm whether this section stays as written or is trimmed for the 1.0 publication.
GuptVault includes developer features for securely using secrets from scripts without hardcoding them.
Depending on your settings and platform:
guptvault run command injects secrets only into the process you start and does not print them.You are responsible for scripts, shell history, logs, environment variables, terminal output, CI systems, and other destinations where you choose to send or expose secrets after retrieving them from GuptVault.
GuptVault may use an Apple App Group container to support widgets and quick actions.
The GuptVault widget receives only a security score, a count of items that need attention, and whether a recovery kit is set up. It never receives item names, user names, websites, passwords, or verification codes. Notifications likewise contain counts only.
When you copy a secret, the value is placed on the clipboard for this device only (on iPhone and iPad it is excluded from Universal Clipboard) and marked to expire. GuptVault clears it automatically after 30 seconds if it hasn’t changed, but the clipboard is a shared operating system feature, and other apps or system features may read it before it is cleared. AutoFill avoids the clipboard entirely.
GuptVault keeps an encrypted, tamper-evident history of sensitive actions — such as unlocks, reveals, copies, AutoFill use, imports, and device approvals — on each device. It is encrypted with a key derived from your vault, is not synced, and is not sent to GuptVault.
Password export files you import are read and parsed on your device. GuptVault does not upload the file. Export files from other password managers are not encrypted, so delete them after importing.
GuptVault may store or access the following data to provide app functionality:
GuptVault does not:
GuptVault can use Apple platform authentication features to unlock the app. Authentication is handled by the operating system. GuptVault is told whether authentication succeeded or failed; it does not receive your biometric data.
Vault data remains stored until you delete it, uninstall the app, delete the relevant iCloud data, or remove it through app features.
Deleting a credential removes it from the local vault database and, when iCloud sync is enabled, deletion should sync through CloudKit. Deletion from all devices may depend on iCloud sync state, connectivity, Apple account state, and CloudKit behavior.
You can also manage app data through Apple device settings and iCloud settings.
GuptVault is designed to protect stored credentials, but your security also depends on:
GuptVault is not directed to children. The app is intended for users who need to store and manage credentials. GuptVault does not knowingly collect children's personal information for tracking or advertising.
This policy may be updated as GuptVault changes. Material changes should be reflected by updating the effective date and publishing the revised policy at the Privacy Policy URL used in the App Store listing.
For privacy questions, contact:
privacy@guptvault.com
If this email address is not active yet, create it before public launch or replace it with your production support address.