The DPDP Rules are phasing in through 2026 and 2027. Organisational compliance is mandatory by 13 May 2027.

What this means for you

Home / About

We build the systems, not just the advice.

Asveera Data Protection and Compliance is a data protection and compliance consultancy working with clients across India. We build compliance into the systems that micro, small and medium businesses already run on.

What we are

A technology practice that reads the law, not a law firm that gestures at technology.

Most data protection problems in a micro, small or medium business are questions of techno-legal interpretation. How many systems hold customer data? Which tools did the team adopt without telling anyone? Who still has access to the shared drive? Does the consent box on the website record anything at all? Is consent taken for one purpose and used for four others?

Those questions do not get answered by a stand alone legal opinion. They get answered by sitting inside your admin consoles and talking to the people who actually use each system. A business that commissions an opinion and tries to scramble with tools to fix it later, usually ends up paying a lot more without fixing its problems.

Our work produces registers, maps, procedures, drafted documents and a dated record of what you did. This is different from legal advice that leaves you to implement changes alone. Our holistic approach identifies the gaps, gives you the advice, helps you implement changes, and create records that prove your compliance.

We also keep the scope honest. A business of thirty people does not need the control set of a bank, and we will not sell one. Engagements end with your team being empowered to continue the work you do, fully compliant to the demands of the law.

How we work

Four rules we hold to on every engagement.

We start with your systems, not a questionnaire

Discovery goes tool by tool through the admin panels, the drives, the group chats, the people and the automations. A questionnaire records what people remember while a console records what is configured. The difference between the two is where the problems live, and identify that.

We size the work to your actual risk

Controls scale with what you hold and what could go wrong. If a step does not apply to your business, it does not go into the scope of the engagement, and you do not pay for it.

We draft with you and help you adopt

Every recommendation arrives as a document or a process ready to be adopted, only after we make business decisions together. Where a compliance solution only works if your team owns it, we build it with them.

We take no money from vendors

We accept no referral fees, commissions or reseller margins from any platform, tool or service we recommend. If we tell you to buy something, the only reason is that you need it. And we will always give you options.

Working terms

How engagements are set up.

These terms are standard across our engagements and are written into the engagement letter.

Confidentiality

Your information stays yours

Nothing from an engagement appears in our marketing, case studies or anywhere else without your written agreement.

Scope

End to end, or only the steps you need

Engage us for end-to-end DPDP Compliance or pick only the steps you need. The engagement letter records your choice and what we commit to. Anything added later is agreed in writing before it starts.

Independence

No vendor money, ever

We accept no referral fees or commissions from any platform or service we recommend. Our only income from an engagement is the fee you pay us.

Common questions

What business owners ask us first.

No. The obligations follow the data, not the headcount. A fifteen person business holding customer phone numbers and employee records carries the same basic duties as a large company. What changes is proportion. Your controls should match your size and risk, which is exactly what the scoping step decides.

Most of the load falls in discovery, where we need interviews with the people who actually use each system. After that your team reviews drafts and makes decisions. Implementation needs developer or vendor time, which we scope in advance so it does not arrive as a surprise.

A tool collects consent. It does not tell you what you are collecting consent for, whether consent is the right basis for that activity, what your vendors do with the data afterwards, or how you delete it later. Tools help once the underlying map and decisions exist. Bought first, they usually end up configured around guesses.

We write them. Notices, policies, procedures, consent text and the data protection terms for your vendor contracts arrive as drafts prepared for your business, which your team then reviews and adopts. A list of recommendations you have to turn into documents yourself is not a deliverable.

Then more than one framework applies to the same systems. We build a single control set and record how it answers each framework, so you run one programme rather than two. That gets agreed in the applicability step, before any drafting starts.

You hold the deliverables, the trained team and a review calendar telling you what to check and when. If you would rather not run it alone, we can stay on for a set number of hours each month, with a named person who already knows your systems, to check new tools before they go live, handle requests as they arrive, keep the record current and be reachable when something goes wrong. That is optional and priced separately. The work is built so you can run it without us.

Start here

Tell us what your business runs on.

Thirty minutes is enough for us to tell you which gaps matter most and which steps your business actually needs.