Trust & Security

Last updated: March 29, 2026

Harvv is built on a simple principle: we should be able to tell you exactly what's broken on your site without knowing anything about your users.

Our Pixel is 6KB Gzipped. Read Every Line.

Our entire tracking pixel is under 3,500 bytes. That's smaller than the paragraph you just read. You can view the full unminified source code right now — it takes about 5 minutes to read.

For comparison: Google Analytics is 47KB. Hotjar is 470KB. FullStory is 59KB. You cannot meaningfully audit those scripts. You can audit ours over coffee.

What We Collect

A Note on IP Addresses

The behavioral pixel never sends your visitors' IP addresses. It is not in the payload, and there is no IP column in the database table where behavioral events live, so an IP can never be joined to what a visitor did on your site. That is the claim above, and it holds.

For completeness, because auditors ask: like every web server on the internet, ours does see the connecting IP on each request. That is how a network connection works. We use it transiently, in memory, for one thing only: rate limiting and abuse prevention. We do not store the raw IP. For security investigations our internal access log keeps only a keyed, daily-rotating hash of it (HMAC, not a plain hash) that cannot be reversed back to the address and cannot be linked across days, and it is never joined to any behavioral event. In short: no IP in your analytics, ever, and no raw IP retained anywhere.

What We Cannot Do

• We cannot read form inputs. If a user types their credit card number, we see "input[text]#card-number" — the element identifier, never the value.
• We cannot see page content. We don't capture DOM snapshots, screenshots, or session recordings.
• We cannot track users across sites. Our cookies are first-party, scoped to your domain only.
• We cannot identify individual users. Our visitor ID is a random hex string with no connection to real identity.

Architecture

• Pixel: 3,363 bytes gzipped. Vanilla JavaScript. No dependencies. Loads asynchronously — zero performance impact.
• Data transfer: Events batched and sent via navigator.sendBeacon every 10 seconds. JSON payload with short keys (v, s, e, t, d).
• Storage: PostgreSQL on Railway (US region). Data retained per your plan terms.
• AI Analysis: Anthropic Claude API for issue diagnosis. Your behavioral data is sent to Anthropic for analysis — Anthropic's privacy policy prohibits training on API inputs.
• Email: Resend for transactional email. Resend's privacy policy.
• Payments: Stripe for billing. We never see or store credit card numbers.

Subprocessors

Compliance

• GDPR: We collect no personal data as defined by GDPR. Random hex IDs are not personally identifiable without additional information we don't have.
• CCPA: We do not sell personal information. We do not share data with third parties for their own purposes.
• Cookie Consent: Our cookies are first-party functional cookies (session management). Many jurisdictions exempt these from consent requirements. We recommend consulting your legal team for your specific situation.

Verify It Yourself

1. Read our full pixel source code — every line, commented
2. Open your browser DevTools → Network tab → filter by "harvv" or "pixel.js" → inspect every request we make
3. Check the payload: it's JSON with short keys (v=visitor, s=session, e=event type, t=timestamp, d=data). No PII anywhere.

Questions? Email jordan@harvv.com — I'll personally walk you through the code.