Security overview

How Obscate handles your data

For security and compliance reviewers. Everything here describes what exists today, unless it is marked planned. Last updated 19 November 2026 (hosting details added at launch).

Data handling

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 the fpe strategy there is no map at all (token_map: {}).
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; tracebacks are never printed.
Account dataEmail, plan, usage counters, the site page you signed up from (path only, e.g. /blog/ff1-explained), and an HMAC of each API key. Raw keys are shown once and never stored.

These guarantees are enforced by automated privacy tests on both success and error paths.

What the hosted API can see: plaintext, in memory, while it processes your request. “Data never leaves your perimeter” is true only for the self-hosted edition (planned — design-partner pilots).

Cryptography

Access control and abuse limits

Hosting and data residency

Service providers

ProviderPurposeRegionData it handles
DigitalOceanHosting and managed PostgresBangalore, IndiaRequest traffic in memory; account data at rest
CloudflareEdge network in front of the APINearest edge locationRequest traffic in transit
ResendVerification emailsTokyo, JapanThe recipient’s account email address only. Open and click tracking disabled.
SentryError reportsEU (Germany)Exception type and stack frames only. Messages, request data and variables are stripped (verified with a real test event).

Verification emails are sent from hello@send.obscate.com, with replies going to contact@obscate.com.

Regulation

Obscate is designed to help you meet DPDP Act obligations such as data minimisation and purpose limitation, and the equivalent GDPR principles. It is not a certification, and using it does not by itself make a system compliant.

Accuracy

On a synthetic 200-document benchmark generated by our test harness (python -m eval.benchmark; methodology): every structured or checksum ID type (card, Aadhaar, GSTIN, IBAN, PAN, SSN, email, phone, IPv4, MAC) scores F1 1.00; PERSON 0.80; LOCATION 0.77; micro-average 0.92. Name and place detection is best-effort; deny-lists help, and an optional LLM tier is coming to hosted plans.

Known limits

Compliance status

No SOC 2 or ISO 27001 certification today. Compliance work is in progress. We are glad to walk your security team through the design and answer questionnaires — contact us.

Planned — not available today

Contact

Our contact address is being set up and will be published here before launch.