Privacy Policy
TIVEXA uses a website, a Cloudflare Worker API and a D1 database to pair a phone with a television and to deliver playlist settings to that paired TV.
Data used for pairing
- TV Device ID.
- A short-lived six-digit pairing code. The server stores a one-way hash of the pairing code rather than the plain code.
- Pairing timestamps, status and failed-attempt count.
Playlist delivery and management
When you choose to send an compatible media source from My TIVEXA, the information you enter is transmitted over HTTPS to the TIVEXA API. Delivery payloads are encrypted before storage in D1 using AES-GCM and are only accepted during the active short-lived pairing session.
For playlist management, the TV can send an encrypted temporary inventory containing playlist identifiers, names, type and active status. TIVEXA does not need to send stored playlist passwords back to the website merely to display this inventory.
Short-lived sessions
Pairing and delivery access is time-limited. The current development version uses a pairing window of about ten minutes. Expired sessions and expired delivery items are no longer accepted for active operations.
Browser storage
The website may store language preferences and temporary pairing state locally in your browser to support the My TIVEXA workflow.
Infrastructure
The current development website and API use Cloudflare Pages, Cloudflare Workers and Cloudflare D1. Requests may therefore be processed through Cloudflare infrastructure.
Content
TIVEXA does not provide third-party media or content. Playlist details are supplied by the user for the purpose of configuring the user's own player.
This development privacy notice will be reviewed again before any commercial release, including final operator/contact details and any required local data-protection notices.