diff --git a/frontend/legal/privacy.html b/frontend/legal/privacy.html index 401c122..c82d217 100644 --- a/frontend/legal/privacy.html +++ b/frontend/legal/privacy.html @@ -26,7 +26,7 @@
Last updated: March 24, 2026
+Last updated: May 15, 2026
ScreenTinker ("we", "us", "our") respects your privacy. This policy explains what data we collect, how we use it, and your rights regarding your information.
@@ -63,6 +63,18 @@Media files (images, videos) you upload are stored on our servers solely to deliver them to your devices. We do not analyze, sell, or share your content.
+Player clients submit error reports automatically so we can fix issues on devices we cannot directly access (smart TVs, embedded signage browsers). Reports may be submitted before a device has paired; in that case only the network IP and user-agent are present, with no device ID.
+| Data | Purpose | Retention |
|---|---|---|
| Browser user-agent string | Identifying which player platforms encounter errors | Rolling buffer (10,000 entries) |
| Error messages, stack traces, and source-file references | Diagnosing player issues we cannot reproduce in development | Rolling buffer (10,000 entries) |
| Recent player log entries (up to 50, including filenames of content being played) | Context for the error so we understand what the player was doing | Rolling buffer (10,000 entries) |
| Screen and viewport dimensions | Diagnosing layout and rendering issues at the device's actual size | Rolling buffer (10,000 entries) |
| Coarse player state (idle, playing, waiting) | Distinguishing errors during playback vs setup | Rolling buffer (10,000 entries) |
This telemetry can be disabled by self-hosters via the PLAYER_DEBUG_REPORTING=off environment variable. On screentinker.com it is on by default.
PLAYER_DEBUG_REPORTING=off.