Privacy policy

1. What we collect

We collect the information needed to run the account and the product:

• Account data — name, email, password hash, company name, billing address, and teammate invites.
• Business profile — website URL, service ZIP codes, industry, and the ICP notes you confirm in onboarding.
• Workspace records you add — contacts, pipeline notes, CSV uploads, enrichment results, exports, quotes, jobs, invoices, messages, photos, and field check-ins when you use those tools.
• Connected systems you authorize — for example HighLevel, QuickBooks, Stripe, Square, Google, Zapier, Angi, or CallRail. We receive the records those connections are set up to sync.
• Payment metadata — Stripe customer and subscription IDs. We do not store raw card numbers. Stripe processes cards. Invoices your business sends through Operate are paid in your own QuickBooks, Stripe, or Square account.
• Support tickets — the subject, feature, urgency, and message you write, plus the browser, page path, and screen size captured with the ticket so we can troubleshoot.

2. How we track use

IntentGrid.com and the signed-in application record first-party product analytics so we can see which pages and features are used. That tracking includes:

• Page views, including the path, referrer, and campaign parameters such as utm_source and utm_campaign when they are present in the address.
• Clicks on links and buttons, including short visible text and any analytics label on that control.
• Scroll depth and time spent on a page.
• A random anonymous identifier and a session identifier stored in your browser. A session resets after about 30 minutes of inactivity. When you are signed in, the server attaches those events to your user and workspace. The browser cannot choose that account association.

We do not record this product analytics on Platform Ops admin screens or on token links that carry a credential in the URL. Analytics is best effort: a failed analytics call does not block the product.

On IntentGrid-hosted pages we may also load an identity pixel. That pixel is for IntentGrid.com and the application on our hosts. We do not load it on a customer's own Operate website domain.

If you install IntentGrid Pixel on your website, that snippet is yours to control. It compares visitors with identity data and, when a match succeeds, can write a contact into your pipeline. Those visitor records belong to your workspace. You decide whether CRM ingest is on, and you are responsible for notices and choices on your site.

3. How we use it

We use this information to:

• Create and secure your account, and invite teammates you add.
• Deliver Priority Contacts, ZIP estimates, and the daily plan for the markets you select.
• Run Pixel, enrichment, AI tools, reports, exports, integrations, and IntentGrid Operate.
• Send transactional email, such as password resets, receipts, and product notices.
• Answer Support tickets, prevent abuse, and keep the service reliable.
• Understand which pages, clicks, and features people use, and improve the product from that usage.

We do not sell your account data. We do not sell contact lists taken from your workspace to other IntentGrid customers.

Intent signals we show you are commercial scores. They are not consent to contact those people. You remain responsible for TCPA, DNC, and any industry outreach rules.

If you are a customer of a business that uses IntentGrid, that business controls the records in its workspace. Contact that business about its quotes, messages, and site. This policy covers IntentGrid accounts and IntentGrid.com.

4. Cookies and browser storage

The application stores a sign-in token and the active workspace in local storage so you stay signed in. Product analytics stores the anonymous identifier and session identifier described above. Checkout and a few desks may keep a draft in local storage until you finish or clear it. The identity pixel on IntentGrid-hosted pages may set its own cookies. Tenant websites that install IntentGrid Pixel are controlled by that tenant.

5. Sharing

We share data with processors who help us run the service — hosting (Vercel), database and auth (Supabase), payments (Stripe), identity and intent data providers that power Pixel and Priority Contacts, email or SMS providers you enable, and CRM or accounting connectors you authorize. We share data if required by law.

6. Retention

Account, workspace, and billing records stay while the account is active and as long as needed for tax, dispute, and security logs. Product analytics is kept to measure and improve the service. After a deletion request we remove or anonymize personal account fields, except records we must keep by law or for fraud prevention, billing disputes, and security.

7. Data deletion requests

Request deletion of your IntentGrid account or of personal data in that account by opening a customer support ticket inside the application. That ticket is how we receive and track the request.

1. Sign in to the IntentGrid account that holds the data.
2. Open Support from the portal sidebar.
3. Choose New ticket.
4. Set the subject to a data deletion request. In the details, include the email on the account and what to delete: the whole account, specific contacts, uploaded files, Pixel visitor records, market and ZIP selections, or product analytics tied to the account.
5. Submit the ticket. You can reply on the same ticket if we need more detail.

We act on the request for the signed-in account named in the ticket. Profile fields you can edit yourself stay available in the portal, and you can reset your password there. Deleting the IntentGrid account does not delete records that remain in systems you control, such as your own QuickBooks, HighLevel, Stripe, or Square account.

8. Children

IntentGrid is a business product. We do not knowingly collect information from children under 16.

9. Contact

Privacy questions and deletion requests go through a Support ticket in the application, as described above. See also Terms of service and Market availability.