Cookies and storage
Version 1.0, last updated 2026-10-05.
Nimbus sets no cookies at all. Not a necessary one, not an analytics one, not a third-party one. The website keeps a few small values in your browser's local storage, which stays on your machine and is never attached to a request automatically. The banner you may have seen is not about cookies: it is asking whether the page may fetch a font from somebody else's server. Paying is a redirect to Stripe, so no payment script ever loads here.
Cookies
None. There is no analytics product, no tag manager, no advertising pixel, no embedded video, and no social widget. There is no session cookie either: the account page signs you in with a token held in local storage rather than a cookie, for the reason given below. There is no session cookie either, because there are no accounts: this site has nothing to sign in to.
You can verify this rather than believe it. Open your browser's developer tools on any page of this site, look under Application, then Cookies, and the list is empty.
What is stored in your browser
Local storage is not a cookie. Nothing in it is attached to a request automatically, and it is readable only by this site. This is everything the site keeps. The first two never leave your browser at all; the sign-in token is sent to the Nimbus server, by our own code, only on requests about your own account. Neither value ever leaves your browser.
| Key | What it holds | Why | How long |
|---|---|---|---|
nimbus.theme |
Light, dark, or system | So the page does not flip back to the wrong theme on your next visit | Until you clear your browser's site data |
nimbus.consent.v1 |
Whether you allowed third-party fonts | So you are asked once rather than on every page view | Until you clear it, or press the settings link in the footer |
nimbus.token.v1 |
Your sign-in token, only if you sign in on the account page | So you are not asked for your password on every visit to your account | Until you sign out, or 30 days |
Clearing site data removes all of them. The page works fine without any: the theme falls back to your operating system's setting and the font question gets asked again, and you sign in again.
The sign-in token is kept in local storage rather than in a cookie deliberately. A cookie is attached to every request your browser makes to this site automatically, which is what makes cross-site request forgery possible; a value in local storage is only ever sent when our own code chooses to send it. Signing out removes it immediately.
The third-party request question
The site can load two stylesheets from servers that are not ours:
| What | From | What they receive |
|---|---|---|
| The Geist webfont | fonts.googleapis.com and fonts.gstatic.com (Google) | Your IP address, your user-agent, and the fact that a browser requested this font |
| The Phosphor icon font | unpkg.com (Cloudflare) | The same |
Neither sets a cookie, and neither is sent anything about you beyond what any web request carries. But an IP address is personal data, and sending it to a third party is a transfer that needs a basis. So the page does not make either request until you say yes.
If you decline
Nothing is requested, and nothing breaks. The page renders in your operating system's own interface font, which is what the font stack falls back to, and the decorative icons are hidden. Every word, link, button and download on the site works identically. Declining is a real option, not a worse version of the site, which is why the two buttons are the same size.
Changing your mind
The footer of the home page has a "Third-party content settings" button. It clears the stored answer and asks again.
Paying for Nimbus Pro
Checkout is a redirect. Pressing "Get Nimbus Pro"
or "Get Lifetime" sends your browser to a page hosted by Stripe at
checkout.stripe.com, and you come back here afterwards.
Managing or cancelling works the same way.
This matters for what the rest of this page promises. There is no Stripe script on any Nimbus page. Nothing from Stripe loads while you are reading the site, nothing from Stripe can set a cookie on this site, and Stripe learns nothing about you until the moment you deliberately start a purchase. An embedded card form would have meant loading Stripe's JavaScript on every page view, which is exactly the thing the consent gate above exists to prevent.
Once you are on Stripe's own page you are on Stripe's own site, and the cookies it sets there are governed by Stripe's privacy policy rather than this one.
Stripe is the seller of Nimbus Pro, which is set out in the
privacy policy, so the checkout page, the
receipt and Stripe's order management at link.com are all
Stripe's. None of them loads anything on this site, and nothing about that
arrangement puts a script or a cookie on a Nimbus page: the redirect is
still a redirect, and it still happens only when you press the button.
The desktop app
The app is not a browser page and has no cookies of any kind. Your decks are written to a file on your own disk, and every study feature works with no network at all.
Its content security policy is default-src 'none'. That means
no remote script, stylesheet, image or font can load into the interface, so
a deck you import from a file or clone from the public library cannot
phone home or pull anything in. You can read the policy at the top of
app/renderer/index.html.
This is the complete list of requests the app itself can make:
- The update check, once a day, against the Nimbus download host. It sends no account data and you can turn it off in Settings.
- Sync, only while you are signed in, and only to the server address shown in Settings. Signing out stops it.
- The two AI features, only when you press the button: a question about a card, or a file you chose to generate cards from. These go to the Nimbus server, which passes the text to the model provider. The app never contacts that provider directly. Both are described in detail in the privacy policy.
Nothing from the AI features is stored on your machine. The conversation in the card panel is held in memory while the panel is open and is discarded when you close it: it is not written to your deck file, and it is not synced.
The fix that removes all of this
Hosting the two fonts from this site instead of from Google and unpkg would remove the third parties entirely, make the page faster, and make this question unnecessary. It is the recommended next step and it is written up in docs/THIRD-PARTY.md.
Nimbus · hello@getnimbus.org · Back to the site