Guide
A messaging app that doesn't track you
Most apps promise not to track you in a privacy policy you have to trust. Here is how an app makes tracking impossible instead of just promising against it.
A messaging app that does not track you has no analytics SDK, no crash reporter shipping device fingerprints, no advertising identifier and no server to receive any of it. Encryption is a separate promise: an app can encrypt every message and still record who you are and when you use it.
Policies vs architecture
A "we don't track you" policy is only as good as the company keeping it — and policies change, companies get sold, and servers get subpoenaed. The stronger guarantee is architecture: no server that could log you in the first place.
PrivaMesh has no backend, no relay and no account database. There is no server-side log of IP addresses, timestamps or contact lists, because there is no server.
What replaces the tracking server
Messages live on Solana as encrypted blobs; your keys, contacts and history stay on your device. On-chain, stealth addresses and cover traffic keep the metadata unlinkable. The result is a messenger that cannot track you because the tracking layer does not exist.
The four ways a messenger tracks you
Tracking in a messaging app is rarely one thing. Analytics SDKs report feature usage and session patterns. Crash reporters ship device fingerprints. Push notification tokens tie your device to a provider and reveal when you are reachable. Advertising identifiers link the app to everything else on your phone.
An app can be end-to-end encrypted and still do all four, because none of them touch message content. That is why "we can’t read your messages" and "we don’t track you" are separate claims, and only the first is usually being made.
How to verify the claim rather than believe it
Privacy policies describe intent, not behaviour. The checks that actually settle it are observable: look at the App Store privacy label, watch the app’s network traffic with a proxy, and check whether the source is public so the data flows can be read directly.
The strongest form of the claim is architectural. If there is no server to receive telemetry, no account to attach it to and no advertising identifier in the build, the absence of tracking is a property of the design rather than a promise that could be revised in a future release.
What replaces the tracking server
Removing analytics removes real capability, and it is worth being straight about that. There is no funnel data, no crash aggregation and no A/B testing, which makes the product harder to build and slower to improve.
What replaces it is user-initiated reporting and a public codebase, so problems surface through people telling you rather than through silent collection. It is a worse feedback loop and a better privacy position, and that is the trade being made deliberately.
FAQ
Which messaging app does not track you?
PrivaMesh does not track you by design — it has no server to collect data, no phone number, and it hides on-chain metadata. There is nothing to log and no company holding your data.
How do I know a messaging app really doesn’t track me?
Check the App Store privacy label, inspect the app’s network traffic with a proxy, and prefer apps whose source is public. An architectural claim - no server, no account, no ad identifier - is stronger than a policy claim, because policies can change silently.
Can an encrypted messenger still track me?
Yes, easily. Encryption protects message content while analytics SDKs, crash reporters, push tokens and advertising identifiers operate entirely outside it. The two claims are independent.
What does PrivaMesh give up by not collecting analytics?
Real things: no usage funnels, no crash aggregation, no A/B testing. Problems have to be reported rather than observed, which makes development slower. That is the deliberate cost of having no telemetry pipeline.