Privacy Policy

1. Information handled on the device

• Identity names, icons, colors, web-space details, URLs, notes, links between records, and preferences are stored in the local application database or settings.
• Passwords, verification-code secrets, encryption keys, and PIN-related security material are protected using the iOS Keychain and local encryption. The software cannot recover a forgotten backup password.
• Cookies and website storage are isolated by web space and encrypted when persisted by the software.
• Membership entitlement status is received from Apple and cached on the device so purchased features can remain available while status is refreshed.

2. Information the developer collects

The developer does not receive or retain vault contents, browsing history, QR images, biometric information, payment-card details, advertising identifiers, contacts, location, or analytics data. There is no developer-operated user account.

3. Permissions and user-selected content

• Camera: used only after you choose QR scanning to add a verification code. Camera frames are processed for recognition and are not saved by the software.
• Face ID: used to unlock protected local content. Authentication is performed by iOS; the software receives only the result and cannot read or store biometric templates.
• Selected photo: the system photo picker lets you choose one image for QR recognition without granting full photo-library access. The selected image is processed locally and is not uploaded to the developer.
• Files: the system document picker is used only when you choose a backup or CSV file or select an export destination.

4. Websites, network access, and Apple services

When you open a website, network requests go directly to that independent website. Its operator may receive information normally associated with a web request, including an IP address, cookies, device/browser information, and data you submit. These independent services follow their own privacy policies. Purchase, subscription, refund, and account verification operations are handled by Apple through StoreKit and the App Store. The developer does not receive payment-card details.

5. Sharing and tracking

The developer does not sell, rent, or share personal data with advertising, analytics, data-broker, or tracking partners. Information you intentionally submit to a website or save to a storage location selected through the system picker is provided directly to that independent service or location at your direction.

6. Backups and exports

Encrypted backups and CSV exports are created only when you request them and are saved to a location you choose. Encrypted backups are protected by the password you provide. CSV exports are plain text and can contain sensitive information; they are not encrypted by the software. Files outside the application container remain under your control and must be deleted from their saved location separately.

7. Retention, deletion, and privacy choices

• Local records remain until you delete them or replace local data during a confirmed restore.
• Web cookies and sessions remain until you clear the relevant session, clear all web data, or delete the related web space.
• You can disable camera or Face ID access in iOS Settings and can disable biometric locking in the software's security settings.
• You can delete identities, web spaces, passwords, and verification codes from their lists, and clear all website sessions from data management.
• Because there is no developer-operated account or server copy, there is no remote account data to request from the developer. iOS may retain Keychain items after an uninstall; delete sensitive records in the software before uninstalling if you want them removed from the device.

8. Security

Local file protection, Keychain, authenticated encryption, device authentication, and isolated website storage are used to reduce unauthorized access. No storage or transmission method can guarantee absolute security. Keep the device passcode and backup passwords private and maintain backups appropriate to your needs.

9. Children

The software is not directed to children, and the developer does not knowingly collect personal information from children.

10. Changes and contact

This policy may be updated when functionality or legal requirements change. The updated date identifies the current version. For privacy questions or deletion guidance, contact chireslommfmfning@outlook.com.