Legal
Refexa Privacy Policy
- Version
- 2026-10-29
- Status
- Effective 29 October 2026.
1. Who we are
Refexa is an affiliate and referral tracking service for software businesses that take payments through Stripe. Refexa records referral links, clicks, which customer an affiliate referred, the commission an affiliate earned under the business's own rules, and the payments the business tells Refexa it made to affiliates outside Refexa. Refexa does not hold or move money for businesses or affiliates.
Refexa is operated by IOANNIS GKOUGKOUSIS, an individual business (sole proprietorship) established in Greece, located in Tholos, Serres, Greece ("Refexa", "we", "us", "our").
Contact for anything in this policy: igkougkousis01@gmail.com (section 14).
2. What this policy covers
This policy describes how Refexa handles personal data when you:
- visit the Refexa website at refexa.io;
- create or use a Refexa account as a founder (a business that runs an affiliate program on Refexa);
- join a founder's program as an affiliate;
- click an affiliate's Refexa referral link; or
- are a customer of a founder whose referral or Stripe payment data reaches Refexa through that founder's Refexa account.
Refexa plays different roles for different data (section 3). Where Refexa handles data on a founder's behalf, the founder's own privacy notice is the primary notice for their customers, and this policy explains what Refexa itself does with that data.
This policy does not cover the founder's own website, product or Stripe account, or how a founder pays its affiliates. Those are the founder's responsibility.
3. Our role for each kind of data
Data Refexa decides the purposes for. Refexa decides why and how personal data is processed for:
- founder accounts, sign-in and account security, and affiliate sign-in and account security;
- billing founders for Refexa's own fees, including the billing profile and card setup;
- service emails, such as verification, sign-in and password-reset emails;
- website and product analytics, only with consent (section 4.7);
- fraud, abuse and security protection;
- legal and compliance purposes; and
- Refexa's own operational records, including the financial history kept after a founder deletes their account (section 10).
Data a founder supplies for their program. A founder decides the business purpose for which program and customer data is supplied to Refexa: affiliate participation in their program (applications, approvals, links, clicks, credited customers, commission and payouts the founder records) and data about the founder's own customers (customer references, optional email addresses, Stripe customer and payment data, and referral click records). Refexa processes that data to provide the service to the founder. Refexa still separately decides its own purposes for security, billing, fraud prevention and legal compliance where that data is involved. The founder is responsible for having a lawful basis for the program and customer data they supply.
Refexa does not currently offer a separate data processing agreement.
4. Personal data we collect
4.1 Founder account data
- Email address and whether it has been verified. Refexa does not ask for a name at sign-up; your account's display name is set to the part of your email address before the "@".
- Password, if you choose password sign-in. Refexa stores only a one-way hash of it, not the password itself. You can instead sign in with a one-time email link.
- Workspace and program details you enter: business (workspace) name, program name, commission rule, default destination URL.
- Server API keys you create. Only a hash and a short lookup prefix are stored.
- Your acceptance of the Terms of Service: when you ticked the box, the Terms and Privacy Policy versions shown to you, and, during the private beta, when you entered a valid access code (not the code itself).
- Notes you write, such as payout references and notes, and reasons for a manual attribution change. Please do not put sensitive personal data in these fields (section 4.9).
4.2 Founder billing data (Refexa's own fees)
If you set up a payment method for Refexa's fees:
- billing email, and optionally a legal business name and postal billing address;
- a display summary of your card (brand, last four digits, expiry month and year);
- the time you agreed to off-session charging and the version of the text you agreed to.
Your full card number and security code are entered into Stripe's own payment form and go directly to Stripe; they are not sent to Refexa's servers. Refexa calculates its fee from affiliate-generated revenue recorded in your account.
4.3 Affiliate data
- Email address (affiliates sign in only with a one-time email link; there is no affiliate password) and a display name derived from it.
- Program membership: which founder programs you applied to or joined, and when you applied, were approved, rejected or had access removed.
- Your referral links, the clicks on them, the customers credited to you, and your commission and payout records as entered by the founder.
The founder whose program you join can see your name and email address, your application status, and your clicks, credited customers and commission in their program. Refexa does not collect affiliate bank, payment or tax details, and does not pay affiliates.
4.4 Referral click data
When someone opens a Refexa referral link (refexa.io/r/...), Refexa records:
- a random visitor token. Refexa stores it in its own
rfx_vidcookie on refexa.io only if you have allowed referral attribution in Refexa's cookie preferences (see the Cookie Notice); otherwise a new token is created for each click and no Refexa cookie is set; - the time of the click and whether it looked like an automated visit (bot label and reason);
- the browser's user-agent string (up to 512 characters);
- the referring website's host name only (not the full referring URL);
- the destination page path only (no query string).
Refexa does not store the visitor's IP address with a click. The visitor is then redirected to the founder's website with the visitor token and the affiliate's link code added to the address, so the founder's site can report the referral back to Refexa. Keeping that token on the founder's own website, so the referral can be credited when you later become a customer, is the founder's decision and is covered by the founder's own privacy and cookie notices.
4.5 Data about founders' customers
A founder's server can tell Refexa about a customer through Refexa's API. Refexa receives:
- the founder's own customer reference (an identifier the founder chooses);
- optionally the customer's email address, which Refexa converts into a keyed hash and does not store in readable form. It is used only to stop an affiliate being credited for referring themselves;
- the visitor token from the referral click, if any;
- the customer's Stripe customer identifier, if the founder supplies one, and whether it is a test or live customer.
When a founder connects Stripe, Refexa receives signed event notifications and reads objects from the founder's Stripe account with read-only permissions: connected account, customers, Checkout Sessions, PaymentIntents, charges and refunds, invoices and invoice payments, subscriptions, disputes and credit notes, and event records. Refexa stores the full content of each Stripe event it receives while the founder's account is active. Depending on how the founder uses Stripe, those events can include a customer's name, email address, billing address, and payment amounts and status. Refexa uses this to work out which payments came from referred customers and what commission they create.
Refexa does not identify customers from Checkout email addresses, metadata or other Stripe fields beyond the Stripe customer identifier.
4.6 Security and technical data
- Session records: when you sign in, Refexa stores your IP address (on our hosting platform, the address our provider reports for the connection) and your browser's user-agent string with the session.
- Rate-limit records: to limit repeated sign-in, sign-up, password-reset and verification requests, Refexa stores counters keyed by IP address and the requested sign-in path.
- Request handling: our hosting provider, Cloudflare, processes every request to refexa.io, including the IP address and request details, to deliver the site and protect it. Cloudflare keeps its own log data about requests on its network, including IP addresses, for a limited period that Cloudflare sets. Refexa has not turned on Cloudflare's features for storing its application's own log output (Workers Logs) or for exporting it (Logpush).
4.7 Analytics data (only with your consent)
Refexa uses Google Analytics 4 and PostHog (EU Cloud) to understand how the site and product are used, only after you accept analytics in the cookie banner. They receive:
- the page path with query strings, fragments and identifiers removed, a similarly cleaned page address and referring page;
- a small set of named product events, for example that a sign-up was completed or a Stripe test connection succeeded, with no further detail beyond a fixed choice such as the sign-up method;
- information each vendor collects from the connection and browser by default: browser, operating system, device type, screen size, language, an approximate location the vendor derives from your IP address, random (pseudonymous) identifiers and timestamps.
Refexa's integration is built not to send these vendors your email address, name, Refexa account or workspace identifiers, Stripe identifiers, referral or visitor tokens, money amounts, or text you type: page addresses are cleaned before sending and event details are restricted to a fixed list. Refexa does not identify you to either vendor and does not create PostHog person profiles. Before you accept, neither vendor's code is loaded.
Google states that Google Analytics does not log or store the IP addresses of users in the EU, Switzerland or the UK: it uses them only to derive an approximate location and then discards them. PostHog's EU Cloud is hosted in Frankfurt, Germany.
Where analytics is not enabled on Refexa, no analytics choice is offered and neither vendor receives anything.
4.8 Emails we send
Refexa sends only service emails: email verification, one-time sign-in links and password-reset links. Refexa sends no marketing email and adds no one to a mailing list. Our email provider, Loops, does not track whether these service emails are opened or which links in them are clicked.
4.9 What we do not collect
Refexa does not ask for or knowingly collect special-category data (such as health, religion or political opinions), government identification numbers, precise location, social media login data, or information about children under 18. Please do not intentionally enter sensitive personal data in free-text fields such as payout notes, program text or attribution reasons; Refexa does not support any such category in those fields, and the Terms of Service forbid founders from doing so (Terms of Service section 10.6).
5. Where the data comes from
- From you: when you sign up, sign in, set up a program, apply as an affiliate, or add a billing method.
- From founders: affiliate decisions and payout records, customer references and optional customer emails sent through the API, and program settings.
- From Stripe: data from the founder's connected Stripe account (section 4.5), and, for Refexa's own fees, the status of the founder's card setup and fee payments.
- Automatically: click records, session and rate-limit records, and (only with consent) analytics.
6. How we use personal data, and our legal bases
| Purpose | Data | Legal basis |
|---|---|---|
| Create and run founder accounts, provide the service, connect integrations such as Stripe, and bill Refexa's fees | Account data, session data, founder billing data, Stripe data | Performance of a contract (GDPR Art. 6(1)(b)) |
| Create and run affiliate accounts and sign-in, so affiliates can use the program they joined | Affiliate account data, session data | Performance of a contract (Art. 6(1)(b)) where one exists; otherwise Refexa's legitimate interests (Art. 6(1)(f)) in providing the service the affiliate signed up for |
| Security, fraud and abuse prevention, rate limiting, reliability of the service, and establishing, exercising or defending legal claims | IP address, user agent, rate-limit counters, session records, click records, and other relevant data | Legitimate interests (Art. 6(1)(f)) in keeping accounts and the service secure, reliable and free from abuse, and in protecting legal rights |
| Analytics | Analytics data (section 4.7) | Consent (Art. 6(1)(a)), given in the cookie banner or Cookie preferences and withdrawable at any time |
Refexa's own referral cookie rfx_vid on refexa.io | Visitor token | Consent (Art. 6(1)(a)), given by allowing referral attribution in Cookie preferences and withdrawable at any time |
| Keep the tax, accounting and other records the law requires | Fee, payment and billing records | Legal obligation (Art. 6(1)(c)), to the extent a law requires them |
| Respond to lawful requests from authorities | Any relevant data | Legal obligation (Art. 6(1)(c)) where a law requires the disclosure |
| Run a founder's affiliate program: record applications, links, clicks, attribution, commission and payouts, and prevent self-referral | Affiliate data, click data, customer data, Stripe data | Processed to provide the service to the founder. The founder is responsible for the lawful basis for the program and customer data they supply |
Automated decisions. Refexa automatically decides which affiliate a customer is credited to (one last-click attribution per customer under the founder's program) and calculates commission from the founder's rules. The founder sets the rules, can correct an attribution manually, and decides what to pay affiliates outside Refexa.
Refexa does not sell personal data, does not use it for advertising, and does not use it to train AI models.
Aggregated and de-identified information. Refexa may use aggregated or de-identified information derived from use of the service to operate, analyse and improve it, but only where that information cannot reasonably be linked back to an individual or to a founder's business. Data in which names or identifiers have only been replaced with other identifiers is pseudonymous, not de-identified, and Refexa treats it as personal data.
7. Who we share it with
- The founder whose program is involved. Founders see their affiliates' names, emails and results, and the customer and payment records in their own account.
- Affiliates see their own links, clicks and commission for programs they joined. Affiliate pages do not show customer references or other affiliates' data.
- Service providers that run Refexa for us (section 8).
- Stripe, as described in sections 4.2 and 4.5.
- Authorities or others where we must by law, or to establish or defend legal claims.
- A buyer or successor of the Refexa business, if it is ever transferred.
8. Service providers
| Provider | What it does for Refexa | Data involved | Location | Role |
|---|---|---|---|---|
| Supabase (PostgreSQL database), Supabase Pte. Ltd., Singapore | Stores all Refexa data | Everything in section 4 except analytics | AWS eu-west-1 (Ireland) for the production project | Service provider under Supabase's data processing terms |
| Cloudflare (Workers, Hyperdrive), Cloudflare, Inc., United States | Runs the application and its database connections | All requests, including IP address | Global network; no regional restriction is configured | Service provider under Cloudflare's data processing terms |
| Loops, Astrodon Corporation, United States | Sends sign-in, verification and reset emails | Recipient email address and the link in the email | United States | Service provider under Loops' data processing terms |
| Stripe, Stripe Payments Europe, Limited, Ireland | (a) reading founders' connected-account data; (b) Refexa's card setup and fee payments | (a) founders' customer and payment data; (b) founder billing data and card details entered in Stripe's form | Stripe's DPA provides for transfer to Stripe, LLC in the United States, and Stripe may process data globally | Stripe states that it also acts on its own behalf for purposes such as fraud prevention and legal compliance |
| Google (Google Analytics 4), Google Ireland Limited | Analytics, only after consent | Analytics data (section 4.7) | Google data centres worldwide, including the United States | Service provider under Google's data processing terms for Google Analytics |
| PostHog (EU Cloud) | Analytics, only after consent | Analytics data (section 4.7) | EU Cloud in Frankfurt, Germany (AWS eu-central-1), ingestion at eu.i.posthog.com | Service provider for analytics |
Refexa's application includes no error-tracking, advertising or session-replay service.
9. International transfers
Refexa's database is in the EU (Ireland). Some providers process data outside the European Economic Area: Cloudflare's network is global, and Stripe, Google and Loops are based in or may process data in the United States.
Where a provider processes personal data outside the EEA, we rely on the safeguards in that provider's data processing terms. You can ask us for details at igkougkousis01@gmail.com.
10. How long we keep data, and account deletion
As of the date of this policy, Refexa has no fixed retention schedule and no automatic deletion job. Data is kept while your account and the founder's program are active, and is deleted, anonymized or kept as described below.
Durations that are already fixed by the product:
- a signed-in session expires after 7 days without renewal (renewed at most once a day while you use Refexa). Expired session records are not automatically removed today;
- email sign-in links expire after 10 minutes; verification and password-reset links after 1 hour;
- the
rfx_vidreferral cookie, when you allow it, lasts 60 days, and the cookie-choice cookie 180 days (Cookie Notice).
Deleting a founder account. A founder can delete their account from Settings > Danger zone, or from the dedicated account deletion page if their program is no longer active. You confirm by typing DELETE and entering your password (or, if you sign in only by email link, by having signed in within the last 15 minutes). Deletion is carried out in one step as soon as you confirm, and cannot be undone. It is blocked only while a Refexa fee payment is being processed.
When you delete your account:
- Access ends. All your Refexa sessions are ended, your password and pending sign-in links are removed, every membership in the workspace is removed, your server API keys are revoked, your program page and referral links stop working, and Refexa's Stripe connection is disconnected and its Stripe access tokens erased. Refexa cannot uninstall its Stripe App from your Stripe account for you; you should uninstall it in Stripe. Stripe notifications that still arrive are kept only in reduced form and not processed.
- Deleted or replaced in that same step: session records (with IP address and user agent), your password, sign-in tokens, Stripe access tokens and connection attempts, your customers' references and email hashes (replaced or removed), the content of stored Stripe events (reduced to the event type and Stripe object identifiers), click user agents, referring hosts and landing paths, and your billing email, legal name, address and card summary. Your name and email address are replaced with a placeholder that does not contain them, unless you are also an affiliate or member of another business on Refexa, in which case your sign-in identity is kept for those relationships.
- Kept, because the records are needed for financial accuracy, accounting, disputes and the history other people (your affiliates) rely on: commission, payout, Refexa fee and payment history, attribution history and the commission rules that applied, Stripe object identifiers, click times and random visitor tokens, your business (workspace) name, notes you wrote on payouts and attribution changes, the time of your agreement to off-session charging, Refexa's own Stripe customer record for your fees, a random internal user identifier on those records, and a minimal record that the deletion happened (with no email or name). These kept records are not fully anonymous: they remain linked to your workspace and to Stripe identifiers.
- Not changed by deletion: data in your own Stripe account; Refexa's own Stripe customer and saved card for fee billing (Refexa can no longer charge it); analytics data already sent to Google or PostHog (Refexa did not link it to your account, so it cannot find it by account); and database backup copies made before deletion, which keep earlier data until they are discarded. Refexa's database provider keeps no automatic backups or point-in-time copies of Refexa's database on its current plan; backup copies are made manually. Local copies are kept on the operator's computer, which uses full-disk encryption. An additional copy may be stored in the operator's iCloud Drive only after it is encrypted on the computer; the encryption key is kept separately. No defined retention schedule for these copies currently exists.
You can sign up again later with the same email address; that creates a new, empty account.
Affiliates. There is no self-service deletion for affiliate accounts yet. Until there is, affiliates can ask for deletion by email to igkougkousis01@gmail.com, and we handle the request manually. We will tell you what we deleted or de-identified and what we kept and why. Commission, payout and attribution records that founders rely on for their own history are likely to be kept, and records that cannot be changed can be de-identified rather than deleted.
Founders' customers. Customer data is handled for the founder; please contact the founder first. We will pass requests we receive to the relevant founder.
11. Your rights
Depending on our role and the legal basis, you may have the right to:
- access the personal data we hold about you and receive a copy;
- correct inaccurate data;
- delete your data (founders can do this themselves, section 10);
- restrict or object to processing, including processing based on legitimate interests;
- data portability for data you gave us under a contract or consent;
- withdraw consent for analytics or for Refexa's referral cookie at any time through the "Cookie preferences" link, without affecting processing before withdrawal.
Refexa does not yet offer self-service data export or editing of your name or email address. Send every privacy request, including access, correction, export, objection and affiliate deletion, to igkougkousis01@gmail.com. Requests are handled manually.
Confirming who you are. If you have a Refexa account, please send your request from the email address on that account. If we cannot be reasonably sure that a request comes from the person the data is about, we may ask for additional information to confirm your identity. We ask only for the minimum reasonably necessary for that purpose, we do not ask for a government-issued ID by default, and we use what you send only to verify your request.
Where Refexa handles data for a founder (section 3), we will refer your request to that founder or help them respond.
You can complain to a data protection authority, in particular in the EU country where you live or work or where an infringement happened. In Greece this is the Hellenic Data Protection Authority (Αρχή Προστασίας Δεδομένων Προσωπικού Χαρακτήρα), Kifissias 1-3, 115 23 Athens, Greece; telephone +30 210 6475600; website www.dpa.gr; email for complaints complaints@dpa.gr.
12. Security
Refexa uses HTTPS everywhere with HSTS, verified encrypted connections to its database, a content security policy that limits which outside sites the pages can load code from, one-way hashing for passwords, sign-in links and API keys, encryption for stored Stripe access tokens, and checks in its data-access code that keep each founder's data separate from every other founder's. No system is perfectly secure, and Refexa does not claim any security certification.
13. Minimum age
Refexa is a service for businesses and the people who promote them. You must be at least 18 years old to create a Refexa account as a founder or an affiliate. Refexa does not check age at sign-up. If you believe someone under 18 has given us personal data, contact us at igkougkousis01@gmail.com.
14. Contact
Questions and requests about this policy or your personal data:
- Email: igkougkousis01@gmail.com
- Operator: IOANNIS GKOUGKOUSIS, Tholos, Serres, Greece
Refexa has not appointed a data protection officer. An EU representative is not needed because Refexa is established in the EU.
15. Changes to this policy
We will post any change on this page with a new effective date. For a material change to how we use personal data, we aim to tell founders and affiliates by email at least 30 days before it takes effect, where practical. Changes needed urgently for legal, regulatory or security reasons may take effect sooner.