Compliance

Enrichment, not certification.
Here's the actual line.

Short answer: TwoCentSkips returns data from legally licensed sources, but it is not a TCPA-safe filter and it's not FCRA-permissible. Here's what that means for how you use it.

What TwoCentSkips is

A consumer identity resolution / enrichment service. We match a phone, email, or name+address against licensed telco carrier data, a B2C consumer graph, auto-owner records, and public voter files — then return the household: name, address, phones, emails, DNC flag, and available demographics.

What it is not

Not a TCPA-compliance filter. Not an FCRA-permissible consumer report. Not a GDPR privacy shield. Not a certification of anything — it's the data, with a DNC flag on it, and it's on you to use it inside the rules for your use case.

TCPA

A DNC flag is not a scrub

The Telephone Consumer Protection Act requires you to scrub your call/text list against the FTC National Do Not Call Registry (and your own internal suppression list) before a regulated campaign. Every phone record TwoCentSkips returns carries a boolean dnc field telling you if that number is on the registry — but flagging is not filtering. Loading a flagged number into your dialer and calling it anyway is still a violation.

TwoCentSkips does enrichment. It does not run the scrub. For the actual TCPA/DNC-safe filtering step — before you touch a dialer — use our sister product, which handles exactly that and nothing else.

Scrub your list at FreeDNCScrub
FCRA

Not FCRA-permissible

The Fair Credit Reporting Act governs consumer reports used for credit, employment, insurance, or tenant-screening decisions — and it requires specific disclosures and consumer-dispute processes we don't run. TwoCentSkips is a consumer identity resolution tool for skip trace, list hygiene, and marketing enrichment. It is not for credit, employment, or tenant-screening decisions. If you need FCRA-permissible data for one of those purposes, use a certified consumer reporting agency instead.

In practice

Good fit vs. bad fit

Same data, different use — one of these is fine, the other gets you a demand letter.

Good use cases

  • Debt recovery — skip tracing for collections
  • Marketing enrichment — appending household data before a campaign, DNC flags included
  • Recruiting — building candidate sourcing and outreach lists
  • Legal discovery — litigation support and asset location
  • Verification — checking whether contact info on an existing customer record is current

Bad use cases

  • Running a TCPA-regulated calling/texting campaign without a real scrub
  • Reselling enriched data to a third party without consent
  • Credit, employment, or tenant-screening decisions — FCRA-regulated purposes
  • Building a training dataset out of lookup results
  • Locating someone for stalking, harassment, or any purpose they haven't agreed to
Before you launch

Pre-campaign checklist

This is a working checklist, not legal advice. When in doubt, loop in counsel — every state layers its own rules (CCPA in California, CPA in Colorado, VCDPA in Virginia, and others) on top of federal TCPA/FCRA.

Sourcing & freshness

Where the data comes from

Four licensed sources, stitched by household: telco carrier data (refreshed roughly every 31 days), a B2C consumer graph (60–90 days), auto-owner records, and public voter files (both quarterly). We don't scrape social networks, and every record traces back to a source.

Phone → identity: 70–85%Name+address → phone: 55–70%Email → household: 40–60%

Those are hit rates, not accuracy scores — a miss (no match) is always free, so a lower hit rate on a given input type costs you nothing extra.

Questions?

For data-deletion or CCPA-style requests, use /opt-out. For anything else: hello@twocentskips.com.