Dingus Domains See how it works

What we collect, and what we don’t.

This policy covers the dingus.domains website and Dingus, the domain monitoring tool it describes.

Last updated 2026-09-21

Who we are

Dingus is made by Spergs, LLC, a Florida limited liability company. We run the dingus.domains website and Dingus itself, and we’re the data controller for everything described below.

Privacy questions, data-access requests and corrections go to privacy@spergs.com.

The short version

dingus.domains is a static website. There’s nothing to sign up for, no accounts, no forms and no comments. We don’t run analytics, advertising pixels, tracking scripts or third-party embeds.

Dingus itself watches domains, not people. It asks registries and nameservers public questions about domains we hold — who the registrar is, when a name expires, where it’s delegated, and whether it still answers — and keeps the answers.

This website

Server access logs

When your browser asks for a page, our web server records:

  • The IP address the request came from.
  • The page you asked for, and when.
  • Your browser’s User-Agent string.
  • The referring URL, if your browser sent one.

These logs live on the server that serves the site, rotate on a normal schedule, and are kept for up to 30 days for operations and abuse investigation. We don’t join them to anything else.

Cookies and local storage

dingus.domains sets no cookies and writes nothing to your browser’s storage. The page’s animations run entirely in your browser and send nothing back. If you see a cookie from this domain, something is wrong — please tell us at privacy@spergs.com.

Email

If you email us, we’ll have whatever the email contains: your address, your name if you signed it, and your message. We keep correspondence as long as it’s useful to follow up on, and delete it on request.

Dingus itself

Dingus is pre-alpha. Today it runs for the domains Spergs, LLC holds, and there are no public accounts. Here is what it keeps.

Facts about domains

  • Registration facts read from public RDAP and whois services: the registrar, the creation and expiry dates, the registry status, and the nameservers. Dingus does not store the registrant, administrative or technical contact details a whois record can carry.
  • DNS answers from the nameservers a domain is delegated to: which server answered, what it said, and when.
  • Decisions and notes we record about our own domains, such as whether we mean to keep or release one, and what a renewal costs.

Answers are kept rather than overwritten, because comparing yesterday’s answer with today’s is how Dingus notices a domain that stopped working.

The mobile app

If you turn on alerts in the Dingus app, the server stores your device’s push token, its platform (Android or iOS), and a label so an old device can be recognised and removed. A token that the push service reports as no longer valid is deleted automatically. The app itself stores no credentials.

What we don’t collect

  • No analytics. No Google Analytics, Plausible, Fathom or any other analytics SDK.
  • No advertising. No ad networks, retargeting pixels or conversion tags.
  • No social embeds. Nothing on this site loads code from a social platform.
  • No third-party fonts or CDNs. Every file this site uses is served from dingus.domains itself, and the server tells your browser to refuse anything else.
  • No fingerprinting. We make no attempt to identify your browser or device beyond the server logs above.
  • No domain-owner contact data. Dingus reads whois for dates and delegation, and leaves the people in it alone.

Third parties

  • Hosting. The site and Dingus run on servers we operate. Our hosting providers have physical access to the hardware as part of normal operations, and no credentialed access to either.
  • Registries and nameservers. To do its job, Dingus sends queries about our domains to public RDAP, whois and DNS servers. Those queries name a domain, not a person.
  • Push notifications, only when alerts are switched on. An alert travels through Expo’s push service to Google’s (Firebase) or Apple’s, which deliver it to your phone. The alert names the domain and what happened to it.

We don’t sell or share data with anyone else.

Your rights

Because we hold so little that’s tied to a person, most requests are short conversations. You can:

  • Ask what we have on you (UK / EU GDPR access, California CPRA right to know).
  • Ask us to delete email correspondence, or a device you registered for alerts.
  • Ask us to correct anything inaccurate in our records.
  • Lodge a complaint with your local data-protection authority (UK: ICO).

Email privacy@spergs.com for any of these. We try to respond within 30 days.

Children

Dingus isn’t directed at children. We don’t knowingly collect personal information from anyone under 13 (or under 16 where that threshold applies); if you believe we have, email privacy@spergs.com and we’ll delete it.

Changes to this policy

If something material changes, we’ll update the date at the top. If Dingus ever starts collecting more — accounts for other people’s domains, for instance — this page is the first thing we’d update.

Contact

Spergs, LLC
privacy@spergs.com