OpenAI API
OpenAI · AI model API
Public sources reviewed . Risk classification and recommended policy are Ayliea's subjective assessments — not vendor certifications.
Scope of this recommendation
Direct OpenAI API with approved endpoints, models, project settings and downstream services.
Public documentation review only. Current audit reports, certificate scope, executed contracts and customer settings were not independently examined. An omitted assurance claim is not evidence that the vendor lacks it.
- Storage and processing locations
- Regional storage and processing depend on eligibility, project configuration, model and endpoint; external tools have separate boundaries.
- Retention and ZDR scope
- Abuse-monitoring content is normally retained up to 30 days, with exceptions. Approved ZDR has endpoint/model limits; stateful resources, caching and external tools require separate review.
- Vendor-reported audits / certifications
- Not established in this public-source review
Why this rating
API data is not used for training by default. Production approval depends on the exact endpoint, retention controls and downstream architecture; neither ZDR nor a generic enterprise contract establishes HIPAA eligibility.
Considerations before deploying
- Verify organization/project retention settings and model-specific exceptions, including stored state and prompt caching.
- For PHI, require an executed applicable BAA, eligible services and required account configuration; do not assume ZDR is always required or sufficient.
- Review data-sharing opt-ins, deletion jobs, remote tools and logging in your own application.
Sources
- OpenAI API data controls (developers.openai.com)
Need a vendor review for your use case?
A scoping call defines the systems, data flows and vendor evidence to review for your use case.