Cash Reader Privacy Policy

Last updated: September 8, 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 Meta Pixel and the AppsFlyer Web SDK to measure page visits and download actions, and it sends your email address and message to Web3Forms only if you choose to submit the contact form. These uses are described below.

Who we are

Cash Reader is provided by Cash Reader s.r.o., which is the data controller:

For any privacy question or request, contact us at [email protected].

Information the app does not collect

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

Page visits and download actions. The main website pages initialize Meta Pixel and the AppsFlyer Web SDK. Meta Pixel records a PageView when one of these pages loads. The AppsFlyer Web SDK measures website visits. When you activate a Download button, 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. If you arrive with utm_source=facebook, utm_source=fb, or a fbclid URL parameter, the website stores the campaign name, ad set, ad, fbclid, landing time, and a fixed website channel value in your browser’s sessionStorage. On that attributed arrival, it records one website_visit event per page session in AppsFlyer, 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.

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.

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:

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:

The optional photo submissions are used only to improve recognition and are not shared beyond this storage.

Your choices

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 analytics data is retained only for as long as it is useful, in line with the providers’ standard retention. 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 is 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 [email protected] 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

[email protected]