One platform, two portals. In the Consent Manager your team makes the consent policy and every consent is kept with a signed receipt. In the Compliance Portal your DPO sees what is still held, what has been erased and what is overdue. Your developer integrates once; SAMMATI runs the rest.
Both portals are part of the same SAMMATI platform. Consent records flow from the Consent Manager into the Compliance Portal, and the compliance side needs no extra code.
Where your admin and developer work.
Where your DPO works.
Your developer integrates SAMMATI once. After go-live, your company writes nothing more.
Five calls: grant, withdraw, check before each use, renew and update. Or drop in the hosted consent widget.
Your app receives a signed event whenever a consent changes.
A configuration file that maps your tables, with no code. It sends placeholders, never personal data.
Your customers' choices and what your systems still hold, side by side.
Your admin publishes your purposes in Policy Studio, as a test policy and a live policy.
They give or withdraw consent in your app or the hosted widget. Each decision is kept with a signed receipt.
A collector beside your database maps where personal data sits and sends placeholders instead of personal data.
When consent has ended but the data is still there, an erase task goes to your team; once you erase it, the collector closes the task.
Signs up, completes the company profile and publishes your purposes in Policy Studio.
Consent ManagerAdds the consent calls or widget, one webhook endpoint and the collector.
Consent ManagerSees readiness, data mapping and erase tasks, and registers your processors.
Compliance PortalBy daily email, webhook or API, and acknowledge each notice.
Verify each signed receipt themselves.
Sign up, verify your email and complete the company profile
Make your policy in Policy Studio, as a test and a live policy
Set your allowed website and register the webhook endpoint
Build on the test key with the consent calls or the hosted widget
Register your database and map your tables
Switch your app to the live key
Register each processor, its purposes and how it wants to be told
After go-live, your company writes nothing more.
Sign up, pay ₹1,000 a month, and your account, keys, compliance portal space and your DPO's login are created for you.
Tell us a little about your company and we'll get in touch to set up your walkthrough.
The Consent Manager is where your team makes the consent policy and where every consent is kept with a signed receipt. The Compliance Portal is where your DPO tracks readiness, data mapping, erasure and processor notices. Both are one SAMMATI platform: consent records flow from one to the other.
Five consent calls in your app (or the hosted consent widget), one webhook endpoint, and a collector set up from a configuration file with no code. After go-live, your company writes nothing more.
Yes. Your developer builds on a test key with a test policy, and switches your app to the live key when everything works.
The collector sends SAMMATI placeholders instead of personal data. That is enough for data mapping and for checking whether data is still present after consent ends.
SAMMATI records the withdrawal, tells your processors, and sends your team an erase task. Once you erase the data in your own systems, the collector closes the task.
₹1,000 a month, which includes your account, keys, compliance portal space and your DPO's login.
Book a demo and we'll walk you through both portals on a live store.