Assurance boundary
1. Scope and service model
Phaseo provides a public AI model directory, a customer dashboard, and an API gateway that forwards requests to third-party AI providers. This paper covers the Phaseo-controlled application, gateway, data stores, and operational integrations. It does not attest to controls operated by an AI provider or a customer-configured destination.
The public website runs as a Next.js application hosted by Vercel and delivered behind Cloudflare. The gateway runs on Cloudflare Workers. Supabase provides authentication and the primary relational database. Additional services are listed in the subprocessor schedule.
2. Gateway data flow
| Stage | Data | Handling |
|---|---|---|
| Client to Phaseo | Request content, credentials, routing options, and network metadata | Sent over HTTPS to Cloudflare and processed by the Gateway Worker. |
| Phaseo metadata | Request ID, model and provider IDs, usage, cost, latency, status, errors, and coarse location | Stored in Supabase for billing, usage views, reliability, abuse prevention, and support. Raw prompts and full outputs are excluded from the primary request record. |
| Response cache | Workspace-scoped cache key, response body, and response metadata | Eligible non-streaming text responses may be stored in Upstash Redis for five minutes by default. A preset may configure 30 seconds to 24 hours. The request body contributes to a SHA-256 cache-key digest but is not stored in the cached record. |
| AI provider | Request content and metadata necessary to fulfil the selected model call | Sent over HTTPS to the provider selected directly or by the customer's routing policy. Provider retention, training, and residency terms apply. |
| Client response | Provider output and Phaseo response metadata | Returned to the client over HTTPS. Streaming data is processed in memory while the connection is active. |
3. Content-storage choices and exceptions
Phaseo does not make a universal zero-data-retention claim. In addition to the short-lived response cache, the following customer choices can extend content storage:
- Private I/O logging: a feature-gated workspace setting can store request, response, and optional provider payloads in private Cloudflare R2 for 90, 180, or 365 days. It is off by default.
- Data contribution: an explicit opt-in can capture successful non-BYOK prompts and completions in private Cloudflare R2 for no more than 30 days. Phaseo applies best-effort redaction, but customers must not treat redaction as a guarantee. A configured sample is sent to OpenAI with API storage disabled for asynchronous task classification.
- Observability exports and notifications: customer-configured destinations may receive prompts, outputs, metadata, or alert content according to the customer's settings.
- Asynchronous and media APIs: providers may retain job state, files, inputs, or generated assets for their own documented periods. Phaseo stores job and billing metadata needed to reconcile those requests.
Disabling a Phaseo storage feature stops new capture subject to propagation and in-flight work. It does not delete data already received by an AI provider or customer-configured destination.
4. Current technical controls
Transport and secrets
- Public service and upstream provider connections use HTTPS.
- Bring-your-own provider credentials are encrypted with AES-256-GCM before database storage.
- API and management keys use keyed one-way derivation; OAuth secrets use one-way password-based or keyed derivation.
- Webhook and notification credentials use encrypted storage where the feature supports stored secrets.
Identity and access
- Workspace roles and database policies constrain account and workspace records.
- OAuth consent screens display requested scopes; grants and tokens can be revoked.
- SAML single sign-on and SCIM provisioning are gated enterprise capabilities, not universal controls.
- Management and gateway keys can be scoped and rotated.
Application safeguards
- Rate limits protect sensitive OAuth and realtime routes.
- Security headers include content-type, frame, referrer, and permissions restrictions; the OAuth consent route has a stricter content security policy.
- Structured validation is used at API and configuration boundaries.
- Billing operations use idempotency and database transaction controls in security-sensitive paths.
- Verified account deletion hard-deletes the Auth account and active database data, then uses a retryable scheduled job to purge private R2 and Gateway KV data within 30 days.
Monitoring and disclosure
- Cloudflare invocation logging and request metadata support operational monitoring.
- Provider health and routing state help contain upstream failures.
- Service health and incidents are published at status.phaseo.app.
- Private vulnerability reports are accepted through GitHub Security Advisories or [email protected].
5. Software and change management
Phaseo's main repository is public. Changes use version control, dependency lockfiles, automated linting and type checks, and targeted automated tests. Security-focused validations cover selected secret boundaries, database policies, authentication flows, and gateway contracts.
These practices reduce risk but do not prove that every change receives a formal security review or that the service is free of vulnerabilities. Phaseo does not currently publish a secure-development certification or an independently audited change-management control.
6. Availability and incident handling
Phaseo uses managed infrastructure and provider-health routing to limit some failures. The public status page is hosted by incident.io. Phaseo does not offer a contractual uptime SLA for the public service and does not claim that its incident-response or business-continuity process has been independently tested.
Security incidents involving personal data are assessed against applicable notification duties. The public vulnerability policy targets acknowledgement of a good-faith report within three business days; this is an operational target, not a contractual resolution deadline.
7. Customer responsibilities
- Do not send sensitive or regulated data unless your chosen Phaseo and AI-provider configuration is appropriate for that data.
- Review provider retention, training, residency, and acceptable-use terms before enabling a route.
- Use provider allowlists and privacy routing controls where route selection matters.
- Protect and rotate account, API, management, BYOK, webhook, and OAuth credentials.
- Limit workspace membership and OAuth scopes to what each person or application needs.
- Review private I/O logging, data contribution, response caching, observability, and notification settings before production use.
8. Known assurance gaps
- No SOC 2, ISO 27001, PCI DSS, HIPAA, or comparable Phaseo certification is claimed.
- No completed independent penetration test or public audit report is claimed.
- No universal zero-data-retention or no-training guarantee applies across all providers.
- No end-to-end regional residency guarantee applies across all routes.
- General retention periods for every account, metadata, backup, support, and operational-log category have not yet been consolidated into one public schedule.
9. Contact
Send security reports to [email protected]. Send privacy, DPA, and subprocessor questions to [email protected].