Annex B - Specific rules for Radio stations
ID: PLAY258-ANEXO-RADIO | Version: 1.0.0 | Audience: station
Integrates: General Terms of Use | Privacy Policy
B.1. Scope of the “Radio” profile
B.1.1. Applies to broadcasters, streaming radio operators, broadcast content producers, or entities using Play258 playout, music requests (SMS/WhatsApp/app), catalog, TTS, broadcast reports, and technical integrations.
B.1.2. Internal station users (hosts, managers) act under liability of the entity holding the Account.
B.2. Permissions
B.2.1. Configure schedules, keywords, queues, request pricing (where applicable), and playout integrations.
B.2.2. Receive spots and insertion orders from Organizations per active modules.
B.2.3. Access logs and execution reports for internal compliance.
B.3. Restrictions
B.3.1. Do not broadcast content without music and phonogram licenses required in the broadcast jurisdiction.
B.3.2. Do not use listener data for undisclosed purposes without legal basis (aggressive marketing, resale).
B.3.3. Do not circumvent API or sync limits in a way that falsifies reports.
B.4. Specific obligations
B.4.1. Obtain and maintain licenses (e.g. collecting societies, phonograms, broadcast authorization) independently of the Service.
B.4.2. Comply with advertising rules, child protection, and limits on political/religious content per local law.
B.4.3. Ensure accuracy of metadata sent to the engine (e.g. track duration for paid request timing).
B.4.4. Maintain secure playout connection when required for spot download or sync.
B.5. Responsibility for content and data
B.5.1. The Radio station is solely responsible for what goes on air, including listener requests and spots.
B.5.2. When the Operator processes listener data on behalf of the station (e.g. message branded by the station), the station must provide information to data subjects (station privacy policy, legal bases) and enter a processing agreement when required.
B.6. Suspension criteria (examples)
- repeated broadcast of content notified as infringing;
- serious non-payment to the Operator;
- abuse of paid requests or queue manipulation;
- security compromise (credentials shared publicly).
B.7. Relationship with other audiences
B.7.1. Artists: the station must respect valid takedowns and repertoire agreements.
B.7.2. Listeners: transparency on pricing, request confirmation, and station customer support when the flow is white-label.
B.7.3. Organizations: execute campaigns per orders; communicate technical unavailability affecting spot delivery.
B.8. Specific data processing
| Data | Purpose |
|---|---|
| Station data | contract, billing, onboarding |
| Internal user accounts | RBAC, audit |
| Playout logs | reports, billing, compliance |
| Listener data (requests) | queue, notifications, anti-fraud |
Operator vs station roles map: https://play258.com/legal/privacidade#quem-e-responsavel-pelo-tratamento.
B.9. Compliance
B.9.1. Telecommunications and broadcast: spectrum licenses or service authorization per country.
B.9.2. Data protection: if the station is joint controller, define obligation split with the Operator.
B.9.3. Payments: compliance with payment-service rules when the station receives funds from listeners.
B.10. Consequences of breach
Suspension of critical features (e.g. paid requests), playout integration removal, contractual termination, indemnification, and notice to affected Organizations when reasonable.
Specific clause — Radio station.