Privacy Policy

1. An overview of data protection

General information

The following information will provide you with an easy-to-navigate overview of what will happen with your personal data when you visit our website or use our mobile applications, specifically “Tesla Radar.” The term “personal data” comprises all data that can be used to personally identify you.

Data recording on our website and in our app

Who is the responsible party for the recording of data (i.e. the “controller”)? The data is processed by the operator, whose contact information is available under the section “Information Required by Law.”

How do we record your data? We collect your data when you share it with us (e.g., contact forms). Other data is recorded automatically by our IT systems (e.g., technical information like web browsers).

In the Tesla Radar Android app, we access specific device sensors and system information, such as the step counter, Bluetooth Low Energy (BLE) scanner, and location services, to provide and enhance app functionality.

What are the purposes we use your data for? A portion of the information is generated to guarantee the error-free provision of our services. In the “Tesla Radar” app:

BLE scanning data is used to detect nearby Tesla vehicles via their Bluetooth beacon signals.
Location data is used to record where sightings occur and to display them on maps.
Physical activity data (step counter) is used exclusively to optimize battery consumption by adjusting the frequency of BLE scans based on your movement.
Device and observer information is used for leaderboard rankings and community statistics.

What rights do you have as far as your information is concerned? You have the right to receive information about the source, recipients, and purposes of your archived personal data at any time. You also have the right to demand that your data be rectified, blocked, or eradicated.

Analysis tools and tools provided by third parties

There is a possibility that your browsing patterns will be statistically analysed when your visit our website. Such analyses are performed primarily with cookies and with what we refer to as analysis programmes. As a rule, the analyses of your browsing patterns are conducted anonymously; i.e. the browsing patterns cannot be traced back to you. You have the option to object to such analyses or you can prevent their performance by not using certain tools. For detailed information about this, please consult our Data Protection Declaration below.

You do have the option to object to such analyses. We will brief you on the objection options in this Data Protection Declaration.

2. General information and mandatory information

Data protection

The operators of this website and its pages take the protection of your personal data very seriously. Hence, we handle your personal data as confidential information and in compliance with the statutory data protection regulations and this Data Protection Declaration.

Whenever you use this website, a variety of personal information will be collected. Personal data comprises data that can be used to personally identify you. This Data Protection Declaration explains which data we collect as well as the purposes we use this data for. It also explains how, and for which purpose the information is collected.

We herewith advise you that the transmission of data via the Internet (i.e. through e-mail communications) may be prone to security gaps. It is not possible to completely protect data against third party access.

The data processing controller on this website is:

toothR new media GmbH
Urstein Süd 15
5412 Puch bei Salzburg
Austria

E-mail: privacy@toothr.com

The controller is the natural person or legal entity that single-handedly or jointly with others makes decisions as to the purposes of and resources for the processing of personal data (e.g. names, e-mail addresses, etc.).

A wide range of data processing transactions are possible only subject to your express consent. You can also revoke at any time any consent you have already given us. To do so, all you are required to do is sent us an informal notification via e-mail. This shall be without prejudice to the lawfulness of any data collection that occurred prior to your revocation.

In the event that data are processed on the basis of Art. 6 Sect. 1 lit. e or f GDPR, you have the right to at any time object to the processing of your personal data based on grounds arising from your unique situation. This also applies to any profiling based on these provisions. To determine the legal basis, on which any processing of data is based, please consult this Data Protection Declaration. If you log an objection, we will no longer process your affected personal data, unless we are in a position to present compelling protection worthy grounds for the processing of your data, that outweigh your interests, rights and freedoms or if the purpose of the processing is the claiming, exercising or defence of legal entitlements (objection pursuant to Art. 21 Sect. 1 GDPR).

If your personal data is being processed in order to engage in direct advertising, you have the right to at any time object to the processing of your affected personal data for the purposes of such advertising. This also applies to profiling to the extent that it is affiliated with such direct advertising. If you object, your personal data will subsequently no longer be used for direct advertising purposes (objection pursuant to Art. 21 Sect. 2 GDPR).

Right to log a complaint with the competent supervisory agency

In the event of violations of the GDPR, data subjects are entitled to log a complaint with a supervisory agency, in particular in the member state where they usually maintain their domicile, place of work or at the place where the alleged violation occurred. The right to log a complaint is in effect regardless of any other administrative or court proceedings available as legal recourses.

Right to data portability

You have the right to demand that we hand over any data we automatically process on the basis of your consent or in order to fulfil a contract be handed over to you or a third party in a commonly used, machine readable format. If you should demand the direct transfer of the data to another controller, this will be done only if it is technically feasible.

SSL and/or TLS encryption

