Operations
Backup and Disaster Recovery Policy
This policy explains StreamPilot's approach to backups and disaster recovery for platform data, customer configuration, scheduling, recording automation data, billing mirrors, audit logs, app configuration and related operational systems.
1. Backup objectives
StreamPilot aims to maintain backups sufficient to recover from common operational incidents such as server failure, database corruption, accidental deployment errors, security incidents or infrastructure loss. Backup coverage, frequency and retention may vary by system, hosting environment and customer arrangement.
2. Data covered
Backups may include databases, customer/account records, station and DJ configuration, schedules, audit logs, subscription mirrors, billing event ledgers, app configuration, uploaded artwork and operational files. Large media files, generated recordings, app build artifacts and temporary files may have different retention or recovery handling depending on storage architecture and plan limits.
3. Recovery objectives
StreamPilot uses best-efforts recovery objectives rather than guaranteed recovery times. Typical internal aims are:
- Recovery Time Objective: restore core platform availability as soon as reasonably practical after a major incident.
- Recovery Point Objective: minimise data loss using available backup intervals and transaction records where available.
Actual recovery may vary depending on incident severity, provider availability, data volume, corruption type, third-party outage, security requirements and customer cooperation.
4. Disaster recovery procedure
In a disaster, StreamPilot will assess impact, secure systems, identify the most reliable recovery source, restore infrastructure or migrate service where practical, validate core services, restore customer-facing access, review logs and communicate where appropriate.
5. Customer responsibilities
Customers must keep their own copies of important media, recordings, show files, artwork, branding, licence documents, schedule source data, app store credentials, stream credentials and business-critical content. StreamPilot backups are not an archival storage service and should not be treated as the only copy of customer material.
6. Restore limitations
Individual item restore may not always be available. Backups may restore a whole database, account, folder, server or system state rather than a single deleted file. Backups may not contain very recent changes. Backup restoration can overwrite newer data and may require customer approval.
7. Testing and review
StreamPilot may periodically review backup and recovery processes. Full recovery testing may be limited by operational risk and hosting constraints, but backup design should be reviewed as the platform scales.
8. Exclusions
This policy does not guarantee recovery from customer-side deletion, copyright takedown, app store removal, customer developer account loss, third-party stream host loss, customer device loss, customer email account compromise or loss of files never uploaded to StreamPilot.