Cookie & Storage Policy
Last updated: 8 October 2026
This policy lists every cookie and every item of browser storage that livelinks itself uses, explains the outside services your browser connects to when you use livelinks, and tells you how to clear it all. It should be read with our Privacy Policy.
1. What cookies and storage are
A cookie is a small text file a website asks your browser to keep and send back on later visits. Local storage and session storage are similar places in your browser where a site can keep small pieces of information; local storage lasts until it is cleared, and session storage is cleared when you close the tab. A service worker is a small script a site can install in your browser, for example to show notifications. The law treats all of these the same way, so this policy covers all of them.
2. Our approach and the law
Under the Privacy and Electronic Communications Regulations 2003 (PECR), a website must ask for your consent before storing information on your device, or reading it, unless that storage is strictly necessary to provide a service you have asked for (regulation 6(4)).
What livelinks itself stores on your device is used to provide what you have asked for: signing in, finishing sign-up, keeping sign-in secure, and remembering your choices about live notifications. The only other item, llShared, is set only when a signed-in page owner presses the Copy button in the editor, contains no information about you and is never sent to us. We do not use advertising cookies, analytics cookies, tracking pixels or any third-party tracking scripts. That is why we do not show a cookie banner for our own storage.
The only things that can set non-essential cookies are embedded players a page owner adds, and those only load after you agree (see section 5).
The one exception is media that a page owner chooses to embed, which is run by other companies. See section 5.
3. Everything we store on your device
This is a complete list of the cookies and storage items set by livelinks. Most people will only ever have one or two of them.
| Name | Type | Purpose | How long it lasts |
|---|---|---|---|
sb-dwkjbddkfkrikiksvxrs-auth-token | Local storage (set by our authentication provider, Supabase) | Keeps you signed in to your account. It holds your sign-in tokens and basic account details (such as your user ID and email address). Only set if you log in. | Until you log out or delete your account. The access token inside it renews itself about every hour while you are signed in. |
sb-dwkjbddkfkrikiksvxrs-auth-token-code-verifier | Local storage (Supabase) | A one-time security code that may be used while you sign in with Google, Discord or Twitch, to make sure the sign-in finishes in the same browser that started it. | Removed once sign-in completes |
ll_tt_nonce | Cookie (secure, HTTP-only, set by our TikTok sign-in function on our Supabase address) | A random one-time value that stops anyone finishing a TikTok sign-in that was started in someone else's browser. Only set if you sign in with TikTok. | 10 minutes at most; deleted as soon as sign-in finishes or fails |
pendingUsername | Local storage | Remembers the link name you picked on the sign-up page while you go off to sign in with TikTok, Google, Discord or Twitch, so it can be filled in for you when you come back. | Deleted when you reach the "Claim your link" screen |
codeStatus | Session storage | Notes that an access code entered while claiming your link did not work. | Cleared when you close the tab |
llShared | Local storage | Records that you used the Copy button for your page link in the editor. It contains only the value "1" and is never sent to us. | Until you clear your browser storage |
llEmbeds | Local storage | Remembers your answer to the cookie banner about embedded players ("yes" or "no"), so we don't ask again on every page. Storing your choice is itself strictly necessary. | Until you change it below or clear your browser storage |
notify:<page ID> | Local storage | Remembers that you turned on live notifications for that page, so the bell shows as on and tapping it turns them off. Only set if you turn notifications on. | Until you turn notifications off for that page or clear your browser storage |
notifyDismissed:<page ID> | Local storage | Remembers that you closed the "Get notified" popup on that page, so we do not keep asking you. | Until you clear your browser storage |
Service worker (/sw.js) and push subscription | Service worker and browser push subscription | Lets your browser receive and show "is LIVE" notifications and open the streamer's page when you tap one. Only installed if you tap the bell, and the push subscription is only created if you then allow notifications. | Until you block notifications for livelinks or clear site data in your browser |
The page ID in the notification items is the internal ID of the streamer's page, not anything about you. The "I'm 18 or older" button on pages with an 18+ warning does not store anything.
4. Outside services your browser connects to
To show livelinks pages, your browser fetches some files directly from other companies. Our use of these services does not involve them setting cookies, but as with any connection on the internet, each provider sees your IP address and basic browser details, and handles them under its own privacy policy.
- Google Fonts (
fonts.googleapis.comandfonts.gstatic.com): the fonts on our site and on pages. A page owner can choose from 66 extra fonts, each loaded only when a page or the editor needs it. - jsDelivr (
cdn.jsdelivr.net): the code library our pages use to talk to our database. - unpkg (
unpkg.com): the icon set used on the home page and in the editor. - Supabase (
dwkjbddkfkrikiksvxrs.supabase.co): our database, sign-in, image storage and server functions. - Netlify: hosts the website itself.
- Sign-in providers (Google, Discord, Twitch and TikTok): only if you choose to sign in with one. You are taken to their site, which uses its own cookies under its own policy.
- Browser push services: if you turn on live notifications, your browser's maker (for example Google, Mozilla, Apple or Microsoft) delivers them through its own push service.
- TikTok's image servers: when you sign in with TikTok, our server (not your browser) downloads a copy of your TikTok profile picture.
- Links on pages: when you tap a link, you go to another website, which may use its own cookies. We do not control those sites.
5. Embedded videos and music
A page owner can add a YouTube video, a TikTok video or a Spotify player to their page. These players are run by those companies and can set their own cookies or use similar storage, including for analytics or advertising, and they receive your IP address, under their own cookie and privacy policies, which we do not control:
- YouTube players use YouTube's privacy-enhanced mode (
youtube-nocookie.com); - TikTok players load from
tiktok.com; and - Spotify players load from
open.spotify.com.
Players do not load until you agree. On a page with an embedded player, we show a short banner asking whether to allow players. Until you choose "Allow players", each player is replaced by a placeholder and nothing is loaded from the provider. You can also load a single player by tapping its "Load" button, which counts as agreeing for that player only. If you choose "Essential only", players stay off and we remember that choice in this browser.
You can change your choice at any time:
6. How to clear or block storage
You can delete everything livelinks has stored at any time:
- Log out from Settings in the editor to remove your sign-in token.
- Turn off notifications by tapping the bell on the streamer's page, or block notifications for livelinks in your browser's site settings.
- Clear site data: in most browsers, open the site settings (usually from the padlock or settings icon next to the address) and choose to clear data or cookies for livelinks. This removes local storage, session storage, cookies and the service worker together.
- Block cookies: your browser settings also let you block cookies, including third-party cookies only. If you block all storage, you will not be able to stay logged in.
Your browser's help pages explain the exact steps: for example Chrome, Safari, Firefox and Edge each have a "clear cookies and site data" guide.
7. Changes and new cookies
If we ever want to use cookies or storage that are not strictly necessary, such as analytics, we will ask for your consent first, with a clear choice to say no, and we will update this policy before they are used. We will also update this page whenever the list in section 3 changes, and change the date at the top.
8. Contact
Questions about cookies or storage? Email Livelinkuk@outlook.com.