For security reasons and to protect the transmission of confidential content, such as purchase orders or inquiries you submit to us as the website operator, this website uses either an SSL or a TLS encryption programme. You can recognise an encrypted connection by checking whether the address line of the browser switches from “http://” to “https://” and also by the appearance of the lock icon in the browser line.

If the SSL or TLS encryption is activated, data you transmit to us cannot be read by third parties.

Information about, blockage, rectification and eradication of data

Within the scope of the applicable statutory provisions, you have the right to at any time demand information about your archived personal data, their source and recipients as well as the purpose of the processing of your data. You may also have a right to have your data rectified, blocked or eradicated. If you have questions about this subject matter or any other questions about personal data, please do not hesitate to contact us at any time at the address provided in section “Information Required by Law.”

Right to demand processing restrictions

You have the right to demand the imposition of restrictions as far as the processing of your personal data is concerned. To do so, you may contact us at any time at the address provided in section “Information Required by Law.” The right to demand restriction of processing applies in the following cases:

In the event that you should dispute the correctness of your data archived by us, we will usually need some time to verify this claim. During the time that this investigation is ongoing, you have the right to demand that we restrict the processing of your personal data.
If the processing of your personal data was/is conducted in an unlawful manner, you have the option to demand the restriction of the processing of your data in lieu of demanding the eradication of this data.
If we do not need your personal data any longer and you need it to exercise, defend or claim legal entitlements, you have the right to demand the restriction of the processing of your personal data instead of its eradication.
If you have raised an objection pursuant to Art. 21 Sect. 1 GDPR, your rights and our rights will have to be weighed against each other. As long as it has not been determined whose interests prevail, you have the right to demand a restriction of the processing of your personal data.

If you have restricted the processing of your personal data, these data – with the exception of their archiving – may be processed only subject to your consent or to claim, exercise or defend legal entitlements or to protect the rights of other natural persons or legal entities or for important public interest reasons cited by the European Union or a member state of the EU.

3. Recording of data on our website and in the “Tesla Radar” App

Server log files

The provider of this website automatically collects and stores information in server log files, which your browser communicates to us automatically. This data is not merged with other data sources.

Data collected by the Tesla Radar App

The Tesla Radar Android app collects and processes the following categories of data. We are committed to transparency and list every type of data the app acquires:

3.1 Device and Observer Information

When you use Tesla Radar, the app collects the following device-level information:

Data	Purpose	Transmitted to server?
Advertising ID (Google Play Services) or a locally generated random UUID	Used as a unique, pseudonymous observer identifier for leaderboard rankings and data uploads	Yes
Device manufacturer (e.g. Samsung)	Displayed in community leaderboards	Yes
Device model (e.g. Galaxy S24)	Displayed in community leaderboards	Yes
Device nickname (user-provided)	Displayed in community leaderboards	Yes
Android version	Displayed in community leaderboards	Yes
App version	Used to identify outdated app versions	Yes
Install referrer	Used to track referral-based installations for the referral program	Yes

Legal Basis: Art. 6 Sect. 1 lit. f GDPR (legitimate interest in providing community features and leaderboards).
Data Transmission: This data is transmitted to our server encrypted (AES-192 + RSA hybrid encryption) via HTTPS to a Google Apps Script endpoint.

3.2 Bluetooth Low Energy (BLE) Scan Data

The app continuously scans for Bluetooth Low Energy (BLE) iBeacon advertisements broadcast by Tesla vehicles. For each detected beacon, the app records:

Data	Purpose	Transmitted to server?
BLE device name (18-character Tesla beacon identifier)	Used to identify and correlate vehicle beacons (C, D, P, R beacons)	Yes (as vehicle identification)
BLE device (MAC) address	Used to correlate multiple beacons from the same vehicle	Yes (stored with vehicle record)
Beacon UUID, Major, Minor values	Used for vehicle type classification	Yes (minor value stored)
RSSI (signal strength)	Used to estimate proximity to the vehicle	No
Estimated distance	Derived from RSSI for distance display	No

The BLE beacon identifiers broadcast by Tesla vehicles do not contain personally identifiable information about the vehicle’s owner.
Legal Basis: Art. 6 Sect. 1 lit. f GDPR (legitimate interest in providing the core vehicle-detection functionality of the app).

3.3 Location Data

The app collects GPS/network location data when a Tesla vehicle is detected:

Data	Purpose	Transmitted to server?
Latitude	Recorded with each vehicle sighting to show sighting locations on maps	Yes
Longitude	Recorded with each vehicle sighting to show sighting locations on maps	Yes
Altitude	Recorded with each vehicle sighting	Yes

Location data is collected via GPS, network provider, and passive provider.
The app requests foreground location access as part of its foreground service and may request background location access so it can detect Tesla vehicles while running in the background.
Location data is stored locally in the on-device SQLite database and transmitted to our server alongside vehicle sighting records (encrypted via AES/RSA).
Legal Basis: Art. 6 Sect. 1 lit. f GDPR (legitimate interest in providing the geo-located vehicle sighting feature and community heatmaps).

3.4 Physical Activity Data (Step Counter)

The app requests access to your device’s Physical Activity sensors (Step Counter).

Purpose: The app uses this data to determine if you are currently in motion. This allows the app to dynamically adjust the frequency with which it scans for BLE beacon signatures of Tesla vehicles.
Battery Optimization: By reducing scan frequency when you are stationary, the app significantly minimizes battery drain.
Privacy & Local Processing: This health-related data is processed exclusively on your mobile device. At no point is this data transmitted to our servers, stored externally, or shared with third parties.
Legal Basis: Art. 6 Sect. 1 lit. f GDPR (legitimate interest in the technical optimization of the app and preservation of the user’s device battery life).

3.5 Vehicle Sighting Records

When a Tesla vehicle is detected via BLE, the app creates a sighting record that is stored in the local SQLite database and periodically uploaded to our server:

Data	Purpose	Transmitted to server?
Vehicle identification (derived from BLE beacon name)	Unique pseudonymous vehicle identifier	Yes
Vehicle type (Model 3, Y, S, X, Semi, Cybertruck)	Determined via our API for display purposes	Yes
Vehicle UUID (iBeacon UUID)	Classification of vehicle generation	Yes
Beacon addresses (C, D, P, R)	BLE MAC addresses of the vehicle’s beacons	Yes
Sighting timestamp	When the vehicle was detected	Yes
Sighting location (lat, lon, alt)	Where the vehicle was detected	Yes

Vehicle type identification is performed by sending the vehicle’s BLE-derived identifier to api.teslaradar.com via HTTPS. No personal data about the vehicle owner is retrieved.
User-provided data such as vehicle nickname, color, variant, and range may be added by the user and are stored locally. Vehicle records (including any user-provided data) are uploaded to our server.
Legal Basis: Art. 6 Sect. 1 lit. f GDPR (legitimate interest in providing community vehicle statistics, rankings, and heatmaps).

3.6 Battery and Power State

The app monitors the device’s power state (plugged in via USB/AC, or unplugged) and battery status.

Purpose: Exclusively used to dynamically adjust BLE scan frequency — increasing scan aggressiveness when the device is charging and decreasing it on battery power.
Privacy & Local Processing: This data is processed exclusively on your mobile device and is never transmitted to any server.
Legal Basis: Art. 6 Sect. 1 lit. f GDPR (legitimate interest in battery optimization).

3.7 Data Uploaded to Our Servers

The app periodically uploads data to our servers via a Google Apps Script endpoint. All data is encrypted before transmission using AES-192 symmetric encryption, with the AES key itself encrypted using RSA public-key encryption (hybrid encryption). The uploaded payloads include:

Device Status — observer information (advertising ID, device manufacturer, model, name, install referrer, Android version, app version).
Vehicle Records — detected vehicle data (identification, type, beacon addresses, UUID, timestamps) along with observer information.
Vehicle Sighting Logs — individual sighting events (vehicle identification, location, timestamp) along with observer information and an encrypted observer key.

Data uploads occur approximately once per minute when there is unpublished data and no pending location updates. Uploads can be disabled by the user in the app settings (“Share Data” toggle).

3.8 Data Downloaded from Our Servers

The app periodically downloads the following aggregated, anonymized community data from our servers:

Data	Purpose
Device Rankings (leaderboard)	Shows how users rank by radar points, spotted vehicles, etc.
Country Rankings	Aggregated vehicle counts per country
Region Rankings	Aggregated vehicle counts per region
Global Activity Feed	Recent community observation events
Heatmap Data	Aggregated geographic distribution of sightings for map display
Map Statistics	Total counts (observers, vehicles, view logs, countries, regions)
Personal Device Statistics	The user’s own rank, points, and activity data

This downloaded data is cached locally using SharedPreferences so the app can display data immediately on startup, even when the server is temporarily unreachable. Downloads can be disabled by the user in the app settings (“Download Statistics” toggle).

3.9 Local Data Storage

The app stores data in the following local storage mechanisms:

SQLite Database (TESLARADAR_VEHICLES.DB): Stores all detected vehicles and sighting logs on-device. Users can configure automatic purging of old entries in the app settings.
SharedPreferences: Stores user preferences (scan aggressiveness, notification settings, nicknames), the encrypted observer key, the advertising ID, and cached server data (rankings, statistics, heatmaps).
Android Keystore: Stores cryptographic keys (preferences encryption key, observer key) in hardware-backed secure storage.

