Data Collection
HowdyGo processes two distinct groups of people differently. This page explains what we collect, from whom, and why.
TLDR; We collect personal data from editors (your team members who sign in to HowdyGo) because they have an account with us. We do not collect personal data from viewers (the prospects and customers who watch your demos) unless you explicitly choose to identify them through lead capture, URL parameters, or the SDK.
Editors
Editors are Admins and Editors within your organization who sign in to HowdyGo to create, edit, and manage demos. Because they hold an account with us, we collect the personal data needed to operate the service.
What we collect from editors:
- Name and email address (used for authentication, team management, and support)
- Authentication identifiers from your identity provider (Google, Microsoft, or your SSO provider)
- Screen recordings captured through the Chrome extension, but only while recording is actively running
Editor data is stored in our production database and treated as confidential. We never sell this data or use it for advertising.
Viewers
Viewers are the end audience of a demo: prospects, customers, or visitors to your website. By default, HowdyGo does not collect personally identifiable information about viewers. We do not know their name, email, IP address, or any other identifier unless you deliberately provide one.
What we collect from viewers by default:
- Anonymous session events (demo opened, step progressed, demo completed)
- Aggregate analytics such as impressions, engagements, and completion rates
- A session identifier used only to stitch together events from the same viewing session
No persistent cookies are set on viewers’ browsers that identify them across sessions, and no third-party advertising trackers are loaded on demo players.
When viewer data becomes identifiable
A viewer only becomes an Identified Viewer if you take one of these actions:
- Lead capture form — the viewer submits a lead capture form inside the demo. The fields you configure are stored in HowdyGo and exportable by your team.
- Email URL parameter — you share a demo link with
?email=viewer@example.com(typically from your email platform). - SDK identification — you call the HowdyGo SDK on a logged-in page in your own product to associate a viewer with an email.
- Third-party integrations — if you connect a CRM or analytics tool (HubSpot, Salesforce, Attio, Segment, etc.), identifying data may be passed to those tools according to their own privacy policies.
In every case, the decision to identify a viewer is yours. HowdyGo never enriches viewer data from external sources.
Data type summary
| Data Type | Editors | Viewers (default) | Viewers (if identified) |
|---|---|---|---|
| Personally Identifiable Information (PII) | ✔️ | ❌ | ✔️ (only what you collect) |
| Credit Card Information | ❌ | ❌ | ❌ |
| Personal Health Information | ❌ | ❌ | ❌ |
| Session and engagement analytics | ✔️ | ✔️ (anonymous) | ✔️ |
Billing is handled by our payment subprocessor and payment card details never touch HowdyGo’s systems.
Controlling viewer data
If you prefer that no viewer PII is ever stored in HowdyGo, you can:
- Skip lead capture forms, or send submissions directly to your CRM via integrations
- Avoid passing
?email=parameters in demo links - Use a third-party integration so identifying data flows straight to your own systems