Privacy Policy

Privacy Policy

Privacy Policy

Prepared: 21 October 2026. Set the effective and last-updated date when published.

Prepared: 21 October 2026. Set the effective and last-updated date when published.

Prepared: 21 October 2026. Set the effective and last-updated date when published.

1. Controller and scope

CAPSILON BROTHERS Sp. z o.o., ul. Mikołaja Reja 18/34, 43-300 Bielsko-Biała, Poland, is the controller for the TachoAngel Android App and the processing described here. Contact: support@tachoangel.app.

This policy covers the Android App, including an individual PRO subscription purchased through Google Play when that feature is available. The purchase section below does not describe company Fleet billing or its separate payment channel. Availability of a feature in development code does not mean it is available in the published App.

2. What stays on the device

The App reads tachograph and driver-card information for its driving-time functions. Depending on the features you use, this can include driving and rest times, card-holder data, DDD files, saved Bluetooth device details, documents and expiry dates, and local alert history. When the planned PRO functions become available, the Daily Report can create a local shift report and archive from available tachograph and card data, and the Ferry Assistant can keep the state of a crossing locally on the device. These data are generally stored in the App’s private storage on your device. You can choose to export or share files using Android; the destination you choose then receives them.

The App does not routinely upload DDD files or the full contents of a driver card to our billing backend. This statement does not cover diagnostic information described in section 5 or identity data you expressly submit when joining a Fleet organisation, described in section 6. Android system backup is disabled for the App. Local files do not have additional App-level encryption.

3. Sign-in and account data

The App uses Google Sign-In and Firebase Authentication. We process the email address, Firebase user ID (UID), display name and profile photo URL supplied for your account. Firebase may process your IP address for security and abuse prevention. We use these data to sign you in, identify your account, and support the service.

4. Individual PRO and Google Play Billing

When you choose to buy or manage individual PRO, Google Play handles the purchase and payment method under its own terms and privacy information. We do not receive your full payment-card number from Google Play Billing.

The App sends a Google Play purchase token with your Firebase sign-in credential to our entitlement backend. We use the token and Google Play Developer API to verify the purchase, recognise the product and plan or offer, check subscription state and paid period, acknowledge eligible purchases, and provide or remove PRO access. Our backend can store the raw purchase token in a protected subscription record, a token hash, your UID, product and plan identifiers, relevant purchase or order identifiers and status, period dates, and an entitlement record. Google Play may receive an obfuscated account identifier derived from your UID to associate the purchase with the correct App account; we do not send your email as that identifier.

The backend can receive Google Play real-time subscription and voided-purchase notifications and re-check the purchase with Google. If you enter or receive a partner or promotion code, we may process that code and its attribution or offer status to decide which Google Play offer is available and to administer the promotion. The install referrer can initially be saved on your device. We do not use these purchase records for advertising.

This section applies when a build with PRO purchasing is actually made available. The exact Google Play products, plans, offers, and data fields used in production must be checked before publication.

5. Diagnostics, security, and other Google services

Firebase Crashlytics collects crash and error reports, including stack traces, device model, operating system and App version, an installation identifier, App state and short technical logs. It can operate from the first launch, before sign-in. We use reports to investigate stability problems. We do not deliberately attach your Firebase UID to Crashlytics reports. In some earlier App versions, logs from rare error cases could include a driver-card number or the Bluetooth address or name of a tachograph. Later diagnostic changes are designed to mask such values; a new release does not erase reports already collected.

In Google Play builds, Firebase App Check and Google Play Integrity process App information, device attestation data and a token to help protect Firebase requests. On Android 11 and older, Android may request location permission for Bluetooth scanning; the App does not use that permission to read or store your location. Automatic connection uses Bluetooth system events, not physical-activity recognition. Google ML Kit text recognition processes image pixels on the device when that function is used. The App does not include advertising or Firebase Analytics in the current release line.

6. Optional Fleet join from the Android App

If a version of the App offers joining a Fleet organisation and you choose that function, the App can send your authenticated UID, join code, and driver-card identity (card number, card-holder name and issuer) to our backend. The backend uses these to verify membership and associate you with the organisation; relevant identity and membership information can then be available to its authorised administrators. This is separate from buying individual PRO through Google Play. The actual production flow and the organisation’s role in processing these data must be confirmed before this section is published.

7. Purposes, legal bases, and recipients

For EEA and UK users, the proposed bases are performance of the service contract for sign-in, purchase verification and PRO access; our legitimate interests in protecting the service and diagnosing errors; and legal obligations where transaction records must be retained. The final legal basis for each data category, any balancing assessment, and any additional consent requirement need legal review.

Google provides Firebase Authentication, Crashlytics, App Check, Play Integrity and Google Play Billing. Our entitlement backend uses Google Cloud/Firebase services. Google may process information outside the EEA under the safeguards applicable to its services. When you voluntarily share a file, its recipient is determined by the Android destination you choose. Fleet organisation access, when available, is described in section 6. We do not sell App or purchase data.

8. Retention and deletion

Account profile data remain while the account is active, subject to a deletion request and any data we must retain. Local App data, including any saved Daily Reports or Ferry Assistant session, remain on your device until you delete them or clear the App’s storage; uninstalling removes App-private storage. A version’s in-App Delete account function can remove the Firebase Authentication account and selected local data, but it must not be treated as proof that all backend purchase, promotion, Fleet or diagnostic records, or all local PRO data, have been deleted.

Purchase tokens, entitlement and transaction records are kept for the periods needed to administer a subscription, resolve disputes, prevent fraud and comply with applicable duties. The exact field-by-field periods and deletion process are still being defined and must be inserted here before publication. Crashlytics reports follow the provider’s retention period and are not necessarily removed when you delete your TachoAngel account. Support correspondence is kept while handling your request and, where necessary, potential claims.

To request account and associated-data deletion, use the App’s Settings → Delete account function where available and see https://tachoangel.app/en/account-deletion, or email support@tachoangel.app. We may need to verify the request. Deleting your TachoAngel account or uninstalling the App does not cancel a Google Play subscription; manage it separately at https://play.google.com/store/account/subscriptions. Some records may have to be retained under applicable law. The account-deletion page and backend process must be reconciled with this policy before publication.

9. Your rights

Depending on applicable law, you may request access, correction, erasure, restriction, portability, or object to processing, and may complain to a competent data-protection authority. Contact support@tachoangel.app to exercise your rights. Where processing relies on legitimate interests, you may object on grounds relating to your situation. The exact scope of a right may depend on legal exceptions.

10. Security and updates

Traffic to Google/Firebase and our backend uses HTTPS/TLS; Bluetooth communication uses the Android Bluetooth stack. We restrict backend access to account and subscription records. No online service is risk-free.

We update this policy when the App or its processing changes. The published page should state its effective date and match the App version, Google Play Data Safety form, and account-deletion information available at that time.