Privacy policy
Last updated: 22 September 2026
1. Who is responsible for your data
Halofloor is a project under development, published on a non-professional basis. The data controller is the publisher of the service, reachable at contact@halofloor.com. Under French law on confidence in the digital economy, a non-professional publisher may withhold their personal contact details from public display provided they have supplied them to their hosting provider, who keeps them available to the judicial authority. They will be published here when the service goes on sale.
The service does not meet the thresholds that would require appointing a data protection officer. Should that change, their identity will appear on this page.
2. What we process, and why
Halofloor is built to work on as little data as possible. In particular, the audio you listen to is never recorded or transmitted: only text metadata and aggregate measurements leave your device.
| Data | Why | Legal basis | Retention |
|---|---|---|---|
| Title, artist and duration of the track playing | Find the album artwork and the matching musical analysis | Performance of the contract | Cached as a fingerprint, with no link to you |
| Computed musical features (tempo, intensity, danceability) | Choose and drive the visual | Performance of the contract | Technical cache shared across all users |
| Email address and account identifiers | Create the account, manage the subscription, provide support | Performance of the contract | Life of the account, then 3 years |
| Billing data | Issue invoices and meet our accounting obligations | Legal obligation | 10 years |
| Server logs: IP address, timestamp, browser | Security, abuse prevention, fault diagnosis | Legitimate interest | 12 months at most |
| Account: email address, first and last name (given by you or by Google/Apple), language, plan; your console settings, favourite radios and listen counts | Recognising you, and finding your settings again from one device to the next | Performance of the contract | As long as the account exists; deleted with it |
What we do not do
- No recording, storage or transmission of your audio.
- No sale or rental of data to third parties.
- No targeted advertising, no advertising profiling.
- No automated decision producing legal effects concerning you.
- Your music platform credentials do not pass through our servers: you sign in with the provider, and we never receive your password.
3. Recipients and processors
We rely on a small number of providers, each for a specific purpose:
- Hosting and computing — providers located in the European Union. Their identity is available on request at the contact address.
- Payment — a licensed payment provider, which handles card data itself; we neither see nor store it. No payment is taken while the service is not on sale.
- Accounts — Supabase, which hosts authentication (Google, Apple or email link) and the database holding your profile and settings. Its servers are in the United States: the transfer relies on the standard contractual clauses (see below). The anti-robot check on the sign-in form is provided by Cloudflare Turnstile, without cookies or identifiers.
- Music catalogues — the platforms you choose to connect, queried to find artwork and information about the track.
- Audience measurement — Umami Cloud, which counts visits without cookies or any identifier that would let us recognise you across sites.
Some of these providers may process data outside the European Union. Such transfers then rely on the European Commission's standard contractual clauses or on an adequacy decision.
4. Cookies and audience measurement
The site uses no analytics or advertising cookies, and therefore displays no consent banner.
Traffic is measured with Umami, a tool that works without cookies and without any persistent identifier. It records the page viewed, the page you came from, the device type and the country, along with a few aggregate actions: a click on a plan, a preview played. This data cannot identify you, is not combined with other sites, and is neither sold nor shared.
During the beta we also measure how the product is used, to understand what matters and decide what to build: sessions (duration, page, country, browser type), features used, audio sources, tracks played and visuals shown. This data is kept in our database (Supabase, United States) under a random identifier specific to your browser and, when you are signed in, linked to your account. We record neither your IP address nor the content of your searches. You can ask for its deletion together with your account at contact@halofloor.com.
The following are also used:
- a session cookie, strictly necessary to keep you signed in;
- three cookies for the console, set only once you use it: the stations you have starred, how many times you have listened to each one (so that the ones you actually play come first), and your display settings for the broadcast screen. Without an account, all three stay on this device, are never sent anywhere else, and are deleted with your browser cookies. With an account, these three settings are also stored in your account (at Supabase, see section 3) so they follow you from one device to the next; they are erased with the account;
- the browser's local storage, to remember your display preferences. It never leaves your device and nobody but you can read it.
5. The Halofloor Chrome extension
The Halofloor extension for Chrome does one thing: tell the console what your browser — or your Sonos speakers — is playing, so the visuals can follow the music.
What it reads. On Spotify, Deezer, SoundCloud and Apple Music pages only: the title, artist, artwork, position in the track and play state, as the page already displays them. It does not read your credentials, your passwords, your playlists or your listening history, and it intercepts no request to those services. It is inactive on every other site.
Where it goes. Only to halofloor.com pages open on your machine, through a message internal to the browser. Nothing is sent to our servers or to a third party, and nothing is kept: the current track disappears with the tab.
Sonos. If, and only if, you ask to follow Sonos speakers, the extension asks your permission to reach port 1400 on your local network, the one speakers answer on. It then queries them directly, from your machine. The chosen speaker is remembered on your device. This permission is optional: without it everything else works, and it can be withdrawn at any time from Chrome's extensions page.
What it does not do. No analytics, no advertising, no identifier, no profiling, no resale. Uninstalling it erases everything it held.
6. Your rights
European regulation gives you the right to access your data, have it corrected, have it erased, restrict its processing, object to processing based on our legitimate interest, and receive the data you provided in a reusable format.
To exercise these rights, write to contact@halofloor.com. We reply within one month. If our answer does not satisfy you, you may lodge a complaint with the French data protection authority (CNIL), 3 place de Fontenoy, 75007 Paris, or with the supervisory authority of your country of residence.
7. Security
Traffic between your browser and our servers is encrypted. Access to account data is restricted to those who need it. In the event of a breach presenting a risk to your rights, we notify the supervisory authority within 72 hours and inform you directly where the risk is high.
8. Minors
The service is not intended for people under 15 and we do not knowingly collect their data. If you find otherwise, tell us: we will delete the account concerned.
9. Changes
This policy may change. The update date appears at the top of the page, and any substantial change will be notified to you before it takes effect.