Data Handling
Data retention, residency, and privacy posture.
This page covers what AI Setu stores about your requests, for how long, and where. It describes the current, verified behavior of the platform — not a final, binding legal document. See your Data Processing Agreement for the contractual terms.
What's logged for billing and observability
Per-request operational logs and the usage ledger record ids, provider and model, status, latency, token counts, cost, cache outcome, and the metadata tags you send (an allow-listed set of short key/value pairs) — not your prompt or response text. Error messages returned to you never echo raw prompt or response content either.
What's cached, and for how long
Enabling response caching does store response content temporarily:
- Exact-match cache — the full response body, keyed by a hash of your request (not the raw text), default TTL 600 seconds, capped at 24 hours.
- Semantic cache (opt-in) — the full response body plus an embedding vector of your prompt (not the prompt text itself), default TTL 10 minutes.
Both are scoped to your workspace and never served across workspaces or
namespaces. Set x-ai-setu-cache: off on a request to skip caching
entirely, or purge a workspace's cache on demand (see
Caching).
When content leaves AI Setu's infrastructure
Two guardrail features you explicitly opt into and configure send content onward:
- Webhook guardrail check — if you configure one, the gateway posts the flagged text and request body to the URL you specify. AI Setu strips its own internal auth headers before forwarding, but your endpoint does receive the content.
- LLM-judge guardrail check — if enabled, flagged content is sent to another model through AI Setu's own normal provider routing (billed like any other request) to get a classification verdict — not a third-party leak, but content does make a second trip to an LLM provider.
Outside of these opt-in checks and the caching behavior above, your request and response content is used only to serve that one call and is not otherwise persisted by AI Setu.
PII and secrets
If you enable the PII or secrets guardrail checks, matched values (emails, credit card numbers, API keys, etc.) are redacted with an opaque token before being logged or returned — the raw matched value itself is never stored or echoed back, only the category and count.
Region
Production infrastructure runs in AWS ap-south-1 (Mumbai). A key or
ephemeral token minted for one gateway region is rejected with 421
(wesence.misdirected_region) if it reaches a different region's gateway —
see Errors. Some upstream providers (OpenAI,
Anthropic) are called at their own standard public endpoints, which are not
necessarily India-local; where a provider offers an in-region option (such
as AWS Bedrock in ap-south-1), routing to it depends on your BYOK and
routing configuration — see Providers.
Deletion requests
AI Setu supports per-user erasure requests (relevant under India's DPDP Act and comparable regimes elsewhere): an erasure request immediately revokes the affected user's API keys within their own workspaces, then anonymizes their account and removes their workspace memberships on a scheduled follow-up pass. Contact your workspace admin or support to request one.
Deeper reading
For the contractual retention, sub-processor, and jurisdiction-specific terms, see your organization's Data Processing Agreement and AI Setu's published privacy policy, both linked from the console's billing/legal settings.