Parental Consent — Kids OpenCode

The text and structure of the Parental Consent capture step in the Family Account onboarding flow. The consent record is stored immutably in Airbotix-AI/platform-backend, is exportable on parent request, and forms the lawful basis for processing each Kid Profile's data.

Designed to satisfy:

• Privacy Act 1988 (Cth) APP 3, APP 5, APP 6 — informed, specific consent
• Children's Online Privacy Code 2026 (when in force) — "informed, current, not withdrawn, specific, unambiguous and voluntary" consent
• Anthropic AUP "Organizations Serving Minors" guideline — explicit parental authorisation
• OpenAI Under-18 API Guidance — recorded parental consent for any kid under the local age of digital consent

Last updated: 2026-06-12 · Version: 0.1 (engineering-side draft pending qualified-AU-lawyer review)

1. When this consent is captured

This consent flow runs:

1. The first time a Parent creates a Kid Profile
2. Once every 12 months thereafter, on the anniversary of the original consent (renewal step)
3. Immediately, if Airbotix makes a material change to processing practices (e.g., adds a new provider, changes audit retention)
4. Immediately, if the Kid turns 18 (separate "Adult transition" flow, not covered here)

The consent is captured as an itemised set of explicit affirmative actions, not a single tick-box.

2. Pre-consent context (shown to the Parent before checkboxes)

Setting up [KID NICKNAME]

Before we start, we want to tell you exactly what happens when [Kid Nickname] uses Kids OpenCode, and ask for your permission for each part.

This page is long because we want to be honest. Please read it. It takes about 4 minutes.

Anything you check below, you can change later from your Family Dashboard. You can also withdraw consent and close [Kid Nickname]'s profile at any time.

If something is unclear, email privacy@airbotix.ai — we'll explain.

3. Itemised consent items

Each item is an independent checkbox. The Parent must affirmatively check each to proceed. Default state: unchecked.

The wording below is verbatim what the Parent reads. Right column is operational notes (not shown to Parent).

Optional consent items (Parent may decline without losing access to the Service)

These are independent and uncheckable without losing the core Service.

4. After the Parent submits

Upon submission, the platform-backend records:

Consent record entry
─────────────────────
- family_id
- kid_profile_id (new)
- timestamp (UTC)
- ip_address_hash (one-way hashed, for fraud / multi-account detection)
- parent_email_at_consent
- consent_items_accepted: [C-1, C-2, C-3, C-4, C-5, C-6, C-7, C-8, C-9, C-10, C-11, C-12, ...optional]
- consent_items_declined: [...optional]
- privacy_policy_version_at_consent (e.g., "0.1")
- terms_version_at_consent (e.g., "0.1")
- next_renewal_due (= consent timestamp + 365 days)
- digital_signature (HMAC of all above with platform-backend signing key)

This record is immutable (insert-only audit table). Subsequent changes to consent (Parent toggles something in the dashboard, or renewal happens) create a new record, not an update.

The Parent can email privacy@airbotix.ai to receive a copy of their consent records as a PDF.

5. Withdrawal flow

The Parent's Family Dashboard has a "Manage Consent" page exposing each consent item with a current-state toggle and a "Withdraw" action.

Withdrawing a required consent (C-1 through C-12) automatically pauses the Kid Profile (cannot run sessions) and prompts the Parent to either re-consent or close the profile entirely.

Withdrawing an optional consent (C-13 through C-15) simply turns off that channel.

Every withdrawal is recorded as a new immutable consent record entry.

6. Material-change flow

If Airbotix makes a material change to processing practices — e.g.:

• Adding a new LLM provider not previously listed
• Changing audit log retention duration
• Changing data-residency region
• Changing the AI tool whitelist (adding tools is material; removing is not)
• Changing the kid-safe system prompt in a way that materially alters AI behaviour

…all active Family Accounts are emailed at least 30 days before the change, and on next login each Parent must re-affirm consent through a delta page that shows only the items that have changed.

If the Parent does not re-affirm within 30 days of the change taking effect, the Kid Profile is paused (cannot run sessions) until consent is updated or the profile is closed.

7. Renewal flow

12 months after the last consent record:

• Parent receives an email asking them to confirm consent is still current
• Parent logs in and reviews the full consent page; checkboxes are pre-filled with their current state
• They affirm or update; a new consent record is written
• If they ignore the email for 30 days, the Kid Profile is paused (cannot run sessions) until renewed

8. Kid turns 18 flow

When the Kid's recorded age band would naturally cross 18:

• 60 days before the assumed birthday (based on the original age band at profile creation + months elapsed; we don't have exact birthdays), the Parent is notified
• On the assumed birthday, the Kid is offered the option to convert to an Adult Account or remain under Family supervision until they actively transition
• Adult conversion requires the Kid (now 18+) to accept the Adult Terms of Service directly; the Parent's consent is no longer the basis for processing
• If they do not convert and do not remain under Family supervision, the profile is paused after a 30-day grace period

9. Workshop consent

If the Kid is using the Service via a school Workshop, the school operates under a separate Workshop Services Agreement that includes school-side parental consent. The Family-account consent above is still required for any data that returns to the Family Account context (e.g., audit log visibility to the family).

10. Audit trail for regulators

The full consent record (per §4) is producible on demand to:

• The OAIC under a privacy investigation
• The eSafety Commissioner under a transparency notice
• Anthropic's compliance team under their AUP audit
• The Parent themselves on request

We are happy to demonstrate the flow to any regulator.

Revision history