Privacy Policy
Last updated: August 24, 2026
1. What TuneWorks collects
TuneWorks collects the information needed to operate the motorsports garage and analysis product. This can include Google sign-in account details, profile information, vehicles, setups, setup revisions, sessions, maintenance records, shop lists, uploaded logs, Race Engineer and AI analysis prompts, Share Build selections, support messages, billing status, product settings, and first-party usage activity.
2. How TuneWorks uses data
TuneWorks uses this data to provide the app, save garage history, process uploaded logs, power AI-assisted analysis, generate summaries, support Share Build, manage teams and account settings, process subscriptions and AI credit purchases, detect abuse, debug reliability issues, measure product usage, and provide support.
3. AI and MCP tools
TuneWorks may send relevant app context to AI providers when users ask for AI-assisted analysis, Race Engineer help, or connected MCP workflows. MCP access is authenticated with TuneWorks OAuth and scoped to the connected user's app objects, including vehicles, setups, sessions, maintenance, shop lists, Share Build, and bounded log context. MCP tools do not expose admin tools, billing administration, checkout, arbitrary SQL, raw databases, user impersonation, or unrestricted exports. OAuth tokens are stored in hashed form, and MCP tool-call metadata may be logged for reliability, abuse prevention, and product analytics.
4. Uploaded logs and vehicle records
Users retain ownership of uploaded logs, vehicle records, setup notes, session notes, and other content they add to TuneWorks. TuneWorks processes that content to provide product features and does not give other users access to private account data unless the user chooses to share it through team features or Share Build.
5. Sharing and Share Build
Share Build lets a user email selected vehicle, setup, and optional session details to another person. TuneWorks sends those details only after the user chooses the content and recipient. Team features may also make selected workspace data visible to team members with access to the same team.
6. Service providers
TuneWorks uses service providers to operate the product, including Google for sign-in, Google Analytics for web analytics, Stripe for billing, Resend for transactional email, Crisp for support chat, Mixpanel for product analytics, AI providers for AI-assisted workflows, and hosting, database, security, and monitoring providers. These providers process data as needed to deliver services to TuneWorks.
7. Analytics, support, and activity logs
TuneWorks uses analytics and first-party activity logs to understand product usage, diagnose issues, improve onboarding, measure feature adoption, and support admin troubleshooting. Support chat may receive account profile details such as email and name when a signed-in user opens chat.
8. Data protection and retention
TuneWorks uses technical and organizational controls intended to protect user data. No internet service can guarantee perfect security, so users should avoid uploading data they are not authorized to use or share. TuneWorks keeps data while needed to provide the service, comply with legal and billing obligations, support security and reliability, or until deletion is requested and completed where available.
9. Choices and contact
Users can manage many records inside the app and can contact TuneWorks through the Contact page for privacy questions, account requests, deletion requests, or data-related support.