GURDN

Privacy

What GURDN knows, and where it keeps it

GURDN observes network configuration, which is sensitive by nature. The design answer is to keep it on your machine and to require nothing of you in exchange.

ScopeThis describes how the application behaves. It is not a legal privacy notice, and it does not claim compliance with any regulation.

01Architecture

Local by construction, not by promise

The privacy properties come from where the code runs. An architecture with no backend has no data to hold, which is checkable in a way a policy is not.

No account
No registration and no sign-in to protect the machine GURDN is installed on.
No cloud service
Observation, assessment, decisions and the record are local. No server has to answer for the product to work.
No mandatory telemetry
GURDN does not require usage reporting to function, and does not send your network configuration anywhere as a condition of running.
Local storage
Written under the machine’s program data directory, resolved from Windows rather than assumed, with some columns encrypted at rest.
Bounded retention
Limited by size and age under a documented policy, so the record does not grow without end.

02Visibility

What the application can see

Being specific here is more useful than a reassuring summary.

  • Network interfaces, their type, status, addresses and gateways.
  • Configured resolvers, and whether they changed from what was recorded.
  • The associated Wi-Fi network, its security type, and previous associations.
  • Whether a VPN interface is present.
  • Host firewall profile state.
  • What Windows reports about a mobile broadband interface, where one exists.
  • The actions you authorised, when, and what GURDN did as a result.

GURDN does not read the contents of your traffic and does not record which sites you visit.

03Transmission

What leaves the machine

Two honest categories, rather than a blanket claim.

Nothing, to run
GURDN does not need to send your configuration anywhere in order to observe, assess or protect the machine.
What you ask for
A check about whether something is reachable needs a network. Checking for an update contacts an update source. A diagnostic bundle you export goes wherever you send it.

This is why the site does not claim everything works offline. Local observation and assessment do; a question about reachability cannot be answered without a network.

04This website

The site itself collects nothing

Static pages, no analytics, no tracking, no cookies, no third-party embeds and no web fonts loaded from another domain.

Viewing these pages makes no request to anyone other than the host serving them, which is enforced by a test over the built HTML rather than asserted here. The host sees the ordinary request information any web server sees.

The privacy documentation covers the product in more detail.