Privacy pages are full of promises that sound alike. We respect your privacy. We take security seriously. We never sell your data. The words matter, but the strongest version of trust is not a better slogan. It is evidence a person can inspect.
Start with a readable policy
A privacy policy should explain what a product collects, why it needs each category, who processes it, and how a person can exercise their rights. It should not require a legal background to identify the business model.
Short does not automatically mean honest, and long does not automatically mean deceptive. The test is whether the policy answers the questions a reasonable person would ask without hiding the important part behind a vague word like partners.
Show the member their own record
Grav's My Grav Record is meant to make part of that evidence visible. A member can review account information such as policy acceptance, activity checkpoints, and subscription status. The goal is not to turn ordinary people into database administrators. It is to make the record understandable enough that someone can compare what Grav says with what Grav stores.
Data export and deletion tools matter for the same reason. A right that exists only in policy text is weaker than a control that can be requested, tracked, and completed.
Document how to test the claims
People should be able to look for advertising settings, inspect app privacy disclosures, review the network behavior of a fresh account, and compare an export with the product surfaces they used. Grav should publish a plain-language self-test methodology on the website so the process does not depend on trusting our private explanation.
Not every check will prove a negative. No single screenshot can show that data is never sold. But repeatable tests can reveal contradictions. If an app claims it does not build interest profiles while exposing inferred topics in settings, the product has answered the question.
Keep operational access accountable
Running a social service requires support, safety work, reliability records, and limited administrative access. Pretending those systems do not exist would not be honest. The better standard is to limit access, separate staff capabilities, record important staff actions, and retain only what has a defined operational purpose.
Privacy is not the absence of operations. It is the discipline to make operations narrow, visible, and accountable.
Correct the record when the product changes
Features evolve. A privacy explanation can become inaccurate even when it was true when written. That is why Grav's public Journal, policies, My Grav Record, and product behavior need to be maintained together. If the product adds a new public surface or changes how something is stored, the explanation should change too.
Trust should survive inspection
We want people to question Grav's claims. A company that asks members to trust private spaces should expect scrutiny and make useful scrutiny easier.
The standard is simple: say what the product does, build controls that match, keep a record of important actions, and give people a practical way to check. Privacy should not become less convincing when someone looks closely.