No Ads, No Tracking

It's worth understanding why mainstream platforms track you in the first place, because it explains why RSocial doesn't. On an ad-funded network, you are not the customer — advertisers are. The product being sold is your attention and a detailed profile of your behaviour, and every "free" feature exists to keep you scrolling so that more of both can be collected. Tracking isn't a bug in that model; it's the entire point of it. RSocial simply isn't built on that model, so it has no reason to watch you.

The alternative RSocial chooses is to align who pays with who benefits. Instead of advertisers footing the bill and therefore calling the shots, the project is sustained by the people who actually use and support it — so the software's only job is to serve them. That's not a minor accounting detail; it's the root cause of every privacy decision downstream. Once no one is paying to profile you, the features that would exist purely to harvest data — trackers, behavioural analytics, data-sharing deals — have no reason to be built, and so they aren't. Privacy here isn't a setting you switch on to claw back a little ground; it's what's left when the incentive to spy on you was never there in the first place.

This is more than a promise — it's visible in what the software doesn't contain. There are no analytics tools, no advertising libraries, and no third-party scripts loaded into the interface at all. Nothing "phones home" to a company in the background as you use it. Modern websites often quietly load code from dozens of outside companies — ad networks, trackers, session recorders — each one a channel through which your activity leaks out. RSocial loads none of them, which means there is no hidden pipe carrying your behaviour off your device.

This is something you can verify rather than take on faith. Open your browser's developer tools on any RSocial page and watch the network panel: the only requests you'll see go to your own instance, not to advertising or analytics domains. There is no Google Analytics or gtag snippet, no Facebook pixel, no Mixpanel, Segment, or Amplitude library, and no session-recorder loading in the background — none of the usual third-party names appear anywhere in the interface's code. Authentication also rides in a bearer token the app sends deliberately, not in an ambient tracking cookie, so there's nothing quietly following you between visits either. The absence of tracking isn't a policy you have to trust; it's the observable behaviour of the software.

To be precise and honest, there is a difference between tracking and ordinary logs. Like any server, your instance keeps basic technical logs — the kind that help you see that it's running and diagnose a problem if something breaks. Those logs exist to keep your own device healthy, not to build a profile of you, and crucially they stay on your device: they don't leave it, and there's no one on the other end collecting them, because there is no other end. It's the difference between a car's dashboard warning light and a tracking device secretly reporting your every trip.

What goes into those logs is the ordinary bookkeeping any web server keeps: that a request arrived, whether it succeeded or errored, and timing information useful for spotting a problem. That's operational data for the machine's own health, not a behavioural profile — and because the machine is yours, you're the only one who ever sees it. You decide how long logs are kept and can clear them whenever you like. The crucial distinction is direction: tracking sends a copy of your activity out to someone else's servers to be aggregated and monetised, whereas a log simply sits on your own device for your own troubleshooting. With RSocial there is no "out" — no external endpoint receiving anything — so even the ordinary logs never become a privacy problem.