Last updated: 3 August 2026
This page explains exactly what ClipLogger stores in your browser, and what it does not. It is short because there is very little to describe. It sits alongside the Privacy Policy, which covers everything else.
Until you sign in, nothing is written to your browser
We checked this with a real browser rather than assuming it. Load any public page — the home page, pricing, the documentation, the blog, these legal pages — scroll around, and leave: no cookie is set, and nothing is written to localStorage or sessionStorage. Not one key.
That is the claim that matters under cookie law, and it is the reason there is no consent banner on this site. It is not a claim that the site is silent: it is not. See the next section.
We do measure traffic, and here is exactly how
Two measurement tools run on the public pages.
Simple Analytics counts visits. It is a privacy-focused analytics company based in the Netherlands, chosen specifically because it works without cookies. It loads scripts.simpleanalyticscdn.com and, for each page you view, requests a small image from queue.simpleanalyticscdn.com with these values attached:
| Sent | Example |
|---|---|
| The page path and the site hostname | /pricing.html |
| Your browser's user-agent string, and its reported browser, OS and OS version | macOS 26.5.2 |
| Screen width and height, and whether the device reports as mobile | 3840 × 2160 |
| Your browser language and time zone | en-US, America/New_York |
| Whether this is your first page view of the visit | unique: true |
| A random page id and visit id, generated fresh in memory and never written to your device | a UUID pair |
| A timestamp |
Netlify Real User Metrics measures how fast pages load — the standard Core Web Vitals — and reports them to Netlify, who host this site and already serve you every page. It is served from our own domain.
Neither one sets a cookie. Neither writes to your browser's storage. The visit id above lives only in the memory of the page you have open; close the tab and it is gone, and there is nothing left behind to recognise you by on your next visit. Neither tool builds a profile of you across sites, and neither is an advertising product — we do not run ads, and we do not sell or share this data.
Your IP address necessarily reaches both, as it does with any web request. Simple Analytics uses it to derive a country and does not store it. Netlify is our hosting provider and already sees it for every request.
What we do not run: no Google Analytics, no advertising pixels, no session recording, no heatmaps, no cross-site trackers, and no fingerprinting library. We do not deny that a user agent, a screen size and a time zone are the raw materials of a fingerprint — they are — but they are sent to count page views, not to identify you, and nothing persists on your device to link one visit to the next.
Everything we store in your browser
Once you sign in, three items exist. All three are strictly necessary to deliver something you explicitly asked for. None of them tracks you, and none of them is shared with anyone.
| Name | Type | Purpose | Lifetime | Strictly necessary |
|---|---|---|---|---|
sb-<project>-auth-token | localStorage | Holds your sign-in session (an access token and a refresh token) so you stay signed in as you move between pages. Set by our authentication provider's browser library. | Persists until you sign out, until the session expires, or until you clear it. | Yes |
cl_join_token | sessionStorage | Carries a team invitation token across the sign-in redirect, so that accepting an invite still works after you log in. | Deleted the moment it is used, and in any case when you close the tab. | Yes |
cl_app_redirect_to | sessionStorage | Carries the desktop app sign-in handoff across the authentication redirect, so signing in on the web returns you to the app. | Deleted the moment it is used, and in any case when you close the tab. | Yes |
That is the complete list. There is no fourth item, and no advertising or analytics cookie exists anywhere on cliplogger.com.
Note that localStorage and sessionStorage are not technically cookies, but privacy law treats storing or reading information on your device the same way regardless of the mechanism, so we list them here as if they were.
Why there is no consent banner
Under the EU ePrivacy Directive and the UK Privacy and Electronic Communications Regulations (PECR), consent is required before storing information on, or reading information from, your device. That rule is about your device, not about analytics as a category.
The three items in the table above do store something, and they fall inside the one narrow exemption: storage that is strictly necessary to provide a service you explicitly asked for. Keeping you signed in after you asked to sign in, honouring the team invite you clicked, and returning you to the desktop app you launched the sign-in from are the service, not extras layered on top of it. A banner asking permission to keep you logged in would be theatre.
The measurement described above stores nothing on your device at all — no cookie, no localStorage, no sessionStorage — so it never crosses the threshold that triggers the consent requirement. We rely on our legitimate interest in knowing which pages are read and whether they load quickly (GDPR Article 6(1)(f)), balanced against a design that deliberately keeps no persistent identifier and builds no profile.
We are not claiming "this site uses no cookies". It uses the three listed above, and they exist only after you sign in.
Our commitment. If we ever add something that does store or read information on your device beyond those three, or anything that tracks you across sites or feeds advertising, we will ask for your consent before it loads, it will be off until you agree, and refusing will be as easy as accepting.
If you would rather not be counted, Simple Analytics honours your browser's Do Not Track setting, and any content blocker or privacy-focused browser will block both tools outright. Nothing on this site breaks if you do — every page works identically, and we would rather you read it than be counted.
Fonts are self-hosted, on purpose
The typefaces on this site are served from cliplogger.com/assets/fonts/. They used to come from a third-party font service, and we moved them.
The reason is a specific one. On 20 January 2022 the Regional Court of Munich I (Landgericht München I, case 3 O 17493/20) held that a website which embedded fonts from a third-party service, causing the visitor's IP address to be transmitted to that service without consent, infringed the visitor's privacy rights, and awarded the visitor damages. An IP address is personal data, and quietly handing it to a font provider on every page load is a transfer the visitor never agreed to.
We took the point. Hosting the fonts ourselves means no third party learns your IP address, your browser, or the fact that you visited, and there is no consent question to raise in the first place.
Stripe's cookies, on Stripe's pages
When you buy a plan or a credit pack, checkout happens on Stripe's own pages, hosted by Stripe. Stripe sets its own cookies there, mainly for fraud prevention and to make the payment work.
Two things follow. First, those cookies are set on Stripe's domain, by Stripe, under Stripe's own privacy notice and cookie policy, not ours. Second, nothing Stripe-related is set on cliplogger.com itself. We do not embed Stripe's fraud detection script across our site, so browsing our pages involves Stripe not at all.
The desktop app
The macOS app is not a browser and has no cookies. When you sign in, it stores its authentication token in the macOS Keychain on your own machine, protected by the operating system. It sends no telemetry. If you never sign in, it never contacts us.
How to clear this storage
Clearing site data signs you out of cliplogger.com. Nothing else is affected, and none of your footage, projects, or sidecar files live in the browser.
- Safari (macOS): Safari menu, Settings, Privacy, Manage Website Data, search for
cliplogger.com, then Remove. To clear everything: History menu, Clear History. - Chrome: open cliplogger.com, click the icon to the left of the address bar, then Cookies and site data, Manage on-device site data, and delete. To clear everything: Settings, Privacy and security, Delete browsing data.
- Edge: open cliplogger.com, click the icon to the left of the address bar, then Cookies and site data. To clear everything: Settings, Privacy, search, and services, Choose what to clear.
- Firefox: Settings, Privacy & Security, Cookies and Site Data, Manage Data, search for
cliplogger.com, Remove Selected. To clear everything: Clear Data. - Safari (iOS/iPadOS): Settings app, Apps, Safari, Advanced, Website Data, then swipe to delete the cliplogger.com entry.
Most browsers also offer a private or incognito window, which discards all site storage when you close it. The site works normally in private browsing, though you will need to sign in again each session.
Changes to this page
If the list of stored items changes, this page changes with it, and the "last updated" date moves. Adding anything that is not strictly necessary would also mean asking for your consent first, as described above.
Questions: hello@cliplogger.com.