Harvv
How it worksWhat we findCase studiesGuidesFree auditPricing
Sign in Start free
How it worksWhat we findCase studiesGuidesFree auditPricingSign in

Harvv legal

Data Processing Addendum

Last updated: November 16, 2026

Effective October 5, 2026. Last updated November 16, 2026. Incorporated into the Terms of Service for every plan.

What changed on November 16, 2026. Annex 1 now lists every category of Visitor Data the pixel collects, including the four first-party cookies and the browser storage that mirrors them. Section 3(j), Section 4 and Annex 1 add rules on health data and other sensitive data. Section 4 and Annex 2 now say where consent-aware capture stands: it is built, it is off for every site today, and no date is set for turning it on. Section 4 also says how Customer can hold the pixel until consent today. Section 7 now states that conversion outcomes are kept for the life of the account. Annex 3 corrects what the AI model provider receives. From pixel version 33 the pixel no longer reads browser display preferences (reduced motion, more contrast, forced colors, dark scheme, reduced data). From May 2026 until version 33 the pixel stored them as one number on the session-start event. Old values leave the live database within 30 days. Copies in the long-term archive stay until a purge; no date is set for that. Harvv's own new commitment in Section 3(j) applies from November 16, 2026. For Customers who accepted the Terms before November 16, 2026, the new Customer duties in Section 4 take effect on December 16, 2026.

This Data Processing Addendum ("DPA") forms part of the Harvv Terms of Service (the "Terms") between Harvv, Inc., a Delaware corporation with its principal office at 101 Valley View Trail, Double Oak, Texas 75077 ("Harvv" or "Processor") and the customer that accepted the Terms ("Customer" or "Controller"). It applies whenever Harvv processes Personal Data on Customer's behalf through the Service. Capitalized terms not defined here have the meaning in the Terms.

1. Definitions. "Data Protection Laws" means all laws applying to the processing of Personal Data under this DPA, including the GDPR, the UK GDPR and Data Protection Act 2018, the CCPA/CPRA, and other U.S. state privacy laws. "Personal Data" means information relating to an identified or identifiable natural person that Harvv processes on Customer's behalf. "Visitor Data" means the behavioral telemetry and purchase records collected from Customer's sites by the Harvv pixel, the Harvv plugins and the conversion API, as described in the Privacy Policy, Section 1.3, and in Annex 1. "Sub-processor" means a third party engaged by Harvv to process Personal Data. "Standard Contractual Clauses" or "SCCs" means the clauses approved by European Commission Decision 2021/914, Module Two (controller to processor), and "UK Addendum" means the International Data Transfer Addendum issued by the UK Information Commissioner.

2. Roles. For Visitor Data, Customer is the controller (and, under the CCPA, the business) and Harvv is the processor (and service provider). For Customer's own account information (name, email, company, billing), Harvv is an independent controller, as described in the Privacy Policy. Harvv's processing of Visitor Data under this DPA is limited to the purposes in Annex 1.

3. Processor obligations. Harvv shall: (a) process Visitor Data only on Customer's documented instructions, which are the Terms, this DPA, and Customer's configuration of the Service, unless required otherwise by law, in which case Harvv will inform Customer unless prohibited; (b) not sell or share Visitor Data, nor retain, use, or disclose it for any purpose other than providing and securing the Service, or combine it with personal information from other sources, except as Data Protection Laws permit for service providers; (c) ensure persons authorized to process Visitor Data are bound by confidentiality; (d) implement the technical and organizational measures in Annex 2; (e) assist Customer, by appropriate technical measures and insofar as possible, in responding to data subject requests, which Customer handles directly with its visitors; on Customer's request Harvv will export or delete the Visitor Data held under a visitor identifier, and a deletion also removes those rows from the archive (backups expire as set out in Section 7); (f) assist Customer with security, breach notification, and data protection impact assessments relating to the Service, taking into account the information available to Harvv; (g) delete or return Visitor Data at the end of the Service as set out in Section 7; (h) make available information necessary to demonstrate compliance and allow for audits under Section 9; (i) notify Customer if it determines it can no longer meet its obligations under Data Protection Laws, upon which Customer may take reasonable steps to stop and remediate unauthorized use; and (j) not process Visitor Data for its own purposes, other than the limited uses Data Protection Laws permit a processor or service provider and the Terms describe (securing the Service, and deidentified, aggregated improvement), and not design or run its own analyses on Visitor Data that infer health, disability, or other special-category or sensitive characteristics of visitors, or that group visitors by signals standing in for such characteristics. Harvv does not identify visitors and does not build advertising profiles. It does not use Visitor Data for advertising, and does not treat any visitor differently based on it. Harvv does score sessions (for example, a purchase-intent score) and keeps a visitor's history under a random identifier for the periods in Section 7.

