Most studios publish one privacy policy and point every product at it. It is less work, and it is almost always wrong. A single policy has to describe every product at once, so it ends up describing none of them precisely.
Our two products could hardly be further apart. form. is a personal app: it holds photographs of a person’s wardrobe, their taste and a rounded weather location, and it is billed by Apple and Google. Tracemark is software for companies: it holds activity data, evidence and the names of the people who approved each figure, and it is invoiced under a written order. One document cannot explain both honestly.
What each product publishes
Every product page on this site ends with the same five links: a privacy policy, terms of use, billing and refunds, account deletion and support. Each is written for that product alone, and says what that product collects, who processes it, how long it is kept and how to remove it.
- The privacy policy names what is collected and why, in the product’s own terms.
- The billing page explains who actually takes the money. For form. that is the app store; for Tracemark it is us.
- The deletion page describes how deletion really works, including what cannot be deleted and why.
Where the hard cases are
Writing per product forces the difficult questions into the open. Tracemark promises an audit trail that can never be altered, so it cannot also promise to erase every trace of a user who leaves. Its deletion page says so plainly: the account closes, and the name stays attached to the approvals already made, because that record is the reason the product exists.
The website itself has its own short notice too. It sets no cookies and runs no analytics, so the notice is brief, and it is accurate.