Trust
Where our data comes from, and how we handle it
GTM Scoop has compiled US company and contact data for GTM teams since 2004. This page sets out the sources, how records stay current, how anyone can opt out, and the rules our customers agree to.
Datasets and coverage
| Dataset | Records |
|---|---|
| US companies | 17.4M companies |
| Contacts | 120M+ contacts (60M+ decision makers) |
All coverage is US only.
Where the data comes from
We compile records from public records, government sources, licensed third-party providers and our own research — 750+ sources over 20+ years — and normalize them through one quality engine. Records can include names, job titles, work email addresses and phone numbers, employers, company details and address information.
Records are refreshed over time, and a record is removed from what we license when a verified opt-out or deletion request applies to it.
How enrichment matches are made
When you enrich a list, each of your records is matched against our data on these signals, checked in this order:
1. Phone number
Tried first
2. Email
Tried next
3. Address + ZIP
Tried last, and required with a phone or email for company data
Every matched record keeps the signal it was matched on (phone, email or address), so you can see how it was found, and you see the coverage before you commit.
How to opt out or see what we hold
Email support@gtmscoop.com with your name and the address, phone number or email we should look up. We suppress your record from what we license, and keep a minimal record of the request so you are not added back.
For cookies and analytics on this site, use . We treat a Global Privacy Control signal from your browser as an opt-out.
How we protect accounts and data
- Every connection to GTM Scoop and its API is encrypted in transit (HTTPS), and browsers are told never to fall back to an unencrypted connection.
- There are no passwords to steal: you sign in with Google or a one-time code we email you. Codes expire after a few minutes, allow only a few tries, and are stored only as one-way hashes.
- API keys are shown once, when you create them, and stored only as one-way hashes. You can revoke a key at any time, and signing out of every device also disconnects your API keys and connected AI apps.
- Your saved audiences, uploads, purchases and enrichment runs belong to your account: our servers check every request against the signed-in account, so another account cannot open them, even with a direct link.
- Admin tools need an administrator role that our servers check on every request, and staff access to a customer's records is written to an audit log.
- Sign-in, code requests and the API are rate-limited to stop guessing and bulk scraping.
- Card payments are handled by Stripe; card numbers never reach our servers.
Found a security issue? Please email support@gtmscoop.com (also listed in our security.txt) instead of testing against the live service.
Compliance
- Because we license information about people we have no direct relationship with, we are a data broker under certain state laws, and we register with state data broker registries where the law requires it.
- Licensing records to customers is a sale of personal information under the California Consumer Privacy Act and similar laws; we say so in our Privacy Policy and honor opt-outs of sale.
- Customers agree to use the data lawfully, including honoring Do Not Call and marketing opt-outs.
- We do not sell or share for advertising the account information, uploaded data or messages of our own users, and this site uses no advertising cookies.
The full terms are in our Privacy Policy, Terms of Use and Cookie Policy.
The company
GTM Scoop is the trading name of M & C Information Systems, Inc., as our Terms and Privacy Policy state, serving US GTM teams since 2004. More on our story, or book a free data review.