Hold My Cards
Privacy Policy
How Hold My Cards handles your information, on your device and when you contact support.
Last updated: September 30, 2026
This policy explains how Hold My Cards for iPhone, developed by Andrei Constantinescu, handles information. Questions can be sent to andrei.cristian.costa@gmail.com.
1. No account, advertising or tracking
Hold My Cards does not require an account. The app does not send your card collection, photos or usage activity to the developer or to a developer-operated server. It contains no advertising SDKs, third-party analytics services or cross-app tracking tools.
2. Information stored on your device
The app stores the card information you save, such as card names, issuers, optional cardholder names and display identifiers, QR or barcode content, favorites, card order and appearance choices. Card contents are encrypted locally using AES-GCM. The local encryption key is held in the iOS Keychain and is restricted to the device.
Preferences such as language, appearance, font, background and selected card are stored locally. The app does not upload these preferences to the developer.
3. Camera and photo access
Camera access is used to scan QR codes and barcodes when you choose the scanning feature. The system photo picker lets you select a photo or screenshot for import; the app does not browse your entire photo library.
Barcode detection and text recognition are performed on your device. The selected image is processed for the import flow and is not retained as a card attachment. The app saves the card information you choose to keep, not the original image or all text found in it. The app does not upload camera images or selected photos to the developer.
You can manage camera permission in iOS Settings and use manual entry instead.
4. App lock and biometric authentication
Optional app lock uses a password verifier stored in the iOS Keychain, not your plaintext app password. If you enable Face ID or Touch ID, iOS performs biometric authentication. Hold My Cards does not receive or store your facial or fingerprint data.
Backup and restore use system authentication to protect access. App lock controls access to the app and does not disable your chosen Home Screen widgets. App lock credentials are not included in exported card backups.
5. Home Screen widgets
To display your selected cards, the app shares a limited encrypted snapshot with its own widget extension on the same device. This snapshot contains card IDs, names, issuers, favorite status, codes, effective card themes, language and display font. It does not include cardholder names, display identifiers or notes.
The widget snapshot uses a separate encryption key shared only between the app and its extension. It is stored with file protection and excluded from device backup. This is local communication between the app and widget, not transmission to the developer.
iOS controls widget refresh and privacy presentation. A previously rendered widget may remain visible until the system updates it. You can change or remove widgets through iOS.
6. Optional device motion
If you enable Subtle card motion, device motion readings are used locally to animate decorative card surfaces. This feature is off by default. Motion samples are not saved or transmitted by the app. You can disable the feature in Settings; Reduce Motion also disables it.
7. Backups and services you choose
You can manually export a password-protected, encrypted .hmcbackup file containing your cards and portable preferences. The app encrypts the file before handing it to the iOS file picker. Local encryption keys, app lock credentials and biometric settings are not exported.
You decide where to save or share the file. If you choose iCloud Drive or another storage provider, that provider handles the file under its own terms and privacy policy. Hold My Cards does not operate a cloud synchronization or backup service and does not receive your exported backup.
Any device-level backup or diagnostic services you enable in iOS are managed separately by Apple. The app's device-only encryption key is not transferred through its manual backup; use the password-protected export to move your cards to another iPhone.
8. Your choices and deletion
You can delete individual cards in the app, remove Home Screen widgets and change your local preferences. Removing the app deletes its local app storage, subject to iOS behavior; iOS may retain Keychain items separately. Copies in previously exported files or device backups are not deleted when you delete a card or uninstall the app. Manage those copies through the storage service or backup settings you used.
The developer cannot access your local card collection, reset your app password or decrypt a backup for which you have lost the password.
9. Support emails
If you contact support, your email address, message and any attachments you choose to send are received by the developer and processed through the email provider to answer your request and investigate the issue. This is separate from the app's local operation. Please avoid sending passwords, private card codes or backup files.
Support correspondence is kept as needed to handle and follow up on the request and meet any applicable obligations. You can contact the same address to request deletion of your correspondence, subject to any required retention.
10. This website
These support and privacy pages are hosted on GitHub Pages. They contain no added analytics, tracking scripts or advertising. GitHub may process technical information about website requests under the GitHub Privacy Statement. Visiting this website is separate from using the app.
11. Changes and contact
This policy may be updated if the app's features or data practices change. The date above identifies the latest revision.
For privacy questions or support, contact Andrei Constantinescu at andrei.cristian.costa@gmail.com.