Child or dependant details
Data about children needs parental consent for online services and a child-appropriate notice.
Keep it how long
The gap we see most
Dependant names collected for an event and kept on the parent record.
What holding it is evidence for
Requirement text and artefacts stated in our own words from the published standards.
Data about children GDPR Art.8 · CCPA/CPRA §1798.120(c) · ISO/IEC 27701:2019 7.2.3
GDPR Art.8 Conditions applicable to child's consentWhere consent is the lawful basis and information society services are offered directly to a child, processing the child's personal data on the child's own consent is lawful only from age 16, or from the lower age a Member State has set in law, which may be no lower than 13. Below that age the proce...
CCPA/CPRA §1798.120(c) Obtain opt-in before selling or sharing data of consumers under 16A business may not sell or share data about a consumer it knows (or wilfully ignores) is under 16 unless the consumer, if 13 to 15, or a parent or guardian, if under 13, has affirmatively authorised it. Under 11 CCR 7070 and 7071 the business must document a reasonable parental-consent method for un...
ISO/IEC 27701:2019 7.2.3 Determine when and how consent is to be obtainedThe organization must determine and document a process by which it can demonstrate whether, when and how consent to processing was obtained, clearly documenting when consent is needed and what obtaining it requires, correlating purposes with how consent is obtained, and taking into account jurisdict...
Do this for your whole CRM
Paste your field list and get this classification for every field at once, with the record of processing per object, the gaps, and the controls the register is evidence for. No account for the first run.
Build my field register