TL;DR: TesCam Studio edits your videos on your own device, and your dashcam footage never reaches our servers. The app has no analytics, advertising or tracking SDKs, and we don't sell your data.
Some features do send information. Some of this happens automatically as you use the app. From launch, whether or not you've joined anything, the app sends a random install ID to our server to check your community standing and Supercharger Day status. It also loads map tiles, city outlines and community items, looks up place names with Apple, and checks the Hub price and firmware updates. The rest only runs if you choose it: the FSD Community Map (public by default once you join), publishing to the Community Gallery (public), Hub problem reports, Cloud Backup to your own iCloud Drive or Google Drive, and connecting Teslascope. Each one is described below.
Introduction
TesCam Studio is made by Paper AI LLC ("we," "our," or "us"). This Privacy Policy explains how we handle information in the TesCam Studio app for iPhone, iPad and Mac ("the app"), the TesCam Hub accessory, and the services we run for them: thefsdmap.com (the FSD Community Map and Community Gallery), our Hub problem-report service, and this website.
Information We Don't Collect
TesCam Studio is designed with privacy at its core. Here is what holds under every setting:
Your dashcam videos never reach our servers. The only media our servers receive are the lock sounds, wraps and light shows you choose to publish to the Community Gallery. If you attach a video or screenshot to a support email, it's kept in our support mailbox.
We never receive raw GPS coordinates or point-by-point routes from your videos or your phone. If you join the FSD Community Map, we receive the location-based information described in that section. Most of it is approximate areas, but for Supercharger Day and landmark badges it includes which specific charger or landmark your car passed, and when.
No analytics, crash-reporting, advertising or tracking SDKs are built into the app.
We don't sell or rent your data, and we don't use it for advertising.
No sign-up is needed. The app never asks for your real name, email address or Apple ID. If you join the community map or publish to the gallery, it asks you to pick a public name. If you connect Google Drive, the app shows your Google email address, which stays on your device (see Google Drive). We only have your contact details if you give them to us: by emailing or messaging us, filling in a website form, joining the referral program, claiming a prize, joining a TestFlight beta, or buying a Hub.
Local Processing
All video playback, editing, telemetry reading and exporting happens on your device. No cloud processing of your video is involved. Your videos leave your device only when you choose to, or inside your own device backup (see Apple Services):
share or save an export yourself (for example to Photos, Files, or a social app),
back up exports or clips to your own iCloud Drive or Google Drive (see Cloud Backup), or
move clips between your own TesCam Hub and your devices over your local network (see TesCam Hub).
Recordings made with the in-app phone drive recorder, including their audio and the location and motion samples recorded with them, are stored on your device and are left out of device backups.
Device Permissions
The app asks for these permissions. Each one is used on your device for the purpose listed, and you can change any of them in your device's Settings.
Location: used to show where you are on the FSD Map and trace the drive you're on until your Hub imports it, find nearby Superchargers, tag phone drive recordings, and check in at landmark chargers. On the day of a Supercharger Day event you've joined, from two hours before the start until syncs close, the app also uses location in the background, which shows the location indicator. The app never sends your phone's coordinates to our servers. Two things based on them are sent elsewhere, both covered below: the first GPS fix of each phone recording is sent to Apple to look up a place name (see Apple Services), and, if you've joined the community map, the app tells our server which landmark you checked in at and when (no coordinates).
Camera: used to record drive videos with the phone drive recorder, and to scan the QR code on your TesCam Hub's sticker during setup.
Microphone: used to record audio with your phone drive recordings, to record a custom lock sound, and to record a song for a light show. Recordings stay on your device unless you include them in an export you share or back up, send them to your Hub, or publish them to the Community Gallery.
Motion sensors: the phone drive recorder records motion data alongside the video, to line your recording up with your Tesla footage. Some screens also use device tilt for a visual effect. Motion data stays on your device.
Photos: used to let you pick Tesla videos from your photo library, and to save your exports to it.
Notifications: used for Supercharger Day reminders and badge alerts. These are scheduled on your device.
Local Network: used to find and connect to your TesCam Hub.
Wi-Fi configuration: used to join your Hub's Wi-Fi network from inside the app, after iOS asks you to confirm.
Files: the app reads the TesCam files and folders you select and saves exports where you choose. When you start a Cloud Backup of a clip list, the app reads every clip in the tab or filter you chose to back up.
TesCam Hub
The TesCam Hub stores your Tesla's dashcam clips so you can view and import them wirelessly. Your clips stay on your Hub and on the devices you import them to. We do not receive them.
Connecting to your Hub
The app talks to your Hub directly over your local network: either the Hub's own Wi-Fi network (protected by the WPA2 password on its sticker), or your home Wi-Fi once you've joined the Hub to it. This traffic never goes through our servers.
Pairing uses the 6-digit code on the sticker. The Hub stores a pairing token for each device you pair, together with that device's name. On iPhone and iPad that name is the generic "iPhone" or "iPad". On a Mac it is the computer's name, which often includes the owner's name.
If you connect your Hub to home Wi-Fi, the network name and password go only to your Hub, which saves them in its network settings. They never come to us. The network name can appear in the Hub's logs (see Hub Problem Reports).
Lock sounds, wraps and light shows you send to your car are written only to your Hub and its storage drive, unless you separately publish them to the Community Gallery.
Opening the Hub's built-in web page in a browser stores a sign-in cookie in that browser and records your acceptance of the Hub Terms in the browser's local storage. The page loads nothing from the internet. Your acceptance of the Hub Terms in the app is recorded only on your device.
What the Hub keeps
Your clips, until you or your car delete them.
A drive history with GPS position, speed, heading, gear and FSD/Autosteer state, about once per second, read from your clips so the app can map your drives, plus driving-event tags for each clip (hard braking, hard acceleration, hard cornering and FSD disengagements). It is kept for 60 days.
System logs (see Hub Problem Reports for what they can contain), the pairing tokens and device names described above, your saved Wi-Fi networks, and the lock sound, wraps and light shows you've sent.
A factory reset removes the pairings, saved Wi-Fi networks and thumbnail cache. It does not erase clips, the 60-day drive history, or the logs. If you plan to sell or give away your Hub, contact us first.
When the Hub uses the internet
The Hub can only reach the internet once you've connected it to your home Wi-Fi. It then:
Checks for firmware updates. The app asks the Hub to check automatically once per app session when it connects, and you can also check by hand. The Hub downloads the update list from updates.tescamstudio.com. It sends no serial number or other identifier, and decides on the Hub itself whether an update applies to it. Like any web request, this shows the update host your network's public IP address. With "Update via This Device," your phone downloads the update from the same host and passes it to the Hub over your local network.
Tests connectivity by briefly connecting to Cloudflare's public DNS service (1.1.1.1) and looking up our update server's address. No data is sent.
Keeps its clock correct using the operating system's standard internet time service.
The Hub contains no analytics or usage reporting, contacts nothing on the internet except as listed above, and never uploads your clips anywhere.
Maintenance login
Like many Linux devices, the Hub runs an SSH maintenance login. It can only be reached from the Hub's own Wi-Fi network or from the local network the Hub has joined, not from the internet. It is protected by credentials that only we hold, and we use it during manufacturing and repair. We have no way to reach your Hub over the internet, and there is no remote-access connection from your Hub to us.
Records we keep about Hubs
When each Hub is made, we keep a manufacturing record of its serial number, its factory Wi-Fi name and password, and its pairing code, so we can support and replace units. These factory codes stay the same for the life of the Hub.
If we enrol your Hub in a beta firmware program, its serial number is listed in our public update file so it can receive the beta build.
If you contact us for support, our support records keep your Hub's serial number in plain text, alongside your name, contact details and order number (see Website, Store and Support).
Hub Problem Reports
Report a Problem lets you send us a Hub support request. When you tap Email support or DM @TesCamStudio on X, the app first uploads your report to our report service, then opens Mail or X with a link to it. The upload happens as soon as you tap, even if you then decide not to send the message. Copy Report copies the text to your clipboard without uploading anything.
The upload contains:
What you typed: your description of the problem, your storage drive, and your Tesla's year and model, plus your app version.
The diagnostics report shown on screen: your Hub's serial number and firmware version, how your device is connected to it (including local IP addresses), storage-drive and system details, Wi-Fi signal information, clip counts, recent events and errors.
If your Hub is paired and reachable, the Hub's system logs from the last 24 hours.
Please be aware that the Hub's logs can include the names of Wi-Fi networks it has used (such as your home network), the hardware (MAC) addresses of your router and of devices that joined the Hub, local IP addresses, and the Hub's own Wi-Fi name and password as printed on its sticker. A router's hardware address can sometimes be used to estimate where it is. No video or GPS data is included.
Reports are stored on our report service, which Cloudflare hosts, and are deleted automatically after 30 days. They include your Hub's serial number in plain text. They aren't listed or indexed anywhere, but anyone who has the link can open the report and download the logs during those 30 days, so share the link only with us. To limit abuse, our service records the uploading IP address for 60 seconds.
The 30-day deletion applies only to the copy on our report service. If you email us, your message and the attached log file go to arthur@tescamstudio.com and stay in our support mailbox. If you DM us on X, your message and the links in it are held by X under X's own policies. You can ask us to delete support emails at any time.
Cloud Backup (iCloud Drive and Google Drive)
Cloud Backup copies your exports, and the clips you choose to back up, to your own iCloud Drive or Google Drive. It is off until you use it. Nothing uploads on its own or on a schedule. An upload only starts when you tap Save to iCloud Drive or Save to Google Drive after an export, or Back Up in your clip list and then confirm.
Files go directly from your device to your iCloud Drive or Google Drive account. They never pass through our servers, and we cannot see them.
What gets uploaded
Exports: the video you made, including any overlays you added (some widgets show speed, location or a map).
Clip backups: the original Tesla camera files, unchanged. Depending on your car's software, these files can contain location, speed and heading data that the car embeds in the video.
Files are placed in a folder named TesCam Studio, under Exports or Clips. Backed-up Hub clips go in a folder named "Hub" plus the last 6 characters of your Hub's serial number, with Tesla's original folder and file names, which include the recording date and time.
Tesla's event.json files, thumbnails, and encrypted clips are not uploaded. Encrypted clips are skipped, and the app tells you how many.
Google Drive uploads use Wi-Fi only. iCloud Drive uploads follow your device's iCloud cellular setting.
Clips from your TesCam Hub
The Hub never uploads anything to the cloud itself. When you back up Hub clips, each clip passes through your device: the app downloads it from your Hub over your local network and keeps a temporary copy in the app's storage. That copy is deleted as soon as the upload is confirmed, or if you cancel. If an upload fails, the temporary copy stays until you retry or remove it under Settings > Connected Services > Cloud Storage > Uploads.
The app also keeps a local history of past uploads on your device: file names, sizes, the destination's file IDs, and an internal reference to the account used. This stops the same clip being backed up twice. It stays on your device until you delete the app.
iCloud Drive
iCloud Drive needs no sign-in in the app. It uses the iCloud account already on your device. The app places files in its own iCloud Drive folder (shown as TesCam Studio in Files and Finder), and Apple's iCloud service uploads them. The copy on your device is removed once iCloud reports the upload is complete. The app never reads your Apple ID. These files are covered by Apple's iCloud terms and stay until you delete them. To stop, turn off iCloud Drive for TesCam Studio in your device's Settings.
Google Drive (Google user data)
To use Google Drive, tap Connect Google Drive under Settings > Connected Services > Cloud Storage and sign in on Google's own page. The app never sees your Google password.
Permission requested: the app requests one permission, Google's drive.file scope, which lets the app work only with files it creates itself. It cannot see, open, change or delete any other file in your Google Drive.
What Google data the app accesses, and why:
Your Google account email address and display name: to show which account is connected, and to warn you if you reconnect with a different account.
Your Google Drive account ID: to tell accounts apart on your device.
Your Drive storage used and total: to show how much space is free, and to warn you before a backup that won't fit.
The IDs and sizes of the folders and files the app creates: to put uploads in the right folder, resume interrupted uploads, confirm each upload finished, and avoid uploading the same clip twice.
Access and refresh tokens issued by Google: to upload on your behalf.
The app does not download or read the contents of any file in your Drive, including the files it uploaded, and it never deletes or shares files. It does not access Gmail, Contacts or any other Google service.
How the app uses it: Google user data is used only to provide the Google Drive backup feature you see in the app: showing which account is connected and how much space it has, and uploading the files you choose. We do not use it for advertising, and we do not sell it. No person, including us, reads it, and it is not used to develop, improve or train AI or machine-learning models.
How it's stored and protected: all of this stays on your device. The tokens are stored in your device's Keychain and are not synced through iCloud Keychain. Your account name and email address are stored in the app's settings on your device, and upload records in the local upload history described above. None of it is sent to our servers. Like other app data, it can be included in your own device backup (iCloud Backup or a computer backup). The app talks to Google only over encrypted connections (HTTPS).
How it's shared: we don't share Google user data with anyone. It never leaves your device except to go to Google, to do what you asked, or inside your own device backup.
How long it's kept and how to delete it: it stays on your device while Google Drive is connected. To disconnect, go to Settings > Connected Services > Cloud Storage and tap Disconnect. The app asks Google to revoke its access, then deletes the sign-in tokens and your Google account name and email address from your device. If Google can't be reached at that moment, the local data is still deleted. The upload history for that account (file names, sizes, Drive file IDs and an internal account reference) and any unfinished uploads stay on your device until you delete the app. If you delete the app without disconnecting first, the tokens can remain in your device's Keychain. Files already uploaded stay in your Drive until you delete them there. You can also remove TesCam Studio's access at any time at https://myaccount.google.com/permissions.
TesCam Studio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
FSD Community Map
The FSD Community Map is an optional shared map, at thefsdmap.com and in the app, showing where the community has driven on FSD and Autosteer, with leaderboards, titles and events. It is off by default. The app offers to let you join only if you have a TesCam Hub. Once you join, the app syncs automatically after each Hub sync.
Community data is pseudonymous, not anonymous. It is stored against an install ID and can carry a public name you choose. On the community map, your Hub's serial number is stored only as a keyed hash, and we never publish it or the hash. (The one place a serial is public is our update file, if we enrol your Hub in a beta; see TesCam Hub.) Because we hold the key and keep manufacturing records of every Hub, we can tell which Hub a contributor's hash belongs to. Where our order, support, prize-claim or problem-report records connect that Hub or your public name to you, we can also tell who you are.
What the app sends once you've joined
An install ID: a random identifier generated on your device. It is not your Apple ID, email address or device serial.
Your Hub's serial number, while a Hub is connected. Our server converts it to a keyed hash (HMAC) on receipt and stores only the hash. We use the hash to tell which contributions come from the same Hub, to allow only one Hub per player in each Supercharger Day, and for gallery moderation (a gallery block can apply to a Hub).
A public name, if you choose one (3–20 characters). Names must be unique across the community map and the Community Gallery.
Your settings: whether you've turned on Anonymous mode (off by default), and whether your public profile page is on (on by default).
Lifetime totals: FSD miles, total miles, longest single FSD run, time on FSD, and Autosteer miles and time.
Disengagements: how many times FSD handed control back to you, and the date and time of the most recent one. Anything within 500 feet of the start or end of a drive is excluded. We don't display this time anywhere.
Monthly mileage: FSD miles and total miles for each calendar month you drove.
A home state: one US state, picked from where you drive most.
The areas you've driven on FSD or Autosteer, as grid squares about 220 metres (roughly 1/8 mile) across. Each square is marked FSD or Autosteer and labelled with its city and state. Manual driving lights nothing. Squares within about a quarter mile (400 m) of the start or end of every drive are removed on your device before anything is sent, so the map never shows where a trip begins or ends.
Our server records when it first received each square. Together, the squares you've uploaded and those times form an approximate record of the roads you've driven on FSD and Autosteer, apart from the start and end of each drive. For the community map, our server never receives raw GPS coordinates, point-by-point routes, video or audio.
Help map FSD trouble spots is a separate switch, off by default, and not currently shown in the app. When it is on, the app also shares takeovers you've labelled Critical or Navigation, each as one grid square and a calendar month, stored against your install ID. Takeovers labelled Drive-Thru, Parking or Preference are never shared. A square only becomes publicly visible, as a rough count, once at least three different drivers have flagged it.
What is public
Joining makes you public by default. If you don't choose a name, you appear as "Driver-" followed by the last four characters of your install ID, together with your figures. You stay public unless you turn on Anonymous mode. Anyone on the internet can see:
Leaderboards and boards (the top 20 or 50 in each): your name with your FSD miles, longest run, manual miles, Autosteer miles, FSD hours, number of cities or area covered, and, on the newest-members list, the exact date and time you joined.
Titles: Mayor and Founder of cities, Governor of a state, President, and past ("Former") titles. We keep a timestamped history of who has held each title.
Your public profile page (thefsdmap.com/driver/your-name). It is on by default once you've set a name, and shows your rank, FSD miles, longest run, FSD hours, Autosteer miles, hands-free hours, member-since month, badges, titles, Supercharger Day results and landmark badges. It also lists every city and state you've driven in, with how many squares you've covered in each and the month your first square there reached our server. Link previews of the page show a summary of your stats.
The map itself: every square, how many drivers have covered it, and whether it's Autosteer-only (no names). Per city, it shows the number of drivers, the Mayor and Founder names, and the exact time the city last gained new ground. In a city with only one driver, every square shown there belongs to that driver.
Community statistics: totals, daily activity counts, and the location and time of the most recently added square (no name). State averages are published only for states with at least five drivers.
Contest standings and winners' names (see below).
Anonymous mode and your profile page
Anonymous mode removes your name from leaderboards, awards and contests. Titles you hold show as "Anonymous." Your squares still count on the map, and your totals still count toward community figures.
The public profile page switch turns your profile page off.
Anonymous mode does not apply to the Community Gallery. Gallery items always show your community name.
Contests and prizes
From time to time the community map runs contests, such as most FSD miles or most new cities in a period. Members who have a name and are not anonymous are entered automatically. During a contest the app also sends your FSD miles inside the contest window. Live standings (name and miles or cities) and winners' names are public. If you win, the claim code is shown only in your app, and you claim the prize by emailing it to us. That gives us your email address and anything you include, such as a delivery address, which we use only to deliver the prize. Promotions run with a partner have their own official rules naming the partner and what they receive.
Supercharger Day
Supercharger Day is a monthly collect-the-chargers event with its own Join button for each event. To take part you must already be a named, non-anonymous community member who joined before the event's cutoff.
For each Supercharger your car passes on FSD or Autosteer, within about a quarter mile (the distance is set for each event) and based on your Hub's GPS track, the app sends the charger's ID, the time your car passed it, whether FSD or Autosteer was active, your install ID, and your Hub serial (hashed on receipt, and used to allow one Hub per player). Charger locations are public, so each pass is effectively a place and a time.
On the day of an event you've joined, from two hours before the start until syncs close, the app uses your phone's location in the background. That keeps it syncing your Hub and sending passes while your phone is locked, and lets it show the nearest charger. Your phone's location is not uploaded.
Pass-level data is deleted 7 days after results. Your results (chargers collected and rank) are kept. After results are announced, the top 10 standings and the winner are public, and your results appear on your public profile.
Landmark badges
On your device, the app checks your Hub's drive history for visits within about a quarter mile of one of our landmark chargers (such as the 50,000th Supercharger or the Tesla Diner). This includes drives from before you joined and drives without FSD or Autosteer. At event landmarks, the app also counts a visit when you tap Check in, or when your phone shows you there while the FSD map is open. If you've joined the community map, the app sends which landmark you visited and the time of the visit that earned the badge, including visits from before you joined. It sends no coordinates. Unlike map squares, these visits are not trimmed at the start or end of a drive, so a landmark is reported even if your trip began or ended there. The badge (landmark name and town) appears on your public profile. The visit time isn't shown publicly, but it is kept.
What's sent even if you haven't joined
The app creates the install ID on first use and sends it to thefsdmap.com when it loads community information: on the home screen and the community, profile, recap and dashboard screens, when it checks Supercharger Day status (while the app is open: every 30 minutes normally, and as often as every 45 seconds around an event), and when you open the Lock Sounds, Wraps or Light Shows screens. Our server uses it only to look up your own standing, results and gallery items. It doesn't store the ID unless you use a feature that does: joining, entering Supercharger Day, or publishing, liking or reporting in the gallery.
To draw outlines on your FSD Passport, the app asks our server for each city and state you've driven through, by name only, with no identifier.
The FSD Year in Review asks our server for state averages without sending any identifier.
Opening the FSD maps loads map tiles from OpenFreeMap (see Third-Party Services).
Leaving
Leave the Community Map (or Stop sharing) stops new uploads from your device. It does not remove anything already on our server, and our server isn't told you left. Your name, profile page and leaderboard entries stay as they were, and changes to your name, Anonymous mode or profile page made after leaving don't reach our server. If you want to leave public lists, turn on Anonymous mode and turn off your profile page before leaving, or ask us to delete your data (see Data Retention and Deletion).
Community Gallery
The Community Gallery lets drivers share lock sounds, wraps and light shows in the app. It runs on our thefsdmap.com servers, and anyone can view and download its items through that site's public web address. Anyone can browse it and publish to it. No Hub or account is needed.
Browsing and saving
When you open the Lock Sounds, Wraps or Light Shows screens, the app loads community items from our server and sends your install ID, so it can mark your own items and the ones you've liked. Browsing doesn't store anything on our server.
Previewing, playing or saving an item sends no identifier. Saves are counted only as an anonymous total per item.
Items are made by other users, not by us.
Publishing
Publishing is optional and done one item at a time, with Publish to Community. When you publish, the app sends:
The file: a lock sound (a short audio clip, up to 5 seconds), a wrap image (with a smaller preview image), or a light show sequence together with its song.
The details you enter: title, optional note, and the car model it's for, plus details the app reads from the item, such as length, tempo (BPM) and style.
Your community name: your community map name if you have one, otherwise the name you type, or the one you used last time. If no valid name is set, you appear as "Driver-" plus four characters of your install ID. The name is saved with each item when you publish it, and doesn't change if you rename later.
Your install ID, and your Hub serial number if any Hub is paired with the app. The serial is converted to a keyed hash on receipt, and only the hash is stored.
Published items are public to anyone on the internet, not just app users. The file, title, note, car model, your community name, the exact date and time you published, and counts of likes and saves can be viewed and downloaded by anyone. Other people can save copies to their own devices, and those copies can't be recalled.
What you publish may contain your voice (a recorded lock sound or song), photos or logos (in a wrap), or music (in a light show). Please publish only what you're happy to make public and have the right to share. For light shows you confirm that you own the rights to the song or that it's royalty-free. A light-show file also carries the show's name on your device inside it, which by default is the name of the audio file you imported.
Likes, reports and moderation
Likes are stored with your install ID and the time. Only the total per item is public. Unliking removes your like.
Reports are stored with your install ID, the reason you picked, and the time. The uploader isn't told who reported. An item reported by three different people within 24 hours is hidden automatically until we review it.
We review published content. We may remove items, and may stop an install ID or Hub from publishing. We keep moderation records: the reasons for removals and blocks, and block status.
Your acceptance of the Community rules is recorded only on your device.
Removing your items
Tap Remove on an item you published to delete its files from our storage straight away. Cached copies may be served for up to about an hour afterwards, and copies other people already saved stay on their devices. A record of the removed item is kept, including its title, note, name, install ID, Hub hash and a fingerprint of the file. Your uploader record, likes and reports are also kept. You can only remove items from the same app installation that published them. To remove items published from another device or before a reinstall, or to erase your gallery records entirely, contact us.
Teslascope
You can optionally connect a Teslascope account to show vehicle data over your footage. It is off until you connect it. You sign in on Teslascope's own page, and the app never sees your Teslascope password.
What the app receives from Teslascope: your vehicle's name, model and software version, your drive list, and, for the drive that matches a clip, timestamped points with GPS position, heading, speed, battery level and range, temperatures and odometer, plus your car's software update history. Teslascope's response also includes your VIN, which the app doesn't use or store.
What the app sends to Teslascope: your sign-in tokens and requests for your vehicle and drive data. It doesn't send the time of your clip: the app pages through your drive list to find the match.
Where it's kept: sign-in tokens stay in your device's Keychain and are not synced through iCloud Keychain. Drive details are cached on your device and reused for up to 7 days. An expired copy is deleted the next time that clip is opened, or when you disconnect. Nothing from Teslascope is sent to our servers.
Disconnecting in the app deletes the tokens, your selected vehicle and the cached drive data from your device. It does not revoke the app's access on Teslascope's side. To do that, remove TesCam Studio in your Teslascope account settings.
Teslascope is an independent service governed by its own privacy policy.
iCloud Sync
If iCloud is turned on for TesCam Studio, the app syncs some data between your devices through your own iCloud account. We cannot access it.
Driving stats and app activity (miles, cities visited, badges, how often you've opened the app, and the recording times of clips you've loaded), through iCloud key-value storage.
Route history: simplified GPS routes of your drives, with date, distance, city and whether FSD was active. This is saved as a file in the app's iCloud Drive folder, which also appears as TesCam Studio in Files and Finder.
Hub pairing: pairing tokens, pairing codes and the list of Hubs you own, through iCloud Keychain. Your list of paired Hubs is synced through iCloud key-value storage: each Hub's serial, the name you gave it, its Wi-Fi network name, your home Wi-Fi network name, and local IP addresses. This lets your other Apple devices connect to your Hub.
Not synced: Google and Teslascope sign-in tokens, the Hub's Wi-Fi password, your home Wi-Fi password, and your Hub Terms acceptance.
You can turn off iCloud for TesCam Studio in your device's Settings. Hub pairing items in iCloud Keychain follow your device's iCloud Keychain setting instead. Forget this Hub in the app removes that Hub's pairing from the synced list.
Apple Services and Maps
Purchases: in-app purchases are processed by Apple through the App Store. We never receive your payment details. The app checks your purchases with Apple, and rating prompts are shown by Apple.
Crash reports: if you've chosen in your device's settings to share analytics with app developers, Apple may give us crash reports and diagnostics under Apple's own terms. If you use a TestFlight beta, Apple also gives us information such as your tester name or email address, how often you use the beta, crash reports, and any feedback or screenshots you send.
Maps: many maps in the app are Apple Maps, which load map data from Apple.
Place names: the app uses Apple's geocoding service to turn GPS positions into place names, sending Apple the coordinates each time. This happens automatically for one point from each newly loaded clip (to record cities visited), points just after turns when a clip with GPS opens in the editor (for street names), the first GPS fix of each phone recording, the centres of roughly 2 km map areas for your FSD Passport, and map pins you tap. Apple handles these requests under its own privacy policy.
Device backups: if you back up your device with iCloud Backup or a computer, the backup can include data stored in the app, including clips downloaded from your Hub, your Google account name and email address, and sign-in and pairing items from your device's Keychain. Phone drive recordings are left out.
Third-Party Services
TesCam Studio does not integrate with any analytics, advertising, or tracking services, and we do not sell or trade your data. These are the outside services that receive information, and when:
Apple: iCloud (if turned on), Apple Maps and place-name lookups, App Store purchases, TestFlight, and optional crash reports. See Apple Services.
Google: Google Drive, only if you connect it. See Google Drive. Our website also loads fonts from Google Fonts.
Teslascope: only if you connect it. See Teslascope.
Cloudflare: hosts our servers, including thefsdmap.com, gallery storage and the Hub report service, and processes every request to them, including your IP address. The Hub's connectivity test also briefly connects to Cloudflare's public DNS.
OpenFreeMap: supplies the background map tiles for the FSD Map and Community Map, for everyone who opens them, whether or not you've joined. It receives your IP address and which map areas you view. On your personal FSD map, those are the places you've driven. The Community Map can be switched to an Apple Maps view instead.
OpenStreetMap Overpass servers (overpass-api.de, overpass.kumi.systems and maps.mail.ru): if you use the 3D driving view in the editor, the app sends them a rectangle around the clip's route to get road layouts. The request goes to all of these servers at once.
OpenStreetMap Nominatim and the US Census Bureau: our server looks up city and state outlines by place name. No information about you is sent.
supercharge.info: the app and our server download its public Supercharger list. No personal data is sent, and your location is used on your device to find nearby chargers.
Shopify: runs our Hub store. The app fetches the current Hub price from it without sending personal data. On our website, the Hub page loads Shopify's Buy Button, which runs Shopify's code in your browser, receives your IP address and keeps your cart there. Orders are handled as described in Website, Store and Support.
Formspree: processes our website forms.
X: if you DM us, including through Report a Problem. Website pages with embedded X posts also load X's widget script.
Microsoft 365 hosts our email, and we may use an AI assistant (Anthropic's Claude) to help us sort and summarise incoming support email.
Our firmware update host (updates.tescamstudio.com): receives your network's IP address when your Hub or phone checks for or downloads updates.
The companies that run services for us (Cloudflare, Microsoft 365, Anthropic, Formspree, GoDaddy, and Shopify for running our store) process your data on our behalf, only to provide those services to us. Services that you choose to use or connect to directly (Apple, Google, Teslascope, X, OpenFreeMap, the OpenStreetMap servers and supercharge.info), and Shopify's own checkout and payment processing, handle your data under their own privacy policies.
Website, Store and Support
Website forms
Forms on tescamstudio.com are processed by Formspree. We collect only what each form asks for:
Stay Updated signup: your email address, to send you news about TesCam Studio and TesCam Hub.
Beta Program signup: your email address and platform preference (iOS/macOS), to send beta invitations and important updates.
Contact form: your name, email address and message, to reply to you.
International Hub notify-me: your email address and country, to tell you when the Hub is available where you live.
You can unsubscribe at any time. We never sell your email address or share it with anyone other than the services that run these forms and our email for us.
Referral program
If you join the referral program, we store your email address and your referral code. When someone opens a referral link, we count the click using a one-way fingerprint made from their IP address and browser details, so each visitor counts once a day. The raw IP address isn't stored. The referral code is saved in the visitor's browser and attached to their order. Referred orders are recorded by order number and shipping date so we can pay referral credits. This data is stored in a database on our website host.
Buying a Hub
Our store runs on Shopify. When you order, your name, contact details, shipping address and payment are handled by Shopify under its privacy policy. Payment card details go to Shopify's payment processing, and we don't see full card numbers. We use your order details to make and ship your Hub, provide support, and handle returns.
Support
When you contact us by email, the contact form or X, we keep the conversation so we can help you. We also keep a record of each support case in our own internal tracker, stored in our iCloud account: your name, contact handle, Hub serial, car model, order number and dates, and any diagnostics you've shared.
Hosting
tescamstudio.com is hosted by GoDaddy, which adds its own performance-monitoring script to our pages. Pages load fonts from Google Fonts. The Hub page loads Shopify's Buy Button, pages with embedded X posts load X's widget script, and our in-browser TesCam Studio (Lite) page loads video-processing code from unpkg.com. thefsdmap.com sets no cookies. It only saves your choice to dismiss the contest banner in your browser, and it loads map software from cdnjs (Cloudflare) and map tiles from OpenFreeMap.
Do Not Track
We don't track you across other websites or apps, so our websites and app behave the same whether or not your browser sends a Do Not Track signal. The third-party code and services described under Hosting (on tescamstudio.com: GoDaddy's script, Google Fonts, Shopify's Buy Button, X's widget script and unpkg.com; on thefsdmap.com: cdnjs and OpenFreeMap) receive your IP address and browser details when those pages load, and those companies handle them under their own policies, which may include recognising you across other sites. No other third party collects information through our websites.
Data Security
All video processing happens on your device, and your footage is never uploaded to our servers, so there is no copy of your dashcam video on any server of ours to expose.
Connections between the app and our servers, Google, Teslascope and Apple are encrypted (HTTPS).
Connections between the app and your TesCam Hub are not encrypted by the app. They rely on your Wi-Fi network's own encryption (the Hub's WPA2 network, or your home Wi-Fi). Devices on the same network as your Hub can reach it, and changing its settings or deleting anything requires pairing. Keep the password on your Hub's sticker private, and be mindful of who is on your home Wi-Fi.
Google and Teslascope sign-in tokens are stored in your device's Keychain.
Community features don't use accounts or passwords. Your install ID is what identifies you to our server, so don't share it in full. The app shows only its first eight characters, and your default public name uses its last four.
On thefsdmap.com, Hub serial numbers are stored only as keyed hashes. Hub problem reports include your Hub's serial number in plain text and are deleted after 30 days, and our manufacturing and support records keep serials in plain text.
Hub problem-report links work for anyone who has them, for 30 days. Share them only with us.
No system is perfectly secure, but we work to keep the data we hold to a minimum.
Data Retention and Deletion
How long we keep things
FSD Community Map data is kept until you ask us to delete it. Nothing is deleted automatically, and leaving the map doesn't delete it. The one exception is Supercharger Day pass data, which is deleted 7 days after each event's results. Results are kept.
Community Gallery files are kept until you or we remove the item. The item's record, your uploader record, likes and reports are kept until you ask us to delete them.
Hub problem reports are deleted from our report service after 30 days. Emails to us are kept in our support mailbox until you ask us to delete them.
Website form, referral, order and support records are kept for as long as we need them for the purpose you gave them for, or until you ask us to delete them, unless the law requires us to keep them (for example, order and tax records).
Data on your devices stays until you delete it or the app. Sign-in and pairing items in your device's Keychain can remain after the app is deleted, so disconnect Google Drive and Teslascope and forget your Hubs first. Data in your iCloud or Google Drive stays in your account until you delete it there.
How to delete your data
Community map: leave the map in the app, then email us to have your contributed data deleted. Please include the first eight characters of the anonymous ID shown on your community screen. Your public name alone isn't enough, since anyone can see it. We may ask you to confirm the request from the app before we act on it. We aim to delete it within 30 days of your request. Our database host keeps a short rolling restore history, so a deleted record can take up to 30 more days to disappear from it.
Gallery items: tap Remove on items you published. Email us to remove items from another device, or to erase your gallery records.
Google Drive and Teslascope: disconnect in the app, then revoke access at Google or in your Teslascope account.
Your Hub: use Forget this Hub in the app to remove its pairing from your devices, and a factory reset to clear pairings and saved Wi-Fi networks from the Hub (see TesCam Hub for what a reset doesn't erase).
Wherever you live, you can ask us for a copy of the personal information our servers and records hold about you, or ask us to correct or delete it, and you can stop using any optional feature at any time. We aim to respond within 30 days, and we won't treat you differently for asking. To make a request, contact us. For community map data, include the ID described in Data Retention and Deletion.
We don't sell personal information, and we don't share it for targeted advertising.
Why we process data: because you asked for a feature (the community map, the gallery, problem reports and support); to take, make and ship your Hub order and handle returns; to keep our services secure and free of abuse (for example, the 60-second IP record on our report service and gallery moderation records); and to meet legal duties, such as keeping order and tax records. Where we rely on your consent, such as when you join the community map, you can withdraw it at any time by leaving and asking us to delete your data. This doesn't affect what we did before you withdrew it.
Where data is processed: we're based in California, USA. Our servers and the providers we use may process data in the United States and other countries.
If you're in the European Economic Area or the UK, you can also object to or ask us to restrict some processing, ask for your data in a portable format, and complain to your local data protection authority.
Children's Privacy
TesCam Studio is not directed at children under 13. The FSD Community Map and Community Gallery are public, and are not for anyone under 13, or under 16 in countries of the European Economic Area that set that age for online consent. We don't knowingly collect information from children. If you believe a child has joined the community map or published to the gallery, email us and we'll delete it.
Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we'll post it here and change the date at the top. We will never start using Google user data in a new way, or for a purpose not described here, without first asking for your consent in the app.
Contact Us
If you have any questions about this Privacy Policy, or want to make a deletion or access request, please contact us:
Back to Home