Privacy & security

What we collect, how requests flow, how to reach us on security.

What Dynoyard handles on your behalf when you send traffic through your /v1 endpoint.

Full Privacy Policy: /privacy Full Terms of Service: /terms

What we collect

• Account — email, organization name, team members.
• Billing — handled by Stripe; we never see card numbers.
• Usage metadata — per-request token counts, latency, timestamps, status codes, model id, API key id.
• Operational logs — auth events, error traces, rate-limit hits.

We do not retain prompt or completion bodies for training or analytics. Request bodies and streamed responses pass through and are dropped after forwarding, with two narrow exceptions:

• Response cache (opt-in, per-org) — when an org enables response caching, a copy of the completion is held transiently in an isolated per-org key store with a short TTL (default ~30 minutes) so an identical repeat request can be served without a second upstream call. Disabled by default; per-org, never shared across orgs.
• Error diagnostics — on a failed upstream request (HTTP ≥ 400) we capture up to the first 1KB of the upstream error body to help debug provider-side failures. Successful completions are never captured this way.

How requests flow

1. Your client hits https://<your-org>.dynoyard.app/v1/....
2. Traffic terminates at the nearest CDN PoP and authenticates against your API key.
3. The request is forwarded to the inference partner serving the model you chose.
4. The partner’s response streams back to you. Token counts and cost are recorded for billing; the content is not retained (save the two exceptions noted above).

The endpoint, API key, and OpenAI-compatible response shape stay identical regardless of which partner serves a given model.

Inference partners

Models in the catalog are served by upstream inference providers selected for cost, latency, and capability. Partner identities are treated as a commercial detail and may change without notice; your client code stays the same. Enterprise customers can request a written list under NDA.

Isolation

Authentication is per-org, enforced per-key. Prompts from different orgs never share a model’s attention cache or context window, and the opt-in response cache is keyed and scoped per-org — no cross-org leakage. Each request is isolated end-to-end.

Data Processing Agreement

We can sign a DPA. Email hello@dynoyard.app for the latest template.

Security disclosures

Security issues: security@dynoyard.app. Coordinated disclosure appreciated; we respond within 48h.