Security & Data Handling

1. Data we process

The service may process account and organization details, authentication and security records, XMLTV files, schedules, playlists, As-Run logs, channel logos, stream URLs, report settings, and generated deliverables. Customers should upload only the data required for the selected operational workflow.

2. Customer ownership and use

Customers retain ownership of their uploaded files and generated deliverables. Broadcast Tool Pro processes customer content only to provide, secure, support, and maintain the requested service. We do not sell customer data or use operational files for advertising.

3. Identity and access controls

• Customer records and reports are scoped to their organization and registered channel context.
• Owner, administrator, operator, and viewer roles control permitted actions.
• Production sessions use Secure, HttpOnly, SameSite cookies and expire automatically.
• Passwords use salted one-way hashing; raw passwords and session tokens are not stored.
• Password-reset links expire after 30 minutes, can be used once, and revoke existing sessions after a successful reset.
• Repeated failed sign-ins trigger temporary account protection, and sensitive endpoints are rate limited.

4. Infrastructure and transmission

Broadcast Tool Pro runs on managed cloud infrastructure. Public production traffic is protected with HTTPS. Application secrets are maintained outside the source code, administrative access is restricted, and browser permissions not required by the service are disabled.

5. Backups and recovery

The application database is backed up every 24 hours. Backup integrity and checksums are verified, local copies use a configured 14-day retention period, and encrypted off-site sets are rotated across daily and weekly recovery points. Recovery procedures are tested without replacing the live database.

6. Retention and deletion

Application-owned temporary working files are configured for removal after 24 hours. Account records, security events, subscription data, and stored reports are retained while needed to operate the service, preserve auditability, resolve disputes, or meet legal obligations. Authorized contacts may request access, export, correction, or deletion; residual backup copies expire through the normal rotation cycle. Removing a channel from future billing disables its operational use at the effective date but does not bypass these retention, auditability, or authorized-deletion controls.

7. Service providers

We use a limited set of providers to operate the platform: Render for application infrastructure, Amazon Web Services for transactional email, Google for authorized communications and encrypted off-site backup storage, and Stripe for subscription and payment processing. Broadcast Tool Pro does not store full payment card numbers.

8. Monitoring and incident response

Authentication outcomes, administrative activity, request failures, backup health, external-backup connectivity, and email-delivery events are recorded or monitored as applicable. Suspected incidents are reviewed for containment, recovery, and customer notification when required by law or contract.

9. Privacy and international requests

For customer-uploaded operational data, the customer generally determines the purpose of processing and Broadcast Tool Pro performs the requested workflow on its behalf. Organizations requiring a Data Processing Addendum or information about international data transfers should contact us before submitting regulated personal data.