Privacy Policy
Last updated September 27, 2026
This policy explains what data Events Lead Capture collects, why, and what you can do about it. There are two parts. One covers this marketing site, eventsleadcapture.com. The other covers the Events Lead Capture product: the dashboard at app.eventsleadcapture.com and Capture by Events Lead Capture, the mobile app that exhibitors use to capture leads. The rules are different for each, so we keep them separate below.
We keep this plain on purpose. If something is unclear, email us and we will explain it in real terms, not legalese.
What we collect on this site
This site collects little. If you fill out the contact form, we collect what you type. Beyond that, we collect anonymous, aggregate analytics about how the site is used.
Like any site, we are also hosted on infrastructure that keeps standard server logs.
- Contact form: the name, email, company, next-show timeframe, and message you submit.
- Analytics: page views and aggregate usage data, via Google Analytics and Plausible (see Cookies and analytics below).
- Server logs: our host records standard request data, including IP addresses and browser user agents.
How we use site data
We use your contact-form details to reply to you and set up a pilot. Nothing else.
When you submit the form, we send the details to Events Lead Capture's founders by email through Resend, our email service. Resend processes the message so it can be delivered to us.
We do not sell this data. We do not use it to build advertising profiles.
Hosting and server logs
This site runs on Vercel. As part of serving the site, Vercel keeps standard server logs that include things like IP addresses and user agents.
These logs are normal infrastructure data. They help keep the site running and secure. We do not use them to track you across other sites.
The Events Lead Capture product and attendee data
The Events Lead Capture product helps exhibitors capture leads at trade shows. When booth staff scan an attendee's badge, the product handles that attendee's data: name, company, contact details, and the answers to the qualifying questions the exhibitor set up.
This attendee data comes from the badge provider the attendee registered with for the event. It is first-party data the attendee already consented to share at registration.
We process this data on behalf of the exhibitor who runs the booth. We do not use it for our own marketing, we do not sell it, and we do not append data from third-party sources.
Attendee details that appear on screen in the dashboard or the Capture app can be included in session recordings made for product analytics. See Product analytics and session recording below.
Capture accounts, camera access, and device storage
Capture uses an account provided by your organization. We process account identifiers, names, email addresses, organization membership, and permissions to sign users in and give them access to their assigned events.
With camera permission, Capture reads the code on an attendee's badge. The app sends the decoded badge value for lookup and lead capture; its scanner does not upload camera photos or video.
Event content, captured leads, form answers, and pending scans can be stored on your device so work can continue when connectivity is interrupted. Pending data is sent to the Events Lead Capture service when it syncs. The app also stores sign-in tokens in the device's protected credential storage.
The service records operational information such as requests, scan results, errors, and response times to operate, secure, and troubleshoot the product. These records can be associated with the signed-in user and organization.
Product analytics and session recording
We use PostHog, a product analytics service, in the dashboard and the Capture app. It helps us understand how the product is used, find and fix errors and crashes, and decide what to improve. PostHog is not used on this marketing site; the Cookies and analytics section above covers this site.
Analytics data is linked to your account. When you sign in, we tell PostHog your user ID, name, email address, role, and organization, so we can see how each account and organization uses the product.
PostHog may also record sessions of your use of the dashboard and the Capture app. A session recording captures what appears on screen and how you interact with it, so we can see where people get stuck and reproduce problems. Recordings can include lead and attendee details shown on screen, such as names, contact details, badge information, and answers to qualifying questions. Recordings can also include which network requests were made and how long they took, and in the dashboard, browser console messages. They do not include the contents of those requests.
We exclude secrets from analytics and recordings. Passwords, sign-in tokens, password-reset and verification links, badge-provider and CRM credentials, and event API keys are masked or removed before anything is sent to PostHog.
PostHog stores this data in the United States and processes it on our behalf as our service provider. In the dashboard, PostHog uses first-party cookies and your browser's local storage to recognize returning browsers. The Capture app stores an analytics identifier on your device.
We use this data only to operate and improve Events Lead Capture. We do not use it for advertising, we do not sell it, and we do not use it to track you across other companies' apps or websites.
- Usage events: screens and pages viewed, taps, clicks, and form interactions, and product actions such as signing in, scanning a badge, submitting a lead, and syncing queued data.
- Errors, crashes, and performance data, such as load times.
- Device, browser, and app information: device model, operating system, app version, browser type, and a device or browser identifier.
- Your IP address, which PostHog uses to estimate your approximate location.
- Session recordings of the dashboard and the Capture app, as described above.
Who controls the data: roles
Two different roles apply, depending on the data.
For this marketing site, the contact form and server logs, Events Lead Capture is the controller. We decide why and how that data is used.
For attendee data captured in the product, the exhibitor is the controller and Events Lead Capture is the processor. The exhibitor decides what to collect and why. We handle the data on their instructions and to provide the service.
For product analytics about how signed-in users use the dashboard and the Capture app, Events Lead Capture is the controller. Attendee details that appear in session recordings remain data we process for the exhibitor, and PostHog handles them as our subprocessor.
AI cleanup
As each lead arrives, AI normalizes and cleans the record. It fixes typos, standardizes formatting, and fills in fields that were captured but messy, so no one spends next week tidying a spreadsheet.
This works on the consented first-party data already in the lead. It does not pull in personal data from outside sources, and it does not append third-party data to a record.
How long we keep data
We keep data only as long as we need it for the purpose it was collected, then we delete or anonymize it.
Contact-form messages are kept while we are in touch and for a reasonable period after. Attendee data in the product is kept for the exhibitor as long as their account needs it, and we follow their instructions on deletion. If you want a specific retention period for your account, ask us and we will confirm it.
Session recordings are kept for a limited period set in our PostHog account and are then deleted automatically. Other analytics data is kept only as long as it is useful for improving the product. You can ask us to delete analytics data about you at any time.
Your rights
Depending on where you live, you may have rights to access, correct, or delete your personal data, and to object to certain uses. We honor GDPR and CCPA-style rights, and we do not sell personal data.
If you contacted us through this site, or you are a visitor, send your request to us directly using the email below.
If you use Capture through your organization, contact your organization administrator or the privacy email below for help with access, correction, or deletion of your account data. We will coordinate with the organization where its instructions are needed.
If you are an event attendee whose data was captured at a booth, the exhibitor is the controller of that data. Send your request to that exhibitor, and we will help them respond as their processor. If you are not sure who that is, contact us and we will point you to the right party.
Contact
For any privacy question or request, email privacy@eventsleadcapture.com. We'll respond as quickly as we reasonably can.