Gohvio subprocessors
Last updated 11 November 2026
These are the companies that process data on Gohvio's behalf to run the service. We give 30 days' notice before adding any subprocessor that touches customer data.
Services you choose to connect, such as HubSpot, Salesforce or Outreach, are your providers, not our subprocessors. Gohvio reads from them with your permission. We also use some of these same companies to run our own business. Those are listed below, and they are separate from anything you connect.
| Company | What we use it for | What data it receives |
|---|---|---|
| Anthropic | The AI model behind Lumi and policy-document import | Up to 50 rows of an uploaded file, including names and contact details. Columns holding card, bank or government ID numbers, passwords, dates of birth or sensitive categories such as health are left out. We detect these by column name and pattern, so something typed into a free-text column such as notes can still reach the model. With more than one file loaded, Lumi also sees Gohvio's comparison of them: file, column and guardrail names, record counts and dollar totals, not the other files' rows. Also your Lumi questions and any images you attach, and your saved rules and their results; the full text of policy documents you import; counts and summaries from connected CRMs |
| Supabase | Database, sign-in, and the functions that connect to your CRM and send emails | Account email, saved rules and imported policy statements, CRM connection keys, plan and usage records, Lumi questions (scrubbed) and job titles, hashed AI audit log, in-app usage analytics, and website visit records if you accept analytics. CRM data passes through in memory; copies of your CRM records aren't saved. Impact snapshots of each scan (counts, dollar totals, findings, and for each deal with a recognised stage a one-way pseudonymised ID with its stage, outcome and amount) for 13 months. Fireside registrations (name, email, company, your answers, the campaign tag on your link) for 12 months after the event; newsletter sign-ups; Fireside survey answers for 12 months after the event (with your registration when you answer from the email link; without a name or email from a posted link); the IP address of each sign-up, topic or feedback attempt for 30 days. Fireside topic submissions for 12 months. The Fireside pages also ask Supabase for the event's public details on load, before any cookie choice. |
| Railway | Hosts the Gohvio app and its server, and serves our website visit tracker | Uploaded files, deleted once read; your working data held in memory for up to 24 hours without activity; requests from our visit tracker on gohvio.io if you accept analytics |
| Stripe | Payments | Billing name, email, payment details, plan |
| Resend | Sends our emails | Your name and email, and email content such as sign-in links, trial emails and receipts. Fireside confirmations, reminders, thank-you (with a link to a short feedback survey) and recording emails, and the newsletter confirmation. For a topic you send: the thank-you email to you, and one email to Emily at Gohvio with your name, email, role, guest-or-covered choice and what you wrote. |
| HubSpot (our own account, not the one you connect) | Our own customer records and website forms | Your name, email, company, job title, trial and plan status, form submissions, and website visits. Fireside registrations: which events, the date, your answers, the campaign source and whether you subscribed to the newsletter. Fireside topic submissions: your name, email, the date and, for a new contact, a job title from your role. Not what you wrote. |
| Zoho | Our email inbox | Anything you email us |
| Calendly | Booking a call with Emily | Your name, email and anything you type when you book. Only if you use a booking link. |
| Sign in with Google, if you choose it; Google Analytics on gohvio.io; reCAPTCHA, if you open the write-back pilot form. Web fonts came from Google until 26 September 2026 and are now served from gohvio.io | Your Google sign-in identity; website usage; and, if you open the write-back pilot form, your IP address and browser, where reCAPTCHA also sees how you interact with the page | |
| Cloudflare | Delivers gohvio.io, and measures it with Cloudflare Web Analytics on every page | Website visit data such as IP address, pages viewed, referrer and page load time. The measurement is added at Cloudflare's edge and does not wait for your cookie choice |
On AI
We do not currently send customer data to any AI provider other than Anthropic.
On website tracking
As of 25 September 2026, the three we control wait for your consent. HubSpot's script is not added to the page until you accept analytics, our own site analytics does not start until you accept and stops the moment you withdraw, and Google Analytics stores nothing until you accept. Since 5 October 2026 our own site analytics is a visit tracker served from app.gohvio.io, added to the page only after you accept, and it does nothing at all if your browser sends Do Not Track or Global Privacy Control. Google Analytics' tag does load on every page and sends Google a cookieless signal that a page was viewed; that one does not wait. The web fonts used to be a second one that did not wait: they were loaded from Google on every page, so Google saw your IP address and browser whatever you chose. Since 26 September 2026 they are served from gohvio.io and Google is no longer involved in them. That is what we found when we checked every page of the build rather than a few. One more does not wait and is not in our code at all: Cloudflare, which hosts this site, injects its Web Analytics beacon at the edge on every page. It sees the page, the referrer, your IP address, your country, your browser, operating system and device type, and the load time. We measured no cookie from it. Because it is added after our code, no check of our code can find it, which is how it went undisclosed until now. On the write-back pilot page a HubSpot form used to load on arrival, bringing Google reCAPTCHA and a cookie with it; that form now waits for you to press a button. Before 25 September 2026, HubSpot's tracking and our own analytics both ran on every page without waiting, and this page said so.
On where your data sits
We're confirming each provider's region and will publish it here. We'd rather leave it blank than guess.
Questions about anything on this page? Talk to us, and we will complete your organisation's security questionnaire.