Repository navigation
Privacy
This page documents every outbound data flow from a Sentry USB device, the reporting controls, how long the data is retained, and how to disable it. If anything you observe on the wire doesn't match what's listed here, it's a bug — please open an issue.
A new installation asks you to choose Yes, count me or No thanks on the Privacy step; device counting starts only if you choose Yes. Cancelling or going Back does not save a selection.
Existing installations keep their saved choice. Existing opt-outs and existing
installations without a recorded choice remain off. The reporting setting in
Settings → System → Device counting controls later changes. Read the
Privacy Policy for the legal disclosures.
-
Endpoint:
POST https://api.sentry-six.com/sentryusb-rusty/telemetry - When: After startup, after enabling analytics, and daily while enabled. Offline attempts retry with bounded backoff. Repeat reports update the same device record.
-
Sent:
fingerprint(a salted SHA-256 hash of the board serial),current_version, andreport_kind: running_version(protocol label). No raw hardware serial, board model, boot ID, architecture, files, locations, or update download/availability data is included. Normal source-IP connection metadata is visible to the server and briefly used for rate limiting. - Identity: The ID derives from the board serial and is stable across reinstalls on Raspberry Pi. The salt is public in the source code, so the ID is pseudonymous: anyone who knows a board's serial can compute it. Devices without a readable hardware serial are not counted; an installation ID is never used as a substitute.
- Purpose: Count known and recently active devices and show their latest reported running versions. The server keeps just the device ID, latest version, and first/last report times. Authorized maintainers can view the minimal records through restricted administrative tools, including Discord commands. Reports describe the running version, not an offered or downloaded update.
- New-device notice: The first time the server sees a device, it posts the software version and first-seen time to a private maintainers' Discord channel. Notices stay there until removed manually.
- Control: New installations choose Yes or No on the Privacy step. The selection is saved when continuing past that step. Existing settings are preserved; existing installations with no choice stay off. Both options provide the same core features and updates.
- Retention: The four-field device summary remains until deleted or deletion is requested. Opting out stops future reports; it does not erase the existing summary. No report-ID receipts or version-history rows are kept.
-
How to disable:
Settings → System → Device counting. To request deletion of stored analytics, contactprivacy@sentry-six.com.
Update checks go to GitHub Releases and work whether device counting is on or
off. When older Sentry USB versions send reports to /sentryusb/telemetry or
/sentryusb/install-beacon, the server discards them on arrival.
-
Endpoint:
GET https://sentryusb.com/api/geoip/me - When: Only when the time zone is set to Detect automatically: during setup, and at boot while the system time zone is still UTC.
- Sent: An HTTPS request. The server uses your public IP address to look up an approximate city, region and time zone and returns them to the Pi.
- Purpose: Setting the Pi's clock to your local time zone.
- Retention: The endpoint rate-limits lookups by IP address for 24 hours.
- How to disable: Pick your time zone from the list instead of Detect automatically.
-
Endpoint:
POST https://api.sentry-six.com/wraps/upload,POST https://api.sentry-six.com/lockchime/upload - Sent: The file you uploaded (plus an optional preview for wraps), display name, model and original filename for wraps, file size, audio duration for lock chimes, and your source IP. The server also generates a submission code and records review status and timestamps.
- Identifier: No device fingerprint. Abuse handling uses the Discord moderation queue plus per-IP rate limits.
- Purpose: Accepting, reviewing, and publishing your contribution, plus proportionate rate limiting, abuse investigation, and moderation.
- Legal basis: Contractual necessity under Art. 6(1)(b) for accepting, reviewing, and publishing the contribution you requested; legitimate interests under Art. 6(1)(f) for proportionate rate limiting, abuse investigation, and moderation.
- Retention: Pending and approved asset files remain until declined or manually deleted. Declining removes the asset file, but the submission row, including its source IP, status, and review metadata, has no fixed automatic deletion period and remains until manually removed or deletion is requested. The source IP is not exposed in the public library view.
- How to disable: Don't submit. Browsing/downloading the library sends no custom or device identifier; the source IP is necessarily seen and briefly used for rate limiting.
-
Endpoint:
GET https://api.sentry-six.com/wraps/download/<code>,GET https://api.sentry-six.com/lockchime/download/<code> - Sent: Standard HTTP request with no custom or device identifier. The source IP is necessarily seen and briefly used for rate limiting.
- Identifier: None.
- Purpose: Fetch the requested asset.
- Legal basis: Contractual necessity — you asked for the file.
-
Retention: Current-client source-IP rate-limit entries remain only
briefly in memory. Legacy per-asset fingerprint download records created by
older clients may remain until manually deleted; contact
privacy@sentry-six.comto request deletion. - How to disable: Don't download.
-
Endpoint:
https://tiles.sentryusb.com, our map server, served through Cloudflare. Its tiles carry OpenStreetMap data, ESA WorldCover land cover, GEBCO bathymetry and Mapzen terrain data. Every map in the web UI loads from this server. In browsers without WebGL2, maps show routes on a plain background and load no tiles. - When: While a page with a map is open in your browser.
- Sent: Standard tile requests for the area and zoom level shown, and your browser's IP address. The requests come from your browser, not the Pi.
- Purpose: Drawing the map.
- How to disable: Don't open pages with maps.
-
Endpoint: Various
https://sentryusb.com/api/pi/...routes. - Sent: When you pair, the 6-digit code shown in your browser, the Pi's public keys, and device details (hostname, board model, kernel version, Sentry USB version, and the last 4 hex digits of a network MAC address). After pairing, the drive history, charging sessions and Home sync data you choose to sync, encrypted on the Pi before upload. Your Sentry Cloud password is never entered on or sent from the Pi. Sentry Cloud does not upload dashcam video.
- Identifier: A per-device token issued at pairing and linked to your Sentry Cloud account.
- Purpose: Cloud sync requires it — the feature can't function otherwise.
- Legal basis: Contractual necessity (Art. 6(1)(b)) — you signed up for the service.
- Retention: See the Sentry Cloud Privacy Policy.
- How to disable: Don't pair this Pi, or unpair it.
-
Endpoint:
POST https://notifications.sentry-six.com/register-code, thenhttps://notifications.sentry-six.com/sendfor each notification. -
Sent: A
device_id(64 random hex characters generated on this Pi),device_secret, a one-time pairing code the Pi creates when Sentry Connect asks to pair, and your Pi's hostname. When a phone pairs, the Sentry Connect app registers its push token (Apple APNs on iPhone, Google Firebase Cloud Messaging on Android), a device name (such as "iPhone" or the phone model) and platform. Each notification's title and message text pass throughnotifications.sentry-six.comto Apple or Google for delivery. -
Identifier: The
device_id— but it's a random value created locally on first run, not derived from your hardware. Resetting it generates a new one. - Purpose: Routing push notifications from your Pi to your phone.
- Legal basis: Consent — you actively enabled this feature.
- Retention: When the last phone unpairs, the hostname and device link are cleared. Registrations with no paired phone and no activity for 90 days are deleted.
- How to disable: Don't pair, or unpair in the Sentry Connect app + delete the credentials on the Pi.
-
Endpoint: Your browser talks only to this Pi at
/api/support/ai/.... The Pi proxies the fixed request types tohttps://api.sentry-six.com/ai-support/.... The local browser-to-Pi hop normally uses HTTP, so chat content and access tokens are not encrypted on that local hop. Use AI Support only from a trusted local network. The Pi's onward connection to the public API uses HTTPS. -
Sent when you start a conversation: The text you enter, a random
conversation/request identifier, the displayed disclosure version,
the installed Sentry USB software version, SBC model, a bounded non-secret
support snapshot, and the fixed product ID
sentry-usb-rusty. The snapshot contains Dashcam Size, Travel Mode flags, archive category toggles, and whether Wraps and Lock Chimes are enabled. The Pi does not send archive destinations, network names, usernames, passwords, tokens, a hardware fingerprint, Pi login credential, or knowledge for another product. - AI processing: Relevant conversation content is processed by Anthropic (the Claude API) to generate a response. Anthropic states that API inputs and outputs are not used to train its models and are deleted from its systems within 30 days, unless longer retention is needed to enforce its Usage Policy or is required by law. Processing may occur outside Canada, including in the United States. The app identifies this as an online AI service; the model is not running solely on your Pi.
- Server logging: A redacted transcript of messages and responses, timestamps, product/version context, action decisions, and limited operational metadata is stored on Sentry Six servers in Canada. Authorized maintainers may review it to troubleshoot failures, find hallucinations, and improve support quality.
- Identifier and local resume data: To resume a chat, your browser stores the random conversation ID and raw random access token in local storage. The Sentry Six backend stores only a one-way hash of that token. The public IP seen from the Pi's connection is processed separately for rate limiting and abuse prevention: raw values remain only in short-lived in-memory rate buckets (up to about two hours), while a gateway-keyed one-way hash and daily diagnostic-upload counters may remain for up to about 49 hours and are not linked to the transcript or diagnostic text. None of these values is derived from your Pi hardware. Clearing browser site data removes local access but does not delete the server copy; use New chat first if you want the current conversation deleted immediately.
-
Purpose and legal basis: Processing the message needed to answer your
support request is necessary to provide the AI Support service you asked
for (Art. 6(1)(b)). Bounded, redacted transcript retention and authorized
review for security, reliability, hallucination detection, and prompt or
knowledge-safety improvements rely on our legitimate interests
(Art. 6(1)(f)). You may object to that processing or request deletion at
privacy@sentry-six.com, subject to applicable law. The pre-chat screen is an acknowledgement of these disclosures, not bundled consent for every processing purpose. -
Retention: Redacted conversation transcripts expire 90 days after
the last activity. You can delete the current conversation immediately
in the UI, or request deletion at
privacy@sentry-six.com. Deletion removes messages and uploaded files immediately. A non-content receipt containing the conversation ID, one-way hashes of the access token and deletion idempotency key, and deletion time remains available solely for safe retries and replay prevention until it expires 24 hours after deletion. The expired receipt is removed during the next scheduled cleanup sweep, normally within about one additional hour. - How to disable: Do not start an AI Support conversation. The rest of Sentry USB continues to work without it.
The assistant cannot browse the Pi or upload a file by itself. The first
supported request type is a predefined Sentry USB diagnostics report. It
collects the date, hostname, uptime, software/OS and board details, storage
and USB-gadget state, local network addresses, service state, temperatures,
and limited tails from designated system and Sentry USB logs, including recent
archiveloop.log entries. It does not search arbitrary files. Log excerpts can incidentally contain local
addresses, device or vehicle identifiers, error payloads, or location-related
details; those are not separate fixed fields requested from the vehicle.
If the assistant asks for the report, the UI shows the exact file, reason, maximum size, destination, and seven-day retention period. Nothing is generated or uploaded until you click Generate & upload diagnostics once for that specific request. That click creates a short-lived, single-use upload token; it is not standing permission for future files. You may deny the request and continue chatting.
The approved report leaves your Pi, is uploaded to the Sentry Six backend, and relevant content may be processed by Anthropic and reviewed by authorized maintainers. The backend accepts only the expected diagnostics request, plain UTF-8 text with control characters removed, and a maximum of 2 MiB. The file is deleted automatically after seven days. Review the disclosed categories before approving, and do not approve an upload if the report may contain passwords, tokens, private keys, precise location, or third-party data you are not authorized to share.
AI Support may suggest the Sentry Six Discord for community or human help. Opening the Discord link does not automatically send the AI transcript or uploaded diagnostics to Discord. Anything you choose to post there is a separate disclosure to Discord and is governed by Discord's policies.
- Updating keeps your saved reporting choice. An existing installation that never made a choice stays off.
- A device report is sent only after you choose Yes and continue past the Privacy step.
- With device counting off, the Pi sends no device analytics, at startup or in the background.
- A diagnostics report is uploaded only when you approve it in AI Support. Any future crash reporter will be a separate opt-in.
- AI Support works from your messages and the reports you approve, and each upload needs its own approval.
- The Sentry USB web UI always uses Sentry USB's own AI Support prompt and knowledge base.
- The device-counting setting covers device counting only. Diagnostics and file uploads, such as wrap or lock chime submissions, each need their own approval.
If you want to verify any of the above against the source:
-
Device analytics:
crates/api/src/device_reporting.rs. The saved reporting setting is checked before creating or sending reports; the startup version is captured before the updater or API starts. Only tagged release builds embed a release tag; other builds capture the installed version once at startup. -
Preference wake-up:
crates/api/src/preferences.rs. Reporting is nudged only after a privacy choice is successfully saved. -
Wraps/chimes header forwarding:
crates/api/src/community.rs→forward_headers(). Should only forwardx-passcode, neverx-fingerprint. -
Notification pairing:
crates/api/src/notifications.rs→register_code_with_backend(). Confirm the request body has nofingerprintfield. -
AI Support proxy and product lock:
crates/api/src/support.rs. ConfirmAI_PRODUCT_IDissentry-usb-rusty, later requests remove product selectors, only the browser-supplied AI conversation token and idempotency key are forwarded, and the trusted product header is injected by the Pi. -
AI Support disclosure acknowledgement and separate upload consent:
web/src/components/support/AISupportChat.tsxandweb/src/api/support.ts.
Open an issue at
github.com/Sentry-Six/Sentry-USB-Rusty/issues
or email privacy@sentry-six.com. If the bug is "the client sent X
even though the docs said it wouldn't" please include a tcpdump or
the relevant journalctl line so we can fix it.
Discord · Report an issue · PolyForm Noncommercial 1.0.0