4. Customer obligations. Customer is responsible for the lawfulness of the collection of Visitor Data on its sites. Customer shall: (a) disclose the use of analytics, and of the cookies and browser storage listed in Annex 1, in its own privacy notice; (b) obtain consent where the laws applying to its visitors require consent for cookies, similar storage on the visitor's device, or analytics, and deploy a consent mechanism for that purpose; and (c) not install or configure the Service on pages or apps whose content reveals health conditions, treatment, or other special-category or sensitive data about identifiable visitors (for example patient portals, pharmacy product pages tied to a logged-in patient, or symptom checkers) without a written agreement with Harvv. Harvv may switch off collection on pages that breach (c). Today the pixel acts on two signals only: Global Privacy Control, and a refusal reported through Google Consent Mode. In that state it does not write cookies or browser storage and uses throwaway identifiers, and it still sends that page's events. It does not read the Shopify Customer Privacy API today, and it does not act on other consent banners unless they are wired to Google Consent Mode. Customer should not rely on the pixel alone to stop collection. Where Customer must hold the pixel until a visitor consents, the one way to do it today is to load the Harvv script only after consent, using the script blocking in Customer's consent tool (the script URL starts with https://harvv.com/px/). Consent-aware capture, described in Annex 2 and in the Terms, Section 7, is built and is off for every site today. No date is set, and Harvv will tell Customer before it is turned on for Customer's site. Customer's instructions shall comply with Data Protection Laws.

5. Sub-processors. Customer authorizes the Sub-processors in Annex 3. Harvv shall impose data protection obligations on each Sub-processor no less protective than this DPA and remains liable for their performance. Harvv will post changes to Annex 3 at harvv.com/trust and give Customer at least 30 days' notice of any new Sub-processor by email to the account owner. Customer may object in writing on reasonable data-protection grounds within that period; if the parties cannot resolve the objection, Customer may terminate the affected site or account with a pro-rata refund of prepaid fees.

6. Security incidents. Harvv shall notify Customer without undue delay, and in any event within 72 hours, after becoming aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Visitor Data in Harvv's systems. The notice will describe the nature of the incident, the likely consequences, and the measures taken or proposed. Harvv will not identify Customer to third parties in connection with an incident without Customer's consent, except as required by law.

7. Retention and deletion. Raw event-level Visitor Data is kept in the live database for approximately 30 days, then in a compressed archive for 13 months by default and never more than 24 months; Customer may shorten the archive window per site. Aggregates, detected issues, and reports are kept for the life of the account. Conversion outcomes (order reference, value, currency, and payment method category) are also kept for the life of the account. When Customer deletes a site or closes its account, raw events (live and archived), sessions, and reports are deleted or returned within 90 days, the first 30 days being a recovery window; thereafter deletion is permanent and includes the archive. Routine deletion is suspended only under a documented legal hold. Backups that can hold Customer Personal Data are deleted on a fixed schedule, at most 35 days after they are made, except the frozen copy of the database at the former host listed in Annex 3, which is kept until it is deleted (Annex 2). The load balancer in front of the Service writes a security log of every request it receives, including requests from the pixel: the time, the connecting IP address, the requested URL including its query string, the response status, the user agent, and connection details such as timing and size. It is kept 400 days in a storage bucket whose policy refuses deletes, then expires on its own; it is not removed when a site is deleted or the account closes. It is readable only by Harvv operators with AWS administrator access, used only to investigate security incidents and abuse, never used for analytics, and never joined to behavioral events.

8. International transfers. Harvv processes Visitor Data in the United States. Where Visitor Data is transferred from the EEA, the SCCs (Module Two) are incorporated by reference, with Customer as data exporter and Harvv as data importer, Clause 7 (docking) included, Clause 9(a) Option 2 (general authorization, 30 days), Clause 11 optional language omitted, Clause 13 and the governing-law and forum clauses completed with the Member State of the Customer's establishment (or Ireland if none), and Annexes I and II completed by Annexes 1 and 2 of this DPA. Where Visitor Data is transferred from the United Kingdom, the UK Addendum is incorporated with the same selections, Part 1 Tables completed by the information in this DPA, and either party may end the UK Addendum as set out in its Section 19. Where Visitor Data is transferred from Switzerland, the SCCs apply with the adaptations required by the Swiss Federal Data Protection and Information Commissioner.

9. Audits. On written request no more than once per year (or following a security incident), Harvv will provide its then-current security documentation, completed security questionnaires, and any third-party audit reports it holds. Where these are insufficient to demonstrate compliance, Customer may conduct, at its expense and on 30 days' notice, a remote audit by an independent auditor bound by confidentiality, limited to the systems processing Visitor Data and not more than two business days.

