Understand where your data goes.
This notice describes the current development application. Production retention periods, legal terms, and privacy contact arrangements still need to be finalized before a public launch.
Information in your workspace
The application stores account details, server registrations, media metadata, destinations, broadcast records, playlist order, schedules, and usage information. Uploaded media is stored through the configured object-storage service. Server agents send system details, measurements, and process reports to the API.
Credentials and sensitive information
Passwords are hashed. Destination secrets are encrypted by the application, while agent authentication uses credential hashes on the API side. The agent needs its own restricted configuration file on your VPS. These protections do not replace securing the deployment, backups, access permissions, or the server itself. Never include stream keys, passwords, private keys, or enrollment files in screenshots or support requests.
Your server and external platforms
When you enroll an agent, the VPS communicates with the configured API. When you start a broadcast, the agent can retrieve the selected media and publish to your configured destinations. Those services have their own data handling and account policies. Your cloud account and streaming accounts remain separate from this workspace.
Browser state and optional forms
The application uses browser state for sign-in and interface preferences. The newsletter form saves an email address through the application API; newsletter delivery is not active in this build. The contact form only prepares text in the current browser and does not submit a support message.
Retention, access, and deletion
Do not assume that removing an item also removes every backup, log entry, external copy, or provider record. Production retention and deletion procedures are not yet defined. In a development deployment, the operator is responsible for access, backups, data cleanup, and the services they configure.
Before using a public deployment
Review the deployment’s actual service providers and configuration, establish a privacy contact and retention policy, and provide users with accurate information about that environment. This development notice should not be represented as a completed production privacy policy.
A useful next step.
Read the current product capabilities, or find a guide for the part of your setup you want to improve.