Compliance · Practice Standard
Minor Safeguarding,
Documented.
Our internal practice standard for content production engagements where minors may appear — consent registers, event-day identification, pre-publish sign-off, filename discipline, crew conduct and retention.
Scope: These rules apply to all shakalakaa / Plixitt Solutions content production engagements where the shoot or content pipeline may involve the presence, likeness, or voice of persons under 18 years of age. This includes school and education-sector engagements, events at venues attended by minors, and any brand content where minors may appear incidentally.
- Repository: shakalakaa-plixitt/compliance-rules
- File: minor-safeguarding.md
- Version: 1.0
- Effective: 2026-09-01
- Status: Documented internal practice. Not legal advice. Not a claim of certification or regulatory compliance.
Rule 1 — Consent register
1.1 Before any production day involving minors, the client institution (school, venue, or event organiser) provides a consent register drawn from their own records — not collected by the production team directly.
1.2 The register identifies, at minimum: (a) opted-in individuals, (b) opted-out individuals who must not be identifiable in published content, and (c) the date the register was collected.
1.3 The production team receives the register before arriving on-site. Production does not commence without it.
Rule 2 — Event-day identification of opted-out subjects
2.1 Before shooting begins, a named representative of the client institution identifies opted-out individuals to the lead crew member.
2.2 The lead crew member is responsible for ensuring opted-out individuals are not identifiable in captured footage or stills.
2.3 Where an opted-out individual appears incidentally in captured footage, that footage is flagged for exclusion during post-production.
Rule 3 — Pre-publish gate
3.1 No content in which a minor is identifiable is published without named institutional sign-off.
3.2 Sign-off is given by a named authorised representative of the client institution (principal, admissions director, head of marketing, or equivalent — confirmed in writing at engagement start).
3.3 Sign-off is recorded per asset, not per batch. A blanket "publish all" approval does not satisfy this rule.
3.4 The sign-off record is retained for the duration of the engagement plus 24 months.
Rule 4 — Consent status on asset filenames
4.1 Delivered assets are named using the convention: [date]_[event]_[consent-status]_[sequence].[ext]
4.2 Consent status codes: C = consent confirmed, R = restricted (do not publish), A = ambiguous (requires review before publish).
4.3 Restricted and ambiguous assets are never delivered to a public-facing channel without explicit resolution.
Rule 5 — Crew conduct
5.1 No crew member has unsupervised contact with students or minors during production.
5.2 No crew member initiates direct messaging with students or minors on any platform.
5.3 All crew communication with the client institution goes through the named institutional contact, not directly with students.
5.4 Any breach of Rule 5 is reported to the client institution within 24 hours and documented in the engagement file.
Rule 6 — Retention and breach protocol
6.1 All asset files, consent records, and sign-off records are retained for the duration of the engagement plus 24 months.
6.2 In the event of a consent withdrawal after publication, the relevant asset is removed from all shakalakaa-controlled channels within 48 hours of notification and the client institution is notified immediately.
6.3 Removal from third-party platforms (social media, partner sites) is requested within 48 hours; actual removal depends on platform response time.
6.4 The breach or withdrawal is documented in the engagement file with date, asset identifier, and resolution status.
Governance
Owner: Plixitt Solutions (shakalakaa operations team)
Review cycle: Annual, or following any breach or material engagement change
Next review: 2027-09-01
This document describes internal practice standards applied by shakalakaa / Plixitt Solutions. It is not legal advice and does not constitute certification or regulatory compliance under any Malaysian, Singaporean, or other jurisdiction's child protection framework. Clients are responsible for their own regulatory compliance obligations.