Cookies & lokaler Speicher
ShieldSync does not use cookies. We do not use tracking, advertising pixels, or third-party marketing scripts on this website or in the web dashboard. To keep you signed in we store a token in your browser's local storage instead, which is described in full below.
Zero tracking. No Facebook Pixel, no Google Analytics, no LinkedIn trackers — and no analytics of any kind.
1. What we store in your browser
These are set by ShieldSync, on your device, and never sent to anyone else. They are required for the dashboard to work, so there is nothing here to opt out of — clearing them signs you out.
| Name | Stored as | Purpose | Kept for |
|---|---|---|---|
| token | Local storage | Keeps you signed in to the dashboard between page loads. It is a signed token, not a copy of your password. | Until you sign out, or the token expires. |
| shieldsync.desktop-linked | Local storage | Remembers that you opened the desktop app from this browser, so signing out here also offers to sign out there. | Until you sign out. |
2. Why local storage and not a cookie
ShieldSync has three clients, and only one of them is an ordinary browser tab. The desktop app runs its interface on a custom tauri:// origin, and the sync engine that moves your files is not a browser at all. All three authenticate to our API the same way, with a token in a request header, because that is the only method available to all three.
We are telling you this because it has a trade-off worth being straight about: a token in local storage can be read by any script running on this page, which an HttpOnly cookie could not. Our answer is to stop hostile script from running here at all — the site sends a Content Security Policy that permits scripts only from our own origin and blocks inline script entirely.
3. Analytics and payments
We run no analytics. There is no Plausible, no Google Analytics, and no telemetry in our desktop app.
Paid plans are handled by Stripe. Going to checkout or opening the billing portal takes you off this site to Stripe’s own pages, where Stripe sets its own cookies to process the payment and prevent fraud. Those are Stripe’s, set on Stripe’s domain and governed by its privacy policy — we cannot read them, and none of them are set while you are browsing ShieldSync. We never see or store your card details. Stripe is listed on our sub-processors page.
4. Why there is no cookie banner
Consent is required for storage that is not strictly necessary to provide the service you asked for. Both items above are strictly necessary — without them the dashboard cannot keep you signed in — so there is nothing to consent to and a banner would be asking you a question with only one answer. Stripe’s payment cookies do not change this: they are set on Stripe’s own pages when you choose to go there, not embedded in ours, and they are strictly necessary to complete a payment you asked to make.
This is true because of what we do not run, not because of a legal opinion about banners. The day we embed analytics, an advertising pixel, or any third-party script that sets a cookie on our pages, this section stops being true — and we will ask for consent before any of it loads, not after.
5. Clearing it yourself
Signing out removes both items. You can also clear them from your browser's site-data settings at any time; the only effect is that you will be signed out of the dashboard. For everything else we hold about you, see the privacy notice, which explains how to download or delete it.