SAMMATI Cloud

DPDP consent and compliance,
as a cloud service.

Your developer integrates SAMMATI once. From then on, SAMMATI keeps every consent with a signed receipt, runs your compliance portal, tells your processors when consent ends, and gives auditors proof they can verify themselves.

One plan · ₹1,000 a month
SAMMATI compliance dashboard showing the DPDP readiness score, open obligations, statutory controls and the consent lifecycle
What you get

You integrate once. SAMMATI runs everything else.

Your developer integrates the SAMMATI API once. From then on, SAMMATI takes care of these four things.

Every consent, with a signed receipt

Each grant, withdrawal, renewal and update your customers make is kept with a signed receipt.

Your compliance portal, ready

Your DPO gets a readiness score, data mapping, rights requests and the "consent ended, data still present" check.

Processors told when consent ends

Each processor hears by daily email, webhook or API, and acknowledges. Unanswered notices escalate after 72 hours.

Proof auditors verify themselves

Every consent's signed receipt can be checked by your auditor directly.

How it works

One platform, from your customer's choice to proof of erasure.

Your consent records and your compliance portal are one platform.

1

Your customers decide

They give or withdraw consent in your app, through SAMMATI's consent calls or its hosted consent widget. SAMMATI records each decision against the notice they saw.

2

Your data stays with you

A collector beside your database maps where personal data sits and sends SAMMATI placeholders instead of personal data.

3

Your DPO sees the full picture

SAMMATI matches consent with what your systems still hold. 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.

For your developer

Three things to set up. Then SAMMATI runs the rest.

Consent calls in your app

Five calls: grant, withdraw, check before each use, renew and update. Or use the hosted consent widget.

One webhook endpoint

SAMMATI sends your app a signed event whenever a consent changes.

The collector

A configuration file that maps your tables, with no code. It sends placeholders, never personal data.

After go-live, your company writes nothing more. Your DPO works in the compliance portal.
A customer choosing a purpose and giving consent at sign-up
Your customer gives consent in your app
Data map from the collector, labelling which columns hold personal data
The collector's data map: labels, never values
Product tour

See what your DPO works with every day.

Real screens from a live store running on SAMMATI, with demo data.

Compliance dashboard
Compliance dashboardReadiness score and open obligations at a glance.
For your whole team

Everyone gets the part they need.

Admin

Sets it up

Signs up, completes the company profile and publishes your purposes in Policy Studio.

Developer

Integrates once

Adds the consent calls or widget, one webhook endpoint and the collector.

DPO

Works in the portal

Sees readiness, data mapping and erase tasks, and registers your processors.

Processors

Hear when consent ends

By daily email, webhook or API, and acknowledge each notice.

Auditors

Check the proof

Verify each signed receipt themselves.

Readiness score and data mapping
Consent ended, data still present
Rights requests, ROPA, DPIA and breach
Processor notices with 72-hour escalation
Audit log and evidence export
Erase and verify tasks, closed by the collector
Going live

Seven steps from sign-up to live.

1
Admin

Sign up, verify your email and complete the company profile

2
Admin

Publish your purposes in Policy Studio, as a test and a live policy

3
Developer

Set your allowed website and register the webhook endpoint

4
Developer

Build on the test key with the consent calls or the hosted widget

5
Developer

Set up the collector: register your database and map your tables

6
Developer

Switch your app to the live key

7
DPO

Register each processor, its purposes and how it wants to be told

After go-live, your company writes nothing more.

Pricing

One plan, one price.

Sign up, pay ₹1,000 a month, and your account, keys, compliance portal space and your DPO's login are created for you.

SAMMATI Cloud

₹1,000a month
  • Your account, keys and compliance portal space
  • A login for your DPO
  • Every consent kept with a signed receipt
  • Processor notices by email, webhook or API
  • Proof your auditors can verify
Book a demo
Book a demo

See SAMMATI running on a live store.

Tell us a little about your company and we'll get in touch to set up your walkthrough.

A customer's consent, from sign-up to withdrawal
The collector on a real database
Your DPO's compliance portal

Questions

Good to know

How much work is it for our developer?

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.

Does our customers' personal data go to SAMMATI?

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.

What happens when a customer withdraws consent?

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.

How do auditors know the records are genuine?

Every consent is kept with a signed receipt, and auditors can verify each receipt themselves.

What does it cost?

₹1,000 a month, which includes your account, keys, compliance portal space and your DPO's login.

Ready to see SAMMATI in action?

Book a demo and we'll walk you through it on a live store.

Book a demo