1. Scope of this policy
This policy applies exclusively to the Shift Driver app, intended for drivers performing transportation services arranged by Shift.
This policy is separate from the privacy policy of Shift's institutional website. The portions of that document dealing with cookies, Google Analytics and embedded content apply solely to browsing on the website. The Shift Driver app does not use cookies, Google Analytics, or any advertising, campaign measurement, or profiling tool.
Data controller: Shift Mobilidade e Agenciamento Ltda., registered under Brazilian corporate number (CNPJ) 13.921.195/0001-54.
2. Who uses the app
Shift Driver is a professional-use app. Access requires an account previously created by Shift or by the contracting company — there is no open public sign-up. The data processed here is data of drivers in the course of their professional activity.
3. Data we collect
3.1 Account data
Name and mobile phone number. The phone number also serves as the login identifier: authentication is performed via a one-time code sent by SMS.
3.2 Profile photo
A selfie captured by the device camera, used to identify the driver to Shift, to the contracting company and to the passengers being transported.
Face-framing verification at the moment of capture takes place entirely on the device itself, with no image sent to third parties. Only the final photo is uploaded to Shift's servers after confirmation. We do not generate, store or share any biometric template, facial signature or any data suitable for automated biometric identification.
3.3 Location
See section 4, dedicated to this topic.
3.4 Diagnostic data
Technical records of app crashes and errors (error type, app version, device model, operating system version), collected to identify and correct defects.
3.5 Notifications
A device identifier generated by Google's notification service (token), required to deliver alerts about newly assigned trips.
4. Location — what we collect, when and why
4.1 What is collected
During an ongoing trip, the app periodically transmits: latitude and longitude coordinates, reading accuracy, speed, heading, distance traveled, detected activity type (still, on foot, in a vehicle), battery level and whether the device is charging, along with the timestamp of each reading.
Battery level and activity type are used to adjust the frequency of readings, preserve device battery life, and distinguish a signal interruption from a powered-off device.
4.2 When it is collected
Only while a trip is in progress, started by the driver themselves inside the app. Monitoring is automatically ended when the trip is finalized. Outside of an active trip, the app does not collect location.
During a trip, collection occurs even with the app in the background or with the screen off — otherwise the trip record would be interrupted every time the driver put the device away. While this happens, the operating system informs the user that background location access is active, through the mechanisms available on each platform (a persistent notification on Android, an active-location indicator on iOS).
4.3 What it is used for
Follow-up on the trip in progress and safety of the passengers being transported: allowing the contracting company and the coordination team to know whether the vehicle is on the way, whether there has been a delay, and where the vehicle is located in the event of an emergency.
4.4 Link to identity
Location data is linked to the driver's account and to the trip it refers to. It is not anonymized, because the very purpose — knowing which vehicle is where — depends on this identification.
5. What we do not do with this data
Location data, and the other data processed by this app:
- are not used for advertising or ad measurement;
- are not combined with data collected by apps, websites or services of other companies;
- are not sold;
- are not shared with data brokers;
- are not used to evaluate behavior outside of working hours;
- are not used in any automated decision-making about the driver.
The app does not read your messages, contact list, photos or files. The verification-code auto-fill uses a native operating system feature that only hands the app the verification message we sent.
6. Whom we share data with
Contracting company. Driver identification data and information about the trip performed, including the route, are made available to the company that contracted the transportation. This is the app's central purpose.
Technical processors. We use the following third-party services, each with a restricted purpose:
| Service | Provider | What it receives | Purpose |
|---|---|---|---|
| Firebase Crashlytics | Crash data (stack trace, error type, memory usage), device model, operating system and version, app version, anonymous Firebase installation identifier, and IP address. | Identification and correction of defects. | |
| Firebase Cloud Messaging | Installation registration token, IP address, and message-delivery metadata (timestamp, success or failure). | Delivery of notifications about newly assigned trips. | |
| Google Maps SDK | IP address, application identifier, SDK and operating system versions, and the coordinates required to render the map view shown on screen. | Rendering the map inside the app. |
The anonymous Firebase installation identifier (Firebase Installation ID) is generated by the SDK itself and lets Google correlate diagnostic and notification data from the same app installation. It is not tied to advertising identifiers (IDFA on iOS, AAID on Android) or to permanent device identifiers (IMEI, serial number), and is regenerated when the app is uninstalled or its data is cleared.
None of these services receive the driver's location data for advertising purposes, and none of them use it for profiling. Third parties with whom Shift shares data, including contracting companies and technical vendors, must provide a level of personal data protection equal to or greater than that set forth in this Policy and required by applicable law.
Authorities. Upon legal obligation, court order or request from a competent authority.
7. How long we keep it
Positions recorded while offline are stored on the device itself for up to 14 days while awaiting upload; after that period they are discarded.
On the server, data from completed trips is retained for the period necessary to comply with contractual obligations to the contracting company and applicable legal obligations.
Upon signing out of the app, the driver's local data — photo, credentials and positions not yet uploaded — is erased from the device.
8. Security
Traffic between the app and our servers is encrypted. Access credentials are stored in the operating system's secure vault (Keychain on iOS, Keystore on Android).
9. Your rights
Under Brazil's General Data Protection Law (LGPD, Law No. 13,709/2018), you may request: confirmation of the existence of processing, access to your data, correction of incomplete or outdated data, anonymization or deletion of unnecessary data, data portability, information about data sharing, and — where the processing is based on consent — the withdrawal of that consent.
Requests to access, correct or delete data may be sent by e-mail to dpo@intuix.com.br. Some records may be retained for the time necessary to comply with legal, contractual or regulatory obligations, even after a deletion request. Data Protection Officer: Intuix — dpo@intuix.com.br.
Refusing to provide location during a trip prevents the activity from being performed in the app, as it is a condition of the contracted service.
10. Permission controls
Location, camera, motion and notification permissions can be revoked at any time in your device's operating system settings. Revoking the location permission prevents new trips from being recorded until it is granted again.
11. Changes
Material changes to this policy will be communicated inside the app before they take effect.
12. Contact
contato@shiftmc.com.br — Estrada São Francisco, 460 — Vila Sônia do Taboão, Taboão da Serra/SP, ZIP 06765-000, Brazil.