Legal
Disclaimer.
We write about Indian regulation in specific terms because vague writing is useless. That specificity is exactly why this page exists: engineering writing is not a compliance opinion, and we are not your lawyers.
Regulatory content is not legal advice
We describe what rules mean for an architecture. Whether a rule applies to you is a question for your counsel.
Several pages discuss the DPDP Act and its Rules, RBI directions on data storage and IT outsourcing, SEBI's AI provisions, IRDAI's work on AI in insurance, CERT-In reporting timelines and MeitY's rules on synthetic content. We cite instruments by number and date, and we name the source, so you can go and read the original.
That is deliberately narrower than advice. We are engineers. We can tell you what an audit trail has to emit for a requirement to be satisfiable, or what deletion has to reach for it to be real. We cannot tell you whether you are a Significant Data Fiduciary, whether a particular direction binds your entity, or what a regulator would make of your specific facts. Your counsel sets the requirement; we make the architecture meet it.
Regulation moves, and pages do not move with it
A consultation paper becomes a circular. A committee reports and its recommendations are adopted, or are not. A draft rule is notified with a clause dropped. Where we describe something as a draft, a proposal or a recommendation, that was accurate when written — and the date at the top of each page tells you when that was.
Check the current position before you rely on it. If you find something on this site that has gone stale or that we got wrong, tell us at hello@zenmagix.com and we will correct it. We would rather be corrected than cited wrongly.
No guaranteed outcomes
We do not guarantee search rankings, and we do not quote accuracy figures before seeing your data.
Anyone guaranteeing a number one ranking is either lying or planning to rank you for a phrase nobody searches. Search engines and AI assistants change their systems constantly and neither of us controls them.
The same holds for model performance. Retrieval accuracy, deflection rate, extraction precision — these depend on your documents, your queries and your tolerance for a wrong answer. A figure quoted before anyone has looked at your data is a guess wearing a decimal point. We will give you a measured number once there is an evaluation set to measure against, which is why we build that first.
Indicative costs are indicative
The bands on the cost page exist because "it depends, contact us" is a non-answer. They are ranges tied to stated assumptions, not quotations. Your project can sit outside them for reasons that are entirely legitimate. A price binds us when it is in a signed proposal and not before.
Third-party names and links
We name tools, providers, regulators and publications where naming them makes the writing checkable. A name is not an endorsement, an affiliation or a claim of partnership, and all trademarks belong to their owners. Where we link out, we do not control what is on the other end.
What is on the site about our own work
Where we describe the kinds of problem we work on, those descriptions are general. We do not publish client names, project metrics or case studies without written permission, so you will not find invented numbers here — and where a real figure would have strengthened a page, we left it out rather than estimate one.
Liability
To the extent Indian law allows, we accept no liability for loss arising from reliance on anything published on this website. Liability under a client engagement is governed by that agreement. The terms and conditions set this out in full.
Related: Privacy policy, Refund policy.