Skip to content
Validated Raw Data Leads
Data Provenance

Where records come from, documented per record.

Data Provenance names the origin of every record and the consent behind it: the capture source, the consent language shown to the consumer, the timestamp and the IP. Each record is defensible on its own, not just in aggregate.

Provenance, validated.

Why provenance

Documented source. Defensible records.

Provenance is what lets a buyer use a record with confidence. The source, consent language, timestamp and IP travel with each record so the contact is defensible, not just asserted.

Compliance posture: Loyalty LTD sells personal information as defined by the CCPA. Each record carries documented opt-in and TCPA consent, including the consent text presented and a timestamp. These are not credit bureau, FCRA-covered or pre-screened records.

What each record carries

  • Contact name and phone number
  • Demand category
  • Service area state and ZIP
  • Capture source and placement
  • Consent timestamp
  • Consumer IP
  • Consent language shown
  • TCPA consent record

Illustrative fields only. Validated Raw Data Leads does not display real consumer information on the public website.

Controls

Buyer-configurable provenance.

01

Source Disclosure

Each record names its capture source and placement.
02

Consent Records

Consent language shown and timestamp carried per record.
03

IP Capture

Consumer IP recorded with the consent event.
04

Category Context

Records associated with demand category and geography.
05

Compliance Documentation

Privacy-compliance expectations documented per campaign.
06

Buyer Workflows

Structured for downstream use in your CRM or workflow of choice.
At scale

How provenance holds across many brands and markets.

Provenance for a portfolio is a documentation problem as much as a data problem.

01

Per-Record Source

Every record carries its own capture source, not just a campaign label.
02

Brand-Level Campaigns

Separate record streams per brand within a portfolio while reviewing performance centrally.
03

CRM and Intake Workflows

Common delivery integrations support centralized CRM intake across the organization.
04

Consent Documentation

Consent language and timestamp records captured per applicable requirements.
05

Source Transparency

Documented campaign and traffic-source attribution for enterprise-level review.
06

Roll-Up Reporting

Record performance reviewable per market and brand and consolidated across the portfolio.
FAQ

Answers, validated.

Can provenance programs run across a national multi-brand footprint?+

Yes. Campaigns can be structured per brand and market with delivery routed to the appropriate intake team, and reporting consolidated across the portfolio.

Are records opt-in?+

Records are collected through consented intake where the consumer agreed to be contacted, with the consent language and timestamp carried on each record.

Is this credit bureau or pre-screened data?+

No. These are opt-in consumer records. They are not credit bureau data, FCRA-covered consumer reports, or pre-screened lists.

Can I receive records into my CRM?+

Common delivery workflows are supported. Integration specifics are agreed at the campaign level.

Does Loyalty LTD sell personal information under CCPA?+

Yes. Loyalty LTD sells personal information as defined by the CCPA. You can opt out at our Do Not Sell page.

Do you guarantee every record converts?+

No. Consumer behavior varies. Provenance documents the consent and source behind a record but does not guarantee outcomes.

Ready when you are

Build your next data program.

Validated Raw Data Leads supplies raw and enriched opt-in data records for national multi-location operators, PE-backed platforms, multi-brand roll-ups, networks and data teams across the United States.

Your next record. Validated.