This Privacy Policy explains how CashierHelper and cashierhelper.com process information, why we process it, and how you can exercise your rights.
CashierHelper is designed to work locally first. Account synchronization is available when you sign in, and the website has separate analytics choices. The mobile app also uses PostHog analytics and error reporting as described below.
Who is responsible for your data?
CashierHelper is published by SARL TEKAPP, 34 rue de Rémusat, 31000 Toulouse, France. TEKAPP is responsible for the processing described in this policy.
For privacy questions or requests, contact contact@cashierhelper.com.
What the mobile app stores
You can count cash and save reports on your device without an internet connection.
Depending on the features you use, the app may store:
- your selected currency and denomination definitions;
- quantities, line totals, the running total, notes, and report dates; and
- local identifiers and information used to retry synchronization.
This information supports the counting and report features. Without an account, the app does not synchronize your reports to Supabase. Mobile analytics may still send the total amount and currency when you save or share a report, as described below.
Optional account and synchronization
CashierHelper offers optional account and report synchronization.
When you create or sign in to an account, Supabase Auth and Supabase Cloud process your account identifier, sign-in email address, profile information, report details, and denomination lines. Reports previously saved without an account are associated with that account. The app then synchronizes reports automatically when a network connection is available, including when the app opens, returns to the foreground, or saves or deletes a report. Access controls limit access to the account owner.
You can use the local counting workflow without an account. Synchronization requires a network connection and an active account session.
Mobile analytics and error reporting
The mobile app uses the PostHog React Native SDK to measure use of its features and report errors. It sends app lifecycle events and events for currency choices, report creation, editing, sharing and deletion, synchronization, and account actions. Saving or sharing a report sends its currency and total amount in minor units. Synchronization events include the number of processed operations.
On iOS, the app reports native crashes, uncaught JavaScript errors, unhandled promise rejections, React rendering errors, and technical failures in storage, authentication, synchronization, and PDF sharing. Diagnostic information includes error messages and stack traces, technical operation names and codes, recent operation steps, screen route templates, app version and build, environment, and device and operating system information. JavaScript diagnostic filters remove recognized credentials, email addresses, URL query strings, and report payload fields. Native crash reports use the native SDK’s reporting pipeline. The app does not record screen sessions.
PostHog assigns a persistent identifier to the app installation and stores analytics data on the device before transmission. When you sign in, the app associates PostHog events with your account identifier and sends your email address and display name to PostHog. The website uses a separate analytics implementation, described below.
What the website processes
The website is a static product site. It does not require a CashierHelper account and does not receive the contents of your mobile reports.
The App Store button links to CashierHelper’s listing. Google Play is marked as coming soon. The homepage has no contact form. Privacy and legal requests can be sent to the contact address published on this site.
The website is hosted on Cloudflare. Cloudflare may process technical request information needed to deliver, secure, and maintain the website.
Optional website analytics
The website uses a consent-based PostHog analytics transport. It starts only after you choose Allow analytics. Choosing Decline prevents analytics from starting. You can change your choice at any time through Privacy choices in the footer or by clearing the site’s stored data.
When enabled, the website sends only these events:
| Event | Properties | Purpose |
|---|---|---|
$pageview |
One of the published routes, its query-free URL, site host, and website language | Understand which pages are viewed |
$pageleave |
The same page properties and how far down the page you scrolled, as a percentage, sent when you leave the page | Measure visit duration, bounce rate, and how much of each page is read |
website_store_click |
Platform, CTA placement, live status, and website language | Understand interest in configured store links |
The browser stores a random pseudonymous identifier so PostHog can distinguish visitors, and a random visit identifier that it renews after 30 minutes of inactivity or 24 hours. Each event includes the visit identifier so PostHog can group the pages of one visit. The website does not attach an email address or mobile report data to that identifier.
The website excludes local development, legal previews, and mock store actions from analytics. It does not use PostHog autocapture, session recording, heatmaps, or exception capture. It does not send cash amounts, denomination values, report contents, email addresses, free-form URLs, or query-string values.
Why we process information
We process information to:
- provide the counting, report, account, and synchronization features you request;
- measure use of the mobile app and diagnose errors;
- deliver and protect the website and its legal pages;
- measure website usage when you have given consent; and
- respond to privacy, legal, security, or support requests.
The legal basis depends on the activity. Requested app features are processed to provide the service, website analytics are processed with your consent, and hosting, security, and legal requests are processed when necessary to operate the service or comply with legal obligations.
Who receives information?
Depending on the feature you use, information may be processed by:
- TEKAPP, to operate CashierHelper and respond to requests;
- Supabase Auth and Supabase Cloud, for account and report synchronization;
- Cloudflare, for website hosting and protection; and
- PostHog, for mobile analytics and error reporting, and for website analytics after you give consent.
These providers receive only the information needed for the service they provide. Their processing locations and transfer safeguards depend on the provider configuration used for CashierHelper.
How long we keep information
We keep each category of information only for as long as needed for its stated purpose or for a legal obligation.
- Local app data remains on your device until you delete the relevant report or app data, subject to any device or backup behavior.
- Account and synchronized report data remains while your account or reports are active, or for as long as needed to meet a legal obligation.
- Mobile analytics, error reports, and diagnostic logs are kept according to the PostHog project settings; the SDK also stores an identifier and queued events and logs on the device.
- Website analytics data is kept according to the PostHog project settings, and your browser keeps the consent choice, pseudonymous identifier, and visit identifier until you clear them or they are replaced. Declining analytics removes both identifiers.
- Website hosting logs and privacy requests are kept according to the applicable Cloudflare settings and the time needed to provide, secure, and document the service.
Your rights
Depending on your situation and applicable law, you may have the right to:
- access your personal data;
- correct inaccurate data;
- request deletion or restriction of processing;
- object to processing in applicable situations; and
- receive your data in a portable format where applicable.
You may withdraw your consent to website analytics at any time. Withdrawal does not affect processing that took place before you withdrew consent.
To exercise your rights, contact contact@cashierhelper.com. You may also lodge a complaint with the Commission Nationale de l’Informatique et des Libertés (CNIL) or another competent supervisory authority.
Changes
We may update this policy when the app, website, providers, or legal requirements change. The date at the top of this page shows when it was last updated.
Contact
For questions about this Privacy Policy or CashierHelper data, contact contact@cashierhelper.com.