Cookie Policy
Last updated: 2026-10-26. The description below reflects how cookies and similar technologies are actually used in Beat Breeze.
1. What cookies are
Cookies are small text files stored by your browser when you visit a site. We also use related technologies such as local storage, session storage, and HTTP request headers to remember you and your preferences.
2. What we use
Beat Breeze uses the following categories:
- Strictly necessary. Authentication, PKCE, selected- organisation, and session cookies used by Beat Breeze and its identity provider. This includes Beat Breeze session and selected-organisation cookies plus Logto's hosted authentication transaction/session cookies. Without these, you cannot stay signed in, switch organisations, or use the platform. A provider cutover requires a clean sign-in; an old provider session is never reused as a Logto session.
- Functional. Preferences such as sidebar-collapsed state, audio-player position, and locale, stored in your browser's local storage. Used only to keep the interface consistent across sessions.
- Analytics. Only if you accept optional cookies, we keep one first-party note in your browser's local storage of how you first reached our site: the campaign tags in the link you followed (such as utm_source), the type of ad you clicked (for example a Google or Meta ad, never the ad's click identifier), the referring website, and the page you landed on. It expires after 90 days. If you create an account in that time, it is saved with the account so we can see which campaigns bring customers, and removed from your browser. We count page visits with Cloudflare Web Analytics, which sets no cookies and does not identify you. We do not run advertising or cross-site tracking cookies.
Payments happen on Stripe-hosted pages, which set their own strictly-necessary cookies.
3. Managing cookies
When you first visit our marketing site we ask whether to allow optional cookies; only essential cookies run until you accept. You can change your choice by clearing site data.
We use only the cookies required by the active identity flow. We do not use authentication cookies for advertising, cross-site tracking, or analytics.
You can clear or block cookies in your browser settings at any time. Blocking strictly-necessary cookies will sign you out and prevent the service from functioning correctly. Blocking functional or analytics cookies will not affect core functionality.
4. Changes
If our cookie usage changes — for example, if we add a new analytics provider — we will update this policy and surface the change in-app where required by law.
5. Contact
Privacy and cookie inquiries: [email protected], or use our privacy-requests form.
See also the Privacy Policy and the Terms of Service.