Useful analytics do not require a detailed identity profile for every visitor. A privacy-first approach starts by collecting only the signals needed to understand link performance and by explaining their limits.
What Goose.re records
For a link click, Goose.re records the request time, referrer when supplied, browser language, a shortened network subnet, user-agent-derived device, browser and operating-system labels, and incoming UTM values. A daily visitor identifier is calculated from the IP address, user agent, and current date so approximate unique visits can be counted without storing the full IP address in the click row.
These fields are still telemetry. A subnet, user agent, and referrer can reveal context, so access and retention should be treated carefully. The dashboard reports aggregates and recent events; it does not identify a person or prove that a click led to a purchase.
Cookies are not one simple story
Browser behavior differs. Safari blocks third-party cookies by default. Firefox partitions third-party storage in its standard protection and blocks all cross-site cookies in strict mode. Chrome continues to let users choose their third-party-cookie setting. First-party cookies also remain widely used, so “the end of cookies” is not an accurate description.
Use the minimum useful signal
Start with click trends, referrers, languages, device classes, and campaign tags. Combine those aggregates with consented conversion data at the destination when a campaign needs deeper measurement. Do not infer sensitive traits from coarse technical signals.
