Executive summary - Play258 legal package
Package: PLAY258-LEGAL-2026-03
Suggested document version: 1.0.0
Language: Portuguese (PT) — authoritative; this page is an English convenience translation.
1. Purpose of the package
This package defines the modular legal architecture of the Play258 ecosystem: terms of use, privacy, cookies, content and intellectual property, operational policies (moderation, reports, data retention), and annexes by user type (Artists, Radio Stations, Listeners, Organizations), with versioning, change classification, and a notification matrix aligned with large-scale technology platform practices.
2. Product description (factual assumptions)
Based on product assumptions defined for this package, Play258 is assumed to include, among others:
- Engine/backend: APIs, administration panels, music requests (free or paid), messaging integrations (e.g. SMS, WhatsApp), payment processing (e.g. gateways such as VonekaPay / M-Pesa), queues and events for playout, campaign/spot modules (Mediabook), communications, reporting, and auxiliary features.
- Playout (local software): catalog sync, on-air queue, event logging, and integration with the engine.
- User channels: web, mobile application, APIs, administrative panels, and authorized third-party integrations.
Critical published operator data: VONEKA (NUIT 400753504), headquartered in Maputo (Mozambique), official contacts info@voneka.co.mz, suporte@voneka.co.mz, and dpo@voneka.co.mz, with Mozambican law and venue (unless mandatory rules apply).
3. Document audiences
| Audience | Brief description in the ecosystem |
|---|---|
| Artists | Rights holders or representatives who make musical content available or authorize it under the service. |
| Radio stations | Broadcasters or operators using playout, music requests, catalog, and broadcast/compliance features. |
| Listeners | End users interacting to request music, receive notifications, or use listening/participation features. |
| Organizations | Advertisers, agencies, or entities creating campaigns, sending spots, and using reporting/network execution. |
4. Jurisdictions and reference law (assumptions)
- Primary: legislation of Mozambique, country of the Play258 operator’s main establishment.
- Complementary / international: where applicable, GDPR-inspired data protection principles for data subjects in the EEA; LGPD for Brazil if targeted offering or effective presence.
- Consumer: local consumer protection laws when Listeners or small stations act as consumers.
5. Personal data (typical categories)
Identification and contact, account credentials, billing and payment data (via processor), device and session identifiers, usage metadata and logs, uploaded content (messages, audio files where applicable), campaign and broadcast data (reports), and data needed for anti-fraud and legal compliance.
6. Components published on the legal section of the website
- Document architecture and rationale.
- General Terms of Use.
- Privacy Policy.
- Satellite policies: Cookies; Content & IP; Changes and notices; Moderation; Reports; Retention/portability.
- Audience annexes (4).
- Audience impact matrix.
(Material reserved for internal use — such as drafting guides or risk assessments for teams — is not listed above and is not served at public /legal/... URLs.)
7. Recommended next steps (product and legal)
- Review by local counsel + DPO.
- Final validation by sampling to ensure no operational placeholders remain.
- Record version and public changelog (see changes policy).
- Link in flows: signup, login, checkout/payment, app (settings / about), playout (first run or license screen), site footer.
- Record acceptances per document version and, where required, proof of notification (timestamp, channel).
Supporting document - does not replace legal counsel.