What data is processed?
When you add a loyalty card, AveRich Cards may locally store the card name, barcode value, barcode type, a category, your choice of overview image, and optionally photos of the front and back. Technical creation and modification timestamps are also stored. A barcode or card number may be linked to a customer account by the card issuer; AveRich does not retrieve that external account.
Local storage
Card data and optional card photos are stored in the local SQLite database cards.db inside Android’s app environment. AveRich Cards has no INTERNET permission and the developer has no access to the contents of your cards.
Camera and barcode scanning
AveRich Cards requests camera access for two features you start yourself: scanning a barcode and optionally taking a photo of the front or back of a card. Camera frames from barcode scanning are not stored as barcode photos; after a scan, the barcode value and detected type are saved. Card photos you deliberately take are stored locally with the card.
Automatic barcode detection
During a camera scan, AveRich Cards automatically uses the detected barcode type. With manual entry, valid EAN-8, UPC-A, and EAN-13 codes are detected automatically; other values are handled as Code 128. The visible barcode is regenerated each time from the stored value and type.
Categories and overview
Cards can automatically infer one of 20 local categories from the card name. You can change the category manually and choose whether the overview automatically uses a card photo or a bundled AveRich illustration. These settings remain local in cards.db.
No account, ads, or tracking
AveRich Cards requires no user account and uses no advertising, analytics, tracking software, or profiling. The app does not need internet access for its own operation.
Backups
You can choose a backup folder yourself. When this feature is active, AveRich Cards keeps a copy of cards.db there; that database also includes any card photos and category settings. The previous external snapshot may be kept as cards_previous.db. With Share backup, the app creates a checked database copy and then opens the standard Android share sheet. You choose which app, storage location, or service receives the file.
Restore backup
When you choose a backup file to restore, AveRich Cards first checks SQLite integrity and the expected database schema. The app uses a local rollback to protect the active database if the restore process cannot be completed correctly.
Sharing with third parties
The developer does not collect, sell, or share your card names, barcodes, card photos, or category data with third parties. Only when you choose to share a backup through another app or service does that file leave the local AveRich Cards environment at your request.
Deleting data
Loyalty cards can be deleted within the app. When the app is removed, Android removes the locally stored app data. Files you saved yourself in an external backup folder or shared through another service must be deleted there by you.
Security
The active database is stored inside Android’s protected app environment. Automatic Android app backup is disabled for AveRich Cards; external backups are created only through the AveRich Cards backup features you choose.
Changes to this privacy policy
This privacy policy may be updated when AveRich Cards functionality changes. The latest version is published on this page.
Contact
Developer:AveRich
Netherlands
For questions about this privacy policy:info@averich.nl.