Capture
The trackers running on your Wix site are detected and inventoried so you can see what is actually firing.
The Product
A compliance platform for your Wix site — not a cookie banner.
DPDPA.support is a self-configuring, multi-tenant DPDP Act 2023 compliance app for Wix, backed by the TSI DPDP CMS. It captures consent with proof, gates trackers until consent, gives your data principals real self-service, honours access and erasure under the Act, and hands your DPO a working console. Every capability below maps to something the platform actually does today.
Self-hosted · Multi-tenant · Provisioned per Wix instance
Consent ledger
Per-purpose consent, recorded with proof.
Every consent decision is captured per purpose and written to the TSI DPDP CMS, your system of record. Consent events flow from Wix to the CMS over webhooks whose signatures are verified with RS256-signed JWTs, and each webhook envelope is persisted to an append-only audit store with a reader endpoint. When the Data Protection Board or an auditor asks, the answer is a record, not a recollection.
- Per-purpose grant and withdrawal, not a single all-or-nothing flag.
- Wix → CMS webhooks, verified with RS256 JWT signatures.
- Append-only audit store of webhook envelopes, with a reader endpoint.
- Two-way enforcement: a withdrawal pushes CMS → Wix so marketing stops.
Cookie & tracker gating
Trackers stay blocked until the principal consents.
DPDPA.support captures the cookies and trackers present on your site and gates them through Wix TAG_OVERRIDE. Analytics and advertising tags do not fire until consent is given — the trackers are gated at the source, not merely hidden behind a banner. Provisioning enforces gating for new tenants, and the setup surface gives you a tracker report with one-click enforcement.
Gate
Analytics and advertising categories are gated via TAG_OVERRIDE until the data principal consents.
Enforce
Gating is auto-applied at provisioning and re-runnable from the setup surface without creating duplicates.
My Data self-service
Your data principals manage their own consent.
At a tenant-branded My Data surface, members are auto-resolved from their Wix identity — no email is ever typed in. An OTP step-up confirms identity to that inbox before sensitive actions, sessions are tenant-bound and HMAC-signed so one site's session is invalid everywhere else, and consent is exposed as per-purpose toggles, both grouped and individual, with accept-all and decline-all.
- Member auto-resolve — no typed email to phish or mistype.
- OTP step-up to the member's own inbox for sensitive actions.
- Tenant-bound, HMAC-signed sessions; isolated per site.
- Per-purpose toggles plus a self-service Download My Data (JSON).
access & portability
One report across every Wix surface.
A access and portability request produces a structured DPDP-AccessReport/1.0 JSON document — the data principal's consent ledger, their grievances, and the Wix fan-out across the surfaces where their data lives. Principals can pull it themselves through the self-service Download My Data action, and the same data underpins portability filing.
- Contacts
- Members
- Marketing consent
- Email subscriptions
- Cookies & trackers
- Orders
- Bookings
- Form submissions
- Inbox / chat
- Invoices / payments
- Loyalty
- Reviews
erasure & legal-hold
Erasure is a processing freeze — not an instant purge.
This is the honest, lawful version of erasure. Under erasure, DPDPA.support stops all processing the moment a request is honoured. But records are not physically destroyed on the spot: the Act's the Act lets a fiduciary retain data under a legal hold, and physical deletion happens only when the retention clock expires. Freezing — not silently deleting — is what keeps you compliant on both sides of the obligation.
1
Processing stops
Consents are withdrawn, Wix marketing consent is revoked, email subscriptions are unsubscribed, and marketing labels are stripped.
2
Wix is brought in line
The Wix Member is deleted so a fresh signup starts clean, while the Wix Contact is frozen rather than deleted — preserving the lawful retention record.
3
Records held under legal hold
Data is retained under a documented legal hold (on the order of years, per the applicable retention rule) — frozen, not actively processed.
4
Physical deletion at expiry
A daily retention-engine sweeper physically deletes records only once their retention period has elapsed.
Why freeze, not purge? A purge-on-request that destroyed retained records would breach the retention obligation. DPDPA.support stops processing immediately and lets the retention engine handle physical deletion at the right time.
DPO console
A working surface for your Data Protection Officer.
DPDPA.support provisions a DPO surface where grievances, corrections, and portability requests are filed and resolved in one place — including a respond-and-action flow that lets the DPO reply to the data principal and choose what happens next. It is a console, not a shared spreadsheet.
Grievances
Receive, respond to, and action grievances raised by data principals, with the response delivered back to the principal.
Rights requests
Correction and portability filings are tracked alongside access and erasure so nothing falls through the cracks.
Principal lookup
Find any data principal and see their consent and request history drawn from the system of record.
Data discovery & RoPA
Know where personal data lives, then map it.
A data inventory step (“List Apps and Storage”) walks the apps and storage attached to your Wix site so you can see where personal data actually sits across surfaces — contacts, members, orders, bookings, forms, inbox, invoices, loyalty, reviews and more. That inventory is the foundation for a Record of Processing Activities your DPO can stand behind.
Discover
Inventory the apps and storage connected to your Wix site to surface where personal data resides.
Classify
Organise discovered data by the Wix surfaces and processing purposes it belongs to.
RoPA
Build toward a Record of Processing Activities grounded in your real data inventory.
Intelligence tier
Bring-your-own-key intelligence, on your terms.
For fiduciaries who want more depth, the Intelligence tier is a bring-your-own-key capability: you supply your own key so analysis runs on your terms — your data stays under your control rather than being handed to someone else's model. It sits on top of the compliance core; the consent, rights, erasure and DPO capabilities above stand entirely on their own without it.
Governance & audit
Evidence by design, tenant-isolated by default.
Governance runs through the whole platform. The append-only audit store persists every webhook envelope and exposes a reader endpoint, tenants are provisioned per Wix instance with keys and policy stored in OpenBao, sessions are tenant-bound, and tenant isolation is enforced fail-closed. The system of record is the multi-tenant TSI DPDP CMS, operated by CynorSense Solutions Pvt. Ltd., Hyderabad.
Append-only audit
Webhook envelopes are persisted append-only, with a reader endpoint for evidence.
Per-instance secrets
Each tenant's keys and policy are stored in OpenBao, provisioned per Wix instance.
Tenant-bound sessions
HMAC-signed sessions are bound to a tenant; one site's session is invalid elsewhere.
Fail-closed isolation
Tenant isolation is enforced fail-closed — the safe default when anything is uncertain.
DPDPA.support is the fiduciary's own consent management and compliance platform. It is not a Board-registered Consent Manager.
See it on your own Wix site.
Install from the Wix App Market, answer two questions during onboarding — your fiduciary legal name and your DPO email — and your tenant is provisioned. Not sure where to start? Begin with the by-need view.