PRIVACY POLICY

Effective date: October 5, 2026

Last updated: October 5, 2026

1. Who is responsible for your data

We are the controller of personal data processed for the purposes described in this Policy, where data protection law assigns that role to us.

For privacy questions or requests, contact jokwbxbchsowkekkfg@gmail.com.

This Policy covers the Auth iPhone app and its Apple Watch app, widgets, Live Activities, and AutoFill extension. It explains our processing practices; it does not replace any consent that must be requested separately under applicable law.

2. Information you store in Auth

You can store authenticator setup keys, account labels, usernames, passwords, website addresses, recovery codes, notes, folders, and tags. Auth processes these records on your device to generate verification codes, organize your vault, provide AutoFill, and perform vault security checks.

Vault records are stored using Apple's Keychain. We do not operate a server that stores your vault, and Auth does not send your passwords, authenticator setup keys, generated verification codes, or recovery codes to Adapty or Firebase as analytics data. Specific disclosures you enable, including iCloud synchronization, logo requests, password breach checks, AutoFill, browsing, and exports, are described below.

Auth creates a random local identifier for subscription management and diagnostics. It is stored in Keychain and may remain after the App is uninstalled. Although it does not contain your name or email address, it can link technical activity and purchases to the same App user. Auth does not require you to register a separate online account with us.

3. iCloud and companion features

If you enable iCloud Sync in Auth and iCloud Keychain in your Apple settings, main-vault records can synchronize through Apple's iCloud Keychain to your eligible devices. This uses Apple's end-to-end encrypted Keychain synchronization. We cannot retrieve your vault records from iCloud on your behalf. Apple's privacy policy and service terms also apply.

Widgets and the AutoFill extension access shared vault records on your device. When you use AutoFill or the browser's fill tools, the credentials or verification code you choose are supplied to the selected app or website. Information submitted to a third-party service is then handled under that service's own practices.

If the companion Apple Watch app is installed and paired, Auth transfers the visible authenticator records, including the setup keys needed to generate codes offline, to your watch using Apple's WatchConnectivity. The watch stores its own copy in Keychain. Selected accounts or codes may appear in widgets, Live Activities, or on your watch according to your settings. Consider who can see those displays.

Travel Mode hides selected records; it does not delete them. Decoy-vault records are not included in Auth's iCloud synchronization or watch transfers.

4. Permissions, imports, and exports

Camera: Auth uses the camera to scan setup QR codes. If you separately enable Intruder Alert and allow camera access, it can take a front-camera photo after repeated incorrect passcode entries. Intruder photos are stored in the App's local storage and are not uploaded by Auth to our servers. You can delete them in Settings > Face ID & Passcode. Device backups created by Apple may include local app files depending on your Apple settings.

Photos and files: Auth reads images or files you select to import supported authenticator data or backups. QR recognition and supported import parsing take place on your device.

Face ID and Touch ID: Authentication is performed by Apple's system. Auth receives the authentication result, not your biometric template.

Notifications: With permission, Auth may show local notifications about Premium features. You can turn them off in iOS Settings.

Clipboard: When you copy a password or code, Auth places it on the system clipboard. Clipboard expiry and the setting limiting it to this iPhone help control exposure. Information you paste into another app is subject to that app's practices.

Exports: Encrypted backups are protected with the password you choose. Plain-text exports, exported QR codes, and Recovery Kit PDFs can contain sensitive setup keys, recovery codes, and any passwords you choose to include. A PDF is password protected only when you enable that option. Files you save, print, or share can be accessed by your chosen storage provider, recipient, or printing service. We cannot delete those copies or recover a forgotten backup password.

5. Subscriptions and purchases

Apple processes App Store payments. We do not receive your full payment-card details or Apple Account password.

Auth uses Adapty to load purchase offers, validate purchases, restore purchases, determine Premium access, and analyze subscription and paywall performance. Data processed for these purposes includes the random Auth user identifier, Adapty profile identifiers, available device or vendor identifiers, device and operating-system information, app version, language, IP address and approximate country, paywall views, and purchase or subscription information such as product, transaction identifiers, price, currency, trial status, renewal, cancellation, and refund status. Information available depends on the purchase, device, platform restrictions, and service configuration.

These records are separate from the secrets in your vault. Subscription cancellation and App deletion do not automatically erase transaction records held by Apple or subscription records that must be retained for restoration, accounting, fraud prevention, or legal obligations.

Adapty's end-user privacy information: https://adapty.io/end-users-privacy/

Apple's privacy policy: https://www.apple.com/legal/privacy/

6. Diagnostics and remote configuration

Auth uses Google Firebase Crashlytics to diagnose crashes and errors, and Firebase Remote Config to deliver settings such as paywall presentation options.

Crashlytics can receive installation and session identifiers, the random Auth user identifier, device model, operating-system and app versions, crash timestamps, stack traces, error information, and diagnostic event logs. Auth also records technical properties such as Premium status and whether an Apple Watch is used. Diagnostic events describe actions such as opening a paywall, copying a code, or changing a setting; they are not intended to include the copied code or password itself.

Remote Config processes Firebase installation identifiers and technical request information to return app configuration. Network services necessarily receive connection information, including IP addresses.

Firebase privacy and retention information: https://firebase.google.com/support/privacy

7. Service icons, password breach checks, and the private browser

When Service icons are enabled, Auth requests logos from Logo.dev using a service name or website domain associated with a record. Logo.dev receives the requested name or domain, your IP address, and technical request information such as the request time. Auth does not include a setup key, password, or generated code in logo requests. If you enter personal or confidential information as a service name or website domain, that information may be included in the lookup. You can stop new logo requests by turning off Service icons in Settings > Appearance.