10. CCPA/CPRA terms. Harvv is a service provider to Customer. Harvv certifies that it understands and will comply with the restrictions in Section 3(b). Harvv does not receive Visitor Data as consideration for any service and will not sell or share it. Customer may take reasonable and appropriate steps to ensure Harvv uses Visitor Data consistently with Customer's obligations.

11. Liability; precedence; term. Each party's liability under this DPA is subject to the limitation of liability in the Terms, except where Data Protection Laws or the SCCs do not permit limitation. In case of conflict, the SCCs prevail over this DPA, and this DPA prevails over the Terms. This DPA lasts as long as Harvv processes Visitor Data for Customer.

12. Contact. Harvv, Inc., Attn: Privacy, 101 Valley View Trail, Double Oak, TX 75077, USA · [email protected].

ANNEX 1: DESCRIPTION OF PROCESSING

ItemDescription
Subject matterBehavioral analytics for Customer's websites via the Harvv pixel.
Nature and purposeCollection of structured behavioral telemetry; detection of user-experience issues; generation of findings, fix recommendations, dashboards, reports, and AI-assisted answers to Customer's questions about its sites.
Categories of data subjectsVisitors to Customer's websites.
Categories of Personal DataPseudonymous visitor and session identifiers: first-party cookies _pxv (random visitor identifier, 2 years), _pxs (session identifier), _pxss (session start) and _pxla (last activity) on Customer's domain, mirrored in the browser's localStorage; throwaway in-memory identifiers where the browser sends Global Privacy Control or Google Consent Mode denies analytics storage. An optional hashed user identifier, and short labels Customer's own code chooses to pass, if Customer's site passes them. Page URL path, page title, meta description and first H1 (truncated), and page audit values (word count, heading and meta-tag lengths, structured-data types). Short visible labels of elements the visitor interacts with (button text, aria-label) and a short clip of the heading of the page section, suppressed inside private containers, inputs and account areas. Clicks, taps and their coordinates, scroll depth and speed, hovers, visible time on page, timing of taps and swipes, pinch-zoom gestures, Tab and Escape key presses (never what is typed), and the length of selected text (never the text). Form field names and whether a field was used (never values). JavaScript errors and failed network requests (status codes and URLs with sensitive query keys removed). Page-speed measurements and structural selectors of the measured elements. Device class, browser, operating system and its version, device model on mobile, viewport size, browser zoom level, device memory, CPU core count, connection type and speed estimate, data-saver flag, time zone and language, and automation signals used to filter bots. Referrer (origin, path and campaign keys), UTM values, ad click identifiers (gclid, fbclid, msclkid, ttclid and similar) and a fixed list of landing-page test keys. Country derived from the IP address at ingest. Whether Global Privacy Control is on and what a consent banner reported. For purchases: order value, currency, payment method category, line items (product title, variant, SKU) and an order reference (a one-way hash on the Shopify checkout path; the store's own order number on the WooCommerce plugin and the public conversion API, where a customer hash derived from the customer ID or billing email is also stored). IP addresses are not stored with events or sessions. They are used at ingest for rate limiting, bot checks and the country lookup. The connecting IP address of each request is kept in the load balancer's security log for 400 days (Section 7).
Data not collected by designNames, email addresses, phone numbers, postal addresses, form field values, typed text, passwords, payment card details, clipboard content or selected text, screenshots, session recordings or DOM replay, and IP addresses in analytics records. Browser display preferences (reduced motion, more contrast, forced colors, dark scheme, reduced data) are not read from pixel version 33 (November 2026). From May 2026 until version 33 the pixel stored them as one number on the session-start event. Old values leave the live database within 30 days. Copies in the long-term archive stay until a purge; no date is set for that.
Special categoriesNone intended. Customer shall not configure or deploy the Service to collect them (Section 4). Harvv does not derive or infer them from Visitor Data (Section 3(j)).
Consumer health data (U.S. state laws)None intended, on the same terms. Customer shall not deploy the Service where page content reveals health conditions or treatment without a written agreement with Harvv (Section 4), and Harvv does not infer health status from Visitor Data (Section 3(j)).
FrequencyContinuous while the pixel is installed.
DurationPer Section 7.

ANNEX 2: TECHNICAL AND ORGANIZATIONAL MEASURES

  • Encryption in transit (TLS) for all pixel, dashboard, API, and third-party calls; encryption at rest for the database and backups; OAuth tokens stored encrypted.
  • Pseudonymization by design: no names, email addresses or other direct identifiers of visitors in telemetry (on the WooCommerce plugin and the public conversion API, the store's order number and a customer hash are stored, see Annex 1); IP kept out of analytics records, processed transiently, and hashed in database security records, except the load balancer's security log, which keeps the full address for 400 days (Section 7); defense-in-depth scrubbing of email, phone, and card-shaped strings from any shipped text.
  • Consent signals today: where the browser sends Global Privacy Control, or Google Consent Mode denies analytics storage, the pixel does not write cookies or localStorage and uses throwaway identifiers for that page. In that state it still sends the page's events. The pixel does not read the Shopify Customer Privacy API or Do Not Track today.
  • Consent-aware capture (built; off for every site today; no date set): once it is on for a site, the pixel sends nothing after a refusal, holds events in the browser's memory until a yes where a consent banner is pending, and for browsers in European time zones sends nothing until a yes. In that mode it reads the Shopify Customer Privacy API, Google Consent Mode, and Global Privacy Control.
  • Access control: role-based access with least privilege; separate database roles for runtime, backup, read-only gates, and replication; JWT authentication with expiring tokens; rate limiting on all endpoints; password hashing (bcrypt, cost 12).
  • Row-level tenant isolation in the database; one customer's data never exposed to another in identifiable form.
  • Logging and monitoring: security audit log retained 7 years; server logs shipped off each host to storage that refuses deletes; load balancer request log retained 400 days; automated invariant checks on ingest and data integrity; alerting on anomalies.
  • Backups: encrypted backups, each kept a fixed time and then deleted, at most 35 days: event store backups 35 days, database dumps 30 days, automated database backups 14 days, with a copy of the automated backups in a second US region kept 7 days; the one exception is the frozen copy of the database at the former host (Annex 3), kept until it is deleted; event archive with enforced per-site expiry.
  • Retention and deletion enforced by scheduled jobs; legal-hold switch documented.
  • Vendor management: Sub-processors bound by written terms; AI model provider under commercial terms that prohibit training on Customer data.
  • Incident response: documented runbooks; 72-hour customer notification commitment.

ANNEX 3: SUB-PROCESSORS (as of November 16, 2026)

Sub-processorPurposeDataLocation
Amazon Web Services, Inc.Application hosting, primary database, cache, encrypted backups (with a copy in a second US region), event archive, analytical replica, alertingAll Visitor DataUnited States
Cloudflare, Inc.DNS, edge network, ingest spillover during outages, email routingVisitor Data in transit; transient spillover bufferUnited States / global edge
Railway Corp.Former application hosting (until November 1, 2026); holds a frozen copy of the database until it is deletedVisitor Data received before November 1, 2026United States
Anthropic, PBCAI-generated findings, fixes, and answers to Customer's questionsFindings, aggregated behavioral figures, and session-level timelines (page paths, page titles, referrer origin, campaign values, element labels, and error text, which are free text taken from the site); visitor and session identifiers are removed before sending; not used for model trainingUnited States
Subotiz Technology Pte. Ltd.Billing and payment processing for subscriptions started on or after October 6, 2026Customer account and payment data (controller data, not Visitor Data)Singapore entity; data stored in the United States
Stripe, Inc.Billing for subscriptions started before October 6, 2026Customer account and payment data (controller data, not Visitor Data)United States
Resend, Inc.Transactional and digest email to CustomerCustomer account email; aggregated findings in digestsUnited States
Apollo.ioProfessional-profile enrichment of Customer's accountCustomer's email and site domain (controller data, not Visitor Data); never for an account created with Sign in with GoogleUnited States
Slack Technologies, LLC; ClickUp, Inc.Only if Customer connects the integration: delivery of findings into Customer's workspaceAggregated findings; no visitor identifiersUnited States
Google LLC; Meta Platforms, Inc.; Microsoft CorporationOnly if Customer connects the integration or signs in with that provider: read-only retrieval of Customer's own analytics, ads, or identity dataData flows from the provider to Harvv; no Visitor Data is sent to the providerUnited States

Not Sub-processors (no Visitor Data is sent): MaxMind (country database runs locally), DataForSEO, Serper, SerpApi (receive only Customer's domain or keywords), GitHub (code hosting), Toast and QisstPay (integrations receiving no Visitor Data).

Harvv

The behavioral pixel for sites you ship to real users. Harvv finds what is broken, explains it in plain English, and hands the answer to your AI.

Product

How it works What we find Pricing For agencies Docs Audit your site

Guides

All guides Case studies Dead clicks Rage clicks Average scroll depth Careless mistakes Fix Lovable SEO

Stores and ads

Shopify analytics Shopify conversion rate Shopify conversion audit Shopify bot traffic Cart abandonment rate Meta Pixel change

AI and MCP

SEO MCP servers AI crawlers list Google Analytics MCP Search Console MCP Google Ads MCP

Compare

Harvv vs Clarity Harvv vs Cloudflare Clarity vs Google Analytics Clarity vs Hotjar Clarity & privacy CIPA and tracking

Company

Partners Contact Trust & security Privacy Terms DPA
© 2026 Harvv, Inc. No recordings. No form values. Every number on this site is measured, not modelled.