Trust

Security & limits

What exists today, stated precisely, and what doesn’t yet. For security reviewers there is a longer security overview with the service-provider list.

Never logged, never stored

Input text / JSONProcessed in memory for the duration of the request. Not written to disk, logs or a database.
Detected valuesNot stored or logged.
Restore mapReturned to you, never kept by Obscate. With fpe there is no map at all.
Server logsOne line per request: timestamp, request id, method, path, status, latency, e.g. INFO rid=437516c03a00 POST /v1/redact 200 4ms.
ErrorsNever echo the request body. Unexpected errors log only the exception type; no tracebacks.
Account dataEmail, plan, usage counters, the site page you signed up from (path only), and an HMAC of each API key.

These guarantees are enforced by automated privacy tests on success and error paths. The integration packages (MCP, LangChain, LlamaIndex) carry the same promise and their own privacy tests.

Controls in place

  • API keys authenticated and requests rate-limited before the body is read.
  • Keys stored only as HMAC hashes and shown once; up to 5 active keys per account, with rotation and revocation.
  • Per-key rate limits by plan (60 / 300 / 600 requests a minute); 1 MB maximum body.
  • Encryption keys come from the environment, never code; in production the server refuses to start without them.
  • One key per account. On the hosted API, each account’s fpe and hash keys are derived per request with HKDF-SHA256 from a service master key, the account and the key version. Nothing per account is stored. Another account’s API key cannot restore your fpe tokens, and hash pseudonyms differ between accounts. The self-hosted edition (in pilot) uses your own OBSCATE_FPE_KEY.
  • Versioned keys. Redact responses include key_version, and restore accepts it, so a key can be rotated while tokens made under the previous version still restore.
  • FF1 with AES-256, tested against all nine official NIST FF1 sample vectors; names and short values use authenticated AES-SIV tokens; every fpe redaction self-checks its round trip.
  • Property tests: restore(redact(t)) == t, and no strategy outputs a full raw value.
  • The homepage playground uses separate demo-only keys, limited to 10 requests a minute per network.

Key change (19 November 2026). When the hosted API moved to one key per account, fpe tokens and hash pseudonyms created before that change stopped restoring and matching. tokenize, synthetic, mask and partial were not affected. Re-redact anything you stored from before the change.

Data residency

  • Processing: the hosted API runs on DigitalOcean App Platform in Bangalore, India (region blr1). Request content is processed in memory there.
  • Account data is stored in managed Postgres in Bangalore, encrypted at rest.
  • Network path: traffic enters through Cloudflare’s edge network (App Platform’s built-in CDN) before reaching Bangalore. We don’t claim data “never leaves India”: it transits the nearest Cloudflare edge.
  • Verification emails go through Resend (Tokyo; recipient address only). Error reports go to Sentry (EU; exception type and stack frames only).

Limits, stated plainly

  • The hosted API sees plaintext in memory while it handles a request. “Never leaves your perimeter” will only be true with self-hosted, which is in pilot.
  • Partial values: if a model quotes only part of a redacted value (“card ending in 7588”), restore can’t map the fragment back, and with fpe the wrong digits look real. Prompt the model to repeat values whole, or use tokenize. Details.
  • Invented values: if an LLM invents a new card or email that looks like a token, key-only restore transforms it too. Names and places are immune.
  • Name and place detection is best-effort (about 0.80 recall on our synthetic benchmark). The optional LLM tier for higher recall is coming to hosted plans.
  • No SOC 2 or ISO 27001 certification yet. Compliance work is in progress.

DPDP Act and GDPR

Obscate is designed to help you meet DPDP Act obligations such as data minimisation and purpose limitation, and GDPR’s equivalents. It is a tool for your programme, not a certification of it, and using it doesn’t by itself make a system compliant.

Planned, not available today

  • Self-hosted / in-VPC edition: in pilot with design partners. Request a pilot.
  • Hosted LLM detection tier: coming to hosted plans.

Questions or a security questionnaire: contact us.

Get a free API key

Free plan: 1,000 requests a month, all strategies. Your key is shown once — we store only a hash of it.

Prefer the terminal?
curl -s API/v1/signup \
  -H 'content-type: application/json' \
  -d '{"email":"you@company.com"}'

Contact

Our contact address is being set up.