Cookie policy.

This policy explains the cookies and browser-storage keys fintechpays.com uses, why, and how you control them. We keep this short because the list is short: two functional keys we always need, optional analytics that stay off until you choose to turn them on, and the affiliate-network cookies a partner sets only after you click through to its site. It complements our privacy policy.

Strictly necessary (no consent required)

These are set by fintechpays.com and are required for the site to function. Under EU GDPR and the EU ePrivacy Directive they fall within the "strictly necessary" exemption, so they need no consent. They are localStorage keys, not transmitted cookies — they never leave your browser and never reach our servers.

• fp-theme — records whether you chose the light or dark theme. First-party, persistent until you clear it.
• fp-consent — records your analytics choice (granted or denied) so the consent banner is not shown again on return visits. First-party, persistent until you clear it.

Analytics (consent required — off by default)

We use Google Analytics 4 with Google Consent Mode v2 to measure traffic and improve the site. Analytics storage defaults to denied: no analytics cookies are set, and GA4 sends only cookieless, consent-pending pings, until you press Accept on the consent banner. If you press Decline — or never choose — no analytics cookies are ever set.

When (and only when) you accept, GA4 sets these first-party cookies on the fintechpays.com domain:

• _ga — distinguishes unique visitors. Expires 2 years after it is set.
• _ga_<container-id> — persists the GA4 session state. Expires 2 years after it is set.

We enable IP anonymisation on GA4. The legal basis for analytics cookies is your consent under EU GDPR Article 6(1)(a); you can withdraw it at any time (see How to control cookies below). Google's handling of the data it receives is governed by the Google Privacy Policy.

Affiliate-network cookies (set on the partner's site)

FintechPays earns commissions when you click an affiliate link and complete an action on the partner's site (see our affiliate disclosure). We do not place these cookies — they are set by the affiliate network on its own domain at the moment you leave fintechpays.com and land on the partner, so the network can attribute the referral. The two networks our programs run on are:

• Impact — sets a click-attribution cookie (and a click identifier passed in the destination URL) so a later signup is credited to the referral. Window and lifetime vary by program; commonly 30 days. Governed by the Impact privacy policy.
• Awin — passes an awc click reference (the Awin Click string) and sets a corresponding attribution cookie on click-through. Window and lifetime vary by program; commonly 30 days. Governed by the Awin privacy policy.

These cookies live in the context of the partner's and network's domains, not fintechpays.com. They are read only if you continue to the partner after clicking. We receive only aggregate, attributed conversion counts — never personally identifiable information about you.

How to control cookies

• Change your analytics choice. Clear the fp-consent key in your browser's site-data settings for fintechpays.com; the consent banner reappears on your next visit so you can decide again.
• Block or delete cookies. Every major browser lets you block or delete cookies and clear local storage per site. Blocking the strictly-necessary keys may reset your theme preference and re-show the consent banner each visit.
• Opt out of GA4 globally. Install Google's opt-out browser add-on.
• Affiliate cookies. Manage these via the network's policy linked above, or by blocking third-party cookies in your browser; doing so does not change anything you see on fintechpays.com.

Changes to this policy

If we add, remove, or change a cookie — for example a new analytics or measurement tool — we will update this page with a new "last reviewed" date and a short note describing what changed.

Dates

• Policy prepared: 17 June 2026
• Last reviewed: 17 June 2026
• Next scheduled review: 17 June 2027, or sooner if our cookie use changes