Do-it-yourself game plans

What must happen before a teen’s prototype is published?

Treat publication as a separate decision with its own budget and responsible adult—not an automatic final lesson. A private demonstration can be the complete educational outcome.

Use this proposed release checklist:

  • The learner can explain the application and its limitations.
  • The intended audience is defined, including whether other children may use it.
  • Data collection and privacy obligations have been reviewed for that audience.
  • No personal or employer data, credentials or identifying repository history is exposed.
  • Code, datasets, images and other materials have appropriate permissions and attribution.
  • Access controls, usage limits and an operational shutdown have been tested.
  • Errors and inappropriate requests have been tested on a bounded basis.
  • A responsible adult owns ongoing costs, maintenance and incident handling.
  • Child identity, voice, image and school are not published without a separate considered decision.
  • The household can explain why a public service is needed rather than a private demonstration.

If the intended service collects information from children, return to the operator-level COPPA analysis and applicable platform policies before launch. A project created by a teenager is not automatically exempt from the rules governing the service’s operation. (ftc.gov)

Sources cited on this page

  1. Complying with COPPA: Frequently Asked Questions | Federal Trade Commission ↗ftc.gov