Cash Reader Privacy Policy
Last updated: September 25, 2026
This Privacy Policy explains how Cash Reader handles information. It covers the Cash Reader mobile apps for iOS and Android and the Cash Reader website at cashreader.app. Cash Reader helps people who are blind or have low vision identify banknotes: you point your device camera at a banknote and the app says its value out loud.
The short version: the Cash Reader apps have no user accounts and do not ask for your name, email, or other identifying details. Banknote recognition runs on your device. The apps use a few standard third-party tools for crash reporting, analytics, and advertising measurement. The website uses Google Analytics 4, Meta Pixel, and the AppsFlyer Web SDK for visit, download, and advertising measurement only if you choose Accept. You can choose Reject and still use the website. If you submit the contact form, your email address and message are sent to Web3Forms independently of your website measurement choice. These uses are described below.
Who we are
Cash Reader is provided by Cash Reader s.r.o., which is the data controller:
- Cash Reader s.r.o.
- Udolni 408/52, 602 00 Brno, Czech Republic
- VAT ID: CZ06797580
For any privacy question or request, contact us at support@cashreader.app.
Information the app does not collect
- No accounts. Cash Reader has no sign-up or sign-in. We do not ask for your name, email address, phone number, or a password.
- No personal information through input fields. The app does not ask you to enter personal details.
- No precise location. The app does not collect GPS or other precise location data.
- No address book, photo library, or microphone data. The app uses the camera only, as described below.
Information the app does collect
Camera. Cash Reader uses your camera to read banknotes. The camera image is processed on your device to recognize the banknote. It is not uploaded or stored as part of normal use. The one exception is the optional photo submission described below, which you start yourself.
Crash reports and analytics. Cash Reader uses Google Firebase for crash reporting and for aggregated usage analytics. This collects technical information such as device model, operating system version, app version, language, crash logs, and counts of in-app events. It is aggregated and is not used to build a profile of you as an individual.
Advertising measurement. So that we can see which of our own ads bring new users and how the app performs, Cash Reader uses AppsFlyer (marketing attribution) and the Meta (Facebook) SDK for basic app events. These tools collect device and usage data in an anonymous or aggregated form. On Apple devices this is governed by Apple’s App Tracking Transparency: if you decline the prompt the app shows during onboarding, these tools do not track you.
Information the website handles
Website measurement choice. The website offers Accept and Reject for Google Analytics 4 (GA4), Meta Pixel, and the AppsFlyer Web SDK together. These services use cookies or similar technologies for website measurement. Before you choose, or after you choose Reject, the website does not load their scripts or send them page-visit pings or download events. Your choice is stored in your browser’s local storage so the website can remember it. You can reopen this choice using the button in this section and withdraw consent at any time. If you reject after allowing measurement, the website clears saved Facebook campaign attribution and reloads the page to stop the active services. Rejection then blocks future website measurement; it does not undo data already sent while consent was active. This website choice does not affect analytics in the Cash Reader apps or a contact form submission you choose to make.
Page visits and download actions after choosing Accept. GA4 measures page visits using the page path and referring page, along with information that can be derived from the request, such as browser and device details and approximate location. The website supplies GA4 with page and referrer URLs stripped of query strings and fragments. Meta Pixel records a PageView when a measured page loads. The AppsFlyer Web SDK measures website visits. When you activate a Download link in the navigation or on the homepage, the website records a download_click event in AppsFlyer with the current page and any available campaign attribution, and records a Meta Lead event identified as a download click. These event names and values come from the website implementation; the website does not create a Cash Reader user account.
Facebook campaign attribution after choosing Accept. If you arrive with utm_source=facebook, utm_source=fb, or a fbclid URL parameter while website measurement is allowed, the website stores the campaign name, ad set, ad, fbclid, landing time, and a fixed website channel value in your browser’s sessionStorage. The website uses AppsFlyer to measure attributed website visits, including the campaign fields, fbclid, and landing page. For up to 30 minutes, the stored record is also used to route Download buttons through an AppsFlyer OneLink URL; the subsequent download_click event includes the source, campaign, ad set, ad, and current page. An expired attribution record is ignored and removed when the website next checks it. Before a choice or after Reject, the website does not store this attribution or rewrite Download links to OneLink.
Language preference. If you choose a website language, the language code is stored in your browser’s localStorage so the website can offer that language again.
Contact form. If you choose to submit the website contact form, the email address and message you enter are sent over HTTPS to Web3Forms, which delivers the submission to us. The website has no account system, and the form is not submitted unless you activate its Submit button.
Optional photo submission
Cash Reader includes one optional feature that lets you send a photo of a banknote to us, for example to report a recognition problem. It is turned off by default.
- It is opt in. The button that submits a photo is hidden until you turn it on in the app settings.
- Submitted photos are stored on Amazon Web Services (AWS), kept only for a reasonable time, used to improve banknote recognition, and then deleted.
- They are anonymous (photos of banknotes, not linked to your identity) and are never shared with third parties.
If you never enable this feature, no photos are ever sent.
On-device processing and offline use
Banknote recognition runs entirely on your device. After a one-time download of a currency, Cash Reader works fully offline. We operate no account system, and the only content you can send through the app is the optional photo submission above. The separate website contact form is described under Information the website handles.
Purchases
Cash Reader offers a paid version. Purchases and subscriptions are handled by the Apple App Store and Google Play. We never see or store your payment card details. Billing, receipts, and cancellations are managed through your Apple or Google account.
How we use information
We use the limited information described above only to:
- operate and provide the app,
- keep the app stable and fix bugs (crash reports),
- understand how the app is used, in aggregate (analytics),
- measure and improve our advertising (attribution), subject to your tracking choice on Apple devices,
- if you choose Accept, measure website visits and download actions through GA4, Meta, and AppsFlyer, and preserve Facebook campaign parameters while routing a Download link,
- deliver and respond to a website contact message you choose to send,
- improve banknote recognition (only the optional photos you choose to send).
We do not sell your information.
Service providers and sharing
We do not sell personal data. We share limited data only with the service providers below, which process it on our behalf to provide the functions described above:
- Google Firebase (Google): crash reporting and aggregated analytics. Privacy
- Google Analytics 4 (Google): website visit measurement, if you choose Accept, using page paths, referrer source, browser and device information, and approximate location. How Google uses information from sites and apps · Analytics privacy
- AppsFlyer: marketing attribution in the apps and website visit, campaign, and download-action measurement through its Web SDK; app tracking on Apple devices is subject to your App Tracking Transparency choice. Privacy
- Meta Platforms: the Facebook SDK for basic app events and Meta Pixel for website page views and download-action measurement; app tracking on Apple devices is subject to your App Tracking Transparency choice. Privacy
- Amazon Web Services (AWS): secure storage for the optional photos you choose to submit. Privacy
- Web3Forms: processing and delivery of the email address and message you choose to submit through the website contact form. Privacy and GDPR information
The optional photo submissions are used only to improve recognition and are not shared beyond this storage.
Your choices
- App Tracking Transparency (Apple devices). When the app asks for permission to track during onboarding, you can decline, and the advertising measurement above will not track you. You can change this later in your device settings.
- Optional photos. Leave the photo submission feature off (its default) and no photos are ever sent.
- Website contact. You can contact us by email instead of submitting the website form. If you do not submit the form, it does not send an email address or message to Web3Forms.
- Website measurement. Choose Reject when first asked, or reopen the choice using the button in Information the website handles above and choose Reject to withdraw consent. The website clears saved Facebook campaign attribution when you reject. You can also clear the website’s
sessionStorageandlocalStorageusing your browser controls. Clearing these values removes the saved measurement choice, campaign attribution, and language preference. It does not undo measurement already sent to Google, Meta, or AppsFlyer while you allowed it. - Stop app collection. You can stop collection by the app at any time by uninstalling it.
Children’s privacy
Cash Reader is not directed at children and does not knowingly collect personal information from children. Because there are no accounts and no personal input fields in the app, the app does not gather the kind of personal information covered by laws such as COPPA. If you believe a child has provided us with personal information through the website contact form or otherwise, contact us and we will address it.
Data retention and deletion
Because there are no accounts, there is no Cash Reader account profile for us to keep or delete. Crash and app analytics data is retained only for as long as it is useful, in line with the providers’ standard retention. Website GA4 data, when you allow website measurement, is subject to the property’s retention settings and Google’s policies; we do not state a fixed period here. Optional photo submissions are deleted after a reasonable time. The website uses a Facebook campaign attribution record only while it is less than 30 minutes old and removes it when it next finds the record expired; its once-per-session marker is stored in sessionStorage, and its language preference and website measurement choice are stored in localStorage. Retention by Meta, AppsFlyer, and Web3Forms is governed by their policies linked above; we do not assign a different provider-side retention period here.
Your rights
Depending on where you live, you may have rights over your personal data, such as the right to access, correct, or delete it, under laws like the EU and EEA General Data Protection Regulation (GDPR). If you have a request or a question, contact us at support@cashreader.app and we will help.
Security
Recognition happens on your device, and we run no account system, so there is no account database. The data described above—including crash and analytics data, website measurement, a website contact message, and any optional photos you submit—is processed by the applicable providers (Google, AppsFlyer, Meta, AWS, and Web3Forms); their policies are linked under Service providers and sharing.
Changes to this policy
We may update this Privacy Policy as the app evolves or as the law requires. When we make a material change, we will update the date at the top of this page.
Contact
Cash Reader s.r.o., Udolni 408/52, 602 00 Brno, Czech Republic