What is recorded

What a visit records

• Per link: how many times it was followed, and when it was last followed. Nothing else.
• No IP addresses. No user agents. No referrers.
• No email addresses anywhere in the service — there is no column for one.
• One exception, and it is volunteered rather than observed: an account holder may type a browser engine and version into a form, and that pair is counted. Nothing detects it, and no report records who sent it.

What that costs, and who pays it

• You cannot be told where your visitors came from, what browser they used, or which of them followed a link twice. Not withheld — never collected.
• There is no email column, so there is no "email me a reset link". That is why backup codes matter here more than they do elsewhere.
• A destination never learns which short link sent somebody, or that geodzk was involved: every redirect carries Referrer-Policy: no-referrer.

The things people expect to be logged, and are not

• Notes sent to the operator carry no attribution at all. The operator sees the note, not who wrote it.
• Browser reports are typed by a person, counted, and never attributed. Nothing on the service detects your browser to fill that in.
• A published collection's page shows nobody's click counts. Those are the owner's operational data and stay on their side.
• Making, changing or deleting a masked link writes no audit row and no log line, and its row names no account. Masked links says what that does and does not buy.

What is recorded, deliberately

• Administrative action, in an audit log: who did it, to what, and when. An operator purging that log leaves the fact of the purge behind.
• A key's last-used date, so an owner can tell a live credential from a forgotten one.
• Nothing in either of those is about a visitor.

Every claim on this page is rendered from the same settings the service enforces. If an operator switches extended analytics on, this page says so on the next request rather than staying comfortable.