Your pixels may be breaking the law before checkout
Most stores load ad pixels, chat tools and analytics the moment a page opens. Under the DPDP Act, shoppers have to say yes first.
Scan your website
Read-only and free. Nothing on your site is changed.
The personal data you hold
- Names, phone numbers and delivery addresses
- Order history and wishlists
- Payment references and UPI handles
- Browsing behaviour from pixels and analytics
- Reviews, returns and support chats
Where businesses like yours slip
Trackers wait for consent
Meta, Google and other ad pixels that fire before the shopper agrees.
Cookies wait for consent
Tracking cookies set on the first page load, before any choice is offered.
Consent banner with equal choices
A cookie banner with only an Accept button, or a Reject option hidden two clicks away.
Third-party sharing disclosed in the notice
Shopper data flowing to many outside tools with no list in the privacy notice.
Common questions
Can we keep our Meta Pixel?
Yes, but it should load only after the shopper agrees. Server-side tracking after consent is the safer way to measure ads.
Do we need consent to send order updates?
Order and delivery messages serve the purchase itself. Offers and newsletters are a separate purpose and need a separate yes that can be withdrawn.
What about our delivery and payment partners?
They process data for you, so you need contracts and should name the kinds of partners in your notice.
This page is general information, not legal advice.
Find out where your website stands
A free, read-only scan with plain-language findings you can act on.