Scope note. This policy covers cookies and similar technologies on raysly.com, including the Raysly partner portal (/portal) and sign-up (/signup), the surfaces Raysly itself operates. It does not cover cookies on a partner's storefront (<partner>.raysly.com, a partner's custom domain, or <partner>.comparisun.net) — those are set under the partner's own cookie policy, described in §5 below.
Key points
- We use cookies for things that make Raysly work (staying logged in, remembering your language), and, only with your consent, for analytics.
- raysly.com and the partner portal now show a cookie banner, matching the one on Comparisun, with rejecting exactly as easy as accepting.
- Storefronts we host for partners have their own consent banner and their own cookie policy, because the partner — not Raysly — is the controller for that data.
1. Who operates this site
[COMPANY_NAME], [COMPANY_ADDRESS]. Contact: [COMPANY_PRIVACY_EMAIL].
2. How consent works here
A consent banner appears on your first visit to raysly.com or the portal. Non-essential cookies (analytics, marketing) load only after you accept them; you can change your choice at any time using the "Cookie settings" link in the footer; rejecting is exactly as easy as accepting. This is the same mechanism used on Comparisun.
3. What are cookies and similar technologies
Cookies are small text files placed on your device. We and our providers also use local storage, session storage and similar technologies for some of the same purposes. Some of these operate even without setting a cookie.
4. Cookie and technology table
| Name | Purpose | Type | Duration | Set by |
|---|---|---|---|---|
backoffice_session |
Keeps you signed in to the partner portal | Strictly necessary | 30 days | Raysly (first-party) |
backoffice_user_type, backoffice_user_role |
Remembers your account type/role for the portal UI | Strictly necessary | 30 days | Raysly (first-party) |
bf_pk_hint |
Remembers that your device has a passkey set up, to speed up sign-in | Strictly necessary | 90 days | Raysly (first-party) |
raysly_partner_name, raysly_partner_company, raysly_partner_avatar |
Shows a personalised "welcome back" greeting on raysly.com | Functional | 30 days | Raysly (first-party) |
portal_active_business |
Remembers which business you're viewing, if you manage more than one | Strictly necessary | 30 days | Raysly (first-party) |
NEXT_LOCALE, login_locale |
Remembers your language choice | Functional | 1 year | Raysly (first-party) |
raysly_region |
Remembers your selected region | Functional | 1 year | Raysly (first-party) |
rl_marketplace_status_ack |
Remembers you dismissed a status banner | Functional | 90 days | Raysly (first-party) |
cookie_consent, cookie_preferences |
Records your cookie choices | Strictly necessary | 1 year | Raysly (first-party) |
ph_session (PostHog) |
Links your activity across a browsing session for product analytics | Analytics | Session/persistent (vendor-set; exact duration to be confirmed) | PostHog (EU region) |
Google Analytics cookies (_ga, _ga_*) |
Measures site usage | Analytics | Up to 2 years (typical GA4 default; to be confirmed) | |
| Sentry error monitoring | Detects and diagnoses errors | Analytics (consent required) — we do not consider general error monitoring "strictly necessary" for the service you asked for | Session-based | Sentry |
| Sentry session replay | Records a sample of sessions (1%, or 50% where an error occurs) with all text and input fields masked | Analytics (consent required) | Session-based | Sentry |
| Vercel Web Analytics / Speed Insights | Measures page performance | Analytics | N/A (cookieless where configured) | Vercel |
| Google Maps | Loads the address-entry map | Strictly necessary (needed for the form you're using) | N/A | |
| Cloudflare Turnstile | Anti-bot check on our forms | Strictly necessary | Session | Cloudflare |
5. Storefronts we host for partners
If you are visiting a page under a partner's own subdomain (for example <partner-name>.raysly.com) or a partner's custom domain, that page is the partner's own storefront. The partner is the controller for cookies and other technologies it chooses to use there, and Raysly acts as the partner's processor/technical host for them. For storefront analytics that Raysly runs on the partner's behalf, the partner is controller and Raysly is processor (see the Data Processing Agreement, Section 1). Raysly's own platform-level analytics and error monitoring on storefronts (described below) are Raysly's own controller activity, consent-gated on the storefront's own banner.
That storefront:
- shows its own consent banner (in every region where consent is required) with Necessary, Functional, Analytics and Marketing categories, each of which you can accept or reject individually;
- links to the partner's own cookie policy, generated from the specific analytics tags the partner has enabled;
- may load the partner's own choice of analytics or marketing tags (for example Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, Microsoft Clarity, Plausible or LinkedIn Insight), each disclosed in that policy.
If you have a question about cookies on a specific storefront, please contact that business directly using the contact details on their site. Raysly's own Google Analytics tag does not run on storefront pages. Platform-level PostHog analytics, Sentry error monitoring and replay, and Vercel performance analytics may run on storefront pages, gated on that storefront's own consent banner; see the note below.
6. Your choices
Once the consent banner described in §2 is live, you will be able to change your cookie choices at any time using the "Cookie settings" link in the footer of raysly.com. You can also control cookies through your browser settings, though blocking strictly necessary cookies may stop parts of the site working.
If you are in Switzerland
Under the Swiss Telecommunications Act (Art. 45c FMG) and the Federal Act on Data Protection, we tell you what device-processing occurs, its purpose, and give you the means to refuse it, as described above.
If you are in the UK
Non-essential cookies are subject to the Privacy and Electronic Communications Regulations (PECR), as amended.
7. Contact us
[COMPANY_NAME], [COMPANY_ADDRESS]. Privacy: [COMPANY_PRIVACY_EMAIL].