Cookie Policy

This Cookie Policy explains how Finray Technologies Ltd ("Finray", "we", "us", "our") uses cookies and similar tracking technologies on the website at https://finray.tech/. It should be read together with our Privacy Policy.

1. What cookies are

Cookies are small text files placed on your browser or device when you visit a website. They are used to remember preferences, recognise returning visitors, and collect usage analytics. Similar technologies include local storage, session storage, pixel tags, and SDK identifiers.

2. Cookies on this website

The Finray marketing website at finray.tech is designed to operate without setting cookies for tracking, profiling, or advertising purposes. Page navigation, layout, and content delivery are served entirely from static files; no marketing or analytics cookie is written to your browser by us when you load the homepage.

Where we operate authenticated surfaces — including the content management interface at /admin/ — a small number of strictly necessary cookies may be set by our authentication provider for the duration of an editorial session. These cookies are essential for operation and do not require consent under EU ePrivacy rules.

On first visit to the marketing website, we ask you to accept or reject the loading of optional cookies. Your decision is stored in your browser's local storage under finray-cookie-consent and applies on subsequent visits. Our current web-analytics providers (Plausible Analytics and Cloudflare Web Analytics — see §4) are cookieless and do not require consent; the cookie-consent preference toggle is therefore retained as a forward-looking control for any future technology that may require consent. You can change your decision at any time by clearing the finray-cookie-consent entry in your browser's local storage.

3. Third-party content

The website may embed assets served from third parties (including typography, certification badges, and partner logos). Where third-party domains are reached, those providers may set their own cookies in accordance with their own policies. We do not control those cookies. Examples of providers we link to or load assets from include:

• typography providers (Fontshare, Google Fonts) for display fonts;
• NQA, our ISO 27001 certification body, for the certification badge link;
• partner integration sites (e.g. TRM Labs) when you click through to them.

4. Web analytics

We use two cookieless web-analytics services running side-by-side. Both are privacy-first by design: neither sets cookies, stores cross-site identifiers, retains raw IP addresses, profiles individuals, or shares data with advertising networks.

4.1 Plausible Analytics

Plausible Analytics measures aggregate, non-identifying usage of the marketing website (page views, referrer, device class, country at aggregated precision). Plausible is EU-hosted and:

• does not set any cookies in your browser;
• does not store cross-site or persistent identifiers;
• does not retain IP addresses (IP is processed transiently with a daily-rotating salt to count unique visits, then discarded);
• does not profile individuals or build behavioural advertising audiences;
• does not share data with advertising networks or social-media platforms.

In addition to page-view counts, Plausible records a small set of named custom events that help us understand which surfaces are useful without identifying any individual. The complete list:

• briefing_open — the “Book a briefing” modal was opened. No properties.
• briefing_submit — a briefing request was submitted successfully. No properties.
• iso_certificate_open — the ISO/IEC 27001:2022 certificate modal was opened. No properties.
• mailto_click — an mailto: link was clicked. The destination email address is recorded as a property so we can distinguish, for example, partnership@ from info@ volume; no other data is captured.
• trm_outbound_click — an outbound link to trmlabs.com was clicked (TRM Labs is our blockchain intelligence partner; this measures partnership-page interest). No properties.

None of these events records the visitor's identity, IP address, or any cross-site identifier — the Plausible event API is the same cookieless transport described above; events are aggregated at the site level only.

Full technical detail: Plausible's data policy.

4.2 Cloudflare Web Analytics

Cloudflare Web Analytics measures Real User Monitoring (RUM) signals — primarily Core Web Vitals (Largest Contentful Paint, First Input Delay, Cumulative Layout Shift) — which Plausible does not capture. Cloudflare's beacon is also cookieless and:

• does not set any cookies in your browser;
• does not use any client-side persistent state or fingerprinting;
• does not retain or transmit personally identifiable information;
• aggregates measurement data at the page level only.

Full technical detail: see Cloudflare's privacy policy and the dedicated Web Analytics product documentation.

4.3 Legal basis and your choices

Because neither service stores or accesses any information on your device, no cookie-banner consent is required under EU ePrivacy rules, and we rely on legitimate interest under GDPR Article 6(1)(f) for both services. To opt out of measurement entirely, the most reliable methods are (a) enabling your browser's "Do Not Track" setting (Plausible respects DNT and excludes such visits from its aggregate counts), or (b) installing a content-blocker extension that blocks requests to plausible.io and cloudflareinsights.com.

We will not deploy any third-party advertising or cross-site-tracking technology on this website without first updating this policy and obtaining consent where consent is required.

5. Managing cookies in your browser

Modern browsers let you accept, reject, or selectively manage cookies on a per-site basis. Refer to your browser's documentation for the specific controls. Blocking strictly-necessary cookies on authenticated surfaces will prevent those surfaces from operating correctly.

6. Contact

Questions about this Cookie Policy may be directed to legal@finray.tech.