Privacy Policy

Grown-up-only data collection

Dinosaur Kids is made for families, but our forms are directed only to parents and grown-ups. Children should not submit forms, create accounts, or send personal information through this site.

• Dinosaur Kids content is for families, but data-collection forms are directed only to adults/parents, not children under 13.
• Do not ask for child names, exact ages, birthdays, school, address, location, photos, voice, interests tied to a child identity, or account credentials.
• Do not create child accounts, behavioral profiles, targeted advertising audiences, or persistent child identifiers.
• Treat any accidental child PII submission as sensitive: do not copy it into issues, logs, analytics, or PRs; delete/ignore it according to the approved retention path.

Current data practices

• Parent newsletter currently accepts one grown-up email address and sends an internal Payload notification email when CONTACT_EMAIL or ADMIN_EMAIL is configured; it is not a child account, child list, or real double-opt-in mailing list yet.
• Contact forms collect a grown-up name, grown-up email address, and a free-text message for support/business contact only; the UI and API prohibit child-submitted messages and child PII.
• No printable unlock storage, paid commerce flow, or persistent signup/download analytics are enabled by this gate.
• The watch page links to YouTube rather than embedding YouTube iframes, so YouTube cookies/scripts are not loaded by the site today.
• Payload's Sentry plugin is default-off unless SENTRY_DSN is configured; production enablement must use the redaction/default-off rules in this gate.

Logging, analytics, and Sentry defaults

• Do not log or send raw form bodies, email addresses, contact messages, IP addresses, user agents, or child-related free text to Sentry, analytics, or application logs.
• Record aggregate counts only for parent signup/download analytics unless Brandon approves a named provider and retention policy.
• Strip query strings from captured URLs and avoid session replay, heatmaps, ad pixels, fingerprinting, or cross-site marketing cookies on child-facing pages.
• If Sentry is enabled, keep it server-error-only by default and add beforeSend/request scrubbing before production data collection.
• If a provider cannot prove child-safe defaults and deletion/export support, keep the integration disabled.

Production approval gate

Parent email capture, printable unlocks, analytics, embedded YouTube funnel changes, Sentry/logging capture, and any production data collection remain disabled or internal-only until the following approval evidence exists:

• DK-51 privacy/terms audit is merged and reviewed.
• Brandon approval is recorded on the relevant GitHub/Linear issue before production deploy or data-collection enablement.
• The selected email/list provider or Payload storage path, double opt-in behavior, unsubscribe path, retention owner, and export/delete process are documented.
• Sentry, logging, and analytics are configured default-off for child-facing flows and redact email addresses, contact messages, request bodies, IP addresses, user agents, and URLs with query strings before capture.
• YouTube embeds, analytics, printable unlocks, and parent email capture have a pre-production smoke test proving no child PII fields or child-directed tracking are present.