Teslatlas
Privacy Policy
Effective date: 15 July 2026 Controller: MAGRATHEAN UK LTD, trading as Magrathean, company number 16955343, registered office 16 Caledonian Court, West Street, Watford, England, WD17 1RY. Privacy contact: [email protected] Product: Teslatlas for iOS, iPadOS and macOS, and the Teslatlas website and support channels. This Privacy Policy explains how Magrathean processes personal data in connection with Teslatlas. It is written for users in the United Kingdom, European Economic Area, Switzerland, and other countries where Teslatlas is made available.
Contents
Short version Scope of this policy Who is responsible for the data EU representative and DPO status Personal data processed by the App on your device Data that leaves your device during normal use Data Magrathean does not collect automatically Purposes and lawful bases Legitimate interests Recipients and processors International transfers Retention Exports, support bundles, and sharing risks Cookies, website storage, and app storage App Store privacy labels Automated decision-making and profiling Children and minors Security Your rights Complaints
Short version
Teslatlas is an independent, offline-first Apple analytics app compatible with separately installed TeslaMate and MyTeslaMate sources. After you sync from a source system you choose, the main vehicle-history database, generated analytics, route artifacts, battery insights, charging history, maps, settings, and exports are stored and processed on your device unless you deliberately connect to a source system, enable an optional provider feature, use Apple platform services, or send information to Magrathean for support.
Magrathean does not operate a Teslatlas cloud account service for your vehicle history. Magrathean does not receive your TeslaMate database, trip history, VIN, routes, charge history, geofences, or battery analytics merely because you use the App. The App has no Magrathean cloud relay for vehicle history, no third-party advertising SDKs, no in-app analytics SDK, and no cross-app tracking. Magrathean does not sell your personal data.
There are important exceptions. The App may communicate directly from your device with source systems and providers you choose or enable, including your TeslaMate PostgreSQL database, a MyTeslaMate-compatible API endpoint, Cloudflare Access or another proxy you configure, Apple services such as StoreKit and MapKit, and optional enrichment providers such as Open-Meteo if you enable weather enrichment. If you contact Magrathean or send an export, support bundle, diagnostic file, screenshot, log, or email, Magrathean will process the information you send.
Vehicle telemetry and location data can be personal data. Trip routes, repeated parking places, charging locations, geofences, and timestamps may reveal home, work, routines, travel, and other sensitive inferences. Use Teslatlas only for vehicles and data you are entitled to access.
Scope of this policy
This policy applies to:
- the Teslatlas App for iOS, iPadOS and macOS;
- the Teslatlas website and legal pages;
- support, security, billing-support, and business communications with Magrathean;
- user-initiated exports, support bundles, diagnostics, screenshots, logs, and attachments that you choose to send to Magrathean.
A self-hosted TeslaMate installation is separate open-source software operated by you or by the server operator you choose. Its database, access controls, logs, retention, and hosting are controlled by that operator, not Magrathean. MyTeslaMate and other hosted providers are separate third-party services.
This policy does not control the privacy practices of Apple, Tesla, MyTeslaMate, your TeslaMate server operator or host, Cloudflare, Open-Meteo, your email provider, your network provider, or any third-party endpoint that you configure or use. Those operators and services may act as separate controllers or processors under their own terms and privacy notices.
Who is responsible for the data
Magrathean is the controller for personal data that Magrathean actually receives or otherwise determines the purposes and means of processing for. This includes website requests, support emails, security reports, business correspondence, user-submitted support bundles, limited App Store and subscription-administration data available to Magrathean through Apple, and any other data you deliberately send to Magrathean.
For local vehicle-history data that remains on your device or in systems you control, Magrathean generally does not determine the processing and cannot access the data. You are responsible for ensuring that you have the right to connect Teslatlas to your TeslaMate database, MyTeslaMate account, API endpoint, proxy, cloud account, or vehicle data source.
If you use Teslatlas for a business, fleet, employer, household, or shared-vehicle purpose, you may be a controller or joint controller for the vehicle and location data you import into the App. You are responsible for any notices, permissions, employee/driver disclosures, retention rules, and lawful bases required for that use.
EU representative and DPO status
Magrathean is established in the United Kingdom. EEA users and supervisory authorities may contact Magrathean directly at [email protected]. Magrathean keeps Article 27 EU GDPR representative requirements under review and will publish representative details if required.
Magrathean has not appointed a statutory data protection officer unless a separate notice says otherwise. The privacy contact for Teslatlas is [email protected].
Personal data processed by the App on your device
Depending on how you configure and use Teslatlas, the App may process the following categories locally on your device:
5.1 Connection and authentication data
This may include TeslaMate PostgreSQL host, port, database name, username, password, TLS setting, MyTeslaMate-compatible API URL, bearer tokens, basic-auth username and password, Cloudflare Access client ID and secret, custom authentication headers, and connection diagnostics.
Cloudflare Access credentials, custom proxy headers, database passwords, API tokens, and other auth material should be treated as secrets.
The App stores sensitive connection details using platform security features such as Keychain where supported. Some non-secret settings and fingerprints may be stored in local preferences. You are responsible for the security of your device, server, database, credentials, VPN, network, and exports.
5.2 Vehicle and source data
This may include car identifiers, car names, model information, VIN or partial VIN, firmware version, odometer, vehicle state, battery level, usable battery level, range estimates, climate data, charge limit, charging status, charging power, charging voltage/current, charger type, fast-charger information, charge cable information, energy added, energy used, charge costs, charge locations, geofences, addresses, timestamps, drives, positions, route coordinates, speed, power, elevation, temperature, and TeslaMate database health information.
5.3 Location, trip, route, and map data
This may include exact or approximate latitude/longitude, start and end addresses, route traces, drive segments, route samples, repeated routes, parked sessions, geofences, map camera state, generated route artifacts, raster tiles, tile segments, route caches, trace caches, and map readiness state.
The App does not need to use your phone’s live GPS location to read TeslaMate routes. If a future version asks for device location permission, the App will show the platform permission prompt and a purpose string before using that permission.
5.4 Battery, charging, efficiency, cost, and analytics data
This may include battery-health estimates, battery samples, capacity estimates, battery machine-learning readiness, parked-drain sessions, charge-doctor findings, efficiency buckets, temperature context, energy-cost plans, time-of-use rates, currencies, manual charge-cost overrides, local annotations, diagnostics, confidence labels, and explanations generated by the App.
These analytics are informational only. They are not repair advice, warranty advice, insurance advice, resale valuation, safety certification, or an engineering diagnosis.
5.5 Local preferences, app state, and caches
This may include selected vehicle, units, language/locale, theme, onboarding state, subscription entitlement cache, last sync date, rebuild state, map optimization state, background-task state, performance settings, diagnostic settings, provider-cache status, database migration state, and local app logs needed to operate the App.
5.6 Exports and user-created local content
The App may allow private backups, support bundles, public-share bundles, CSV exports, diagnostics exports, local annotations, and cost-plan entries. Export content depends on the export type. Private backups can include exact VIN, timestamps, places, coordinates, local-only annotations, settings, and diagnostics. Support bundles are intended to reduce risk by masking or shortening VIN, rounding timestamps, clipping place labels, and rounding coordinates. Public-share bundles are intended to remove VIN and place labels and coarsen timestamps and coordinates. No export is risk-free. Review an export before sharing it.
Data that leaves your device during normal use
6.1 Source systems you configure
If you configure a TeslaMate PostgreSQL database, MyTeslaMate-compatible API endpoint, Cloudflare Access endpoint, VPN, reverse proxy, or custom-auth endpoint, the App communicates directly from your device to that system. Magrathean does not receive those source-system requests or responses unless you send them to us.
Your source system may log IP address, device information, request times, URLs, authentication attempts, query volume, and returned data. The operator of that source system is responsible for that processing. If you operate the server, you are responsible for its security, logs, access controls, backup retention, and legal basis.
6.2 Optional online enrichment providers
Online enrichment is off by default. If you enable weather enrichment, the App may send rounded vehicle-location coordinates and relevant dates directly from your device to Open-Meteo to retrieve weather context for charge, parked-drain, and efficiency features. The App stores returned weather data, provider cache entries, fetch logs, and provider audit rows locally on your device.
Magrathean does not receive Open-Meteo enrichment queries or responses unless you choose to send us an export, diagnostic file, screenshot, support bundle, or other support material that includes them. Open-Meteo may receive your IP address and the query details needed to provide the weather response. Open-Meteo’s own terms, privacy practices, availability, rate limits, and retention rules apply.
Future optional enrichment features may include other provider categories, such as elevation, charging-context, electricity-market, or carbon-intensity context. Magrathean will describe the provider, data sent, purpose, and controls before or when such a feature is enabled. If a feature is not exposed in your App version, it is not used merely because it exists in code or documentation.
6.3 Apple services
The App uses Apple platform services. Apple may process data as an independent controller or service provider under Apple’s own terms and privacy documentation. Relevant Apple services may include:
- App Store download, update, review, and purchase infrastructure;
- StoreKit subscription purchase, entitlement, trial, renewal, cancellation, refund, and restore flows;
- App Store Connect subscription and sales reporting available to Magrathean in limited form;
- Apple MapKit and map tile services when maps are displayed;
- iOS, iPadOS, or macOS diagnostics, crash, and performance reporting if you have enabled sharing such information with Apple and developers;
- device-level privacy and security controls.
Magrathean does not receive your payment-card details. Payment information is handled by Apple. Magrathean does not receive your vehicle route coordinates through StoreKit. Magrathean does not receive your local TeslaMate database through Apple merely because you install or use the App.
6.4 Website and support channels
When you visit the website or legal pages, Magrathean or its hosting providers may process technical information such as IP address, user agent, requested URL, referrer, time, error logs, and security logs. The Teslatlas website does not intentionally run Google Analytics, advertising pixels, remarketing tags, or cross-site tracking scripts. When you email or contact support, Magrathean processes the contact details, message content, attachments, metadata, and any files or screenshots you choose to send.
Data Magrathean does not collect automatically
Unless you deliberately send it to Magrathean, Magrathean does not automatically collect:
- your Tesla account credentials;
- your TeslaMate database;
- your PostgreSQL password;
- your MyTeslaMate token;
- your full VIN;
- your trip history;
- your route coordinates;
- your home, work, geofence, or charging locations;
- your battery-history database;
- your charging-history database;
- your local cost plans or annotations;
- your local generated map artifacts;
- your local exports.
Teslatlas does not include third-party advertising tracking. Teslatlas does not use your vehicle data to build advertising profiles. Teslatlas does not sell your personal data.
Purposes and lawful bases
Where Magrathean is the controller, Magrathean relies on the following purposes and lawful bases. Different laws use different terms; this table is written for UK GDPR and EU GDPR purposes.
| Purpose | Data categories | Lawful basis |
|---|---|---|
| Provide the App, legal pages, support links, documentation, and subscription access | App state, subscription entitlement information, support communications, website logs | Contract performance, legitimate interests in operating the product and website |
| Process support requests, bug reports, security reports, and user-submitted exports | Contact details, message content, attachments, diagnostic data, support bundles, screenshots | Contract performance, legitimate interests in support, security, product improvement, and dispute handling |
| Apple in-app subscription administration | Apple-provided subscription, entitlement, purchase, renewal, refund, and sales-report information available to developers | Contract performance, legitimate interests, legal obligations for accounting and tax records |
| Optional online enrichment that you enable | Provider query data such as rounded coordinates and dates, provider responses and local provider cache if included in support material | Consent or your request to enable the feature; contract performance for the enabled feature; legitimate interests in security and debugging if you send support material |
| Website operation, security, analytics, measurement, and campaign attribution | IP address, user agent, request logs, error logs, security logs, pages viewed, events and interactions, referring source, UTM and ad-click identifiers (such as gclid, gbraid, wbraid, msclkid), approximate location derived from IP address, device/browser/OS information | Legitimate interests (Article 6(1)(f) UK GDPR) in operating, securing, and troubleshooting the website and in understanding and improving how the website and campaigns perform; legal obligations where applicable |
| Legal, accounting, tax, corporate, and compliance records | Invoices, Apple reports, correspondence, support records, legal notices | Legal obligation and legitimate interests in record-keeping, claims, and compliance |
| Prevent abuse, misuse, unauthorised access, fraud, or security incidents | Security reports, logs, support metadata, suspected-abuse records | Legitimate interests and legal obligations |
| Send product, legal, or security notices | Email address and communication preferences if available | Contract performance, legitimate interests, or consent depending on the message |
| Marketing communications, if introduced | Contact details and consent/soft opt-in records | Consent or soft opt-in where lawful; legitimate interests only where permitted |
Magrathean does not rely on consent for processing that is necessary to perform a contract, comply with law, defend legal claims, or protect security. Where processing is based on consent, you may withdraw consent at any time, without affecting processing that happened before withdrawal.
Legitimate interests
Where Magrathean relies on legitimate interests, those interests may include operating Teslatlas, securing the product and website, responding to support and security reports, preventing abuse, maintaining records, improving product reliability, enforcing terms, defending legal claims, and communicating product or security information. Magrathean will not rely on legitimate interests where your rights and freedoms override those interests.
Recipients and processors
Magrathean may share or receive personal data with the following categories where necessary:
- Apple, for App Store, StoreKit, platform, review, crash/performance, and map services;
- hosting, DNS, security, email, domain, and infrastructure providers for the website and support channels;
- support, issue-tracking, security, legal, accounting, tax, banking, and professional advisers;
- law enforcement, regulators, courts, counterparties, or public authorities where legally required or reasonably necessary to protect rights or safety;
- acquirers, investors, or advisers if Magrathean is involved in a corporate transaction, subject to appropriate confidentiality and legal safeguards.
When you configure or enable them, your data may also be processed by systems and third parties outside Magrathean’s control, including your TeslaMate server operator or host, MyTeslaMate, Tesla-related services accessed by your source system, PostgreSQL hosts, Cloudflare Access, VPN providers, reverse proxies, Open-Meteo, Apple MapKit, and any other custom endpoint you configure.
Magrathean does not sell vehicle data. Magrathean does not share vehicle data for third-party advertising.
International transfers
Magrathean is based in the United Kingdom. If you are in the EEA, Switzerland, or another jurisdiction with transfer restrictions, your personal data may be transferred to the United Kingdom and to countries where Magrathean’s providers operate.
Where required, Magrathean will rely on an adequacy decision, UK adequacy regulations, the UK International Data Transfer Agreement or Addendum, EU Standard Contractual Clauses, processor terms, or another lawful transfer mechanism. Third-party services you configure or enable may make their own international transfers under their own terms.
Retention
Retention depends on the data category and whether Magrathean receives the data.
| Data category | Typical retention |
|---|---|
| Local App database, caches, map artifacts, generated analytics, provider cache, route history, TeslaMate mirror, preferences, and local exports | Stored on your device until you delete, reset, clear, export, overwrite, or uninstall according to platform behaviour. Some operating-system protected items, such as Keychain entries, may persist according to Apple platform rules unless removed through the App’s reset/delete controls or system/account controls. |
| Source-system logs on your TeslaMate, MyTeslaMate, proxy, Cloudflare, VPN, host, or server | Controlled by you or the third-party operator, not Magrathean. |
| Website access/security logs | Normally up to 90 days unless needed longer for security, abuse investigation, legal claims, or operational troubleshooting. |
| Support emails and ordinary support records | Normally up to 24 months after the support matter closes, unless a longer period is needed for legal, security, accounting, or dispute reasons. |
| Security reports and vulnerability correspondence | Normally up to 6 years, or longer if needed for coordinated disclosure, legal claims, or security history. |
| User-submitted support bundles, exports, diagnostics, attachments, and screenshots | Normally deleted or minimised when the support matter no longer requires them, and usually within 24 months unless needed longer for legal, security, dispute, or accounting reasons. |
| Apple subscription and App Store records available to Magrathean | Retained according to Apple availability and Magrathean’s accounting, tax, legal, and support needs. |
| Accounting, tax, company, legal, and transaction records | Normally 6 years or any longer period required by law. |
| Marketing consent records, if marketing is introduced | Until withdrawal plus a suppression record where needed to respect opt-out. |
You can delete local app data using in-app reset/delete features where available, by deleting local exports you created, and by uninstalling the App. You should also delete data from source systems, backups, iCloud/device backups, email attachments, shared folders, and third-party services where you have copied or exported it.
Exports, support bundles, and sharing risks
Exports are created locally. Nothing is uploaded to Magrathean merely because an export is created. If you share an export through the system share sheet, the destination you choose receives the file and may process it under its own terms.
Private backups are designed for your own use and may contain exact personal data. Support bundles and public-share bundles reduce risk but can still contain personal data or re-identifiable information. Location traces, timestamps, charging locations, repeated routes, vehicle model, and usage patterns can identify you even where VIN and place names are removed. Review any file before sharing it.
If you send Magrathean an export, diagnostic file, support bundle, screenshot, or log, Magrathean will process it for support, debugging, security, legal, and record-keeping purposes. Do not send data about another person unless you have authority to do so.
UK 2026 data-law update: recognised legitimate interests, complaints and local-first boundaries
This notice is drafted for the UK GDPR, the Data Protection Act 2018 and PECR as amended by the Data (Use and Access) Act 2025 where those laws apply.
For ordinary website operation, support, app administration, service delivery, account administration and security logging, we rely on the lawful bases stated elsewhere in this notice. We may rely on the UK GDPR recognised legitimate interests basis only where the relevant statutory condition is available, such as prevention or detection of crime, safeguarding, emergency response, national or public security, or disclosure to an organisation or public authority that needs the information for a public task. We do not rely on recognised legitimate interests for routine commercial marketing, app analytics, cross-site advertising, retargeting or general prospecting.
Teslatlas is local-first for TeslaMate/MyTeslaMate vehicle history, routes, charge data, battery analytics, local mirrors, map artifacts, exports and support bundles. Magrathean normally cannot search, delete or export data stored in your TeslaMate database, MyTeslaMate endpoint, device or vehicle-related local cache unless you send it to us or give us access under a separate written support arrangement.
If a support request, bug report, screenshot, export, diagnostic bundle or legal request contains secrets, tokens, keys, passwords, private footage, raw tenant exports, special-category data, children’s data, criminal-offence data or other high-risk material, we may reject, delete, quarantine, return or restrict that material unless a secure written handling process has been agreed. Sending material to Magrathean does not make Magrathean responsible for data we did not request and cannot reasonably inspect before receipt.
Cookie and storage-technology implementation note
The Teslatlas website does not intentionally use analytics cookies, advertising pixels, remarketing tags, or cross-site tracking scripts. If a Magrathean website or product page uses cookies, local storage, tracking pixels, scripts, tags, link decoration, device/browser signals or similar storage/access technologies, those technologies should be read in three groups:
- strictly necessary, security, anti-abuse, load-balancing, rate-limiting, form-protection and fraud-prevention technologies;
- low-risk analytics or measurement technologies, only if enabled and where an applicable UK PECR exception is available and the use is not for advertising, cross-site tracking or user-level profiling;
- advertising, remarketing, cross-site tracking, tag-based conversion measurement, fingerprinting, behavioural profiling or similar technologies, only if enabled.
The operational position for the Teslatlas website is no intentional analytics, advertising, remarketing, or cross-site tracking tag. You can still block or delete cookies and similar technologies through browser, device, DNS, content-blocking or network controls. This notice describes the processing; the live cookie/tag configuration should be kept aligned with this notice and with any product-specific statement.
Cookies, website storage, and app storage
Website: no intentional analytics or tracking scripts
The Teslatlas website does not intentionally use Google Analytics, advertising pixels, remarketing tags, cross-site tracking scripts, or analytics cookies. We do not display a cookie consent banner because the Teslatlas website is intended to work as a simple static site without non-essential tracking tags.
Hosting, DNS, security, and network infrastructure may still process standard technical request data, such as IP address, user agent, requested URL, referrer, time, error logs, and security logs, to deliver and protect the site.
Your controls: you can block or delete cookies, scripts, and similar technologies in your browser settings; use privacy/content-blocking extensions; use DNS or network controls; or object to our legitimate-interests processing by emailing [email protected]. We do not currently respond to browser Do-Not-Track signals. Blocking non-essential scripts should not stop you reading the site.
App: local device storage
The App uses local device storage, SQLite, Keychain, UserDefaults, generated files, map artifacts, caches, provider caches, and diagnostic state to provide requested App functionality, secure credentials, remember settings, support offline use, and allow user-controlled export/delete operations. This storage is part of the App service requested by you. Optional provider features may create additional local provider caches and audit rows. The App does not use analytics or tracking cookies, does not embed third-party advertising or analytics SDKs, does not send app analytics to Magrathean, and does not track you across other apps or websites.
App Store privacy labels
Apple’s App Store privacy labels use Apple’s own definitions. In general, data that is processed only on your device and is not sent off-device to Magrathean or a third-party partner is not treated by Apple as “collected” by Magrathean for App Store label purposes. Data that leaves your device, including optional provider queries, support submissions, App Store subscription information, or Apple platform data, may need to be reflected in App Store metadata depending on Apple’s rules.
The privacy label is a summary. This policy provides the fuller explanation.
Automated decision-making and profiling
Teslatlas may generate local analytics, estimates, scores, warnings, confidence labels, and insights about battery health, charging, parked drain, efficiency, costs, and route history. These features do not make decisions with legal or similarly significant effects about you. They are informational only and should not be relied on for repair, warranty, insurance, resale, safety, or financial decisions.
Magrathean does not use Teslatlas vehicle data for advertising profiles. Magrathean does not use support data to make automated decisions with legal or similarly significant effects.
Children and minors
Teslatlas is not directed to children. Teslatlas is intended for adults who have authority to access and process the relevant vehicle data. Do not use Teslatlas if you are under 16 without a parent or guardian, and do not use it if you are under 13 in any case.
Do not use Teslatlas to process a child’s personal data unless you have the legal authority and responsibility to do so. If Magrathean learns that it controls children’s personal data without appropriate authority, Magrathean will delete or restrict it where required.
Security
Teslatlas uses platform security controls such as Keychain for sensitive local credentials where supported. The App is designed to read from TeslaMate/MyTeslaMate sources and not to command Tesla vehicles. Direct PostgreSQL access should use TLS, VPN, private networks, strong credentials, and least-privilege database accounts wherever possible. Optional provider calls use HTTPS to the relevant provider.
No app, device, network, or database is perfectly secure. You are responsible for device security, passcodes/biometrics, operating-system updates, server patching, database permissions, TLS certificates, VPN configuration, backups, exported files, and sharing destinations.
Report security issues privately to [email protected] with the subject line “[SECURITY] Teslatlas”. Do not include unnecessary personal data in security reports.
Your rights
Depending on where you are located and which law applies, you may have rights to:
- access personal data Magrathean controls about you;
- correct inaccurate data;
- delete data;
- restrict processing;
- object to processing based on legitimate interests;
- receive data portability for data you provided and that is processed by automated means on consent or contract basis;
- withdraw consent where processing is based on consent;
- complain to a supervisory authority.
These rights apply to data Magrathean controls. Magrathean usually cannot access or delete local vehicle data that remains only on your device, in your TeslaMate database, in MyTeslaMate, in Apple services, in your backups, or in third-party services you choose. For those systems, use the App’s local delete/reset/export controls, your device controls, your server controls, Apple controls, or the relevant third party’s privacy process.
To exercise rights against Magrathean, contact [email protected]. Magrathean may need to verify your identity and may ask for information needed to locate the relevant records. Do not send unnecessary vehicle-history data when making a rights request.
Complaints and rights-request handling
You may complain to Magrathean first by emailing [email protected]. Please include enough information for us to identify the product, website, account, support thread, submission, export, device-local issue or customer engagement involved. Do not include passwords, private keys, bearer tokens, recovery codes or unnecessary raw personal data in the first message.
Where UK data-protection law requires complaint handling, we will acknowledge a data-protection complaint within 30 days and respond without undue delay. A complaint is separate from a UK GDPR rights request, but we may treat the same message as both where it asks us to exercise a data-protection right.
For rights requests, we normally respond without undue delay and within one month of receipt, or within one month of receiving information reasonably needed to confirm your identity or clarify the request. Where the law permits it, we may extend the response period by up to two further months for complex or multiple requests. Searches for access requests will be reasonable and proportionate. For local-first product data, we can usually act only on data Magrathean actually controls or has received.
You may also complain to the UK Information Commissioner’s Office (ICO): https://ico.org.uk/make-a-complaint/. We would prefer the chance to address the issue first, but you are not required to contact us before contacting the ICO.
If EU GDPR applies to your use, you may also complain to a supervisory authority in the EU Member State where you live, where you work or where you believe an infringement occurred.
Third-party rights requests
If you want to exercise rights against Apple, Tesla, MyTeslaMate, Open-Meteo, Cloudflare, your TeslaMate operator or host, your email provider, or another third-party endpoint, contact that operator or third party directly. Magrathean will help where it reasonably can for data Magrathean controls, but Magrathean cannot act on data it cannot access.
Changes to this policy
Magrathean may update this policy to reflect product, legal, security, operational, or provider changes. If Magrathean makes a material change to how it processes personal data as controller, it will take reasonable steps to bring the change to users’ attention before or when the new processing starts. The latest policy will be available at https://teslatlas.eu/privacy.
Vehicle-data sensitivity
Vehicle history can reveal precise locations, home and work patterns, charging locations, travel routines, VIN, vehicle identity, and other sensitive personal information. Treat exported files, screenshots, support bundles, public share files, route data, and diagnostics as sensitive. Review and redact them before sharing. Data is not sent to Magrathean unless you deliberately send material to us.
StoreKit and subscription state
Teslatlas may use Apple StoreKit to check subscription products, trial status, entitlement state, renewal dates, cached entitlement state, restoration, transaction updates, and payment status. Apple manages App Store billing and may process Apple ID, purchase, tax, region, payment, and device data under Apple's terms.
Contact
MAGRATHEAN UK LTD Company number 16955343 16 Caledonian Court, West Street Watford, England, WD17 1RY Email: [email protected]