Everything we can prove, in one place.
What's shipped today, what isn't yet, what happens to prompt data, and where we stand on DPDP Act 2023 compliance — consolidated so there's one page to point an auditor or a buyer to, not three.
PromptSec holds no compliance certifications today — not SOC 2, not ISO 27001, not DPDP-certified. Detection runs on-device by default, prompt content never reaches our servers unless an organization explicitly opts in to cloud escalation, and every audit entry is hash-chained so an edited or deleted row is detectable. This page is the single place all of that is stated together.
Last updated:
Where prompt data goes
Nowhere, by default
Detection runs inside the browser extension. Analysing a prompt takes no network call, so prompt text never reaches our servers unless cloud escalation is explicitly turned on.
Telemetry is metadata
The control plane receives the decision, the detected categories, and a timestamp — not the prompt. Sensitive spans are masked before anything is transmitted.
Tenant isolation in the database
Per-tenant row-level security is enforced by Postgres itself — a query that forgets its tenant filter returns nothing, rather than someone else's data.
Tamper-evident audit trail
Each audit entry is hashed together with the entry before it. Editing or deleting a row in the middle breaks the chain, detectably.
The full data-handling writeup, including what happens when cloud escalation is turned on, is at /security.
No vaporware. Here is the honest list.
In security tooling, one inflated claim reasonably makes a buyer distrust everything else you say. So both halves get published, at the same size, on the same page.
Shipped today
- Browser extension (Chrome MV3): content scripts + background worker
- Regex detectors: Aadhaar, PAN, credit card, SSN, email, phone, AWS keys, generic secrets
- Prompt-injection heuristics: instruction override, DAN jailbreaks, prompt leak
- Encoding bypass detection (base64, hex, unicode)
- Policy DSL: allow / redact / warn / block, versioned and rollback-able
- Go telemetry backend with per-tenant isolation enforced in Postgres
- Hash-chained audit trail — an edited or deleted row breaks the chain
- Admin dashboard: live prompt monitor, policy manager, audit logs
- Optional cloud escalation to Amazon Nova Pro on Bedrock (off by default, fails open)
- SSO (SAML 2.0 / OIDC) and SCIM 2.0 provisioning, set up by us
- Event export (CSV / JSON), and alerts to Slack, email, webhook, PagerDuty
Not shipped
- On-device ML model provisioning (the classifier itself is built and tested)
- Named entity recognition for unstructured personal data
- Signed policy bundles, and public anchoring of the audit chain
- SIEM connectors — the export exists, the connectors don't
- Self-serve signup, trials, and in-product billing
- Automated enforcement of audit-retention windows
- Any compliance certification — SOC 2, ISO 27001, DPDP
Every significant architecture decision — browser-first deployment, on-device inference, the policy DSL, the audit chain — is written up in a public decision record you can check the reasoning against.
Designed for compliance from day one.
Detection methods commoditize. The signed, immutable, regulator-ready log of "who said what to which AI, and when" doesn't. PromptSec is designed to make compliance a byproduct of running the product, not a separate project sitting on top of it. The hash-chained audit trail and detection foundation are live today; public anchoring and signed policy bundles are next.
Pre-built Policy Templates
DPDP Act, RBI cybersecurity, SEBI, IRDAI, and Aadhaar Act templates are designed and ready to fork, customize, and ship.
Signed Policy Bundles
The architecture calls for Cosign/Sigstore-signed policies that the extension checks before applying one. On the roadmap.
Tamper-Evident Audit
Every audit entry is hashed to the one before it, so an edited or deleted row is detectable on verification — live today. Anchoring those hashes publicly to Sigstore Rekor is next.
Regulatory Mapping
Every detection maps to specific Indian regulatory controls — DPDP Act sections, CERT-In directions, RBI/SEBI/IRDAI guidelines. The audit log is structured for how an auditor actually reads one.
Digital Personal Data Protection Act — consent, data fiduciary obligations, breach reporting
Cyber incident reporting within 6 hours, 180-day ICT log retention, time-sync with NIC/NPL NTP
Reserve Bank of India data localization, board-approved cybersecurity policy, incident response
Securities and Exchange Board of India — cybersecurity guidelines for regulated entities, AI in capital markets
Insurance Regulatory and Development Authority — data protection and cybersecurity for insurers
Ministry of Electronics and IT — AI platform labeling, consent for personal data, no bias propagation
Information security management system — globally recognized, adopted by Indian enterprises
Aadhaar number detection is live today, checksum-validated and blocked by default; full mapping to the Act itself is still the design goal
Event export in CSV and JSON is available today, so you can get decisions into your own pipeline before the direct connectors land.
What we are not claiming
We hold no compliance certifications. Not SOC 2, not ISO 27001, and not certified against the DPDP Act. The architecture is built around data minimisation and on-device processing — the substance those audits look for — but substance isn't a certificate, and we won't imply otherwise.
Detection is not exhaustive. Regex and heuristics catch structured identifiers and known attack shapes well. They still miss things.
This is one control, not a boundary. It covers browsers. It doesn't cover native apps, terminals, or someone photographing a screen.
Find out what your team is
already sending to AI.
The first week of telemetry usually answers that better than any policy document. No credit card, no commitment — you reach the founding team directly.
Want to see it on your own team before talking price? Join the Design Partner Program — free for 30 days