This website does not set or use any cookies. It is a static marketing site with no login, so there is nothing for a cookie to remember. It also does not use localStorage, sessionStorage, or any similar browser storage.
One part of the site does have a small server-side component behind it — the contact form, described below — but that component doesn't set cookies either. "No login, mostly static" and "zero cookies" are two different claims; this policy is only making the second one.
A cookie is a small piece of data a website asks your browser to store and send back on later requests. Cookies are commonly grouped by how long they last and who sets them:
None of these are present on this site; the categories are listed here only for reference.
Because visitors often expect to see these on a company website, we're stating explicitly which ones are not present, rather than leaving it to inference:
If any of these are ever added, this policy will be updated first, and the "Effective date" above will change.
Three resources are fetched by your browser when you visit this site or use the contact form. None set a cookie:
| Resource | Provider | Purpose | When |
|---|---|---|---|
| Google Fonts | fonts.googleapis.com, fonts.gstatic.com |
Loads the Poppins and JetBrains Mono typefaces used throughout the site. | Every page |
| jsDelivr CDN | cdn.jsdelivr.net |
Loads D3.js, TopoJSON, and world-map boundary data to draw the interactive activity map on the homepage. | Homepage only |
| Contact-form API (ours, not a third party) | execute-api.eu-west-1.amazonaws.com |
Receives and processes contact-form submissions — see the next section. | Only when the form is submitted |
None of these set a cookie for these requests, but your browser's IP address is visible to whoever receives the request, since that's how any network request works — including the contact-form endpoint, which is our own infrastructure, not a third party.
When you submit this form, your browser sends it directly to a small backend we operate on AWS (the endpoint listed above) — not to a third-party form service, and not as an email your browser assembles itself. That backend stores the submission and emails us a notification at demo@seismocode.com. If that request ever fails, the form falls back to opening a pre-filled mailto: draft in your own email application instead, so your message isn't lost — you'd then choose whether to send it yourself.
Neither path sets a cookie. The verification code shown on the form is generated and checked entirely in your browser; it is not a third-party CAPTCHA service. Full detail on what's collected, where it's stored, and for how long is in the Privacy Policy — this page only covers whether cookies are involved, and they aren't.
This site links out to LinkedIn, YouTube, and the MicSer platform (micser.seismocode.com, a separate Seismocode product with its own Cookie Policy). These are plain links, not embedded content. Nothing loads from those services unless you click through, and once you do, you're on their site, governed by their own cookie and privacy practices.
Since this site sets no cookies, there is nothing to manage or opt out of here. Your browser's own cookie and site-data settings still apply to any third-party site you click through to (LinkedIn, YouTube, MicSer). You can review or clear existing cookies, or block them going forward, in your browser's own settings:
If this site's construction changes in a way that introduces cookies or new third-party tracking, this policy will be updated first and the date above will change.
Privacy enquiries: privacy@seismocode.com
Legal enquiries: legal@seismocode.com