Logo.dev's privacy policy: https://www.logo.dev/legal/privacy

If you run a password breach check, Auth uses the Have I Been Pwned Pwned Passwords service. Auth computes a SHA-1 hash on your device and sends only its first five hexadecimal characters to the range-search API, together with ordinary network information such as your IP address and an App-identifying request header. It does not send the complete password, complete hash, or username in that request. The response is compared with the remaining hash locally, and the check result is stored on your device. This check does not guarantee that a password has never been compromised.

Have I Been Pwned's privacy policy: https://haveibeenpwned.com/Privacy

Pwned Passwords API explanation: https://haveibeenpwned.com/API/v3#PwnedPasswords

The built-in browser uses a non-persistent website data store. Websites you visit and their service providers can receive your IP address, requests, browser information, and information you submit. Cookies and other website data can exist during the session. Clearing the browsing session removes its local session data, but does not erase records held by websites, internet providers, or other network operators. Private browsing does not make network activity anonymous.

8. Why we process information

Where the GDPR, UK GDPR, or similar requirements apply, our legal bases depend on the activity:

- Providing the functions you request, managing purchased access, and restoring purchases: performance of our contract with you.

- Essential diagnostics, service security, fraud prevention, and maintaining reliable configuration: our legitimate interests in operating and protecting Auth, subject to your rights and applicable legal requirements.

- Optional processing for which the law requires consent: your consent. You may withdraw it without affecting processing that was lawful before withdrawal.

- Records needed for tax, accounting, regulatory compliance, or valid legal requests: compliance with legal obligations.

You choose which vault content and optional features to use. Some technical and purchase information is necessary to provide online features and verify Premium access; without it, those functions may not work. We do not use your vault secrets for advertising. We do not make decisions producing legal or similarly significant effects about you solely by automated processing.

9. Sharing and international processing

Information is disclosed to Apple, Adapty, Google Firebase, Logo.dev, and Have I Been Pwned for the functions described above, and to email providers when you contact us. A provider may act as our processor for some activities and as an independent controller for its own platform operations. We require providers processing personal data on our behalf to use it for the relevant services and protect it consistently with applicable law and this Policy.

We may also disclose information when legally required, to protect lawful rights or investigate misuse, or as part of a business transfer subject to applicable protections and notice requirements. We do not sell personal data or share it for cross-context behavioral advertising.

Providers may process information outside your country, including in the United States. Where the law requires safeguards for an international transfer, the applicable arrangements must provide those safeguards, such as an adequacy decision, an eligible Data Privacy Framework certification, or standard contractual clauses with any required additional protections. Contact us for information about the safeguards applicable to your data or a copy where available.

10. Retention and deletion

Vault records remain in Keychain until you remove them. Deleted codes and logins normally enter Recently Deleted for 30 days; after that period, Auth removes expired records when its cleanup runs. To remove an item sooner, use Delete forever in Settings > Recently Deleted. Main and decoy vaults have separate records. Deletion can propagate through iCloud Keychain when synchronization is active, subject to Apple's synchronization behavior. A disconnected device or watch may retain its previous copy until an update reaches it.

Intruder photos remain until you delete them. Password breach-check results and app preferences remain in local app storage until removed with that storage, subject to restoration from a device backup. Exported files, printed Recovery Kits, and device or cloud backups remain under your control or the control of the provider or recipient you selected. Turning off synchronization alone is not a substitute for deleting existing copies. Uninstalling Auth does not guarantee that Keychain records, iCloud copies, or watch records are erased.

Firebase states that Crashlytics retains crash traces and associated identifiers for 90 days before beginning removal from its live and backup systems. Firebase Remote Config retains installation identifiers until deletion is requested through Firebase's mechanisms. Adapty retains subscription data according to the services it provides, our applicable contractual arrangements, and legal requirements. Logo.dev retains API logs for service delivery, security, and billing needs.

If you contact support, we receive your email address and the information you send. We keep correspondence for the time needed to resolve your request and any related dispute or legal obligation. Purchase and compliance records may need to remain for applicable accounting or limitation periods. Anonymized information that no longer identifies you may be retained longer.

To request deletion of personal data we or our processors hold, email jokwbxbchsowkekkfg@gmail.com. We may need limited information to find the relevant records and verify your request. Do not send passwords, setup keys, active verification codes, or recovery codes. We cannot remotely erase a vault held only on your devices. Deleting data does not cancel an Apple subscription.

11. Your privacy rights and choices

Depending on your location and the applicable law, you may request access to, correction of, deletion of, or a portable copy of your personal data; restriction of processing; or object to processing based on legitimate interests. You may withdraw consent where processing depends on it and complain to your local data protection authority. Applicable law determines the scope and exceptions of these rights.

Send requests to jokwbxbchsowkekkfg@gmail.com. We will respond within the period required by applicable law and explain any permitted refusal or extension. You will not receive discriminatory treatment for exercising a privacy right. Where legally required, an authorized agent may submit a request subject to verification.

You can also disable optional app features and manage camera, biometric, photo, and notification permissions through the available App or Apple settings. Disabling a feature or permission does not automatically erase information already processed.

12. Security, children, and updates

Auth uses Apple's Keychain, system authentication, and password encryption for encrypted backup files. Online providers apply their own security measures. No app, device, or transmission method can guarantee absolute security. Protect your devices, Apple Account, app passcode, and exported recovery material.

Auth is not intended for children under 13, or below a higher minimum age required by local law. We do not knowingly collect their personal data through our online services. If you believe this has happened, contact us so we can investigate and take appropriate action.

We may revise this Policy when practices or legal requirements change. The revised date will appear above. For material changes, we will provide additional notice and obtain consent where required before new processing begins.

Privacy contact: jokwbxbchsowkekkfg@gmail.com