CrumbCheck Privacy Policy
How Alexandr Korsak (Bitscorp) collects, uses, and stores data in the CrumbCheck mobile app (co.bitscorp.crumbcheck).
Privacy Policy
Effective date: 14 November 2026. I take your privacy seriously. This notice explains what CrumbCheck stores on your device, what (if anything) leaves the device, and how to contact me.
Alexandr Korsak (Bitscorp), a self-employed professional (autónomo) in Spain, operates the mobile application CrumbCheck (co.bitscorp.crumbcheck). Bitscorp is a trading name, not a registered company. This page applies to CrumbCheck on iOS and Android. The website https://bitscorp.co has a separate Privacy Policy and Terms and Conditions.
The app
CrumbCheck checks a packaged food against allergy and diet profiles you keep on the device. You scan a barcode, look the product up, or photograph an ingredient label. Label text is read on the device. Product facts for a barcode come from Open Food Facts. There is no CrumbCheck account.
Data stored on your device
- Profiles (a name or label you choose, allergen and diet selections, custom ingredient words), scan history, ingredient text, verdicts, and saved product details in a local SQLite database.
- Ingredient-label text recognized on the device from the camera or a photo. That image is not sent to a cloud vision service.
- Allergy-card files while you generate them.
Data that leaves your device
- Allergy profiles and scan history are not uploaded to a Bitscorp server.
- When you look up a barcode, the app sends that barcode to the Open Food Facts API, with a User-Agent that names CrumbCheck, bitscorp.co, and the operator address alex@bitscorp.co. It does not send your profile, your name, or a device advertising identifier. The response (product name, brand, ingredients, allergen tags, and an image address) is saved on the device. Showing the product photo then loads that image from Open Food Facts.
- A history export or an allergy card leaves the device only when you choose to share the file.
- If you send feedback, your email app may include the app version, build number, operating system, and device model in a message to alex@bitscorp.co.
- Purchase and subscription status are handled by Apple or Google and RevenueCat, as described below.
Permissions
- Camera (optional): to scan a barcode or photograph an ingredient label. You can type a barcode or ingredients by hand.
- Photo library (optional): to read a photo of a label for on-device text recognition.
You can change or withdraw permissions in the operating system settings.
Sensitive information
Allergy and diet profiles, and the foods you scan, can be health information. They stay on your device unless you share an export or an allergy card. A barcode lookup sends the barcode, not the profile.
Analytics and crash reporting
CrumbCheck does not include a third-party analytics or crash-reporting SDK. I do not run Mixpanel, Google Analytics, Firebase, Sentry, or a similar product inside this app. The stores and RevenueCat may keep their own purchase or install records under their policies.
Third parties
I only involve the parties below for the purposes stated. Each has its own privacy policy.
- RevenueCat: To check and restore your Pro entitlement. RevenueCat receives purchase tokens, subscription status, and an anonymous app user identifier. It does not receive the journal, photos, files, or other content you keep in the app.
- Apple: If you buy or manage a subscription or a lifetime purchase on the App Store, Apple processes the payment. We do not receive your full payment card number.
- Google: If you buy or manage a subscription or a lifetime purchase on Google Play, Google processes the payment. We do not receive your full payment number.
- Open Food Facts: When you look up a barcode, Open Food Facts receives that barcode and a User-Agent naming the app. Product text and images in the response come from Open Food Facts. Your allergy profile is not included.
Accounts, servers, and retention
No Bitscorp server. Profiles and scans stay in on-device SQLite. Barcode lookup calls Open Food Facts. Label text recognition does not leave the device.
CrumbCheck does not require a Bitscorp account. Information stored only on your device remains there until you delete it in the app or uninstall the app. Purchase records are kept by Apple or Google and by RevenueCat for as long as they need them to provide the subscription. If you email me, I keep the message long enough to respond and then delete it when it is no longer needed.
Your rights
Because most CrumbCheck content never leaves your device, the practical way to access or delete it is in the app, or by uninstalling the app (which removes local data). For any personal data I hold in email, or questions about purchase records, write to alex@bitscorp.co. If you live in the European Economic Area, the United Kingdom, or another region with similar rights, you may also request access, correction, deletion, or a restriction of processing of personal data I hold, and you may lodge a complaint with your local supervisory authority. In Spain that authority is the Agencia Española de Protección de Datos (AEPD).
International processing
I am based in Spain. Apple, Google, and RevenueCat may process purchase data in other countries. Their policies describe those transfers.
Changes to this policy
This Privacy Policy is effective as of 14 November 2026. I may update it from time to time. The current version will always be at https://bitscorp.co/crumbcheck/privacy. Material changes will be reflected on this page, and I may also note them in the app.
Contact
Questions about this policy or about CrumbCheck: alex@bitscorp.co. There is no telephone contact number. Related pages: CrumbCheck Terms and Conditions, and the list of Bitscorp app policies.