This document explains what ONE//FM internet radio's websites store on a visitor's device, why, on what legal basis, and how to control it. It supplements the Privacy policy and takes precedence over it in everything that concerns access to the device. The list in section 4 covers everything the portal itself stores: it is generated directly from the portal's code, so it cannot drift from what actually happens. Records set by third-party services, including Google advertising, are described in section 5.
1. What this document covers
A cookie is a small record a site stores in the browser and receives back with every subsequent request. Alongside it, browsers offer two further stores: local storage, which lives until it is cleared, and tab storage, which disappears the moment the tab is closed. Technically these differ, but the law looks at the fact of access to the user’s device, not at the name of the technology. Throughout this document “cookie” therefore covers all three, and the list states which store each record belongs to.
2. Legal basis
Records without which the site cannot do what it was asked to do — the chosen language, the signed-in state, the safeguard against voting twice, the player's operation — are stored as necessary to provide the service and on the basis of our legitimate interest (Articles 6(1)(b) and 6(1)(f) of the General Data Protection Regulation, GDPR); Article 5(3) of Directive 2002/58/EC exempts strictly necessary records from consent. The site's own statistics store no identifier on the device: visitors are counted by the server. Only the cookies of Google advertising (section 5) require consent: where the law demands it, Google sets them only with your consent (Article 6(1)(a) GDPR). In Ukraine the Law of Ukraine "On the Protection of Personal Data" applies.
3. Who we ask for consent
Consent to Google advertising cookies is requested by Google's certified consent platform — from visitors in the European Economic Area, the United Kingdom and Switzerland, as the law of those countries requires. Until consent is given, personalised ads are not shown. Other visitors are not shown the request. You can change your choice at any time through the "Cookie settings" link at the foot of every page.
4. The full list
Below is everything the portal stores on the device. The “Choice” column shows whether a record can be switched off without depriving the site of the ability to work.
Cookies
Sent to the server with every request. These are first-party records: the portal sets them itself, not a third-party service.
| Record | Purpose | Lifetime | Choice |
|---|---|---|---|
NEXT_LOCALE | The language the reader chose. Without it every later visit would revert to the default language. | 1 year | necessary |
onefm-staff | A marker for editorial devices. It appears only on the devices of station staff when they sign in to the admin panel, so that their own page views are kept out of the statistics. Readers' browsers never have it. | 1 year | necessary |
Local storage
Kept in the browser until the reader clears it, and not sent to the server automatically — the portal reads it only when it needs to.
| Record | Purpose | Lifetime | Choice |
|---|---|---|---|
onefm-voter-id | Voting identifier. Prevents voting twice for the same track; an IP address is unfit for this because whole networks share one. | until the browser is cleared | necessary |
onefm-listener-auth | The reader’s profile and a session refresh token, so a sign-in survives a page reload. Created only after signing in. | until sign-out | necessary |
Tab storage
Lives exactly as long as the tab is open. Closing the tab removes these records without any action by the reader.
| Record | Purpose | Lifetime | Choice |
|---|---|---|---|
onefm_access_token | Short-lived API access token. Lives in the tab and does not survive its closing. | until the tab is closed | necessary |
onefm-listen-sid, onefm-listen-at | The identifier of the current listening session and the time of the player's last signal. Thanks to it, reloading the page mid-broadcast is not counted as a new switch-on. | until the tab is closed | necessary |
onefm:resume-playback | A marker that the player was playing before the reload, so the stream resumes by itself. | until the tab is closed | necessary |
onefm:stream-cors | Whether the stream permits the spectrum analyser. Stored so the question is not asked again each time. | until the tab is closed | necessary |
5. Third parties
Advertising on the site is served by our own ad server and by Google AdSense. Our server sets no cookies and builds no reader profile. Google AdSense is loaded from Google's servers and sets its own cookies — for example __gads, __gpi and IDE — to show and measure ads, to prevent fraud and, if you have agreed, to personalise ads; their make-up and lifetimes are determined by Google (policies.google.com/technologies/cookies). The Cloudflare delivery network through which the site runs may set its own technical records to protect against automated attacks. Embedded content — videos, social media posts — is loaded from the servers of the respective platforms and is subject to their rules; we have no access to what they store.
6. How to control it
The "Cookie settings" link at the foot of any page shows what is stored and lets you change your choice about Google advertising: visitors from the European Economic Area, the United Kingdom and Switzerland can reopen Google's consent request there, and anyone can switch off Google ad personalisation at myadcenter.google.com. Independently of this, your browser lets you delete or block any records; the site will still work, but it will forget your language and you will have to sign in every time.
7. What we do with it
None of the portal's records is used for advertising, profiling or passing to third parties. Our own statistics count visitors on the server, without cookies: they show what is read and listened to, not who is doing it. Records in tab storage never leave the device, except the listening identifier: the player sends it with its signal so that the server does not count one listening session twice.
8. Changes
The list in section 4 is updated together with the portal itself, because it is generated from its code. Material changes to the basis or the composition of the data will be announced separately, and the date of the last update is always shown at the top of the page. Questions about this document go to the station address given in the site footer.