Understand how TesClip keeps videos and vehicle data on your device, which optional services may process browsing data, and how to exercise your rights.
Your videos stay on your device. TesClip processes footage directly in the browser instead of uploading it to a remote server.
You can open, review, and export supported clips without creating an account or linking Tesla credentials.
Because the analysis happens locally, you can inspect footage quickly while keeping full control over the original files.
All your Tesla videos are processed directly in your browser. No video files are uploaded to our servers.
With your consent, Google Analytics / Microsoft Clarity measures audience and Google AdSense displays one advertisement in the loaded clip library. Those services do not receive video files, filenames, GPS positions, vehicle telemetry, events, or searches. If you separately choose Publish on YouTube, the exported video and selected publication metadata are sent directly to Google and YouTube as described below.
Your interface preferences and a separate metadata cache for each selected TeslaCam folder are stored locally in your browser. They are never uploaded to TesClip.
In accordance with GDPR, you have the right to access, rectify, and delete your data. To exercise these rights, contact us at
When you display a map or export a video with a map, your browser requests the selected light, dark, or satellite tiles from OpenStreetMap or Esri. Those providers receive standard connection data and tile coordinates representing the displayed area. TesClip never sends them video files or vehicle telemetry.
After a completed payment, you may optionally send TesClip a message of up to 10,000 characters. It is linked to your account and Stripe Checkout Session, stored in the TesClip database, and emailed to the publisher so it can be read and answered. You may request its deletion at any time.
For any questions or requests, please contact us: [email protected].
TesClip uses the YouTube Data API only when you choose to publish an exported video. The youtube.readonly permission reads the selected channel identifier and name so you can verify the destination. The youtube.upload permission sends the video and the title, description, audience, and visibility you selected to that channel.
The exported video and the title, description, audience, and visibility you select are sent directly from your browser to Google and YouTube solely to complete the publication you request. Video bytes never pass through TesClip servers. Only if you separately opt in to the TesClip community does TesClip receive the YouTube video identifier and the publication metadata you chose, under the storage and deletion rules below.
The Google access token and selected channel data stay only in browser memory during authorization and upload; TesClip revokes and discards the token after publication, cancellation, or failure. If you explicitly add the upload to the TesClip community, TesClip stores the YouTube video identifier and public metadata, revalidates and refreshes them at least every 30 days, and permanently deletes that record and its related community activity as soon as you remove it from TesClip. Other valid deletion requests are completed as soon as possible and within 7 calendar days. Removing it from TesClip does not delete the video from YouTube.
You control the channel, video, metadata, audience, and visibility before publication. You can revoke TesClip access at any time from your Google Account permissions.
TesClip uses YouTube API Services. By using YouTube publishing, you also agree to the YouTube Terms of Service. Google processes data under its Privacy Policy.
Optional analytics and advertising services are disabled until you make a choice. You can change or withdraw your consent at any time.
You can configure your browser to refuse cookies or be alerted when a cookie is set.
Name: Thibault BAZIN
Email: [email protected]