We don't track you.
No analytics. No tracking cookies. No third-party scripts. No fingerprinting. No ad networks. Nothing on rackwatch.io is here to figure out who you are.
Verify it yourself
Don't take our word for it — every claim on this page is verifiable from your terminal in 10 seconds.
1. No analytics or third-party scripts in the page source
Pull the homepage and grep for the usual suspects:
$curl -sS https://rackwatch.io/ | grep -iE "google|analytics|gtag|plausible|fathom|mixpanel|amplitude|segment|hotjar|fullstory|sentry"
Output should be: nothing. (Empty result.)
2. No external script tags
List every JavaScript source the page loads:
$curl -sS https://rackwatch.io/ | grep -oE '<script[^>]*src="[^"]*"'
Output should be: nothing. The site has zero <script src="..."> tags pointing anywhere — first-party or third-party.
3. No cookies set on the marketing site
Make a request and dump the response headers:
$curl -sIv https://rackwatch.io/ 2>&1 | grep -i "set-cookie"
Output should be: nothing. Cookies are only set if you sign in to /dashboard.html — and only the first-party session cookie used for auth.
What we don't do
- Run Google Analytics, Plausible, Fathom, Mixpanel, Amplitude, Segment, or any analytics platform
- Set tracking cookies, fingerprinting cookies, or third-party cookies
- Embed Sentry, Hotjar, FullStory, LogRocket, or any session-replay tool
- Load Google Fonts, Google Tag Manager, Facebook Pixel, or LinkedIn Insight
- Sell, share, or trade visitor data
- Use ad networks or retargeting
- Check device IDs against advertising-identifier databases
- Profile visitors across the web
What we do log
Standard HTTP request logs at the edge: IP address, user agent, request path, timestamp, response code. Used to detect abuse and rotated within 30 days. That's it. Privacy policy has the full list and subprocessors shows which vendors operate the edge.
Why this matters for an ops audience
The people RackWatch is built for — sysadmins, SREs, MSPs, ops teams running their own racks — block trackers by default and treat ad-heavy SaaS marketing pages as a code smell. A monitoring product that quietly snitches to a half-dozen ad networks is not a product that respects the data on the dashboard either.
The whole RackWatch posture is "your data stays on your infrastructure." This page is the marketing-site half of that promise: you don't have to trust us — you can verify it.
The dashboard
The signed-in dashboard at /dashboard.html sets one first-party cookie (rackwatch_session, HTTPOnly, Secure, SameSite=Lax) to hold your auth token. That's a functional cookie, not a tracking cookie — required for authentication, cleared on sign-out.
The platform binary you self-host
Same posture: no phone-home, no usage telemetry, no auto-update beacons. The binary doesn't talk to RackWatch the company at all once it's on your network. See security policy for details.