CardJar Privacy Explained: An Account-Free Loyalty Wallet That Keeps Cards on the Device
CardJar's published privacy model starts with absence: no CardJar account, no email address, no advertising identifier, no in-app analytics and no CardJar server holding the user's loyalty-card list. Cards are stored in the app's private storage on the device.
What stays on the phone
The collection, card numbers, names, colors and count remain on the device. The 508-scheme retailer catalogue is compiled into the app rather than fetched each time, so opening a known retailer card does not reveal that choice to a logo server.
Camera scanning and screenshot import also run locally. CardJar reads the barcode and nearby words using models included in the app. Camera frames are processed and released rather than saved by CardJar.
With backup left off, the official privacy page says the app makes no network requests.
The outbound paths CardJar documents
Privacy is more useful when exceptions are named precisely.
Android system backup
Android's own backup can carry CardJar data into the user's Google account as part of normal device backup and transfer. CardJar says this is Android's mechanism: the company does not receive the backup or request it through CardJar servers.
Encrypted export file
A user can seal the collection into one file with a chosen passphrase, then save or share that file through the operating system. CardJar does not keep a copy of the file or passphrase.
Card sharing
A shared card is placed after the hash symbol in the URL. Browsers do not transmit that fragment to the web server. The recipient receives a copy rather than a permanently synchronized shared object.
Wear OS favorites
Favorite cards move across the existing paired-phone connection to the CardJar Wear OS app. The watch stores its own copy. CardJar says this transfer does not reach its systems.
Local controls
CardJar can require fingerprint, face or PIN unlock when the app opens. When the lock is active, Home Screen quick actions stop naming saved retailers. That detail prevents a locked phone's launcher menu from exposing the shopping list the lock is meant to protect.
Uninstalling removes the on-device collection. Separately exported files remain wherever the user saved them, and Android backup follows the operating system's retention behavior.
What the public evidence supports
Apple's App Store listing identifies Convert Case Ltd as the developer and reports “Data Not Collected” based on the developer's disclosure. CardJar's own privacy page goes further by itemizing outbound requests and the behavior of import, backup, sharing and watch transfer.
Review the product on CardJar's official site and inspect the full privacy policy before deciding whether its model matches your requirements.
Frequently asked questions
Does CardJar require an account?
No.
Does CardJar use in-app analytics?
The official site and privacy policy say the app does not.
Can I move my cards to another phone?
Yes, through normal Android transfer/backup where applicable or an encrypted CardJar export file.
Can CardJar read my exported file?
CardJar states that it does not hold the passphrase and cannot open the file.
Verified sources
