This policy explains what data the TransferCRM Driver mobile app collects, why, and what we do with it. It applies in addition to the platform-wide TransferCRM privacy policy.
1. Who runs this app
TransferCRM (the “Operator”) operates the driver app and the underlying SaaS platform used by chauffeur and limousine companies. Your employer (the company that invited you) is the data controller for the operational data we hold on you. We act as the data processor on their behalf.
2. What we collect
- Account. Name, email, phone (if your employer set one), workspace identifier, role, last sign-in time. Provided by your employer when they invite you.
- Location during active trips. GPS coordinates, heading, speed, accuracy, sent every 30 seconds while you are on duty. Reporting pauses automatically when no trip is active.
- Push token. Firebase Cloud Messaging device token, used only to deliver assignment and status notifications. Revoked on logout.
- Device info. Platform (iOS/Android), OS version, app version, device model. Used for crash reports and to troubleshoot support tickets.
- Trip records. Assignments, travel-status timestamps, earnings attributed to you. Visible to your employer in TransferCRM.
- Biometric authentication. Face ID / Touch ID / fingerprint data never leaves your device. The app only asks iOS/Android to confirm “is this the device owner?” — we do not see or store the biometric itself.
We do not collect contacts, calendar, photos, microphone, or any advertising identifier.
3. Why we collect it
- To show you your schedule, route details, and pickup info.
- To let your dispatcher know where you are during a live trip.
- To deliver assignment notifications to your phone.
- To calculate earnings and produce the per-trip breakdown you see.
- To diagnose crashes and help you with support requests.
No data is used for advertising, profiling, or sold to third parties.
4. How long we keep it
- Location pings: 90 days, then deleted. Aggregate trip routes are retained for as long as the trip record itself exists.
- Trip records:retained per your employer's business and tax rules (typically 5–7 years for accounting).
- Account: retained until your employer terminates your access, or you exercise your right to erasure (subject to legal retention obligations).
- Push tokens: deleted immediately on logout.
5. Who else sees it
- Your employer (the workspace that invited you). They see your schedule, location during active trips, earnings, and notifications history.
- Firebase Cloud Messaging (Google) — to deliver push notifications. They receive the push payload but not your account data.
- Pusher Channels— for real-time dispatcher updates. Channel names are scoped to your employer's workspace.
- Twilio — for SMS sign-in links and trip-status SMS, when your employer enables that channel.
We do not sell or share your data with advertising networks, data brokers, or analytics services. There is no third-party SDK tracking activity inside the app.
6. Where the data lives
Servers are hosted in the European Union. Backups are encrypted at rest. Data in transit is encrypted over TLS 1.2+.
7. Your rights (GDPR)
You have the right to access, rectify, port, restrict, object to, and erase the personal data we hold about you. Most operational data is exercised through your employer (they are the controller). For platform-level requests, email hello@transfercrm.com and we will respond within 30 days.
8. Account deletion
To delete the app, uninstall it from your device. To revoke your sign-in everywhere, go to Settings → Log out. To request full account erasure from the platform, email hello@transfercrm.com — your employer will be notified to confirm the removal.
9. Children
The driver app is intended for professional drivers and is not directed at anyone under 18.
10. Changes to this policy
We will post any material changes on this page and update the “Last updated” date above. Continued use of the app after changes means you accept the updated policy.
11. Contact
Questions or requests: hello@transfercrm.com. Need help with the app itself? See the driver app support page.