a CoEvolution AI center · ← back to centers
We don't use cookies. No cookie banner exists because there is nothing to consent to — nothing is written to or read from your device.
Each page you load on this site, and each time you click a center's "Sponsor / buy sessions" button, sends exactly one request to our own self-hosted pixel — the same first-party tracker RFI-IRFOS runs on rfi-irfos.com. The literal request:
POST https://lighthouse-rfi-irfos.fly.dev/lighthouse/api/track
{"path": "/{center-slug}", "referrer": "...", "utm_source": "...", "site": "coevolution-factory", "section": "{center-slug} or {center-slug}:offer_click"}
What lands in our database from that request: the page path, the referring domain normalized into a channel bucket (organic search, direct, referral, linkedin, and so on), the UTM parameters if present, the site tag, and the section tag (which center, and whether it was a pageview or an offer click). That's the full field list: path, source, referrer, utm_source, utm_medium, utm_campaign, site, section.
No cookie is set. No visitor identifier is ever populated by this site's copy of the pixel, so two visits from the same person land as two independent, unlinked rows, never one growing profile. No IP address column exists in that table. The offer-click beacon exists so we can see which centers people are actually interested in enough to click through to Stripe — that's it, we don't track anything past the click; what you do on Stripe's own checkout page is between you and Stripe.
Because nothing is stored on or read from your device, the ePrivacy Art. 5(3) cookie-consent trigger does not apply. Because nothing here identifies you individually, this is not personal data processing requiring a GDPR Art. 6 legal basis in the first place — it is anonymous, aggregate usage counting.
Payment processing runs through Stripe, linked from RFI-IRFOS's account. We never see or store card details — that is handled entirely by Stripe.
Questions: rfi.irfos@gmail.com