What CleoSocial Knows About You — and How to Check

Privacy pages usually come in two genres: the legal document nobody reads, and the marketing page that says "we care about your privacy" and hopes you stop there. This post is the third genre: a plain-language walkthrough of what CleoSocial actually knows about you, organized around a principle you can hold us to — followed by the checks you can personally run to verify it.

The principle first, because it explains everything downstream: CleoSocial's feed does not rank content, so it has no structural need for a behavioral dossier. Most platforms' data appetite is not villainy; it is architecture — an engagement-ranking feed is a prediction machine, and prediction machines are hungry. Remove the ranking machine, as this app does by design, and the hunger goes with it. What remains is a short list.

What the App Knows, Category by Category

Account basics. What you gave at signup: credentials, profile details, and age — the last one load-bearing, because ads here are adults-only with unknown-age suppression, which requires knowing who is confirmed 18+.

Your settings. Ceiling, Feed Control topics, Quiet Hours window. This is the data that runs your feed — and notice its character: every item is something you stated, sitting in screens you can open and edit. Your feed configuration is not inferred about you; it is authored by you, and it is inspectable in Settings at any time.

Your activity, as function requires. Posts you make (rated like everything else), interactions, follows — the operational record any social product needs to be a social product. What the architecture does not require, because nothing ranks: the behavioral residue mainstream feeds live on — dwell-time profiling, reaction-pattern modeling, the inferred-interests shadow profile that knows you follow no fitness accounts but linger on fitness content.

Ad-related processing — only after your yes. The consent-gated category. Before you consent: ad systems are set to denied and the advertising script does not load. After an explicit yes: standard ad-serving processing operates, as disclosed at consent time and in the privacy policy. A Global Privacy Control signal from your browser is honored as a standing no. This gate is real in the load-bearing sense — not "we ask nicely," but "the code does not run."

The authoritative specifics — retention, processors, the formal enumeration — live in the privacy policy at cleosocial.app and the App Store privacy label. This post is the map, not the statute; where they differ, the statute governs, and we keep it current there precisely so it can.

The Four Checks

Claims are cheap; here is the audit. Four checks, one evening, no expertise required beyond following instructions.

Check 1: The consent gate (5 minutes, on the website). Open cleosocial.app in a fresh browser session, open developer tools → Network tab, and decline consent. Filter for ad-domain requests: the adsbygoogle script should be absent. Accept consent in another session and watch it appear. You have just verified "denied by default" empirically — the check we most want users to run, because it is the one that would expose us fastest if it ever stopped passing.

Check 2: The GPC check (5 minutes). Enable Global Privacy Control in a browser that supports it (or via extension), visit fresh, and observe: the site should treat you as a no without asking. This is the quiet promise — honoring the signal most sites ignore.

Check 3: The settings inspection (2 minutes, in the app). Open Settings and confirm the authored-not-inferred claim: everything governing your feed — ceiling, topics, hours — is visible and editable. Compare with any mainstream app's attempt at the same screen: an "ad interests" page listing inferences you never made is what a dossier looks like when it is forced to introduce itself.

Check 4: The exit test (whenever you choose). The final privacy feature is the door. Deleting your account is available, uncomplicated, and unaccompanied — no retention-team gauntlet, no data held hostage, no streaks mourning you. An app's true data posture shows at the exit: systems built on your profile make leaving expensive, because the profile is the asset. Here the asset is the product's integrity, which survives your departure intact.

What We Ask of You, Data-Wise, Going Forward

Transparency has a maintenance schedule, so here is ours and yours. Ours: material changes to data practices land in the privacy policy at cleosocial.app before they land in code you encounter, the App Store label stays synchronized, and posts like this one get a visible update stamp when reality moves — the same standard we applied when the ads model arrived and this series updated to match, in public, rather than quietly.

Yours, if you are willing: re-run Check 1 occasionally — after major app updates, or whenever a headline about ad-tech makes you wonder. A privacy posture verified once is a snapshot; verified seasonally, it is oversight. The consent gate is the single point where our incentives and your interests could someday argue, which is exactly why we routed it through code you can watch rather than policy you must trust. Users who check are the enforcement mechanism this model was designed around. It is a strange thing for a company to ask for auditors, but the whole app is a strange bet of that kind: that the platform that hands over the controls — and the receipts — is the one that earns the decade.

Why This Model Holds

A fair skeptic asks what stops the drift — every platform's data appetite grew, so why not this one's? The structural answer, again: appetite follows architecture. Data hunger at the giants is not a policy that could be reversed by a nicer CEO; it feeds the ranking machine that is the product. CleoSocial's product is settings that hold; building a shadow-profile pipeline would be an expense in search of a purpose, and its first fruits — a feed that second-guesses your stated preferences — would be the product breaking, visibly, in the one place users watch. The business model runs on consent surviving audit. We have arranged things so that respecting your data is the lazy path and violating it would be work. That is a sturdier guarantee than virtue.

Reading Other Apps' Labels With Calibrated Eyes

A side benefit of understanding this model: it makes you a sharper reader of everyone else's. Next time you open an App Store privacy label, apply the architecture test from this post. Ask of each disclosed category: what product function requires this? "Data linked to you: contact info, user content" — function, fine. "Data used to track you: browsing history, purchase history, identifiers" on a feed app — that is the ranking machine and its advertisers introducing themselves, and no settings toggle inside the app meaningfully un-feeds it. The label taxonomy makes hunger visible if you know that hunger follows architecture; an app's data appetite is set by what its feed needs to predict, and no privacy policy rewrites that. This is also why our own short list is credible in a way a promise could never be: it is not restraint, it is the absence of the machine that would need more.

The Bottom Line

CleoSocial knows what you told it, what social function requires, and — only after your explicit yes — what ad serving processes, with GPC honored and the door unlocked. No dossier, because nothing here eats dossiers. Four checks verify the picture tonight, and the policy at cleosocial.app carries the formal version.

Privacy pages ask for trust. This one asks for inspection — download CleoSocial free from the App Store and run the checks. An app whose premise is that the feed asks first should expect its users to check whether it does. Please be one of them.