Built to know less.

This policy describes information handled by DashMic through dashmic.com, the optional product-updates list, Tesla connection flow, Live Lyrics experience, product feedback, support channels, and private product diagnostics.

DashMic is in Free Early Access. If the legal operating entity, payment model, or data practices change before a later commercial phase, this policy will be updated before those changes apply.

If you choose to receive DashMic updates, DashMic stores the normalized email address you submit, the date and version of your consent, and a coarse signup source such as the homepage or footer form. This is used only to send product and launch updates that you asked to receive.

The email-updates list is optional and is not required to connect Tesla or use Free Early Access. DashMic does not attach Tesla account information, vehicle information, music history, or location to that email record. If you email support, general, or privacy addresses, the content of that email is handled as necessary to respond to you.

To preserve Early Access history for possible future founding-member benefits, DashMic may keep a privacy-safe membership record containing an opaque Member Code, the first valid Live Lyrics use timestamp when available, the Early Access cohort, and a joining-order number. Legacy preview users may be assigned a founding joining date from their existing DashMic connection date when earlier first-use history was not recorded.

This founding-member metadata does not contain a VIN, Tesla account identifier, vehicle location, song title, artist, listening history, payment card, or Tesla access token. Founding-member history does not currently create a payment requirement or guarantee any specific future discount, free period, price, or other benefit.

When a user connects a Tesla account, authorization happens through Tesla’s own sign-in and consent flow. DashMic currently requests Vehicle Information access only. It does not request Tesla’s separate Vehicle Location permission, vehicle-command access, or charging-control access for the lyrics experience, and DashMic does not query or store vehicle location.

Tesla OAuth credentials needed to keep your connection working are stored server-side in encrypted form. DashMic does not expose plaintext Tesla access tokens to browser JavaScript. Server-side connection/session identifiers and a selected-vehicle cache may be used so the app can securely reconnect without repeatedly asking Tesla for the same information.

After you explicitly start Live Lyrics, DashMic may process the media state your authorized Tesla reports, including track title, artist, album, duration, playback source, playback status, and elapsed playback time. This information is used to identify the current track and synchronize the lyrics display.

The current implementation stores a current-state record that is overwritten as playback changes. DashMic does not maintain a permanent song-by-song listening-history table. Aggregate reliability metrics are designed not to contain song titles, artist names, VINs, or location.

If you open an explicitly tagged DashMic campaign link, we record the campaign label and a daily aggregate count of link visits. A short-lived first-party cookie prevents the same browser being counted repeatedly that day and remembers the referral for up to seven days. If you create a new Tesla connection during that period in the same browser, we may store the campaign label against the internal connection record to understand which outreach brought new users. No IP address, browsing history, email address, VIN, or listening history is stored in this referral record. Referral analytics are available only to the DashMic owner.

Connected Early Access users can choose to send product feedback. A feedback submission can include the category you select, an optional 1–5 rating, the message you type, the DashMic route where feedback was opened, whether the browser reports that future voice-note APIs are available, the deployed app build, triage status, and timestamps.

DashMic also keeps an opaque internal connection identifier with the submission so it can authenticate the sender, limit abuse, and review repeat reports. The feedback record does not store a VIN, location, Tesla access token, song title, artist, listening history, or an IP-address archive.

The current feedback feature does not request microphone permission, record audio, or store raw voice notes. If voice-note submission is enabled later, DashMic will disclose the applicable recording, retention, and deletion practices before audio is collected and will update this policy when needed.

DashMic uses secure cookies for authenticated sessions and limited server-side caching. During an active Live Lyrics session, a short-lived cookie may also help count aggregate active minutes without creating a detailed event history.

Aggregate diagnostics can include counts such as active minutes, telemetry ingests, Tesla REST-read attempts, track changes, pause/resume transitions, and lyric lookup outcomes. Local browser viewport diagnostics are shown to the user for layout troubleshooting and are not stored in the usage-history database.

Hosting, database, email, and security providers may generate ordinary infrastructure logs needed to operate and protect their services under their own policies and retention practices.

DashMic relies on service providers to operate the product. Depending on the feature being used, these may include Tesla for authorized vehicle information, hosting and database providers, email providers, and lyric or artwork providers. DashMic sends each provider only the information reasonably needed for that feature.

Third-party services have their own terms and privacy practices. DashMic does not control how those providers handle information they receive directly from you or as necessary to provide their services.

Product-update email and consent records are kept while the communication purpose remains active, unless you ask to unsubscribe or delete the record sooner. Current media state is overwritten as new state arrives rather than retained as a listening timeline. Aggregate operational metrics may be kept longer because they do not contain song titles, VINs, or location.

Product feedback may be kept while it is useful for product support, quality improvement, abuse prevention, and follow-up triage. Feedback can be marked new, reviewed, or resolved internally. You can also ask DashMic to delete feedback associated with your connected session or other information that can reasonably be identified from the details you provide.

You can ask to access, correct, unsubscribe, or delete information associated with your email or feedback by contactingprivacy@dashmic.com.

DashMic uses measures intended to reduce exposure of sensitive connection data, including encrypted Tesla-token storage, secure HTTP-only session cookies, least-privilege Tesla authorization, server-only secrets, and private backend tables for telemetry, diagnostics, feedback, and owner administration. No internet service can guarantee absolute security.

Material changes to this policy will be reflected by changing the date above and, when appropriate, notifying users or email subscribers before the change takes effect.

Privacy questions: privacy@dashmic.com. General questions: hello@dashmic.com.