Cookie Notice

01What cookies and similar technologies are

A cookie is a small text file a website asks your browser to store and hand back on every subsequent request. Cookies are how sites remember you are logged in, what is in your basket — and, very often, everywhere else you have been.

Related technologies do the same job by other means:

Local storage & session storage

Key-value stores in your browser. Local storage persists until deleted; session storage clears when you close the tab.

IndexedDB & Cache Storage

Larger client-side databases and offline caches, usually used by web apps and service workers.

Pixels, web beacons, and tracking scripts

A one-pixel image or a snippet of JavaScript loaded from another company's server. The mere act of loading it tells that company your IP address, what page you are on, and often ties it to a profile of you.

Fingerprinting

Identifying a device from the combination of its fonts, screen size, time zone, and rendering quirks — no storage required, and much harder to opt out of.

Regulators treat all of these together. UK and EU rules on “cookies” apply to any storage of, or access to, information on your device — not just to files literally called cookies.

02What this site actually uses

Nothing from that list. Here it is category by category.

03Verify it yourself

Do not take our word for it. Everything above is checkable in about thirty seconds with tools already in your browser.

1. Press F12 (or ⌥⌘I on a Mac) to open developer tools.
2. Open the Application tab in Chrome or Edge, or Storage in Firefox or Safari. Look under Cookies, Local Storage, Session Storage, and IndexedDB for sd.digital. All of them will be empty.
3. Open the Network tab and reload the page. Every single request will be to sd.digital. There are no other hostnames.

The site is also entirely open source in structure: it is a handful of static files served by GitHub Pages, with no server-side code of ours running anywhere.

04What happens that we cannot switch off

Two things occur whenever anyone loads any website, including this one. Neither involves storing anything on your device, but we would rather list them than pretend they do not exist.

4.1 Server logs

Delivering a page requires a server to receive a request from your IP address. Our host, GitHub, Inc., records those requests — IP address, timestamp, file requested, user-agent string, and referrer — to operate the service and defend it from attack. We do not have routine access to these logs and do not use them for analytics. This is covered in section 4.2 and section 11 of our Privacy Policy.

4.2 Browser HTTP caching

Your browser stores copies of images, fonts, and stylesheets so that returning to the site is fast. This is ordinary HTTP caching, controlled by your browser, containing no identifiers and readable by nobody but you. It is exempt from cookie consent rules, and clearing your browser cache removes it.

4.3 If you submit the contact form

Submitting the form sends your name, email address, and message to our form-delivery provider, FormSubmit, which emails it to us. That is a single deliberate request that only happens when you press the button — not passive tracking. It sets no cookie in your browser as part of our page. What happens to that information afterwards is described in our Privacy Policy. If you would rather not use the form at all, call or text (619) 777-1313.

05Why there is no consent banner

Under UK and EU rules, consent is required before storing information on, or gaining access to information already stored on, a user's device — unless that storage is strictly necessary to deliver a service the user has requested.

We store nothing. There is therefore no lawful basis to seek, no preference to record, and no banner to display. Showing you a cookie banner would be theatre — and, ironically, storing your banner choice would require setting the only cookie on the site.

06The law we are applying

This notice is written to satisfy the transparency requirements of the following, all at once:

• UK — the Privacy and Electronic Communications (EC Directive) Regulations 2003 (PECR), regulation 6, read with the UK GDPR and the Data Protection Act 2018.
• EU — Article 5(3) of the ePrivacy Directive 2002/58/EC as implemented in each member state, read with the GDPR (EU) 2016/679.
• California — the CCPA as amended by the CPRA, and the California Online Privacy Protection Act (CalOPPA), including its Do Not Track disclosure requirement at Cal. Bus. & Prof. Code § 22575(b)(5).
• Other US states — the comprehensive privacy statutes of Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Delaware, New Jersey, and others, each of which regulates targeted advertising and the sale of personal data. We do neither.

6.1 Do Not Track

We do not track visitors across third-party websites or over time, so a “Do Not Track” browser signal makes no difference to how this site behaves. It is already doing what DNT asks for.

6.2 Global Privacy Control

We honour Global Privacy Control and equivalent opt-out preference signals as valid opt-outs of the sale and sharing of personal information. We sell and share nothing, so the signal has nothing to change.

07Controlling cookies in your browser

You have nothing to clean up from us, but for the rest of the web it is worth knowing where the controls are. Every major browser lets you view, block, and delete cookies and site data:

• Chrome — Settings → Privacy and security → Third-party cookies / Site data.
• Firefox — Settings → Privacy & Security → Cookies and Site Data; Enhanced Tracking Protection is on by default.
• Safari — Settings → Privacy → Manage Website Data; Prevent Cross-Site Tracking is on by default.
• Edge — Settings → Cookies and site permissions.
• Mobile — the equivalent items in iOS Settings → Safari, or Android Chrome → Settings → Site settings.

Blocking all cookies everywhere will break sites that genuinely need them, such as anything you log into. It will not break this one.

Browser extensions such as uBlock Origin, and browser-level features such as Global Privacy Control, extend that control further. We support all of it.

08If this ever changes

If we ever add a technology that stores or reads information on your device, we will:

1. update this notice and its version number before the change goes live;
2. describe each cookie, its purpose, its provider, and its lifetime in a table here;
3. where the technology is non-essential, ask for your consent first — with a genuine refuse option, no pre-ticked boxes, and nothing firing before you choose;
4. give you a standing way to change your mind afterwards.

Until then, the honest table is the empty one above, and we would like to keep it that way.

09Contact

Questions about this notice, or think you have spotted something on the site that contradicts it? We would genuinely like to know.

Email

privacy@sd.digital

Phone — call or text

(619) 777-1313

Related documents

Privacy Policy · Terms of Service · Accessibility Statement