Home / Privacy

Privacy, in plain language.

No legalese. No banner. Nothing hiding behind either.

Most privacy pages are written to protect the company posting them. This one is written to be read. The short version: this site collects very little, and the visit log never leaves our server.

What This Site Collects

A visit log, and not much else.

Loading a page here writes one row to a database on our own server. That row holds:

  • The page path you visited, and the referrer that sent you, if there was one.
  • Coarse location from a GeoIP database stored on this server. No lookup service is called.
  • Your browser family, read from the user agent your browser sends. Bot traffic is flagged.
  • A hashed identifier. Your IP address is hashed before storage. The raw IP is never kept in the analytics table.

That is the whole pipeline. First-party, in SQLite, on our hardware.

What It Never Does

The list that matters more.

  • No third-party analytics. No ad pixels. No session replay. No fingerprinting scripts.
  • No data sold or shared. Nothing about your visit goes to anyone, for any price.
  • No CDN in the loop. Fonts and every other asset are self-hosted, so no delivery network sees that you were here.
The Cookie Banner

Why there is no banner.

Cookie banners exist because most sites let other companies follow you across the web. Nothing on this site does cross-site tracking. It sets one first-party cookie: a random identifier so your repeat pageviews count as one visit. It holds nothing about you and means nothing to any other site.

Once per visit, the site also notes whether you scrolled, tapped, or typed, so automated traffic can be told apart from people in our counts. That note is a single flag kept in your browser tab until you close it; nothing else is recorded with it.

If your browser sends Global Privacy Control, we go further: this site records no visit for you, sets no cookie, and keeps no page history. A request you send still reaches us, with only what you typed into it.

If we tracked you across the web, we would have to ask first. We do not, so there is nothing to ask. The missing banner is the evidence.

Briefing Requests

What happens when you write to us.

If you request a briefing, we store what you typed: your name, role, company, contact details, property details, interests, timeline, and notes. It lands in the same database, on the same server, and is used for one thing: preparing your briefing.

When you send a request or a message, we can also see which pages of this site you viewed on the way, so we arrive prepared. That view comes from the one first-party cookie above, stays on our server, and is never combined with anything from other sites.

  • Confidential by default. We do not share it, sell it, or mention it.
  • One reply, from a person. Steve Golter, our founder and senior engineer, answers personally.
  • Booking a call is optional. If you choose Pick a time after sending a request, you book on our calendar provider's own page, and what you enter there is handled under its terms.
  • Resources need no email. If you ask for a follow-up about one, we keep your name, email, and organization with your request and reply once. That is all it is used for.
  • No mailing list. Submitting the form subscribes you to nothing. No sequences, no drip. If you want to hear from us again, you will have to write back.
Retention

Kept briefly, or kept for a reason.

Visit rows are deleted automatically after 90 days. What remains is daily totals (how many visits, from which kind of source, to which pages) with no visitor identifiers. Briefing requests are correspondence, so we keep them as ordinary business records. If you want yours deleted, ask, and we will do it.

Questions about any of this?

Write to contact@doraduslabs.com and a person will answer. If anything here is unclear or wrong, we want to know first.

Last reviewed August 2026. This is a plain-language statement of how this site works today, not a legal document. When our practice changes, this page changes with it.