Privacy
Ludic Pulse Privacy Policy
Effective September 30, 2026 · United States beta
You can create a Ludic account with Apple and separately authorize Tesla vehicle access. We do not receive your Apple or Tesla password, sell personal data, run advertising, or use data to track you across other companies' apps or websites. Exact route history is optional. Our public marketing pages use cookie-free aggregate analytics.
Who this policy covers
This policy explains how Ludic Technologies LLC provides Ludic Pulse and handles data in the iOS app, cloud service, and Live Activities. The service is currently offered to US beta users and is not directed to children under 13.
Data we collect and why
| Category | Examples | Purpose |
|---|---|---|
| Contact and identifiers | Name and email when you request private beta access or when supplied by Apple or Tesla; Apple and Tesla provider identifiers; a random Ludic account UUID; device-session identifiers; selected vehicle/VIN; push tokens | Private beta invitations, sign-in, securely linking services, future purchase restoration, vehicle selection, account security, optional Shared ETA display, notifications, support, and abuse prevention |
| Vehicle data | Battery, range, charging, climate, locks, closures, windows, Sentry, tire pressure, odometer, software version, trip state, drives, and command results | Car status, commands, automatic tracking, charging, Insights, alerts, and reliability |
| Precise location | Current parked location; user-approved route history; recorded charging coordinates or addresses; and the latest route, destination, and position during a manually created Shared ETA | Parked-location and directions features, optional route maps and drive details, selected-charge maps and place lookup, and time-bounded trip sharing |
| User choices and home energy | Units, optional home profiles, dated electricity rates, entered charging costs and household bills, manual session assignments, privacy settings, and alert choices | Personalize calculations, compare matching billing periods, and honor consent |
| Website analytics | Page viewed, referrer origin, campaign path, coarse region, device type, browser, and operating system | Measure launch traffic and the private-beta signup funnel using anonymous aggregate statistics |
| Diagnostics | Sanitized crashes, performance spans, app/build version, and fixed subsystem labels | Detect failures and improve reliability |
| Optional Ask Pulse questions | Your submitted question and limited query context, described below | Use Apple Private Cloud Compute to interpret questions about recorded history and vehicle features |
Location, routes, and Shared ETA
Vehicle location may be used transiently to show the latest parked location and provide directions. Exact route points are excluded from route history unless you turn on Save route history. Shared ETA is separate, manual, and off by default: when you create a link, the latest position, destination when permitted, Tesla ETA and distance, and route geometry when available are shown to anyone with that link until arrival, route cancellation or replacement, manual stop, or four hours. If Tesla does not provide route geometry, the recipient browser may ask Apple Maps for an estimated remaining route between the current position and destination; it is labeled as estimated, while Tesla remains the source of ETA and remaining distance. The plaintext token is kept in the URL fragment and iOS Keychain, not the database. Shared ETA recipient views have no analytics, ads, replay, or third-party tracking. Screenshots, session replay, VINs, coordinates, tokens, request bodies, email, and user identity are excluded from Sentry diagnostics.
Charging locations
When you view charging history or open a charge, Pulse may send a visible session’s saved coordinates or full street address to Apple Maps to display its location and look for a matching current place name. It limits and queues these requests, reuses completed results across recent sessions, history, and detail, and stops pending lookups when they are no longer needed or the app enters the background. It does not request your phone’s current GPS location for this lookup or scan your entire charging history in the background. A pin derived from an address is labeled separately from a recorded charging point. Saved place names such as Home take priority; generic labels such as Away are not treated as venue names, and ambiguous nearby businesses are not presented as the charging site. Apple place details describe the current map directory and do not establish which business occupied an address when an older charge occurred. Pulse keeps lookup results only in a bounded, short-lived in-memory cache, clears its cache when the account or vehicle context changes or you sign out, and does not write those results into charging history or persist them on disk.
Car activity and vehicle schedules
The Car screen can display two summaries from recorded history. Tile choices are saved for the selected car on this iPhone. If you select Next scheduled event, Pulse may send up to eight enabled schedule locations to Apple Maps to resolve their time zones while that screen is active. This does not request the phone’s GPS location, change vehicle schedules, or send Tesla credentials to Apple. Lookups are queued, cached briefly in memory, and cancelled when no longer needed or when the app enters the background; private caches are cleared on sign-out or a vehicle/account change. Pulse retains timestamped vehicle-connectivity and last-active evidence for up to 30 days. Connectivity loss alone is not treated as sleep; a sleep-duration label requires Tesla state evidence and identifies an observed minimum rather than inventing an exact sleep time.
Vehicle appearance
Automatic appearance makes an initial request to Tesla for factory-paint options for your authorized vehicle. We retain the paint code, paint name and lookup time with your account’s vehicle record and cache them on this iPhone; we do not retain the full options response. A successful result is reused without recurring polling. This lookup does not issue vehicle-data, wake or command requests. An unsuccessful initial lookup can be retried explicitly. Manual color and No illustration choices are saved on this iPhone and take priority over automatic matching. Signing out clears the local factory-paint cache. Account deletion removes your cloud factory-paint record.
Optional home energy and frequent routes
Home charging is optional. Confirmed home profiles, electricity rates and entered household bills are private to your account and selected vehicle. Whole-house bills are entered amounts, not inferred from vehicle telemetry. Private route place names, grouping-radius preferences and corrections are stored on this phone. When you choose to import Tesla charging costs, Pulse reads Tesla charging history and stores finalized billed amounts, fee breakdowns and a provider session reference for uniquely matched recorded sessions. Your manual cost entries are not overwritten. This import does not store payment-card details or invoice PDFs. If you connect Apple EnergyKit, Apple supplies guidance and reported energy categories, not monetary bills. Separately choosing to share eligible charging history sends measured charging-load events to Apple; those loads may be visible to members of the selected Apple Home. No private route labels are included. Apple venue IDs, guidance tokens and stable submission payloads remain in protected, backup-excluded storage on this phone. Local guidance expires after 30 days and is pruned on the next refresh or sign-out; reporting records prevent duplicate transmission. Our cloud stores only the charging-session reference, opaque reporting-installation identifier and delivery status, not Apple guidance tokens or venue IDs. Signing out clears the new private local caches. Account deletion removes your cloud home settings, bills and reporting identifiers. If another legitimate account retains a shared vehicle session, a delivery marker without your account or installation identifier remains solely to prevent duplicate reporting.
Website analytics
Our marketing, support, legal, and private-beta pages use Vercel Web Analytics to report anonymous aggregate page views, referrer origins, campaign paths, coarse regions, devices, browsers, and operating systems. It does not use cookies, store IP addresses, record session replay, or receive names, email addresses, form values, VINs, coordinates, or tokens. Analytics is not loaded on Shared ETA recipient views or Tesla callback pages.
Optional Ask Pulse and Private Cloud Compute
Ask Pulse, Explain this, and the vehicle guide offer optional question interpretation using Apple Private Cloud Compute (PCC). Before submitting a question, you must choose Continue with PCC in the app. This is cloud processing by Apple, not on-device model processing. Pulse sends the question you submit and limited context: the selected question area, the last validated query interpretation for follow-up questions, the current local date and time zone, and a fixed list of supported vehicle-feature keys. Pulse does not automatically include your VIN, account or Tesla tokens, route coordinates, raw driving or charging session records, or calculated results in that request. Anything you type in your question is included, so avoid entering credentials or other sensitive information.
PCC interprets the question; Pulse validates that interpretation and calculates answers on your phone using the app’s existing recorded history and vehicle-feature evidence. This does not change where that underlying history is normally stored, as described elsewhere in this policy. Questions, query interpretations, and answers remain in volatile app memory for the current Ask Pulse experience; Pulse does not save a chat history or send this content to its analytics or diagnostic logs. Private-history clearing and account or vehicle changes clear that screen’s private context. Pending requests are cancelled when the screen loses focus, the app enters the background, or the request’s evidence context is invalidated, and invalidated responses are not used. Cancellation cannot undo data already sent to Apple.
Ask Pulse requires iOS 27 or later, an eligible Apple Intelligence device and configuration, network access, and available PCC usage allowance. Availability and usage limits are controlled by Apple; ordinary history and vehicle features remain available when PCC is unavailable. Ask Pulse is read-only: it does not wake the vehicle, issue vehicle controls, diagnose faults, or assess whether the vehicle is safe to drive.
Retention
| Data | Retention |
|---|---|
| Ask Pulse questions, query interpretations, and answers | Volatile app memory for the current Ask Pulse experience; no saved Pulse chat history or analytics/diagnostic content logs. Submitted questions and limited context are processed by Apple PCC. |
| Raw high-frequency Fleet Telemetry | Up to 30 days |
| Private beta request name and email | Until the private beta ends, you withdraw, or you ask us to delete the request |
| Aggregate website analytics | According to the Vercel Web Analytics reporting window; currently one month on the Hobby plan |
| Compact drives, charging sessions, battery samples, preferences, and user-approved route history | Until account deletion, subject to another legitimate user's rights when a vehicle is shared |
| Apple and Tesla authorization credentials | Encrypted until the service is disconnected or the account is deleted; Apple authorization is revoked before deletion completes |
| Identity-link challenges and OAuth exchange codes | Five minutes or less and one use |
| Device and notification tokens | Until session revocation, provider rejection, or account deletion |
| Active Shared ETA location and route | Latest state only, in the live cache; removed when sharing ends, with a four-hour maximum. Shared per-vehicle route state is removed when its last share ends. |
| Active Shared ETA destination comparison data | A keyed, per-share comparison code in the database, not a readable destination name or coordinates; cleared when the share ends or during expiry cleanup, which runs at least hourly. The separate matching key is not included in database backups. |
| Ended Shared ETA metadata without location or destination comparison data | 24 hours for an idempotent ended/expired response, then purged |
| Encrypted database backups | 30 days; account deletion ages out of backup history within 30 days even if backup creation stops |
| Sanitized diagnostics | According to the configured Sentry project retention; deleted or aggregated under the provider's service lifecycle |
| Aggregate operator billing counters | Retained as non-user accounting records without a user, VIN, or location |
These deletion times describe live service records, not immediate physical erasure of every storage copy. Removed cache data can remain in persistence files until their rewrite; Pulse requests a rewrite at least daily. Database recovery logs and obsolete storage pages rotate or are reclaimed through normal database maintenance. Older database backups may include the former readable destination comparison data and expire under the 30-day backup policy.
Service providers and disclosures
- Tesla supplies authorized vehicle data and receives commands that you request.
- Microsoft Azure hosts the Ludic Pulse API, database, cache, and encrypted backups.
- Vercel hosts the public website and provides cookie-free aggregate Web Analytics for non-sensitive public pages.
- Resend delivers an operator email containing the name, email address, and submission time when someone requests private beta access.
- Sentry receives bounded, sanitized crash and performance diagnostics.
- Apple authenticates users who choose Sign in with Apple, distributes the app, processes APNs/Live Activity tokens and notifications, presents user-initiated share sheets, renders native vehicle, route, charging, and Shared ETA maps, resolves selected charging coordinates or addresses, and may calculate clearly labeled estimated route geometry when Tesla omits it.
Providers may process data only for the services they supply to Ludic Pulse. We may also disclose data when legally required or to protect users and the service. We do not sell or share personal data for cross-context behavioral advertising.
Security
Network traffic is encrypted in transit. App credentials are stored as hashes by the service and in iOS Keychain on the device. Apple and Tesla refresh credentials are encrypted at rest. Apple identity tokens are verified for issuer, audience, signature, and one-time nonce. Tesla OAuth uses short-lived, single-use PKCE exchanges. Linking Tesla stages encrypted provider results and requires final approval from the same signed-in app session that initiated the link. Access is scoped to the signed-in user and selected vehicle. No system can be guaranteed perfectly secure; report suspected issues to support.
Your choices and rights
Settings provides route-history controls, individual opt-in notifications, Live Activity privacy controls, structured data export, device-session revocation, and permanent in-app account deletion. Deletion first revokes stored Sign in with Apple authorization, then removes the user's credentials, linked identities, preferences, sessions, attributable usage, and user-associated data; it also attempts to stop telemetry when no other legitimate Ludic Pulse user shares the vehicle. Tesla consent and a vehicle virtual key remain controlled separately, so you may also revoke third-party access in Tesla and remove Ludic Pulse's virtual key from the vehicle.
Manage third-party Tesla access
Changes and contact
Material policy changes will update the effective date and, when appropriate, appear in the app. Questions, export/deletion help, or privacy requests: ludictechnologiesllc@gmail.com.