Treat public release as a new approval decision, not the automatic final lesson. Our recommended default is a local or access-restricted demonstration until the release questions are answered.
Before allowing outside users:
- Identify the adult responsible for operation, spending and shutdown.
- Remove personal, school and employer-confidential information.
- Check authentication, credentials and access to stored data.
- Establish who can submit content and how inappropriate or unexpected use will be handled.
- Verify spending controls and a practical shutdown mechanism.
- Recheck the rules for applications serving minors.
Spend notifications alone are not a shutdown mechanism: OpenAI’s key-safety guidance distinguishes alerts from hard enforcement and warns that enforcement is not instantaneous. Its under-18 API guidance also calls for additional safeguards for applications serving minors. (help.openai.com)
If the household cannot assess these controls, keep the project private and obtain a technical review. A successful educational prototype need not become a public service.
Sources cited on this page
- Best practices for API key safety | OpenAI Help Center ↗help.openai.com