SecureConsent provides a REST API for DPDP-compliant consent capture, identity document storage, purpose tracking, and withdrawal handling. We're opening sandbox access to a limited number of teams with a genuine use case.
Create, track, and honour consent across its full lifecycle - from first capture to withdrawal and deletion. Every state change is timestamped, signed, and auditable.
Encrypted document storage with per-access audit logs. Users upload once and share selectively with any business in the network - no re-uploads, no rogue photocopies.
DPDP mandates a privacy notice, a grievance officer, and a response SLA. The API generates compliant notices dynamically and routes grievance requests with tracking.
Push consent events to your systems in real time. Every API call, document fetch, withdrawal, and deletion is logged in an immutable audit trail ready for regulator inspection.
Create a new consent request for a data principal. Returns a consent link to send to the user and a consent ID for tracking.
Fetch the current status of a consent record - granted, pending, withdrawn - with full purpose-level breakdown and timestamps.
Honour a withdrawal or deletion request. Triggers data purge, generates a signed certificate of deletion, and fires the webhook.
Request access to a document from a user's vault. User receives an approval prompt. Access is logged with your purpose code.
Return all data held for a principal - consent records, documents, purposes, access log - for display in a rights portal.
Generate a DPDP-compliant privacy notice for a given set of purposes and languages. Returns HTML and plain text ready to embed.
Export the full audit log for your organisation - filtered by date range, principal, or purpose - as JSON, CSV, or signed PDF.
Create a grievance ticket on behalf of a data principal. Automatically assigns to your Grievance Officer and starts the 30-day SLA clock.
We review every request before issuing credentials. This keeps the platform secure and lets us assign a dedicated sandbox environment matched to your industry and use case. Approval typically takes 1–2 business days.
Email [email protected] with your company name and a brief description of what you're building. We want to know: what industry, what data you'll be collecting, and how consent fits into your product flow. Two sentences is enough.
We check that your use case is within scope of the DPDP Act - Data Fiduciary status, legitimate purpose, and Indian data storage. We may ask a follow-up question or two. If approved, you'll get a sandbox API key, a test dashboard login, and a copy of the integration guide.
The sandbox mirrors production exactly. You can create test consents, trigger withdrawals, request documents, and inspect the full audit trail - all against test principals. Webhooks fire to your local endpoint via our tunnel tool. No surprises when you go live.
Send us your company name and use case. We'll review and get back to you within 1–2 business days with your sandbox credentials and integration guide.
Your registered company or startup name. Individuals building a product are welcome too.
What you're building and how consent fits in - e.g. "guest check-in for hotel chain" or "lead capture for real estate CRM".
Your product collects data from people in India and you intend to become a Data Fiduciary under DPDP.
Opens your mail client with the subject pre-filled. Send to [email protected].
Drop a consent widget into your existing onboarding. Users see a branded consent screen for each purpose - in their language. You get a signed receipt. Five lines of code.
Link identity verification to consent. No document fetch happens without active consent for the exact purpose. Every fetch is logged. Supports Aadhaar XML, DigiLocker, and manual upload.
Before sending a WhatsApp campaign, check consent status via API. If withdrawn, the contact is suppressed automatically. Integrates with HubSpot, Leadsquared, Zoho, and custom CRMs via webhook.
DPDP classifies health data as sensitive. Our API supports purpose-limited access with stricter controls - consent required per use, per sharing partner, with separate audit log for regulator review.