PPitFlowTechnical Workflow
PRIVACY

Privacy Policy

Last updated: September 23, 2026

1. About PitFlow

PitFlow is a workshop technical reporting and case communication application for authorized users. It enables users to create structured technical reports, attach case documentation, send reports to configured recipients and follow case-related communication.

2. Information processed by PitFlow

Depending on how the service is configured and used, PitFlow may process account information such as name and work email address; technical case information such as vehicle details, mileage, customer complaint, workshop checks and findings; files, photographs or videos intentionally uploaded to a case; configured recipients; and case-related email metadata and messages required to provide the case workflow.

3. Google user data

When a user chooses to connect a Google account, PitFlow uses Google OAuth 2.0 and requests the Gmail API scope https://www.googleapis.com/auth/gmail.send. This permission is used only to send emails that the user initiates through PitFlow, including technical reports and case updates, from the connected Google mailbox.

PitFlow does not request Gmail scopes that allow it to read, modify, or delete the user's Gmail inbox. PitFlow does not use Google authorization to scan a user's personal inbox.

4. How Google user data is used

Google authorization data is used to authenticate the connected mailbox and to obtain the authorization needed for the Gmail API to send user-initiated messages. OAuth credentials/tokens may be stored securely by the application as necessary to keep the user's mailbox connection active until the user disconnects it, access is revoked, or the authorization expires.

PitFlow does not sell Google user data, does not use Google user data for advertising, and does not use it to build advertising profiles. Google user data is not transferred to third parties except as necessary to provide the user-requested functionality, comply with applicable law, protect security, or as otherwise expressly directed by the user or organization operating PitFlow.

5. Google API Limited Use

PitFlow's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

6. Case email and dedicated reply mailbox

PitFlow may use a dedicated PitFlow mailbox to receive replies to technical cases. This is separate from the connected user's Gmail inbox. Case replies received by that dedicated mailbox may be associated with the relevant PitFlow case and displayed to authorized users of that case.

7. Retention

PitFlow is configured to retain active case/chat content and associated case files in the application for 15 days from the latest case activity, after which they are removed according to the application's retention process. Copies of email that exist in the sender's, recipient's, or other mail systems are governed by those systems and their respective organizational retention policies.

8. Mobile apps, biometrics and notifications

The PitFlow mobile apps may store an authenticated session and encrypted login credentials on the device, request camera, microphone and photo access only when the user chooses to add documentation, and register a device token for case notifications. Face ID, Touch ID or Android biometric matching is performed by the operating system; PitFlow does not receive or store biometric templates.

9. Private manufacturer consultation

Where an authorized technical user explicitly forwards a case for manufacturer consultation, selected case text, the technical department note and selected files are sent only to the configured manufacturer recipients. Text may be translated to English by the configured translation provider. Manufacturer correspondence is restricted from workshop users and is not included in claim material unless an authorized technical user separately adds an approved conclusion to the workshop case.

10. Security and access

Access to PitFlow is limited to authorized users and enforced by role, workshop, brand, action and report scope. Reasonable technical and organizational safeguards are used to protect application data and OAuth credentials. Users should protect their account credentials and disconnect connected services when they are no longer required.

11. Revoking Google access

A user may disconnect Google from within PitFlow where that option is available, and may also revoke PitFlow's Google Account access through Google's account security controls. Revocation prevents future use of that Google authorization by PitFlow.

12. Account and deletion requests

Accounts are created by an authorized organizational administrator and cannot be created publicly in the app. A user may ask the administrator to disable the account and may submit an access or deletion request to [email protected]. Requests are handled subject to legal, warranty, security and organizational record-retention duties.

13. Changes to this policy

This policy may be updated when PitFlow's functionality or data practices change. The current version will be published on this page with an updated date.

14. Contact

Questions about this policy or PitFlow's handling of Google user data can be directed to [email protected].