SDR to HDR
Sign in

Cookie Policy

SDR to HDR uses a minimal set of cookies and similar technologies. We do not run advertising trackers, retargeting, or third-party social cookies.

Last updated May 6, 2026

The short version

A plain-language summary. The numbered sections below are the operative text; where the two differ, the sections govern.

Which cookies do I have to accept?

Only the strictly necessary ones: the Supabase sign-in session cookies and a small number of Next.js routing cookies. Blocking those signs you out and breaks the app. Section 1 below is the operative list.

Do you use advertising cookies?

No. There are no advertising cookies, no sale of data to ad networks and no cross-site retargeting. Section 3 below.

How do I opt out of analytics?

Google Analytics 4 runs with IP anonymisation and counts visits in aggregate. Use your browser's Do Not Track setting or block GA in your privacy settings. Section 2 below.

1. Strictly necessary

These keep you signed in and remember your language: Supabase auth cookies (sb-access-token, sb-refresh-token), the NEXT_LOCALE locale cookie, and a small number of Next.js routing cookies. Without these the service does not work; they cannot be disabled while you are using SDR to HDR.

2. Analytics

We use Google Analytics 4 with IP anonymization to count visits and conversions in aggregate. You can disable this by using your browser's "Do Not Track" or by blocking GA in your privacy settings.

3. No advertising

We do not place advertising cookies, do not sell data to ad networks, and do not run cross-site retargeting.

4. How to disable cookies

Every modern browser lets you block or delete cookies. Note that blocking strictly-necessary cookies will sign you out and may break the app.

5. Retention

Session cookies expire when you close the browser. Persistent cookies (sign-in refresh, locale) live for at most 12 months.

6. Contact

Questions about cookies: [email protected].

Questions? Email [email protected].