DriveBy

Privacy Policy - DriveBy

Effective date: 2026-07-05 Document version: 1.3 Controller: DriveBy - [email protected]

1. Scope

This Privacy Policy explains what data the DriveBy Android application ("App") processes, why, and what your rights are under the General Data Protection Regulation (Regulation (EU) 2016/679 - "GDPR").

DriveBy is a personal profit calculator for couriers working with food-delivery platforms. The App is not affiliated with, endorsed by, or connected to Glovo, Uber Eats, Bolt Food, Wolt, DoorDash, Deliveroo, Stuart, or any other delivery platform.

2. Data we DO NOT collect

DriveBy is designed around the principle of data minimisation. We do not collect, store, transmit, or sell:

Your name, phone number, or postal address
Your card number or billing address - payment data is handled entirely by our Reseller (Merchant of Record) and never passes through the App or our servers (see 3.4-3.5)
Your precise location, GPS coordinates, or movement history
Any photographs, screenshots, or images
Any screen content from delivery platforms - text recognised on-device by the Accessibility Service or ML Kit is held in memory only for the duration of one calculation (typically under 200 ms) and is then discarded
The amounts or distances of any individual order you receive
The identity of the merchants, restaurants, or addresses involved in your orders
Your delivery platform account credentials

The App contains no network calls to any delivery platform's API.

3. Data we DO process

3.1 Stored locally on your device only

The App stores the following on your phone (and never transmits it to any server):

Vehicle profile data you enter manually: name, fuel type, fuel consumption (L/100 km), fuel price (€/L), wear cost (€/km), minimum acceptable profit (€).
App preferences (e.g. whether onboarding has been completed, currently active vehicle profile).
Optional calculation history (you choose whether to save it).

This data lives in the App's private storage (Room database). The App itself never sends it to our servers; we have no access to it.

Backup to your own Google account (Android Auto Backup). If you have Android's "Back up to Google" feature enabled (Settings → Google → Backup), Android automatically includes the above on-device data - your vehicle profiles, calculation history and app preferences - in your own Google account backup, so you can recover it after reinstalling the App or setting up a new phone. This backup belongs to you and is governed by Google's terms; we never see, receive or store it. Screen content from delivery apps is never backed up - it is never written to disk in the first place. Subscription/billing state and per-device settings are excluded from the backup. You can turn this off at any time in your Android backup settings (or disable backup for DriveBy specifically). Uninstalling the App deletes the on-device copy.

Manual backup to a file you control. From Settings you can also export a full backup of your on-device data (vehicle profiles, calculation history, work sessions and your tax/fee settings) to a single JSON file that you save wherever you choose through the Android system file picker (your own storage, Google Drive, etc.), and import it back later or on another phone. This file is created by you, stays entirely under your control, and is never sent to us. As with the automatic backup, it contains no screen content and no individual order data from delivery apps - that is never stored in the first place.

3.2 Anonymous diagnostic telemetry (Firebase Analytics)

When the App detects an order on screen and calculates a result, it sends a small bucketed event to Firebase Analytics:

platform (e.g. glovo, wolt)
distance bucket (e.g. 3-5km) - never the exact value
fee bucket (e.g. 4-5eur) - never the exact value
whether the result was profitable for you (true/false)
end-to-end latency in milliseconds

Bucketing is deliberate: we measure platform-level distributions and parser accuracy without ever observing the financial details of any individual courier or order.

3.3 Crash diagnostics (Firebase Crashlytics)

If the App crashes, Firebase Crashlytics records the stack trace, Android version, device model, and the App's build type. This is essential for fixing bugs that affect your earnings during a shift.

3.4 Subscription state

Your trial and subscription are sold and managed by our Reseller acting as Merchant of Record (see Sub-processors). Our licence server confirms only an entitlement signal (active trial / active subscription / inactive) tied to your purchase e-mail - no payment details whatsoever (card number, billing address, etc.) pass through the App or our servers; those are held by the Reseller.

3.5 Your e-mail address (subscription identity and optional waitlist)

Because DriveBy is not distributed through an app store, we verify your subscription by e-mail instead of a store account:

