Where your data lives, and how we treat it.

Where your data lives

Agent Ping runs on DigitalOcean in London, United Kingdom, on infrastructure managed through Laravel Forge. The UK holds an EU adequacy decision, so data from EU customers is transferred under it. We store your run records (timing, status, cost, evaluation results), the step-by-step detail of each run, and the content your agents report to us through the SDK or API.

How long we keep it is set by your plan: step-by-step detail and run history each have their own retention window. The full table is on the data retention page, and you can export everything at any time, on every plan.

Encryption

Data is encrypted in transit with TLS, including between your agents and the ingest endpoint. Credentials, API keys and channel secrets are encrypted at the application layer, with the key held outside the database. Database backups are stored off the server in object storage.

How evaluations handle your data

When evaluations are on, Agent Ping sends the relevant run content to two model providers to be scored against your goal: Jev, a decision model from TypeSafe, screens every sampled run, and Anthropic's Claude scores the ones Jev is unsure about. Neither Anthropic nor TypeSafe trains on data submitted through its API.

Evaluations are an explicit per-team switch, and teams you create later start with it off. If you would rather no run content ever leave Agent Ping, leave evaluations off; health checks still run and send nothing to any model. This is your control, not ours.

Subprocessors

The third parties that process data on our behalf, and why:

  • DigitalOcean — hosting, compute, and the database (London, UK).
  • Laravel Forge — server management and deployment.
  • TypeSafe (Jev) — evaluation screening, only when evaluations are enabled for a team.
  • Anthropic — evaluation scoring, only when evaluations are enabled for a team.
  • Stripe — payment processing for paid plans.
  • OneSignal — web push notifications, if you opt in.
  • Our transactional email provider — alert and account emails.

We keep this list current. When it changes, this page changes with it.

Access control

Your API keys carry scopes: an ingest key can send data, a read key can pull it back, and the two are separate. Teams isolate data inside your account.

On our side, access is limited to the founder, for support and debugging, and only when needed. We do not give third parties access to your data, and there is no ad tech in the product.

Backups and recovery

The database is backed up automatically on a daily schedule through Laravel Forge, to object storage separate from the server. Backups follow their own expiry schedule; when you delete data, copies in backups age out on that schedule rather than living forever.

Responsible disclosure

Found something? Email [email protected]. We commit to acknowledging your report within 72 hours and working with you on a fix. We don't run a paid bounty program, but we are grateful and will credit you if you'd like.

Data Processing Agreement

Our standard DPA, incorporating the EU Standard Contractual Clauses, is available to download and sign: read the DPA.

Your data and exports → Data retention → Plans and limits →