Privacy Policy
Last updated 2026-07-26
We take your data seriously and we're writing this honestly. Below is what we actually do with the data our website sees — no marketing spin, no legalese, and no claims we can't back up in code.
How we measure traffic
To understand which pages people actually use, we run a small first-party visit counter that lives on our own servers. Here's the honest breakdown of how it works:
- No cookies for tracking. We don't drop any cookies just to count visits. We use localStorage only for things you'd expect us to remember (your preferences, your consent choice if you make one) — never as a tracking beacon.
- Anonymous visitor hash that rotates daily. Each visit gets a one-way hash so we can tell two clicks in the same session apart from two separate people. That hash rotates every 24 hours UTC, so there's no way to link what you did today to what you did yesterday. By design.
- Raw IP addresses are never stored. Your IP touches our server for a millisecond as part of the hash calculation, then it's dropped. It never lands in any database row.
- Raw event data lives for 180 days, then expires. Aggregated daily rollups (page X had Y visits on date Z) stay indefinitely because they're not tied to individuals.
- Data stays on our servers. Nothing from this first-party counter is sold, shared, or sent to any third party. Meta Pixel is a separate thing — see below.
What we actually see: page views, an approximate count of unique visitors, top pages, which site (if any) referred you here, UTM campaign tags on shared links, and a coarse device class (mobile / tablet / desktop only — no operating system, no browser version, no fingerprint).
Third-party tracking — Meta Pixel
We run Meta's advertising measurement tag on non-admin pages of this site. In plain English:
- What it is. A small script from Meta (Facebook / Instagram's parent company) that tells them when someone lands on our pages. It's how we measure whether our Instagram + Facebook ads actually bring people who care about clean yards.
- What flows to Meta. The URL you visited, what site referred you here, standard browser signals Meta collects across every site that runs their pixel, and event-level pings like "PageView" when you change pages inside our site. We don't send Meta your name, your email, your address, your dog's name, or anything you type into a form on our site.
- Meta's data handling is Meta's responsibility, not ours. Once data reaches Meta, it's governed by their privacy policy — not this one. Their policy lives at facebook.com/privacy/policy.
- The pixel ID is public. Every site that runs Meta Pixel exposes its pixel ID in outbound requests — it's not a secret. Ours is
4398315853749426. Mentioning it here is transparency, not a leak. - Consent controls are being implemented. Today the pixel fires on non-admin pages regardless of your consent. That's appropriate for our current operating region and scale; it won't stay that way if we start serving users in the EU or California, or when our ad spend meaningfully scales. The consent-gate code is ready to flip on when that day comes.
Our first-party visit counter (see the section above) is never gated on consent — it's designed to be legally defensible without one (cookieless, daily-rotating hash, no raw IP, no cross-day linkability). The consent gate, when it's live, applies to Meta Pixel and any future third-party pixel we add — nothing more.
PostHog historical disclosure
A template-included third-party analytics snippet was discovered and removed on July 25; we have requested deletion of any data it collected.
The plain-language version: the project template we started from silently included a PostHog analytics script. It wasn't something we chose or configured — it slipped through with the starter code. As soon as we identified it on July 25, 2026, we removed the snippet from our public site, and on July 26, 2026 we submitted a formal deletion request to the platform provider asking them to purge any data that snippet may have collected while it was live.
We'll update this page as we learn more. If you'd like to check in on that in the meantime, reach out through the Contact link in our footer.