Privacy

Privacy Policy

We built this site for infrastructure professionals who may be entering real environment data. Here's exactly what we collect, what we don't, and why.

The Short Version

🍪

A small number of analytics cookies. Nothing else. Google Analytics sets a few first-party cookies to distinguish returning visitors from new ones in aggregate traffic stats. No preference cookies, no tracking pixels, no cross-site cookies.

👤

We don't know who you are. No accounts, no login, no profiles. There is no mechanism on this site to associate any action with a specific person.

🔒

Your calculator inputs never leave your device. Every calculation runs entirely in your browser. The numbers you type — rack counts, power budgets, IP ranges, model parameters — are never transmitted to any server.

📊

We log which tools get used — that's it. When you load a tool or export a result, we record which tool was used and an approximate location (country level). This tells us where to focus development. Nothing else.

🚫

No ads right now. Never any data sales. We don't currently run advertising network code or retargeting pixels (see Section 6 if that ever changes). Google Analytics gives us aggregate traffic stats — not a profile of you — and we don't sell or share data with anyone.

1 What We Collect

We collect exactly one type of data: aggregate tool usage events. When you load a calculator page or trigger an export, our system logs:

Field	What It Contains	Why We Collect It
Tool name	The name of the calculator or page loaded (e.g., "Rack Density Calculator")	To understand which tools are most valuable so we can prioritize improvements
Event type	Page load, export, share action	To understand how tools are used, not just viewed
IP address	Your public IP at the time of the request	Approximate geographic context (country/region) only — used to understand if our audience is international. IPs are not stored long-term or used for identification.
Device type	Desktop or Mobile (derived from browser user agent)	To ensure the site works well on both form factors
Timestamp	Date and time of the event	To identify usage patterns over time

What is not collected: Calculator input values, output results, search queries, referral URLs, browser fingerprints, or any information that could identify you as an individual.

2 Your Calculator Inputs Stay on Your Device

This is the most important thing for infrastructure professionals to understand. Every calculation on this site — rack density, power phase, RAID capacity, IOPS, backup windows, GPU sizing, subnet math — runs entirely in your browser using JavaScript.

When you type a rack unit count, a power budget, an IP address, or a model parameter count into any field on this site, that value is processed locally and never transmitted to any server. It exists only in your browser tab for the duration of your session.

This is an architectural fact, not a policy promise. Our backend infrastructure has no endpoint that could receive calculator input data even if we wanted to collect it. You can verify this by opening your browser's network inspector while using any tool — you will see no outbound requests carrying your input values.

The same is true of the Architect's Whiteboard. Canvas content lives entirely in your browser's memory and is only transmitted if you explicitly click "Share / Export."

3 Cookies & Local Storage

We use Google Analytics (GA4) for standard site traffic reporting. It sets a small number of first-party cookies (e.g. _ga, _ga_*) to distinguish returning visitors from new ones in aggregate stats. These cookies don't carry your name, email, or any other personal identifier — they're a random ID your browser holds onto.

You can block or delete these at any time in your browser's cookie settings, or opt out globally via Google's Analytics opt-out browser add-on, without breaking any calculator on this site.

Beyond Google Analytics, we set no other cookies. We do not use localStorage or sessionStorage to persist any data between sessions — each visit otherwise starts completely fresh with no stored state from previous visits.

If your browser reports any other cookies on this domain, they were not set by us. This could occur if a browser extension, corporate proxy, or CDN layer has injected them — none of which we control or benefit from.

4 How Usage Logging Works (Firebase & Google Analytics)

We log usage two ways, side by side:

Google Analytics (GA4) handles standard traffic reporting — page views, approximate location (city/country level, from IP address), device type, and referral source. This is the industry-standard, aggregated-at-a-glance traffic data most sites run, governed by Google's privacy policy.
Google Firebase Firestore, a cloud database we query directly, logs a lightweight internal event per tool interaction: the fields described in Section 1 (tool name, event type, IP, device type, timestamp). This feeds our own internal tool-usage view — it's not a behavioral analytics product, just a simple event log.

Neither system receives your calculator inputs, your drawing canvas content, or any information beyond what's described above and in Section 1.

Logged usage data is retained for internal development reference and is not shared with third parties beyond Google (as the operator of GA and Firebase), sold, or used for advertising purposes.

5 Third-Party Services

This site loads resources from a small number of third-party CDNs to render the interface:

Google Analytics (GA4) — logs aggregate traffic stats and sets the cookies described in Section 3, as detailed in Section 4.
Google Fonts — loads the Inter typeface. Google may log the font request including your IP.
unpkg.com — loads the Lucide icon library. Standard CDN request logging applies.
cdnjs.cloudflare.com — loads the html2canvas library used for export. Standard CDN request logging applies.
Google Firebase — receives our internal usage event logs as described in Section 4.

These are the only third-party services this site communicates with. There are no advertising networks, social media tracking pixels, heat mapping tools, session recording tools, or A/B testing platforms.

6 Advertising

None right now. DCWorkbench.com does not currently run any ads, ad network code, or retargeting pixels. If that changes — for example, by joining Google AdSense — this page will be updated first, and any ad network in use may set its own cookies or use device identifiers to serve relevant ads, similar to most ad-supported sites. You'd be able to opt out of personalized ads at any time via Google's Ads Settings or the Digital Advertising Alliance's opt-out page.

7 Children's Privacy

This site is designed for infrastructure professionals and is not directed at children under 13. We do not knowingly collect any information from children.

8 Changes to This Policy

If we ever change what data we collect or how we use it, we will update this page and revise the date below. We will not make changes that compromise the core privacy commitments in Section 2 (calculator inputs stay on-device) without making that change explicit and prominent.

This policy was last reviewed in August 2026.

9 Contact

Questions about this privacy policy or how data is handled? Reach us at devnull@dcworkbench.com.