3.10 Cryptographic Keys and Security

An observer key (AES-192) is generated on first launch, encrypted with an Android Keystore-backed key, and stored in SharedPreferences. This key is used to provide a cryptographic identity for sighting log uploads.
All data uploaded to our servers is encrypted using a hybrid encryption scheme (AES-192 for data, RSA for key exchange) with our public key embedded in the app.
The observer key is transmitted with vehicle log uploads to allow server-side verification.

3.11 Third-Party API Access

The app contacts the following external endpoints:

Endpoint	Purpose	Data Sent
`api.teslaradar.com`	Vehicle type identification	BLE-derived vehicle identifier (pseudonymous, not PII)
`script.google.com` (Google Apps Script)	Data upload and statistics download	Encrypted payloads containing observer + vehicle data

Vehicle Type API: The app sends the vehicle’s BLE-derived identifier (a 16-character string from the beacon advertisement) to api.teslaradar.com to determine the Tesla model type. This identifier does not contain personally identifiable information about the vehicle owner.

3.12 Referral System

The app includes a referral program. When a user shares the app:

The user’s Advertising ID is hashed (MD5) to create a pseudonymous referral hash.
A Play Store install link containing this referral hash is generated.
The referral hash is shared only when the user actively chooses to share the app via the built-in share function.

Request by e-mail, telephone or fax

If you contact us by e-mail, telephone or fax, your request, including all resulting personal data, will be stored and processed by us for the purpose of processing your request. We do not pass these data on without your consent.

4. Analysis tools and advertising

Google Mobile Ads SDK

The app integrates the Google Mobile Ads SDK (AdMob, Application ID: ca-app-pub-4328632951652635~2486107169). Google may collect the following data through the Ads SDK:

IP address (for ad serving and fraud prevention)
Device identifiers (Advertising ID)
App usage data (ad interactions)

For more information, please consult Google’s Privacy Policy: https://policies.google.com/privacy.

Legal Basis: Art. 6 Sect. 1 lit. f GDPR (legitimate interest in financing the free app through advertising).

Matomo (formerly called Piwik)

This website uses the open source web analysis service Matomo. Matomo uses so-called “cookies,” which are text files that are stored on your computer and that make it possible to analyse your use of this website. In conjunction with this, the information about the use of this website generated by the cookie will be archived on our server. Prior to archiving, the IP address will first be anonymized.

Matomo cookies will remain on your device until you delete them.

The storage of Matomo cookies and the use of this analysis tool are based on Art. 6 Sect. 1 lit. f GDPR. The website operator has a legitimate interest in the analysis of user patterns, in order to optimize the operator’s web offerings and advertising.

The information generated by cookies concerning the use of this website shall not be shared with any third parties. You may prevent the storage of cookies at any time by making pertinent changes to your browser software settings; however, we have to point out that in this case you may not be able to use all of the functions of this website to their fullest extent.

If you do not consent to the storage and use of your data, you have the option to deactivate the storage and use of such data here. In this case, an opt out cookie will be placed in our browser, which prevent the storage of usage data by Matomo. If you delete your cookies, this will also result in the deletion of the Matomo opt out cookie. Hence, you will have to reactivate the opt out when you return to visit our website.

5. Plug-ins and Tools

Google Web Fonts

To ensure that fonts used on this website are uniform, this website uses so-called Web Fonts provided by Google. When you access a page on our website, your browser will load the required web fonts into your browser cache to correctly display text and fonts.

To do this, the browser you use will have to establish a connection with Google’s servers. As a result, Google will learn that your IP address was used to access our website. The use of Google Web Fonts is based on our interest in presenting our online content in a uniform and appealing way. According to Art. 6 Sect. 1 lit. f GDPR, this is a legitimate interest.

If your browser should not support Web Fonts, a standard font installed on your computer will be used.

For more information on Google Web Fonts, please follow this link: https://developers.google.com/fonts/faq and consult Google’s Data Privacy Declaration under: https://policies.google.com/privacy?hl=en.

Font Awesome

To ensure that fonts used on this website are uniform, this website uses so-called Web Fonts provided by Fonticons, Inc. When you access a page on our website, your browser will load the required web fonts into your browser cache to correctly display text and fonts.

To do this, the browser you use will have to establish a connection with Fonticons Inc’s servers. As a result, Fonticons, Inc. will learn that your IP address was used to access our website. The use of Web Fonts is based on our interest in presenting our online content in a uniform and appealing way. According to Art. 6 Sect. 1 lit. f GDPR, this is a legitimate interest.