DriveTone Privacy Policy
DriveTone creates driving sounds using your phone’s motion sensors and speed information from Location Services. This policy explains how Inevitable Labs, LLC handles information when you use DriveTone or contact us.
Location and motion during a drive
DriveTone uses speed data from Location Services to keep driving sounds in sync, including while the app is in the background. Location data is accessed only during active drive sessions. These sessions include startup and calibration and end when the session stops.
Live driving requires Location access with Precise Location enabled for reliable speed estimates. DriveTone also uses motion measurements, including acceleration, rotation, orientation, and gravity, to calibrate and operate the simulation. The stationary demo remains available without Location access.
The app’s drive diagnostics do not record latitude or longitude or a map of your route. They can contain speed, direction of travel, accuracy measurements, and timestamps. This information can still describe aspects of your driving activity.
Information kept on your device
DriveTone stores preferences, setup progress, automation history, drive milestones, and recent drive and review information on your device. Drive diagnostic files can include motion and speed measurements, calibration results, simulation state, audio performance, audio-route names, device and app information, timestamps, and a drive identifier.
Detailed diagnostic files are not automatically uploaded by DriveTone. You can choose to attach them to a feedback email, use “Send debug log” to prepare an email, or use “Share debug log” to choose a destination in the standard iOS share sheet. Device backups may include app data according to your device and backup settings.
Usage analytics
DriveTone currently sends usage and technical information automatically to TelemetryDeck, our analytics provider. We use it to understand which features people use, assess reliability, and improve the driving experience.
This includes setup and automation events, drive starts and stops, drive duration and configuration, changes to simulation settings, and summaries of calibration results. App events also include your current plan and access status; we record changes to that status, introductory driving allowance, and cooldown use to understand the purchase and driving experience. Technical diagnostics help us understand performance and improve DriveTone; these include calibration quality and, when you submit a drive review, system-defined audio-output types and measured audio delay. Analytics uses these output categories rather than your audio device’s name. Events may include an independently generated analytics-only drive identifier, separate from the identifier in diagnostic exports. The analytics SDK also supplies technical information such as app version, operating system, device model, language or region settings, and session information. It derives a hashed identifier from a device vendor identifier when available, with an SDK-defined fallback otherwise.
These identifiers help us associate related app events, such as a drive and its review. DriveTone also sends its hashed TelemetryDeck user identifier to RevenueCat to associate purchase activity with usage analytics. We do not send your name, email address, or Discord username to either provider, or use support correspondence to look up your analytics activity. The analytics-only drive identifier is separate from the identifier used in diagnostic exports and is not included in feedback emails or diagnostic attachments. DriveTone does not use advertising SDKs or track your activity across other companies’ apps and websites for advertising.
TelemetryDeck describes its identifier protections in its anonymization guidance. Because DriveTone associates analytics and purchase records, we do not describe the combined records as incapable of being linked to a person. There is currently no in-app analytics consent banner or opt-out switch. Written feedback and audio-device names are excluded from analytics, and diagnostic exports use a separate drive identifier. The legal bases and privacy-request options below apply to our handling of this information.
Purchases and purchase offers
Apple processes in-app payments. We use RevenueCat to verify purchases, restore access, determine your current plan and subscription status, provide purchase screens, and understand purchase activity. RevenueCat processes your app user identifier, purchase and transaction history, product identifiers, trial and renewal status, and technical information such as app and operating-system versions, device platform and model, locale, currency, and a device vendor identifier when available. RevenueCat also receives purchase-screen interactions such as views, dismissals, selections, and purchase cancellations, together with the app user identifier and screen, product, and technical context, to understand how the purchase screens are used. We do not receive your payment-card details or Apple Account password.
DriveTone does not require a separate account. RevenueCat assigns an app user identifier, which is also shown as your Member ID in supporter perks. This generated identifier associates purchases and the app information described below with your RevenueCat customer record. If you request supporter community access, we can associate that record with your email address and Discord username as described below.
DriveTone also sends RevenueCat whether you have completed a qualifying drive, total completed driving time and qualifying-drive count, whether your introductory allowance is exhausted, your active plans and access status, and your most recently recorded fun and sound-consistency ratings when available. Drive completion and current-plan information determine which offers you see, such as an introductory trial or a lifetime upgrade. The additional usage summaries and ratings are stored with the customer record for understanding the purchase experience; they do not currently determine which offer you see. These attributes do not include your route, precise location, written feedback, or audio-device name. The shared analytics identifier is provided for connecting purchase and usage analytics. RevenueCat is configured to forward purchase and subscription events to TelemetryDeck for this analytics purpose.
Founding supporter community access
Joining our Discord community is optional and is not required for lifetime driving access. To activate private supporter-channel access, join the server and send us your Member ID and Discord server username. The app can prepare an email containing your Member ID; you add your username and decide whether to send it. You may instead copy your Member ID and contact us using your preferred email service.
We use the Member ID to check your RevenueCat supporter entitlement and grant the appropriate Discord server role. During verification, the request connects your purchase record with the username and email address you provide. We do not copy those contact details into RevenueCat or analytics, use the request to identify your analytics activity, or retain a Member ID-to-Discord account mapping after the request is resolved. We delete verification correspondence when closing the request, subject to provider backup retention and any legal retention obligations. Your Discord membership and assigned role remain in Discord. Discord processes your account, server participation, and messages under its privacy policy; information you post may be visible to other server members according to channel permissions.
Reviews, feedback, and diagnostic sharing
Contacting us with feedback or questions is optional and is not required to use DriveTone. From time to time, you may choose to contact us by email or other electronic means. These communications may include your contact information, information about your use of the app, and anything else you choose to share. We use this information to respond to you, investigate reported problems, and improve DriveTone.
Submitting a drive review sends your ratings, any vehicle details you enter, and associated drive information to TelemetryDeck. Vehicle make, model, and year are optional and help us understand how DriveTone performs across different vehicles. Please enter only those vehicle details in these fields, not names, contact details, vehicle identification numbers (VINs), or registration numbers. Associated information can include the analytics-only drive identifier, duration, simulation settings, system-defined audio-output types, and audio delay. Written feedback entered under “Tell us more” is included only in the email you choose to send, not in analytics.
Submitting the review and sending an email are separate actions. You can submit ratings without emailing us or attaching diagnostics. Cancelling a subsequent email does not undo an already-submitted review. If you choose email feedback or diagnostic sharing, DriveTone prepares a message or opens the standard iOS share sheet; you decide whether to send it and whether to include the offered diagnostic attachment.
Feedback emails include a drive summary with app/build and operating-system information, audio-route name and delay, drive duration, simulation choice, ratings, and any vehicle details you provided. Detailed diagnostic attachments remain optional. DriveTone does not automatically email this information; you choose whether to send each message.
Email sent to us includes the message, any attachments, and information your email service supplies, such as your email address, display name, or signature. We use Gmail through Google Workspace to receive and store this correspondence. The email summary omits the drive identifier. We do not link support correspondence or diagnostic attachments to TelemetryDeck analytics records. New drives use separate identifiers for analytics and diagnostic exports; earlier app versions used a shared drive identifier.
When you share information with another recipient or service, their handling of that information is governed by their own policies.
Recipients and purposes
We require service providers handling information on our behalf to provide protection consistent with this privacy policy and applicable privacy requirements.
TelemetryDeck processes analytics and submitted review information for the purposes above. Google processes correspondence and attachments delivered to our Gmail mailbox. Our access to that information supports troubleshooting and responding to you. We may also disclose information when required by law. These services may process information outside your country.
TelemetryDeck states that it hosts usage analytics within the European Union and describes its security and anonymization commitments in its data protection agreement. We use Google Workspace for support email; Google describes its processing, security, and international-transfer safeguards in its Cloud Data Processing Addendum. Support information may be processed in the United States and other countries where Google operates.
RevenueCat acts as our service provider, processing purchase records and the app information described above on our behalf to provide purchase management, reporting, and offer selection. Our handling of this information is described in this policy; RevenueCat explains its role and safeguards in its privacy information and Data Processing Addendum. Apple handles App Store transactions under its privacy policy. Discord handles the community service, and Google Workspace receives supporter-access emails as well as other support correspondence. These services may process information in the United States and other countries.
Legal bases
Where applicable, we process purchase and membership information to provide the access you purchase and fulfill your requests. We rely on our legitimate interests to operate and secure the app and purchase service, analyze usage and reliability, improve DriveTone, and present relevant offers for our own app, subject to your applicable rights. These legal bases are subject to applicable consent requirements. We process information to meet legal obligations where required. Contact us if you wish to object to processing based on legitimate interests.
Where applicable data-protection law requires a legal basis, we process support correspondence and voluntarily shared diagnostics for our legitimate interests in answering your requests, investigating problems, and improving DriveTone, while respecting your privacy rights.
Retention and deletion
On your device, DriveTone retains preferences and selected recent-drive or pending-review records. It removes superseded diagnostic files when they are no longer referenced by its retained drive records. This is based on app activity, not a fixed time limit. Deleting the app does not necessarily remove all identifiers or records used to manage purchases and free access. Some information may remain on your device, in backups, or with our purchase-service providers. Uninstalling does not cancel a subscription or retract information already sent to us or other services.
We retain support correspondence and diagnostic attachments for as long as reasonably necessary to respond to requests, investigate issues, and improve DriveTone. We periodically review retained information and delete or anonymize information that is no longer needed for those purposes. We may retain information longer where required by law. Deletion from provider systems and backups may take additional time under their retention and deletion processes.
TelemetryDeck currently publishes no fixed deletion schedule for archived analytics events. Analytics may therefore be retained indefinitely, including after our TelemetryDeck account closes. Its Privacy FAQ describes these retention practices. We do not promise that deleting DriveTone or contacting us will delete particular analytics events that we cannot associate with you.
The app information sent to RevenueCat is retained while needed for offer selection and understanding purchase activity, subject to review and applicable deletion requests. Purchase records and associated identifiers may be retained to maintain and restore paid access, resolve billing issues, prevent fraud, and meet legal obligations. Supporter verification correspondence is deleted when the request is resolved, including copies under our control, unless retention is legally required. Provider backups may take additional time to expire. We retain the membership and role in Discord, but do not keep a separate Member ID-to-Discord account mapping for future lookup. We do not promise that deleting the app deletes Apple or RevenueCat transaction history. Contact us to request deletion or review of records associated with your Member ID. A later community-access request may require you to provide your Member ID again so we can verify eligibility.
Your choices and requests
You can change DriveTone’s Location permission and Precise Location setting in iPhone Settings. Disabling required access prevents live driving sessions; the stationary demo remains available. Reviews and diagnostic sharing are optional. Discord participation and supporter-access emails are also optional. You can leave the Discord server or contact us to request removal of your supporter role. Manage or cancel Apple subscription renewals in Apple subscription settings; deleting the app or requesting data deletion does not cancel renewal.
For privacy questions or to request access to or deletion of personal information we hold about you, including purchase-related records and supporter membership information, contact [email protected]. Please provide enough information to locate your correspondence or report without sending unnecessary sensitive information. We may need to verify your request. We may not be able to identify particular analytics records from your email address alone.
Depending on where you live and the law that applies, you may have additional rights to correction, restriction, objection, portability, withdrawal of consent, or a complaint to a data-protection authority. Some information may need to be retained where the law permits or requires it.
Changes and contact
We will update this policy when our practices change and provide additional notice or request consent where required. The effective date appears at the top of this policy.