Skip to content

SG PDPA

Singapore PDPA — Children's Guidelines

Singapore's data-protection regime and the PDPC guidance on children's personal data.

18 obligations in this framework — full source text, applicability logic, and engineering tickets inside Landfall.

18 obligation pages · last updated 11 September 2026

SG-PDPA-13-17-UNDERSTANDINGHIGHRequirementConsent

Ensure children aged 13-17 can understand consent consequences; obtain parental consent if understanding is insufficient

PDPC Advisory Guidelines on Children's Personal Data, Section 3.2 - Consent for Children Aged 13 to 17 · Read the full page →

Featured — source excerptA child aged between 13 and 17 is able to give valid consent provided that the organisation's policies on the collection, use and disclosure of personal data are readily understandable by the child.
SG-PDPA-ACCESS-CORRECTIONHIGHRequirementUser Rights

Enable parents and age-appropriate children to access and correct personal data, with responses within 30 days

PDPA Sections 21-22; PDPC Advisory Guidelines on Children's Personal Data, Section 9 - Access and Correction · Read the full page →

Featured — source excerptIndividuals have the right to request access to and correction of their personal data held by an organisation. For children, these rights may be exercised by their parent or guardian on their behalf.
SG-PDPA-ACCOUNTABILITYHIGHProcessGovernance

Implement comprehensive accountability measures including DPO designation, children-specific policies, staff training, and regular compliance audits

PDPA Sections 11-12; PDPC Advisory Guidelines on Children's Personal Data, Section 13 - Accountability · Read the full page →

Featured — source excerptOrganisations must develop and implement policies and practices necessary to meet their obligations under the PDPA with respect to children's personal data.

See how these become your engineering backlog

Landfall turns each of the 18 Singapore PDPA — Children's Guidelines obligations into traceable engineering tickets — with full source text, applicability logic, and a citation chain your auditors can follow.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations