Slowburn – Cookies and Local Storage Notice
Operator: PowerQuant ApS, trading as ONEWORD Entertainment, Denmark. Contact: hello@onewordentertainment.com.
1. What we store on your device
1.1 Slowburn uses no advertising cookies, no third-party tracking cookies and no social-media pixels.
1.2 Without asking, we store only strictly necessary items in your browser's local storage:
| Item | Purpose | Lifetime |
|---|---|---|
| Session token | Keeps you signed in after you click your magic link | Until sign-out or expiry (1 hour, refreshed automatically while you use the app) |
| Banner dismissed | Remembers that you closed the age notice or a beta message | 12 months |
Your answer about visit counting (ow_consent) | Remembers whether you said yes or no to visit counting, so we do not ask on every visit. It contains the word “yes” or “no” and the date of your answer. It is stored only once you have answered. | 12 months from your answer; then it is deleted and we ask again |
1.3 These items are needed for the service to work, or to remember a choice you made, and do not need consent under the Danish Cookie Order (Cookiebekendtgørelsen).
1.4 The random ID, only if you say yes. Page views are counted either way; what needs your yes is the ID that tells a returning reader from a new one. We ask on every page that counts visits. If you say yes, we store two more items in your browser's local storage:
| Item | What it contains | Lifetime |
|---|---|---|
ow_vid | A random 20-character ID, made in your browser at the moment you say yes. It is not derived from you, your device or your browser. | 12 months from your answer, or until you withdraw. After 12 months it is deleted the next time you open our front page or another page that counts visits, and we ask again on the front page. |
ow_ref | The channel label from the link that brought you here: the ref or utm_source value in the page address, for example “newsletter”. Stored only if your link had one, and replaced if you later arrive with a different one. It is never the address of the site you came from. | Same as ow_vid. |
1.5 What we use them for: only to count visitors per channel. The ID is sent to our own database inside the page-view counts for this website, so that one person who opens five pages counts as one visitor. It is not sent with the sign-up form, it is not passed on to the app, and we do not connect it to an email address or an account. The channel label is added to the links from this website into the app, so that a reader who comes back later is still counted under the channel that sent them; if you then ask for a sign-in link in the app, the label is sent to our database together with your email address.
1.6 First party only. Both items are written and read only by our own scripts on this website; the code is in track.js. They are not cookies, they are not shared with anyone else, and we do not fingerprint your browser. The counts are kept in our own database, hosted in the EU by our processor Supabase.
1.7 If you say no, or do not answer, we store neither item. If you say no, we also stop counting your page views from that point on, and only your answer is kept (ow_consent, see 1.2). If you do not answer, our scripts on this website store nothing in your browser, a channel label travels only in the page address while you click around, and page views are counted without any ID.
2. Analytics
2.1 We count page visits, signups and feature use with events stored in our own database. In the app, these events are tied to your account ID. On this website they are not tied to an account: a page-view count holds the page, the version of the page you saw, your browser's language and user-agent string, the channel label or referring address of that visit and, only if you said yes under 1.4, the random ID. A sign-up on this website also holds the email address you enter, and never the random ID. Nothing goes to Google Analytics or any external analytics service. See the Privacy Policy for details.
3. Third parties
3.1 Our hosting provider may set technical cookies for secure delivery, such as bot protection. These are strictly necessary and not used for tracking.
4. Your choices
4.1 You can clear local storage in your browser settings at any time. Clearing it for the app signs you out; clearing it for this website removes your visit-counting answer, ID and channel label. Blocking local storage entirely prevents sign-in.
4.2 Visit counting: your current answer in this browser is shown below, and you can change it here at any time. Withdrawing deletes ow_vid and ow_ref from this browser at once. Page-view counts already recorded keep the old random ID until they are deleted under the retention period in the Privacy Policy; if you want them deleted sooner, email us the ID shown below before you withdraw.
Turn on JavaScript to see and change your answer here. Without it, clear local storage in your browser settings.
5. Changes
5.1 We ask for your consent before we store anything that is not strictly necessary, as we do for the random ID used in visit counting, and we update this notice whenever that changes.