"You are not the product" has been printed on enough landing pages to stop meaning anything. It is a claim about a business model, and business models leave evidence. You do not have to trust the sentence. You can check it.
What the business model can tell you
An ad-funded app has incentives to serve advertisers as well as the people using it. Advertisers pay for precision, and precision requires knowledge: who you are, what you want, who you know, where you go, what you linger on. The product improves as that knowledge deepens. Growth pressure and privacy pressure point in opposite directions, permanently, no matter how sincere the people building it are.
A subscription or paid-access app has a different problem. It needs you to keep paying, which means the incentive is to make the thing good. A paid model does not by itself prevent excessive collection. Check the documented purposes, recipients and controls rather than assuming payment guarantees restraint.
The business model is one part of the picture. Check the actual data practices, permissions and controls rather than treating price or advertising alone as a privacy guarantee.
Signals it is treating you as the product
- Personalized ads anywhere in the app. Not a signal to interpret. A statement of fact about the revenue model.
- An interest or topic list in settings. Check whether the categories are inferred from activity, explicitly chosen by you, or both. A topic list alone does not establish how it was created or used.
- A third-party SDK list in the privacy policy. Analytics, attribution, and ad SDKs are code from other companies running inside the app you trusted. Count them.
- The word "partners." Specifically "we may share information with our partners" or "affiliates." Read which information is shared, with whom and for which purposes. These words alone do not establish advertising, sale or use of private content.
- Free, forever, with no visible way to pay. Somebody is paying. If no purchase surface exists anywhere in the product, work out who.
- A privacy policy that takes twenty minutes to read. Length alone does not establish how many parties receive data or how protective a service is. Read the actual data categories, recipients, purposes and exceptions.
Signals it is not
- App Store privacy disclosures can help you inspect the developer’s reported data collection and uses. They are not an inventory of every SDK or proof that no advertising code is present.
- Clear statements about profiling and inference, supported by the available controls and evidence. The absence of an inferred-topics screen does not prove that no inferences are made.
- No "partners may use your data" clause, and named subprocessors rather than a vague category.
- A policy that clearly explains what is collected, why, who receives it and how long it is kept. Reading time alone is not a privacy test.
- A sustainable way to pay for the service. A clear subscription or support model gives an app a reason to be on your side, even when it also offers a useful free tier.
What Grav collects, and why
Because we are asking you to check other apps, here is ours in plain terms.
We collect an account identity, which is an email address and a username, because an account has to exist for an invite-only network to work. We store what you post inside your Feeds, because storing it is the feature. We store the minimum operational records needed to run the service, such as sign-in events for security and device tokens if you turn on notifications.
This is a summary; our privacy policy describes the data categories and purposes in full. No ad SDKs. No interest categories. No behavioral profile, no data sold, ever, to anyone. Messages are on your terms: you decide who can start a conversation with you. We do not use private Messages for advertising, profiling, sale, cross-app tracking, or training AI models. Photo metadata is stripped on upload, so location data baked into a camera file does not travel with the image.
Grav offers one Feed for free, while Grav+ subscriptions and direct support help pay for the service. That is the boring reason all of the above is possible. We have written about what Grav+ supports, and the privacy policy is short enough to actually read. If you want to see the mechanisms rather than the promises, how Grav protects you is the technical walkthrough.
Related reading: your kids' photos don't belong on a stranger's feed applies these tests to family sharing specifically.
Keep reading
- The people we gravitate towardProduct
- Privacy Should Be ProvablePrivacy
