A short, honest explanation of every cookie this site sets, why, and how to control them — no legal jargon, no dark patterns.
Cookies are small text files a website stores in your browser so it can remember something between visits — that you're logged in, or that someone referred you. This page lists, in plain language, every cookie thecircle.ng actually sets. Nothing here is vague "may use cookies for various purposes" boilerplate — if a cookie isn't listed below, we don't set it.
Just five cookies, in total:
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
cc_session |
Keeps you logged in as you move between pages, and protects your account from cross-site request forgery. | Strictly Necessary | Until you log out, or 24 hours of inactivity |
cc_cookie_consent |
Remembers the choice you make on the cookie banner below, so we don't ask you again every visit. | Strictly Necessary | 180 days |
cc_ref |
When you arrive via a member's referral link, remembers who referred you so they're credited correctly if you later join. Only set with your permission. | Functional (optional) | 30 days |
_ga, _ga_* |
Set by Google Analytics to distinguish visitors and sessions, so we can see aggregate traffic patterns. Only set with your permission — IP addresses are anonymized and we've turned off Google's ad-personalization signals. | Analytics (optional) | Up to 2 years |
The cc_session and cc_cookie_consent cookies are
strictly necessary — the site can't log you in or remember your cookie
choice without them, so there's no toggle for these.
The cc_ref referral cookie and Google Analytics are both
entirely optional, and controlled independently of each other. You can
accept or decline each the first time you visit, and change your mind at
any time:
You can also block or delete cookies entirely through your browser's own
settings. If you block cc_session, you won't be able to stay
logged in — everything else on the site will still work.
If you grant the Analytics category above, we load Google Analytics (GA4) to see which pages get used and where visitors drop off. Nothing loads — not even a single request to Google — until you grant it. We've configured it with IP anonymization on and Google's ad-personalization signals ("Google Signals") turned off, since we don't run ads and don't want this data used for advertising anywhere. See Google's Privacy Policy for how Google itself handles this data.
We don't use a third-party card payment provider — every membership and purchase is paid for by direct bank transfer, with the receipt reviewed personally by our team before access is granted. No payment popup or redirect means no third-party checkout cookies are set on our site, and we never see or store your card or full bank account details ourselves.
If we ever start using a new cookie, we'll add it to the table above and
update the effective date at the top of this page. If a new cookie isn't
strictly necessary, we'll ask for your permission first, the same way we do
for cc_ref today.
If anything here is unclear, reach out any time at challengecirclecore@gmail.com — see our Privacy Policy for full contact details.