Privacy
dug has no accounts, no database and no session. There’s nothing to sign up for and nothing to sign in to, so there’s no profile to build. Each query goes to the upstreams it names, comes back, and then dug forgets it. The only copies that outlive the request are the one in your browser tab and the one in a shared HTTP cache, held for the lifetime the answer itself declares.
- queries
- not stored, not logged to any datastore
- targets
- not retained after the request that named them
- accounts
- none exist
- cookies
- none set by this app
- history
- kept in the tab, lost on reload
- cache
- in the tab, and in a shared http cache by ttl
The site is hosted on Vercel, which terminates TLS and therefore sees request metadata as any host does. Two Vercel scripts run on the page, and one model provider is called from the prompt:
- Analytics
- aggregate page views, no cookie and no cross-site identifier
- Speed Insights
- anonymous page timing, sampled
- OpenAI
- receives the sentence you type in plain words, only when the planner runs, with retention turned off
Vercel injects both scripts only on a deployment, so a local run of this project sends no beacons at all. A command such as TLS example.com never reaches the model provider: the planner runs only for a question in plain words, sends that text and nothing else, and asks the provider not to store it.
The deployment makes the lookup, not your browser, so the target sees a request from this service, not from you. That cuts both ways. Your address isn’t exposed to the domain you ask about, and the domain you ask about is visible to the resolvers and registries the command names.
PORTS is the one command that completes a TCP handshake against the target, so it appears in that target’s logs as a connection from this deployment. Only run it against hosts you’re allowed to probe.