When you unlock the App you enter the e-mail address tied to your purchase and confirm it with a one-time code (a "magic link"). We process this e-mail only to (a) send you the one-time code and (b) check, against our Reseller's records, whether that e-mail has an active trial or subscription. There are no passwords and no separate user account.
If you choose to join our pre-launch waitlist on the website, we store the e-mail you submit solely to notify you when DriveBy becomes available - together with the page language and your country (taken from our hosting provider's request geolocation at the moment of sign-up; the IP address itself is not stored), so the launch notice only goes to people in countries the App actually supports. You can unsubscribe at any time.

The one-time codes (and any waitlist notifications) are sent through our e-mail provider, and the entitlement check runs on our licence server; both are listed under Sub-processors. On our servers we store at most your e-mail address, current entitlement status (active / inactive) and a count of the devices that have been activated with your subscription. The device count exists only to enforce a reasonable limit (a subscription may be used on up to three devices) and to stop one purchase being shared across many phones; it is a random per-installation identifier, not a hardware serial, and carries no personal information. We never store the financial details of any order.

3.6 App updates

Because DriveBy is installed from our website rather than an app store, the App periodically checks https://driveby.dev for a small version manifest to tell you when a newer version is available, and - only if you choose to update - downloads the new installer file from there. Like any request to a website, this involves your device's IP address and is handled by our hosting provider (Cloudflare, see Sub-processors); we do not use it to build a profile of you or link it to your identity.

4. Legal basis for processing

Purpose	Legal basis (GDPR)
Calculating profit on your device	Performance of the service you requested (Art. 6(1)(b))
Anonymous bucketed diagnostics	Our legitimate interest in improving service quality (Art. 6(1)(f)) - the data is not linked to your identity
Crash diagnostics	Our legitimate interest in product stability (Art. 6(1)(f))

We do not engage in profiling under Art. 22 GDPR, and we do not make automated decisions that produce legal effects concerning you.

5. Sub-processors

We use the following processors. Each is bound by a data-processing agreement and, for any transfer outside the EU/EEA, the Standard Contractual Clauses. We remain the Controller.

Google LLC / Google Ireland - Firebase Analytics, Crashlytics and Remote Config, europe-west1 region (Frankfurt, Germany; Remote Config is a one-way pull of parsing patterns, not telemetry). Google also provides Android Auto Backup to your own Google account (see 3.1). Governed by the Google Cloud EU Data Processing Addendum.
Lemon Squeezy (Merchant of Record) - processes your subscription purchase and holds the purchase e-mail plus billing/payment data as the seller of record. For the payment and tax records it must keep by law it acts as an independent controller; for our entitlement lookup it acts as our processor.
Resend - delivers the one-time login codes (and, at launch, waitlist notifications) to your e-mail address.
Cloudflare, Inc. - hosts the driveby.dev website, runs our licence server (the entitlement worker that checks your e-mail against the Reseller) and routes e-mail sent to our support address.

We do not sell your data or use it for advertising.

6. Retention

On-device data: until you uninstall the App or delete the data within Settings.
Firebase Analytics events: 14 months (default Google Analytics retention).
Crashlytics traces: 90 days.

7. Your rights under GDPR

You have the right to:

Access (Art. 15) - request a copy of any data we hold linked to your installation. In practice, the only personally-linked data is in your own device storage; we have nothing on our servers tied to you.
Rectification (Art. 16) - you control all vehicle/profile data directly in the App.
Erasure / "right to be forgotten" (Art. 17) - uninstall the App, or request deletion of Firebase Analytics data tied to your install ID by emailing us.
Restriction (Art. 18) and Objection (Art. 21) - you can ask us to stop processing your anonymous analytics by emailing us, or simply uninstall the App.
Portability (Art. 20) - you can export your calculation history as CSV, or your full on-device data as a JSON backup file, directly from the App.
Lodge a complaint with a supervisory authority - in Poland: Prezes Urzędu Ochrony Danych Osobowych (UODO), ul. Stawki 2, 00-193 Warszawa.

To exercise these rights, e-mail: [email protected]. We respond within 30 days as required by GDPR.

8. Children

DriveBy is intended for couriers, who must be at least 18 years old in most jurisdictions to work for a delivery platform. We do not knowingly collect any data from anyone under 18.

9. Security

All data sent to Firebase and to our licence server travels over TLS 1.2+ with certificate pinning where applicable.
We never store credentials of any kind, nor your card details or delivery-platform logins - payment data stays with our Reseller.
The entitlement token our licence server issues is short-lived and cryptographically signed, and is verified on-device.

10. Changes to this Policy

We may update this Privacy Policy as the App evolves. The current version is always linked from the App's "About" screen and at:

https://driveby.dev/legal/privacy-policy

Material changes will be announced in-app at least 14 days before they take effect.

11. Contact

DriveBy (Controller) e-mail: [email protected] Country of registration: Poland (EU)

Polish version: Polityka prywatności (PL). In case of any conflict, the English version prevails for legal purposes; the Polish translation is provided for the convenience of Polish-speaking users - except where Polish mandatory consumer-protection law requires otherwise.

DriveBy · [email protected] · driveby.dev