Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Gauges is a simple, lightweight real-time web analytics tool developed by Steamclock. It tracks page views, referrers, top content, and visitor locations using a small JavaScript snippet and analytics cookies. It is a low-risk analytics service but still requires cookie consent for EU visitors and processes data on US servers.
Gauges is a simple, real-time web analytics service developed by Steamclock (previously by GitHub founders under the Order brand). It is designed as a lightweight alternative to more complex analytics platforms, offering a clean dashboard that shows page views, unique visitors, referral sources, top content, and visitor locations without the complexity of event tracking or funnel analysis. Website operators add a small JavaScript snippet served from track.gaug.es to their pages, which fires on each page load.
Gauges is classified as a low-risk analytics tool. It does not use cross-site tracking, does not serve advertising, does not build individual behavioural profiles, and does not integrate with data management platforms. Its primary purpose is simply to count and characterise page views in real time.
Gauges sets analytics cookies to distinguish unique visitors from repeat visits to the same page, enabling accurate unique visitor counts. The cookies store a random visitor identifier that allows Gauges to calculate session counts without retaining personally identifiable information in its dashboard. In addition to cookie data, Gauges receives each visitor''s IP address (used for geo-location to show visitor country and city), the page URL, the HTTP referrer (the previous page or website), the browser user-agent string, and a timestamp.
Under the GDPR, IP addresses are considered personal data even when used only for geo-location. The website operator using Gauges is the data controller and Gauges acts as a data processor. A Data Processing Agreement should be in place. Under the ePrivacy Directive, the analytics cookies set by Gauges are not strictly necessary for the website to function and therefore require prior consent from EU visitors. Some regulators accept a legitimate interest argument for truly anonymised, aggregated analytics, but Gauges'' use of persistent cookies and IP-based identification means that consent is the more defensible basis in most EU jurisdictions.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Consent for Gauges analytics cookies must be obtained before the tracking snippet fires. Your CMP should block the Gauges JavaScript until the visitor accepts the analytics cookie category. Because Gauges is a low-risk tool with a simple data model, the consent notice can be straightforward: explain that Gauges counts page views and shows referral sources to help you understand your audience. Withdrawing consent should result in the Gauges cookies being deleted and the script not loading on subsequent pages.
Gauges is operated by a US company and transmits page view data, including visitor IP addresses, to US servers. This is an international transfer of personal data subject to GDPR Chapter V. As a legacy and relatively low-traffic tool, Gauges may not have formal EU-US DPF certification; verify the current status. Standard Contractual Clauses provide the appropriate transfer mechanism. Document the transfer and the mechanism in your records of processing activities.
To deploy Gauges compliantly: obtain and sign a Data Processing Agreement with Gauges, configure your CMP to block the Gauges snippet until analytics consent is obtained, add Gauges to your cookie notice and privacy policy listing it as a US analytics processor, document the transfer mechanism (SCCs), set a retention period for analytics data in line with your data minimisation obligations, and consider whether Gauges still meets your needs or whether a privacy-first EU-hosted analytics alternative would be simpler to justify.
Websites using Gauges must obtain user consent under GDPR regulations.
DPIA considerations
A full DPIA is unlikely to be required for Gauges given its low-risk profile: it collects only aggregated page view and referral data, does not build individual user profiles, does not process special-category data, and does not enable cross-site tracking or advertising. However, you should document your legitimate interest assessment or consent approach and note the US transfer in your records of processing activities. If Gauges is one of several analytics tools operating simultaneously on the same site, the cumulative profiling risk should be evaluated.
Sample consent text
We use Gauges, a simple web analytics tool, to understand how visitors interact with our website in real time. Gauges sets analytics cookies to count page views, identify referral sources, and show which pages are most popular. These cookies are not strictly necessary and require your consent. By accepting, you allow Gauges to collect anonymised usage data that is processed on servers in the United States. You can withdraw consent at any time via our cookie settings.
Third-party domains contacted
gaug.essecure.gaug.estrack.gaug.esCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| gauges_unique | analytics | 2 years | Persistent visitor identifier that distinguishes unique visitors from returning visitors to enable accurate unique visitor counts in Gauges real-time dashboard |
| gauges_session | analytics | Session | Session-level cookie that tracks page views within a single browsing session; expires when the browser is closed |
| gauges_referrer | analytics | 30 days | Stores the referring URL or domain to attribute site visits to their source, enabling Gauges to populate the referrers report |
| gauges_geo | analytics | Session | Temporary cookie used in conjunction with the visitor IP address to derive an approximate geographic location (country and city) for the visitor location report |
Gauges collects user analytics data — you legally need a consent banner. Try FlowConsent free.
Gauges sets analytics cookies to distinguish unique visitors from repeat visits and to track page views across a session. The primary cookie stores a randomly generated visitor identifier that allows Gauges to calculate session counts and unique visitor totals. These cookies do not store names, email addresses, or other directly identifiable personal data, but the visitor identifier combined with an IP address constitutes personal data under the GDPR.
Yes, consent is required. Although Gauges is a simple and low-risk analytics tool, the ePrivacy Directive requires prior consent for any analytics cookie that is not strictly necessary for the website to function. Gauges cookies are used to count and characterise visitors, which goes beyond the strictly necessary threshold. EU visitors must actively accept analytics cookies before the Gauges tracking snippet fires on the page.
Consent (Article 6(1)(a) GDPR) is the most appropriate legal basis for Gauges. Some operators argue legitimate interest (Article 6(1)(f)) for simple, aggregated analytics that do not build individual profiles, but Gauges uses persistent cookies and receives IP addresses, meaning it does not meet the threshold for full anonymisation required for a robust legitimate interest argument in most EU member states. Consent is the safer and more defensible basis.
Yes. Gauges is operated by Steamclock, a US company, and page view data including visitor IP addresses is transmitted to and stored on US servers. This is an international transfer under the GDPR. You should verify whether Gauges holds EU-US Data Privacy Framework certification; if not, Standard Contractual Clauses should be used as the transfer mechanism. Document the transfer and the mechanism in your records of processing activities and reference it in your privacy policy.
A full DPIA is generally not required for Gauges given its low-risk profile. It does not process special-category data, does not build individual user profiles, does not enable cross-site tracking, and collects only simple aggregated page view metrics. However, you should document a proportionality assessment and note the US data transfer in your records of processing activities. If Gauges is used alongside other analytics or advertising tools, evaluate the cumulative profiling risk.
Configure your Consent Management Platform to block the Gauges JavaScript snippet (track.gaug.es) until the visitor consents to the analytics cookie category. Sign and store a Data Processing Agreement with Gauges if one is available. Add Gauges to your cookie notice with a description of the cookies set, their duration, and the purpose. Reference the US data transfer and the applicable mechanism (SCCs or DPF) in your privacy policy. Set a retention period for analytics data and delete data that exceeds it.
Yes, several EU-hosted analytics tools offer comparable simplicity with better privacy credentials. Plausible Analytics (EU-hosted, cookieless option available, GDPR-compliant by design) and Fathom Analytics (EU isolation option) are popular privacy-first alternatives. Matomo (self-hosted, EU) offers full data ownership. These tools can often be deployed without a cookie banner when configured in cookieless mode, eliminating consent requirements entirely and simplifying compliance.
Add a dedicated entry for Gauges in your cookie policy table. List the cookie name (e.g., the Gauges visitor identifier cookie), its type (analytics), its duration (typically 1 to 2 years for persistent cookies), its purpose (counting page views and unique visitors), and the entity setting it (gaug.es, secure.gaug.es, track.gaug.es). State the legal basis (consent) and explain how visitors can withdraw consent. Reference the US data transfer and note that Gauges processes data on servers in the United States.