Information We Collect
- Google sign-in profile data, such as name and email address, for authentication and access control.
- Slack user names and user IDs used to map workers to tasks and notifications.
- Turo trip details from connected Gmail trip-event emails, including vehicle, reservation, trip dates, locations, guest-visible trip text, public listing URL, and cancellation or change status.
- Operational records entered in the dashboard, including tasks, task status changes, worker planning settings, time off, expenses, receipt attachments, payouts, car locations, and audit events.
- Browser push subscription data when a user enables phone or browser notifications.
How We Use Information
- To authenticate approved users and route them to their own dashboard views.
- To create, update, assign, and audit trip-related work for the host team.
- To show users their assigned work, unassigned work they can help with, expenses, payouts, and related settings.
- To notify users about assigned tasks, unassigned host work, schedule changes, and operational alerts.
- To help admins generate tomorrow planning drafts and payout reports.
Google User Data
Turohelper uses Google OAuth for dashboard sign-in and Gmail OAuth for the connected mailbox. Gmail access is used only to read Turo trip-event messages needed to create, update, validate, or cancel trip and task records. The app is configured to watch the Turohelper Trip events label when Gmail watch is enabled.
- The recommended Gmail setup is a dedicated Turohelper inbox that receives only forwarded Turo trip-event emails from the primary Turo mailbox.
- Turohelper does not sell Google user data.
- Turohelper does not use Google user data for advertising.
- Turohelper does not use Google user data to train generalized AI or machine learning models.
- Turohelper only shares Google user data with service providers needed to run the app, such as hosting, storage, database, and notification services.
- Turohelper's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Storage, Retention, And Security
Operational data is stored in Turohelper-controlled infrastructure. The app uses authenticated sessions, server-side permissions, CSRF protection for mutating dashboard requests, audit logging for changes, and restricted admin-only settings for sensitive actions.
Data is retained while it is needed for active operations, auditability, payout history, and business records. Admins may remove or correct records when appropriate.
Your Choices
- Users can sign out from the dashboard at any time.
- Users can disable browser push notifications from their device or Turohelper notification settings.
- Admins can disconnect Gmail from Turohelper settings.
- Team members can ask an admin to correct or delete personal profile, availability, time-off, expense, or notification data when operationally appropriate.
Contact
For privacy questions, contact the Turohelper administrator or email support@turohelper.com.