Cookie policy

This is a plain-language template. It is not legal advice; have it reviewed by a qualified lawyer for your jurisdiction before relying on it.

Last updated: 2026-07-05

This policy explains how NoDowntimeShield uses cookies and similar technologies on our website and dashboard. It sits alongside our Privacy Policy. The short version: we use a small number of cookies to keep you signed in, keep the Service secure, remember your cookie choice, and spot bugs. We do not use cookies for advertising or to track you across other websites.

What cookies are

Cookies are small text files a site stores on your device. Some are essential to make a site work; others are optional and only run if you agree. We also use closely related technologies (such as browser local storage) for the same purposes, and we treat them the same way here. Cookies are either "first-party" (set by us) or "third-party" (set by a provider we use), and either "session" (deleted when you close your browser) or "persistent" (kept for a set time).

The categories we use

Strictly necessary (always on). These are required for the Service to work and cannot be switched off. They keep you signed in, protect the site from abuse, and remember your cookie choice. Because they are essential, they do not require consent.

Analytics / performance (only with your consent). These help us spot and fix bugs and understand where the Service is slow. They run only after you accept.

Functional. Cookies that remember preferences you set. Today we do not set separate functional cookies beyond the essential ones below; if we add any, we will list them here and ask for consent where the law requires it.

Advertising. None. We do not run advertising or cross-site tracking cookies.

The cookies we set

Strictly necessary (always on):

• nds_consent (set by NoDowntimeShield, first-party, lasts 1 year) — remembers whether you accepted or declined non-essential cookies.
• Supabase auth, e.g. sb-…-auth-token (set by NoDowntimeShield, first-party, lasts up to ~400 days) — keeps you signed in to the dashboard.
• Cloudflare, e.g. __cf_bm, cf_clearance (set by Cloudflare, third-party, 30 minutes to 1 year) — bot and DDoS protection that keeps the site secure and available.
• Stripe, e.g. __stripe_mid, __stripe_sid (set by Stripe, third-party, session to 1 year) — fraud prevention on the billing and checkout pages.

Analytics / performance (only with your consent):

• Sentry (set by Sentry, third-party, short-lived) — error and performance monitoring so we can spot and fix bugs. Sends data only after you accept (until then, nothing leaves your browser).

Exact cookie names can change when providers update their products; the purposes above stay the same. Providers such as Cloudflare and Stripe set their cookies only on the pages where their service runs.

How to control cookies

• Our banner. The first time you visit, our banner lets you Accept or Decline non-essential cookies. We only load analytics cookies if you accept. Declining is as easy as accepting.
• Change your mind. To reset your choice, clear the nds_consent cookie in your browser and reload — the banner will appear again.
• Your browser. Every major browser lets you block or delete cookies in its settings. Blocking strictly necessary cookies will stop parts of the Service (like signing in) from working.

Consent

We do not place analytics cookies until you accept them, and we treat declining as a valid choice — the Service still works. Because our cookies are limited to sign-in, security, and bug-spotting, we do not sell data or share it for advertising (see our Privacy Policy).

Changes

We will update this policy if the cookies we use change — for example if we add a new tool. The "Last updated" date above always reflects the current version.

Contact

Questions about cookies? Email [email protected].