Skip to main content
A platform team asks two questions before depending on a vendor: is it up, and is it safe. This page answers both and tells you who to contact when you need more.

Checking service health

The API exposes a health endpoint you can poll from your own monitoring:
A healthy API returns 200 with {"status":"ok"}. If every request from your side is failing at once, check this endpoint before debugging your code, then contact support@tirdad.ai with the time, environment, and any request IDs.
Ingestion is asynchronous. POST /events returns 202 as soon as the event is queued, so a healthy API and a delayed metering pipeline can coexist briefly. The architecture page describes the buffering that protects events during that window, and the freshness guarantees for balances and alerts.

Availability and latency commitments

Published targets for availability, ingestion latency, and query latency live on the architecture page. Enterprise agreements carry their own SLA terms.

How your data is protected

  • Tenant isolation. Every request is scoped to a tenant and an environment. A sandbox key cannot read or change production data.
  • Encryption. Data is encrypted in transit and at rest.
  • Private data tier. Only the API service is reachable from the internet, behind a load balancer and WAF. Databases, brokers, and caches run in private subnets with no inbound internet route. See System architecture.
  • No card data. Payment credentials are handled by your payment provider and never pass through Tirdad.
  • Access control. Dashboard roles and scoped API keys limit what each person and integration can do. See RBAC.
For a security review or questionnaire, email support@tirdad.ai. Our privacy policy is at tirdad.ai/privacy.

Data residency

Where your data lives depends on how Tirdad is deployed: See Deployment models for how the two differ.

Reporting a security issue

Send vulnerability reports to support@tirdad.ai with “Security” in the subject and reproduction steps. We acknowledge reports within three business days and work with good-faith researchers to fix issues before any public disclosure. Do not run automated scanners against Tirdad Cloud without permission, and do not test against other customers’ data.

Rotating a leaked credential

If an API key or webhook secret is exposed:
  1. Delete the key in the dashboard under Developers, or with DELETE /secrets/api/keys/{id}. It stops working immediately.
  2. Create a replacement and deploy it.
  3. Rotate the webhook signing secret from the endpoint’s page; deliveries carry both signatures during the grace period. See Signature verification.