Privacy and data boundaries
Review what Finetic stores locally, what configured metadata providers receive and the limited information used for commercial entitlement.
Local by design#
Your source media, paths, local users, viewing history, playback sessions, metadata state and server analytics remain inside the Finetic installation.
Data destinations#
| Destination | Data that may be sent | Why |
|---|---|---|
| Configured metadata provider | Search title, year, media type and provider identifier | Metadata and artwork enrichment |
| Finetic entitlement service | Installation identity, licence state, platform, installed version and check result | Validate authorised use and deliver releases |
| Email service configured by administrator | Invitation recipient and message | Account invitation |
Video files are not uploaded to the entitlement service. Provider integrations receive only the queries needed for the configured feature.
Secrets#
Provider keys and SMTP credentials are encrypted at rest and redacted in browser responses. Session cookies use secure browser attributes where HTTPS is configured. Public documentation never contains real credentials.
History and telemetry#
Administrators choose retention periods and whether IP addresses are included. Users can view their own history. Administrators can clear one user's analytical data or all analytical data according to policy.
Guest access#
Guest sessions are server-issued and counted independently. Media assets use short-lived scoped claims. Password unlock attempts are rate limited. Downloads remain disabled.
Entitlement boundary#
An expired or revoked licence disables the application runtime and directs the operator to support. The entitlement check is deliberately separate from local viewing analytics.