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.
| Data | Purpose | Retention |
|---|---|---|
| Email address | Authentication, notifications | Until account deletion |
| Name | Display in dashboard | Until account deletion |
| Password hash | Authentication (bcrypt, never stored in plain text) | Until account deletion |
| OAuth provider ID | Google/Microsoft sign-in | Until account deletion |
| Data | Purpose | Retention |
|---|---|---|
| Device ID | Unique device identification | Until device removal |
| IP address | Network connectivity, security | Overwritten each connection |
| Android version, screen resolution | Compatibility, display optimization | Until device removal |
| Battery, storage, RAM, CPU, WiFi | Device health monitoring | 90 days (rolling) |
| Device fingerprint (hardware hash) | Prevent trial abuse | Until device removal |
| Data | Purpose | Retention |
|---|---|---|
| Content play logs | Proof-of-play reporting | 90 days |
| Activity log (API actions) | Audit trail, security | 90 days |
| Screenshots (on-demand) | Remote monitoring | Latest only per device |
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.
We do not sell your personal information. We share data only in these limited circumstances:
If you self-host ScreenTinker on your own infrastructure:
PLAYER_DEBUG_REPORTING=off.You have the right to:
The Service is not intended for use by children under 13. We do not knowingly collect information from children under 13.
If you access the Service from outside the United States, your data may be transferred to and processed in the United States. By using the Service, you consent to this transfer.
We may update this policy from time to time. We will notify registered users of material changes via email. The "Last updated" date will be revised accordingly.
For privacy-related questions or data requests, contact us at:
Email: support@screentinker.com