Privacy Policy
1. Who we are
Driverpoint (“we”, “us”, “the Service”) operates a crowdsourced, anonymous driver-density radar for gig-economy workers. This Privacy Policy explains what we collect, why, how long we keep it, who we share it with, and the choices you have.
Contact for privacy questions, access, or deletion: legal@driverpoint.app
If we later publish a registered company name and postal address, they will appear in this policy and on https://driverpoint.app/privacy. Until then, email is the official channel.
2. Scope
This policy covers the Driverpoint mobile app (iOS and Android), our API, and the public pages at driverpoint.app (including /privacy and /terms).
It does not cover third-party sites or apps you open from Driverpoint (for example a partner offer, the App Store, or Google Play). Those services have their own policies.
3. Data we collect
We collect only what we need to run Driverpoint. Categories:
Account: email address; first and last name; password hash if you register with email (we do not store your password in plain text); Sign in with Google or Apple identifiers (Google sub / Apple sub); email verification time; language (English or Spanish); account creation and update times.
Onboarding choices: the home city you pick (country, region, city name, place key, approximate coordinates, timezone) and the gig platforms you say you drive for (for example Uber, Lyft, Uber Eats, DoorDash). This is not a GPS history of your house.
Location while your shift is ON: approximate coordinates sent at the ingest cadence (movement and rate limits) so you can see the live radar and contribute anonymous presence. Live radar requires shift ON and “Always” / background location permission. When the shift is OFF, we stop using you as a live peer on the map.
Shift records (Pro): start and end of each shift, distance in meters accumulated on the server, a last-ping coordinate used only to compute that distance while the shift is open, home city snapshot for that shift, and optional earnings you type in by platform (we store amounts, not your bank or wallet). We do not store a turn-by-turn trip route.
Your zones: names, polygons you draw, and alert thresholds (full / empty / stagnant).
Community reports and comments: title, body, topic, city, platform, echoes (votes), comments and replies, and a snapshot of your first and last name on the report at the time you post it. Other drivers in that city can read this content. We do not collect photos in reports.
Assist / SOS: problem type (for example battery, tire, fuel, other), the map point of the request, status, who created it, and who accepted it. Nearby drivers can see an active request. If you connect to professional help, that partner receives what they need to respond (typically location and problem type). Assist is not a substitute for emergency services.
Alerts inbox: zone alerts and operational announcements we send you, and when you last opened Alerts.
Rewards / partner offers: if you tap an offer, we log that you opened it (user, offer, tracked URL, time) so we can operate the program. The partner site may collect its own data.
Purchases: Pro entitlement and store metadata via Apple, Google, and RevenueCat (product, expiration, renewal, store). We do not store full payment card numbers. The store is the merchant of record.
Push tokens: a device token so we can send zone alerts, Assist, ops announcements, and account/session notices you allow.
Sessions: signed-in sessions and refresh tokens (limited number of devices) so we can keep you logged in and revoke a session if needed.
Diagnostics: crash reports (Firebase Crashlytics) and optional performance telemetry (Grafana Faro). Telemetry is limited to a user id (UUID) and technical signals — not your name, email, or a map trail. You may see this switched by remote configuration.
Support: whatever you send to legal@driverpoint.app or another contact we publish.
We do not collect: precise individual trip routes; your vehicle identity on the map; government ID; photos in community reports; full card numbers; contacts; microphone; or advertising profiles.
4. How we use data
To create and secure your account, verify email, and remember language and onboarding.
To run the anonymous radar (heatmap and peer dots) only from presence shared while your shift is ON, without showing your name or vehicle on the map.
To run zones, alerts, community reports, comments, Assist, shift mileage, optional earnings, rewards links, and Pro access.
To send the notifications you enable and to email you about your account (verification, security, terms).
To prevent abuse, debug outages, and keep the Service reliable.
We do not sell your personal information. We do not use your location to build an advertising profile. We do not show ads in the app.
5. Location — what is and is not on the map
Live contribution is voluntary in the product sense: you turn the shift ON. Radar live also requires Always / background location so presence can update while you drive.
Other drivers see heat and anonymous dots, not your name, email, or vehicle. There is no artificial “wait 60 seconds before anyone can see you.” Peers update with live ingest cadence and presence rules (including TTL after you stop sharing).
Presence on the live map expires when the shift ends or the presence TTL expires. We do not keep a continuous GPS breadcrumb of your day.
Your chosen home city is stored as a place you selected, not as a live track of your home.
The map SDK (Mapbox) needs location and viewport to draw the map. Mapbox processes that as its own processor — see Mapbox’s privacy policy.
6. Legal bases (where a privacy law requires one)
Contract: account, radar while you are on shift, Pro, zones, reports, Assist, and support you ask for.
Consent: optional notifications; Sign in with Apple/Google; Always location on platforms that treat it as consent; any marketing we do not currently send.
Legitimate interests: security, fraud prevention, crash diagnostics, anonymous aggregates that cannot reasonably identify you, and improving reliability — balanced against your rights.
Legal obligation: records we must keep if a law or a store requires it (for example a billing dispute).
7. Sharing
Other drivers: anonymous presence on the radar; reports and comments you publish (including the name snapshot on a report); an Assist request you create (location and problem type to nearby drivers or a professional partner).
Processors that only use data to provide their service to us: cloud hosting and databases; Redis for short-lived presence; Mapbox (maps); Apple and Google (sign-in, push, app stores); RevenueCat (subscription status); email delivery; Expo push; Firebase Crashlytics; Grafana Faro / observability.
Partner offers: if you tap a reward link, the partner and their network may see that you arrived from Driverpoint. Their privacy policy applies on their site.
Law and safety: we may disclose information if required by law, a valid legal process, or to protect people from serious harm.
Business transfer: if Driverpoint is sold or merged, personal data may transfer to the successor under this policy or a successor policy we will announce.
We do not sell personal information and we do not “share” it for cross-context behavioral advertising in the sense of California law.
8. International transfers
We may process data in the United States and other countries where our hosting or processors operate. Those countries may not have the same privacy laws as yours. We use processors under contracts that limit use to providing the Service.
9. Retention
Account and profile: until you delete the account, plus a short technical period needed to finish deletion and keep the system consistent.
Live map presence: minutes — shift off and/or presence TTL (configured in the product; not a permanent trail).
Shift sessions, mileage, and optional earnings: while the account exists, so you can see history. Deleted with the account.
Zones, reports, comments, echoes, Assist rows you created, push tokens, reward clicks, entitlements, and sessions: deleted with the account (or unlinked where the database only stores a reference, for example an Assist you accepted for someone else).
Anonymous city-level aggregates (for example hourly density with no user id) may remain because they cannot reasonably identify you.
Crash and telemetry: kept only as long as needed to fix issues.
Legal holds: we may keep a narrow copy if the law requires it (dispute, fraud, tax, store audit).
10. Your rights and how to delete your account
Depending on where you live (for example the EEA, UK, or California), you may have the right to access, correct, delete, restrict, or port personal data, to object to certain processing, and to complain to a supervisory authority.
Delete account in the app: More → Delete account. You confirm with your email. This permanently deletes your Driverpoint account and the personal data tied to it, as described above. This is the native path — you do not need to email support to delete.
You can also email legal@driverpoint.app. We will verify it is you before acting.
You can turn off location or notifications in the phone settings. If you turn off Always location or the shift, you will not contribute to or see the live radar as designed.
You can sign out, restore or manage the subscription in the store, and stop using partner links at any time.
We do not currently offer a full self-serve data-export file. If you need a copy of the personal data we hold, email legal@driverpoint.app and we will provide it in a reasonable electronic format.
11. Children
Driverpoint is for adult gig-economy workers. You must be at least 18 years old to create an account.
The Service is not directed to children under 13 (or under 16 in the EEA/UK where that is the digital-consent age). We do not knowingly collect personal data from children. If you believe a child has an account, email legal@driverpoint.app and we will delete it.
12. Security
We use industry-standard measures: encrypted transport (HTTPS), hashed passwords, limited sessions, and access controls on production systems. No method of transmission or storage is 100% secure. If we become aware of a breach that the law requires us to notify, we will do so.
13. Phone permissions
Location When In Use: suggest a city and show you on the map while the app is open.
Location Always / background: required for live radar while you drive with the shift ON. We do not use Always location to track you after you end the shift.
Notifications: optional. Zone alerts, Assist, ops announcements, and account events.
We do not ask for camera, microphone, contacts, or photo library for the current product.
14. Changes
We may update this policy. The version date at the top will change. Material changes will appear in the app (More → Privacy Policy) and at https://driverpoint.app/privacy. If the change also affects the Terms you accepted, we may ask you to accept the new Terms before you continue.
15. Contact
Privacy requests: legal@driverpoint.app
Public policy: https://driverpoint.app/privacy
Terms: https://driverpoint.app/terms