Privacy First. Sentry Clip Viewer is designed with a strong commitment to your privacy: playback, rendering and video export happen on your device. The app does not automatically upload footage to Qloud or Tesla. Network activity can include Tesla key requests, optional telemetry providers, Apple map and place-name services, and network storage you select.
Information We Don't Collect
Sentry Clip Viewer is built on the principle of data minimization. We do not collect, store, or transmit any of your personal information or video data to our servers — the app does not report footage or usage analytics to Qloud. All video processing, including playback, telemetry overlay rendering, and export, happens exclusively on your device. Network features are described under Third-Party Services below; they do not upload your footage to Qloud.
Video and Telemetry Data
Sentry Clip Viewer requires access to your files to function. We use this access to:
- Read Tesla dashcam video files from your selected folder
- Extract telemetry metadata embedded in video files
- Process and render telemetry overlays on video frames
- Export videos with burned-in telemetry overlays
All of this processing occurs locally on your device. The app does not upload your footage to Qloud or Tesla. Encrypted-clip key requests send clip header metadata to Tesla; optional telemetry, map/place-name services and network storage may exchange data as described below.
Photos Library Access
If you choose to export videos, Sentry Clip Viewer requests permission to save exported videos to your Photos library. This permission is:
- Optional: Only requested when you initiate an export
- Limited: Only used to save your exported videos
- Local: Videos are saved directly to your device's Photos library
You can revoke this permission at any time through your device's Settings app.
Internet Connection
Sentry Clip Viewer works offline for its core functions. For local clips with available decryption keys, the following core functions can run offline. Network-backed maps, provider refreshes and network storage require a connection:
- Video playback and multi-camera synchronization
- Video export with overlays
- Browsing and organising clips
Encrypted clips need available keys, which may require Tesla sign-in and a network request. Optional telemetry providers and Apple map/place-name services may also make network requests. A folder you choose on network storage is accessed over that connection. Core local playback and export do not require a Qloud account or a Qloud server.
No Analytics or Tracking
We do not use any analytics services, tracking SDKs, or telemetry collection tools. We have no way of knowing:
- How you use the app
- What videos you view
- What clips you export
- Your location or driving patterns
- Any other usage data
Qloud does not receive app usage analytics. Connected services handle requests under their own privacy policies.
No User Accounts
Sentry Clip Viewer does not require a Qloud account or registration with Qloud. Encrypted playback may require sign-in to your Tesla account. Optional telemetry integrations use your chosen provider account or server credentials.
Data Security
Playback, rendering and export processing all occur locally on your device, and the app does not upload your footage to Qloud or Tesla. Network features are described under Third-Party Services below. Your data is also protected by:
- Your device's built-in security features (passcode, Face ID, Touch ID)
- iOS sandboxing and security protections
- File system encryption on your device
The app does not send your footage to Qloud. You control the source files and any export destinations you choose.
Third-Party Services
Sentry Clip Viewer integrates no analytics, advertising, crash-reporting or tracking SDKs, and does not collect usage analytics for Qloud. We receive nothing about your use of the app, because nothing in it reports to us.
Encrypted clips. Where Tesla has enabled per-clip USB encryption, each clip is locked with a key only Tesla can unwrap. To unlock the clips you open, the app signs in with your own Tesla account and asks Tesla’s key service (dashcam.tesla.com) to unwrap them. That request carries small clip-header fields, including the vehicle VIN, key identifier, timestamp, wrapped key and public key — not the full video. Unwrapped keys are kept on your device, so cached keys may avoid repeat requests for the same clip. The decryption itself happens entirely on your device.
Third-party telemetry, only if you connect one. The optional telemetry overlay can pull data from Tessie, TeslaMate, or TeslaScope — services you choose to connect with your own account or your own server, entirely separate from us and from Tesla. Connecting one means that service receives your vehicle’s VIN and whatever else its own API requires; each has its own privacy practices, which we do not control. With no provider connected, the optional provider integration does not make provider requests.
Maps and place names. Apple map snapshots and reverse geocoding can send location or map requests to Apple to display routes and addresses. Apple’s privacy terms apply. Selecting an SMB/NAS or other network folder also uses that network service to access the files you choose.
Children's Privacy
Sentry Clip Viewer is suitable for users of all ages. Since we do not collect any personal information, we do not knowingly collect data from children under 13 years of age.
Your Rights
Since we do not collect, store, or process any of your personal data on our servers, there is no data for you to access, correct, or delete. Original files, exports and shared copies remain in the storage destinations you choose and are managed separately.
Deleting the app does not delete original footage or exports saved to Photos, files or shared destinations. Connected-account credentials may remain in the device’s Keychain; manage provider access with the relevant service.
Changes to This Policy
We may update this Privacy Policy from time to time. Any changes will be reflected by updating the date at the top of this policy. We encourage you to review this Privacy Policy periodically.
Since we don't collect contact information, we cannot notify you directly of changes. Continued use of the app after changes constitutes acceptance of the updated policy.
Compliance
We aim to respect applicable privacy requirements. This policy explains the app’s processing and the connected services you can choose; third-party services have their own terms and privacy practices.
Contact Us
If you have any questions about this Privacy Policy or our privacy practices, please contact us at privacy@qloud-ltd.com.