Cookie Policy
This Cookie Policy explains the cookies and similar technologies used by the RayRF website at rayrf.com. It is part of our broader Privacy Policy; please read both together.
1. What cookies are
Cookies are small text files that a website saves on your device when you visit. They let the site remember things between page loads (for example, that you are signed in) and let us measure anonymous traffic patterns. Some cookies are set by us (first-party); some are set by the services we use, such as Vercel (third-party).
2. Categories of cookies we use
2.1 Strictly necessary
These cookies are required for the site to function. Without them, you cannot sign in or complete checkout. They cannot be disabled through the cookie banner.
| Name | Purpose | Expiry | Source |
|---|---|---|---|
sb-* | Supabase authentication session and refresh tokens. Keeps you signed in across page loads. | Session and up to 1 year | First-party (Supabase) |
pending_checkout_session | Lets us resume a Stripe Checkout return flow if you are bounced to the sign-in page mid-checkout. | Up to 30 minutes | First-party |
| CSRF tokens (when applicable) | Protect form submissions from cross-site request forgery. | Session | First-party |
rayrf_consent | Records your cookie-banner choice so we do not re-prompt you every page load. Versioned, so a policy update re-prompts. | 6 months | First-party |
2.2 Functional
Functional cookies remember preferences that improve your experience but are not strictly required to use the site.
| Name | Purpose | Expiry | Source |
|---|---|---|---|
preferredSignInView | Remembers whether you last signed in with email, password, or Google so we can take you back to that view. | 1 year | First-party |
2.3 Analytics, first-party
First-party analytics cookies identify your browser and the current visit so we can measure traffic, dwell time, scroll depth, and Web Vitals without sharing anything with a third-party tracker. No personally identifying information is stored in these cookies; the values are random uuids generated on first visit.
| Name | Purpose | Expiry | Source |
|---|---|---|---|
rayrf_vid | Visitor uuid v4. Set on first visit, used to identify a browser across visits for traffic measurement and A/B assignment. Not linked to your account unless you sign in. | 1 year | First-party |
rayrf_sid | Session uuid v4. Set on first visit and refreshed on each page load with a sliding 30-minute idle window. Used to group page views into sessions. | 30 minutes (sliding) | First-party |
These cookies are set and read only when you have accepted the Analytics, first-party tier in the banner. Rejecting that tier deletes nothing on its own (existing cookies expire on their own schedule), but no further analytics requests are sent from your browser.
2.4 Analytics, behavioral
Behavioral analytics records per-section engagement on each page you visit. For each named section of the page, we record how long it was visible, how long the pointer hovered over it, and how many times it was clicked. This tier also loads Microsoft Clarity, a session-replay and heatmap tool that records clicks, scrolls, and a DOM-level reconstruction of the page so we can see where the UI is confusing. Clarity masks form inputs by default. We do not record raw pointer coordinates, the text you click, the contents of input fields, or screenshots from our own first-party telemetry. This tier is off by default in every region and only collects data when you explicitly opt in via the banner.
2.5 Analytics and advertising, third-party
This tier covers two services. Vercel Analytics and Vercel Speed Insights collect anonymous, aggregated traffic and performance data without personal identifiers. Google Ads measures conversions on advertising we run on Google, so we can tell which ads led to a sign-up or paid subscription. Google Ads runs under Consent Mode v2: when you reject this tier, the script still loads but is configured to set no cookies and send no identified events; Google receives only aggregate modeled signals.
| Name | Purpose | Expiry | Source |
|---|---|---|---|
| Vercel Analytics | Anonymous page-view and basic-traffic measurement. No personally identifiable information is collected. | Session and up to 24 hours | Third-party (Vercel) |
| Vercel Speed Insights | Anonymous page-performance measurement (load times, layout shift, etc.). | Session | Third-party (Vercel) |
Google Ads (_gcl_au, _gcl_aw, NID, IDE) | Measures the effectiveness of ads we run on Google. Records that a click on a Google ad led to a sign-up or paid subscription. Hashed email address is sent for Enhanced Conversions so Google can match without a tracking identifier. | Up to 90 days | Third-party (Google) |
rayrf_gclid | Google click id captured from the ad URL on landing. Used to attribute a later sign-up or paid subscription back to the original ad click, including when the conversion happens days or weeks after the click. | 90 days | First-party |
Third-party scripts are not loaded with full functionality until you accept this tier in the cookie banner. If you reject it, Vercel Analytics and Speed Insights requests are not sent at all, and Google Ads runs in a no-cookie, no-identifier mode that contributes only to aggregate measurement.
3. Managing your choices
On your first visit you will see a cookie banner with three options: Accept, Essentials only, and Customize (which lets you toggle Functional, Analytics first-party, Analytics behavioral, and Analytics and advertising third-party individually). Strictly necessary cookies are always on, as the site cannot operate without them. In the EU, UK, and EEA, all optional tiers default off until you opt in.
You can change your choice at any time by clicking Cookie preferences in the site footer; this re-opens the banner. You can also clear cookies and site data in your browser settings, which will cause the banner to appear again on your next visit.
Most browsers also let you control cookies directly through browser settings. For instructions, see your browser's help documentation, for example:
4. Changes to this Policy
If we change this Cookie Policy materially, we will update the "Last updated" date at the top of this page and, where appropriate, re-prompt for your consent through the cookie banner.
5. Contact
For questions about cookies or this Policy, contact support@rayrf.com.