Privacy policies and terms of use
Privacy policy · Terms of use · App store review
In short
We draft and update the documents your users see: the privacy policy, terms of use, and refund and cookie policies. Many privacy policies will need revising for the DPDP Rules before May 2027.
Where problems usually start
Privacy policies are often adapted from another company's, mention laws and practices that do not apply, and leave out the analytics, session recording and support tools that are running. Terms of use were written before the pricing changed. Without an owner, these documents are updated only when an app store or a customer insists, and the version on the website differs from the one in the repository.
How we approach it
We draft the privacy policy, terms of use, acceptable use policy, cookie and tracker notices, and cancellation and refund terms so that they describe how the product works. These are the first documents a regulator, a journalist or an enterprise buyer reads, and the only ones a user can check against their own experience of the product. A privacy policy written before the DPDP Rules usually needs revising alongside the consent notices the Rules now require.
What our work involves
- Public documents rewritten against the real data flows, vendors and product behaviour, in language a user can follow.
- A privacy policy, terms, refund policy and in-product copy that do not contradict each other.
- Coverage of cookies and trackers, support access, analytics and marketing consent.
- Versions for app stores and enterprise buyers, with a review timed to product releases.
For startups and in-house teams
A product at launch needs its first set of public documents. A business with several websites needs them to agree with each other and with its consent notices. Both need the versions app stores and enterprise buyers ask for.