Recommended document architecture - Play258
Version: 1.0.0
Related to: README.md.
1. Design principles
- General layer + audience annexes: common rules in a single core (General Terms + Privacy Policy); specifics in referenced annexes, avoiding contradictory duplication.
- Satellite policies: cross-cutting topics (cookies, moderation, reports, retention) in standalone documents for frequent updates without reopening full GTUs.
- Semantic versioning per document (
MAJOR.MINOR.PATCH) and global package ID for coordinated releases. - Audit trail: human-readable changelog + technical acceptance log when law or risk requires.
- Segmented notification: changes affecting only one audience trigger targeted communication (see 04-POLITICA-ALTERACOES-VERSIONAMENTO.md).
2. Document map
PLAY258-LEGAL
├── 02-TERMOS-GERAIS-USO.md ← base contract with all users
├── 03-POLITICA-PRIVACIDADE.md ← data processing (legal bases, rights)
├── POLITICA-COOKIES.md ← cookies, pixels, analytics SDKs
├── POLITICA-CONTEUDO-E-PI.md ← uploads, DMCA-style notices, licensing
├── ANEXO-A-ARTISTAS.md
├── ANEXO-B-RADIOS.md
├── ANEXO-C-OUVINTES.md
├── ANEXO-D-ORGANIZACOES.md
├── 04-POLITICA-ALTERACOES-VERSIONAMENTO.md
├── 05-POLITICA-MODERACAO-SUSPENSAO.md
├── 06-POLITICA-DENUNCIAS-RECURSO.md
└── 07-POLITICA-RETENCAO-DADOS.md
3. Normative hierarchy (in case of conflict)
- Mandatory legal provisions of the applicable jurisdiction (non-waivable by contract).
- Specific commercial agreement signed between Operator and Radio or Organization (if any).
- Audience-specific annex (Artist, Radio, Listener, Organization).
- General Terms of Use and Privacy Policy.
- Satellite policies (complementary interpretation).
Model clause in GTUs: “In case of conflict between these Terms and an annex specific to your profile, the annex prevails where more specific to your profile, unless mandatory law provides otherwise or a written agreement states differently.”
4. Why this architecture fits Play258
| Product need | How the architecture responds |
|---|---|
| Multiple actors (4 audiences) with distinct obligations | Annexes per profile + common GTUs |
| Payments, messaging, and sensitive data | Central privacy + retention annex + purpose segregation |
| Musical content and campaigns (IP + advertising) | Separate Content & IP policy, referenced in GTUs and annexes |
| Frequent changes (API, moderation, cookies) | Versioned satellite policies; notification matrix |
| App + web + playout | Same canonical documents (single URL); deep links per channel |
| Compliance and audit | Changelog, change classification, acceptance logs |
5. Mandatory linking in product
- Registration / account creation: link to GTUs + Privacy + (if applicable) Cookies; checkbox where law requires.
- Annexes: explicit acceptance or clear reference in onboarding for Artist, Radio, Organization; Listener when using specific features (e.g. payments).
- Payments: summary of relevant conditions + link to GTUs and Privacy Policy.
- Playout / software license: EULA or software license clauses may be an additional document; must reference platform GTUs for data and account.
6. Per-file metadata (recommended)
Each document should include at the top (YAML or table):
document_id(e.g.PLAY258-TGU)versioneffective_datelast_review_dateaudiences(list:all|artist|station|listener|organization)language
7. Internal owner
Assign owner (Legal/Product) and technical reviewer (Security/DPO) for each package release.
Supporting document — integrate with internal release processes.