Legal
Refexa Cookie Notice
- Status
- Last updated 27 October 2026.
This notice explains the cookies and similar browser storage used on refexa.io, including the Refexa app, founder and affiliate dashboards, and Refexa referral links. It is operated by IOANNIS GKOUGKOUSIS, Tholos, Serres, Greece ("Refexa", "we"). For how we handle personal data generally, see our Privacy Policy.
What cookies and browser storage are
Cookies are small files a website stores in your browser. Browser storage (local storage) works in a similar way and stays until it is cleared. Some of what Refexa uses is needed for the site to work; the rest is used only if you agree to it.
Our categories
Refexa uses three categories:
- Necessary: always on. Needed for sign-in, security, remembering your cookie choices and core features.
- Referral attribution: off until you switch it on in Cookie preferences. Lets Refexa keep a referral visitor token in its own cookie on refexa.io.
- Analytics: off until you choose "Accept analytics" or switch it on in Cookie preferences. Used to understand traffic and product use with Google Analytics and PostHog, where analytics is enabled on Refexa.
Each optional category is a separate choice: allowing one never allows the other. Refexa uses no advertising, social media, personalization or session-recording cookies. Refexa's service emails contain no tracking pixels and no click tracking: our email provider, Loops, does not track opens or link clicks in these emails.
Cookies and storage we use
Necessary (no consent asked)
| Name | Provider | Purpose | Type | Lifetime | When it is set |
|---|---|---|---|---|---|
__Secure-better-auth.session_token | Refexa (first party) | Keeps you signed in as a founder or affiliate. HttpOnly, not readable by page scripts | Cookie | 7 days, renewed at most once a day while you use Refexa | When you sign in |
refexa_consent | Refexa (first party) | Remembers your analytics and referral attribution choices, and when you made them. Holds no identifier | Cookie | 180 days, then we ask again | When you save a choice in the banner or Cookie preferences |
refexa:founder:currency:<id>, refexa:affiliate:currency:<id> | Refexa (first party) | Remembers which currency you chose to view in your dashboard | Local storage | Until you clear site data | When you change the currency on a dashboard |
| Stripe cookies | Stripe | Secure card entry and fraud prevention in Stripe's payment form; Stripe describes its fraud-prevention cookies as essential. Names and lifetimes are set by Stripe and described in Stripe's own cookie policy | Cookies set by Stripe.js | Set by Stripe | Only for founders on the Refexa fees page, when Stripe's payment form loads |
Stripe's payment form loads only when a founder chooses to add a card for Refexa's fees, because it is needed to provide that card setup.
Referral attribution (only after you allow it)
| Name | Provider | Purpose | Type | Lifetime | When it is set |
|---|---|---|---|---|---|
rfx_vid | Refexa (first party, on refexa.io) | Keeps the random visitor token from a Refexa referral link, so a later click on a link from the same browser can reuse it. HttpOnly, SameSite=Lax | Cookie | 60 days | When you open a Refexa referral link (/r/...) after allowing referral attribution |
Without your permission, Refexa does not read or set this cookie when you open a referral link, and removes one that is already there. The referral link still works: Refexa records the click with a new random token and sends you on to the founder's website with that token in the address. If you switch referral attribution off and save, Refexa deletes this cookie from refexa.io.
The same visitor token on the founder's own website. When Refexa redirects a referral visit, it adds the visitor token to the address of the founder's website. A founder can keep it in a rfx_vid cookie on their own domain, for example with Refexa's /rfx/v1.js helper (60 days requested). This is the main way a referral is credited when you later become the founder's customer, and it does not depend on Refexa's cookie. That cookie belongs to the founder's website, and the founder's own cookie notice covers it.
Analytics (only after you accept)
These are created only after you choose "Accept analytics" (or switch Analytics on in Cookie preferences). Before that, Refexa's pages do not load Google's or PostHog's code, so these vendors set no cookies or storage through Refexa's pages and receive no analytics data from them. Where analytics is not enabled on Refexa, no banner appears and none of these items is created.
| Name | Provider | Purpose | Type | Lifetime | When it is set |
|---|---|---|---|---|---|
_ga | Google Analytics 4 (set on refexa.io) | Distinguishes visitors with a random identifier | Cookie | 2 years | After you accept analytics |
_ga_<container-id> | Google Analytics 4 (set on refexa.io) | Keeps the state of your visit session | Cookie | 2 years | After you accept analytics |
ph_refexa_anonymous_id | Refexa, used by PostHog | A random identifier Refexa creates and stores so PostHog can recognise the same browser across page loads. It is pseudonymous: Refexa does not link it to your Refexa account, name or email | Local storage | Until you withdraw consent or clear site data | After you accept analytics |
The 2-year lifetimes are Google's default; Refexa's code does not change them. Your browser may delete these cookies sooner.
How PostHog storage is set up. Refexa configures the PostHog SDK with memory-only persistence, so the SDK keeps its own state in the page's memory for the current page load rather than in a cookie or browser storage. The one thing kept in your browser for PostHog is the separate ph_refexa_anonymous_id identifier above, which Refexa stores in local storage after you consent. The PostHog integration does not persist raw page addresses, query strings or campaign parameters (such as utm_ tags or ad click identifiers) in your browser.
Refexa turns off Google's advertising features (Google signals, ad personalisation and every advertising consent signal), so Refexa's setup does not create Google advertising cookies.
Your choices
- Banner. On your first visit, where analytics is enabled, you can choose "Accept analytics", "Reject analytics" or "Manage preferences". Both choices are equally easy, and nothing is pre-selected. Accepting analytics does not allow referral attribution. Rejecting changes nothing about how Refexa works.
- Cookie preferences. Use the "Cookie preferences" link in the site footer or at the bottom of sign-in, onboarding and affiliate pages. It shows a separate switch for Referral attribution and, where analytics is enabled, for Analytics. Both start off until you switch them on.
- Change your mind at any time. When you switch Analytics off and save, Refexa stops sending analytics from that browser straight away and removes the Google Analytics cookies, the PostHog identifier and any other PostHog keys it can find in the cookies and browser storage that Refexa's pages can access. When you switch Referral attribution off and save, Refexa deletes its
rfx_vidcookie from refexa.io. Data already sent before you withdrew stays with Google or PostHog under their retention settings. - Your browser. You can delete or block cookies in your browser settings. If you block necessary cookies you will not be able to sign in.
- Signals. Refexa does not currently read Global Privacy Control or Do Not Track signals; the cookie banner and Cookie preferences are how you choose.
Changes
We will update this notice when the cookies we use change, and change the date above.
Questions
Email igkougkousis01@gmail.com.