Nebraska

Plain:Use a reasonable age-verification method to determine whether an account applicant is a minor before an account is created.

Engineering:Run a reasonable age-verification/estimation check at account creation to route minors (under 18) into the parental-consent flow.

Statute’s own ages: Account holders 17 and under ('minor' = under 18).

Plain:Obtain express parental or guardian consent (verified identity plus a signed authorization) before a minor may create or hold an account; allow the parent to revoke consent and have the account removed.

Engineering:Gate minor account activation on a verified parent/guardian identity check and signed consent artifact; expose a parent-initiated consent-revocation and account-deletion path.

Statute’s own ages: Account holders 17 and under ('minor' = under 18).

Plain:Give a consenting parent access to a dashboard to view the minor's posts and messages, control privacy and account settings, and monitor and limit time on the platform.

Engineering:Provide a parent-facing dashboard exposing the minor's posts/messages, privacy and account settings controls, and screen-time monitoring/limits, scoped to the consenting parent.

Statute’s own ages: Account holders 17 and under ('minor' = under 18).

Plain:Set the default settings of covered design features to the highest level of privacy protection available for minor users.

Engineering:Ship maximum-protection defaults (restricted visibility, discovery, contactability, and data sharing) for accounts reasonably likely to belong to minors.

Statute’s own ages: Applies to 'minors'; the Act is styled as an Age-Appropriate Online Design Code (under-18 model). Exact statutory age cut-lines pending primary-text verification.

Plain:Give minors accessible tools to opt out of or limit engagement-maximizing design features, for example a chronological (non-algorithmic) feed option, and controls over notifications, autoplay, and in-app/in-game purchases.

Engineering:Expose per-account controls to disable or cap 'covered design features' (infinite scroll, autoplay, push notifications, recommendation personalization, in-game purchases) and offer a reverse-chronological feed alternative.

Statute’s own ages: Applies to minor account holders; precise age scope pending primary-text verification.

Plain:Collect only the minimum personal data necessary to provide the service the minor requests; restrict profiling except where strictly necessary, limit precise-geolocation sharing with notice, and do not deliver targeted advertising to minors.

Engineering:Enforce data minimization for minor accounts; disable profiling and targeted ads by default; gate precise geolocation behind explicit notice/controls.

Statute’s own ages: Applies to minor account holders; precise age scope pending primary-text verification.

Plain:Provide parental tools (privacy management, blocking financial transactions, and limiting time on the service); these tools are enabled by default for known children under 13.

Engineering:Ship parent-facing controls for privacy settings, purchase blocking, and time limits; default them on when the account is a known child under 13.

Statute’s own ages: Default-on parental tools apply to known children under 13; parental tools are otherwise available for minor accounts.

Plain:Suppress push notifications to minors during school hours (8 a.m.–4 p.m.) and overnight (10 p.m.–6 a.m.); sources differ on whether both windows are limited to weekdays during the school year.

Engineering:Gate push notifications for minor accounts by local time: no pushes 08:00–16:00 and 22:00–06:00. Whether the windows apply only on weekdays during the school year (Koley Jessen’s reading) or every day (Reed Smith lists the windows unqualified) is unresolved pending the enrolled text.

Statute’s own ages: Applies to minor account holders; precise age scope pending primary-text verification.