Your cards. Your privacy.
Bluvera LLC uses the information below to run CardPacket. Contact us at [email protected] about your data.
Your collection and account
We store your collection, quantities, variants, conditions, purchase costs, estimates, notes, wishlist and recorded collection values. A random account identifier connects this information to your session. If you use Apple sign-in, we also store the Apple account identifier and credentials needed to maintain or revoke that connection.
Photo recognition is your choice
Before the first photo upload, CardPacket asks permission to send your chosen card photo through our server to Gemini on Google Cloud Vertex AI. The photo is used to read printed card details. CardPacket does not save the uploaded photo. Scan records contain candidate card identifiers, timestamps and confirmation status. You can reset this permission in Privacy on iOS or in the web scanner. Manual search needs no photo upload.
Services that help CardPacket work
Google Cloud processes photos for recognition. Apple and RevenueCat handle purchases and subscription status; CardPacket does not receive your payment-card details. TCGdex provides card images, catalogue information and market references. These services process information under their own applicable terms and policies, including provider retention and abuse-monitoring settings.
Storage, logs and cookies
The iOS app keeps a local collection copy so you can view saved cards offline. The website uses a session cookie to open your collection and browser storage to remember photo permission. Operational logs may include request addresses, times and error details. Uploaded photos, authorization headers and private credentials are not intentionally included in those logs. CardPacket does not include advertising trackers or sell your collection data.
Export, correction and deletion
You can edit your collection and export it from your profile or web collection. You can request account deletion from the iOS profile or by contacting support. Deletion removes the account and collection from the active database and clears the local account in the app. Deleting an account does not cancel an Apple subscription. Provider billing records and limited records required to resolve disputes or comply with applicable obligations may remain with the relevant provider. Deleted records can remain in routine backups until the backups expire. The production backup configuration retains backups for 14 days. Operational logs rotate with bounded storage.
Google Cloud · RevenueCat · Apple
Last updated: 6 October 2026