Cookie Notice
Last updated: 3 July 2026 · This notice is provided for our closed alpha and is a working draft — it will be reviewed and finalised before general availability.
1. What are cookies?
Cookies are small text files that a website stores on your device (computer, tablet or phone) when you visit it. They are widely used to make websites work, to keep you signed in, and to remember your preferences. Similar technologies — such as local storage, session storageand device tokens — can be used for comparable purposes; where we refer to “cookies” in this notice we mean these technologies too.
Cookies can be first-party (set by rayberg.ai) or third-party (set by a service we rely on, such as our authentication or payment provider). They can also be session cookies (deleted when you close your browser) or persistent cookies (kept until they expire or you delete them).
2. How we use cookies
During our closed alpha we keep cookie use to the minimum required to run the service. We use cookies to:
- keep you securely signed in to your account between page loads and visits;
- protect your session and the service against fraud and abuse (e.g. CSRF and bot protection);
- carry you safely through the checkout and billing flow when you buy a plan or token pack;
- remember basic preferences you set in the interface, so the app behaves consistently.
We do not use cookies to build advertising profiles, to track you across other websites, or to sell your data. We do not currently run third-party advertising or cross-site tracking cookies.
3. Categories of cookies we use
We group cookies into the following categories, following common practice under the EU ePrivacy rules and the GDPR:
- Strictly necessary. Required for the website to function and for you to use core features such as signing in and paying. These cannot be switched off through our interface, because the service would not work without them. Examples: the Clerk authentication session cookie and the Stripe checkout session cookie.
- Functional / preferences. Remember choices you make (such as interface preferences) to give you a more personalised and consistent experience. These are optional; disabling them may reset your preferences on each visit.
- Analytics / performance. Help us understand how the alpha is used so we can find bugs and improve reliability. Where used, we prefer aggregated, privacy-respecting measurement. We do not run analytics cookies today; if we introduce them, we will update this notice and, where required, ask for your consent first.
- Advertising / targeting. Used to deliver or measure advertising and to build profiles across sites. We do not use advertising or targeting cookies.
4. Cookies we set
The table below lists the main cookies used on rayberg.ai. Exact names, providers and lifetimes can change as we develop the alpha; this is a representative, non-exhaustive overview.
| Name | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
__session | Clerk (authentication) | Keeps you signed in and maintains your authenticated session. | Strictly necessary | Session / up to ~7 days |
__client_uat | Clerk (authentication) | Tracks authentication state so the app knows whether you are signed in. | Strictly necessary | Persistent (~1 year) |
__csrf / anti-forgery token | Rayberg | Protects form and API requests against cross-site request forgery. | Strictly necessary | Session |
__stripe_mid / __stripe_sid | Stripe (payments) | Secures the checkout flow and helps detect and prevent payment fraud. | Strictly necessary | Session / up to ~1 year |
ray_prefs | Rayberg | Remembers non-essential interface preferences you set. | Functional | Persistent (up to ~1 year) |
5. Third-party cookies
Some cookies are set by the trusted providers we rely on to operate the service. These providers act as our processors and use the cookies for the purposes described above:
- Clerk — authentication and session management. See their privacy policy.
- Stripe — payment processing and fraud prevention during checkout. See their privacy policy and cookie policy.
- Vercel — hosting and content delivery, which may set strictly-necessary cookies for security and load balancing.
We do not control cookies set directly by these providers. Please refer to their own policies for full details, and see our Privacy Policy for how the underlying data is handled.
6. Managing and disabling cookies
You can control and delete cookies through your browser settings. Most browsers let you view the cookies stored, block all or third-party cookies, and delete existing cookies. You will usually find these options under the browser’s privacy or security settings — for example in Chrome, Firefox, Safari or Edge.
Please note that strictly necessary cookies cannot be disabled without breaking the service: if you block them, you will not be able to sign in or complete a purchase. Blocking functional cookies may reset your preferences on each visit.
7. Do Not Track
Some browsers offer a “Do Not Track” (DNT) signal. There is currently no common industry standard for how services should respond to DNT. Because we do not track you across other websites or serve targeted advertising, our behaviour does not change based on a DNT signal — we only ever set the strictly-necessary and functional cookies described here.
8. Changes to this notice
As Rayberg AI evolves through its alpha, we may update this Cookie Notice — for example if we introduce optional analytics or preference cookies. When we make material changes we will update the “Last updated” date above and, where the law requires it (such as before setting non-essential cookies), ask for your consent.
9. Contact
If you have any questions about our use of cookies or this notice, please contact us at hello@rayberg.ai. For more on how we handle personal data, see our Privacy Policy.