or-sim.dpapi.org

Privacy Policy

Last updated: 2026-07-23 · Endpoint: https://or-sim.dpapi.org

This is an experimental OpenAI-compatible API used for provider dry-runs and integration testing. Do not send production secrets, payment data, or personal information you are not authorized to process.

1. Who operates this service

This endpoint is operated by the owner of dpapi.org for experimental model-serving and OpenRouter-style provider rehearsal. Contact: [email protected].

2. What this policy covers

It applies to API traffic and related operational logs for https://or-sim.dpapi.org (including paths under /v1). It does not automatically cover other dpapi.org products unless those sites link here.

3. Data we process

  • API content: prompts, messages, and model outputs you submit or receive.
  • Request metadata: timestamps, model id, token usage, status codes, and approximate client IP / User-Agent when available.
  • Authentication: API keys are required (Bearer token). We validate keys; we do not ask for passwords on this page.

We do not intentionally collect government IDs, payment card numbers, or account passwords through this API. Please avoid sending such data in prompts.

4. How we use data

  • To run inference and return completions.
  • To debug reliability, abuse, and security issues.
  • To measure basic capacity (for example token usage).

We do not use prompts or outputs to train, fine-tune, or improve foundation models.

5. Retention

Temporary debug logs (which may include prompt/response text while troubleshooting) are retained for up to 7 days, then deleted or rotated out of active storage. Aggregated metrics without prompt text may be kept longer for capacity planning.

6. Sharing & subprocessors

We do not sell personal data. Limited infrastructure parties may process traffic as needed to run the service:

  • Cloudflare — DNS / CDN / TLS edge (when enabled for the domain).
  • Hosting / VPS provider — origin server for HTTPS reverse proxy.
  • Inference host — GPU machine that generates model outputs (may be a lab or home endpoint during dry-run).

We may disclose data if required by law or to protect the service against abuse or security threats.

7. Security

  • Access requires a valid Bearer API key.
  • Transport to the public hostname uses HTTPS.
  • This is an experimental node; availability and uptime are not guaranteed.

If you believe there is a security issue, email [email protected].

8. Contact & updates

Questions about this policy: [email protected].

We may update this page as the experiment evolves. The “Last updated” date at the top will change when we do.