Effective date: 5 September 2026
Just Cards is developed by Peter Kresanic, the data controller for the processing described in this policy. For privacy questions or requests, email [email protected].
Just Cards helps you store and present loyalty, membership, gift, and similar cards. You do not create a separate Just Cards account. The app is sold as a one-time purchase through Apple's App Store, with no subscription.
The app stores the information you add, such as card and issuer names, category, color, barcode content, membership number, optional cardholder name and notes, and any saved barcode image. It also stores settings and library information such as favorites, ordering, creation and edit dates, card-opening history, usage counts, and deletion dates.
Your library is stored on your device. With an available iCloud account, Just Cards uses Apple's private iCloud/CloudKit storage to synchronize your library across your devices. This is separate from optional analytics. Your private library is not uploaded to PostHog or to a developer-operated card database, and we do not receive it through a Just Cards account.
Apple processes iCloud data under its own terms and privacy policy. Availability, synchronization, backups, and deletion propagation depend on Apple’s services, your settings, and connectivity. The app can check whether iCloud is available; it does not receive your Apple Account password.
Camera access is used to scan card barcodes when you choose that feature. Photo import uses the system picker to access images you select. Barcode recognition runs on your device; selected images and camera footage are not sent to an external recognition or AI service. A barcode crop saved with a card becomes part of your library and may sync through iCloud. Earlier versions may have stored card artwork.
Optional App Lock uses Apple’s device authentication, such as Face ID, Touch ID, or your device passcode. Just Cards receives the authentication result, not your biometric template or passcode. You can manage permissions in iOS Settings.
Widgets use a local cache shared between the app and its widget extension. This includes card identifiers, display and issuer names, category, color, and a relative most-used ranking. It excludes barcode contents, membership numbers, cardholder names, notes, card images, and detailed usage history. Card names may appear on the Home or Lock Screen according to your widget and iOS settings.
Sharing is initiated by you. An exported card file or iCloud invitation can include the card and issuer names, appearance and category, barcode format and usable barcode data, membership number, and a saved barcode crop. The sharing payload excludes the separate cardholder-name and notes fields, favorites, local identity, and usage history. Information you put in a card’s display name remains part of the shared content.
iCloud sharing uses Apple’s private and shared CloudKit storage and the access options you choose in Apple’s sharing interface. The invitation may show a card title and preview. Other apps or services you select to send a file or invitation process it under their own policies.
Cloud invitations are accepted by Just Cards only within seven days of creation. Expired invitation records are removed when the app can perform maintenance; this is not a promise of deletion at the exact expiry time. Recipients can retain imported or exported copies. Revoking an invitation or deleting your original card does not erase copies already held by recipients.
Analytics is off until you allow it. Declining does not restrict the app’s card features. If you allow analytics, Just Cards sends limited usage events to PostHog’s EU Cloud service to help us understand feature use and improve the app.
Events describe app openings, the app screens viewed, card creation or editing and whether it began manually, by scanning, or from photos, card opening from the library or a widget, favorite changes, and counts of cards imported, skipped, deleted, or restored. Events include random installation and session identifiers, event identifiers and timestamps, app version/build, operating-system version, analytics-library version, and whether the build is for development or production.