05 — Trust

Built for scrutineering.

In racing, scrutineering is the inspection a car passes before it's allowed on track. This page is ours. If your job is reviewing call sources before they run on your network, here is our posture — consent, data, traffic quality, disputes — in plain language, with the paper trail to back it.

Consent & TCPA posture

Consent-first, by design.

The core unit we sell is a consumer-initiated phone call — a person choosing to dial. Everything around that moment is engineered so nobody ever has to argue about whether they meant to.

C-01

Inbound by default

Our primary unit is an inbound call the consumer places from a page that states plainly what the service is and what happens when they call. The consumer dials. That is the cleanest expression of intent the industry has, and it's the one we built the business around.

C-02

Written consent, captured properly

Where a form is involved, consent language sits next to the submit action — plain English, naming who may contact the consumer, by what means, and about what. No pre-checked boxes, no consent buried in a terms page, no gray-on-gray fine print. Prior express written consent is captured where the law requires it, and the capture itself is recorded.

C-03

The property says what it is

Every property discloses its identity and its role — a referral service connecting consumers with independent licensed providers — before the call happens, not during it. No impersonating a local contractor, an insurer, or a government program. A consumer who feels tricked is a complaint, a chargeback, and a brand problem; we don't buy growth with any of those.

C-04

Recording notices

Where calls are recorded, that's disclosed — on the property and at the start of the call where required. All-party-consent states get all-party treatment. Recordings exist to resolve disputes and improve intake, and they're handled under the same retention discipline as everything else.

C-05

Built for the strictest reading

TCPA rules move — the one-to-one consent rule was written, litigated, and vacated before it ever took effect. We don't build to the current minimum; we build consent flows to the strictest plausible reading, so a rule change is a config note, not a crisis. When your compliance team's requirements exceed the law's, send them over — that's a normal Tuesday here.

Data handling

Every record carries its receipts.

D-01

Consent trails stored per record

Each lead and call record stores its own evidence: timestamp, source page, the exact version of the consent language displayed, and the submission as the consumer made it. The trail is attached to the unit and travels with it — so when a reviewer asks "show me consent for this record," the answer is a lookup, not a reconstruction.

D-02

State privacy rights honored

Access, correction, deletion, and opt-out requests are honored under applicable state privacy law, with recognized preference signals such as Global Privacy Control respected where required. Each property publishes its own privacy policy and its own contact for requests — and a request sent to the wrong door gets routed, not bounced.

D-03

Opt-out and deletion, propagated

A deletion request doesn't just clear a row — it suppresses the record from further use and, where the agreement requires, is passed along to partners who received it. Opt-outs are permanent by default. We would rather lose a record than argue about one.

D-04

Scoped delivery, not list-selling

Consumer data goes to partners under a written agreement, for the purpose the consumer was told about — connecting them with a provider who can help. We don't sell aged lists, we don't monetize records outside that scope, and each property's policy discloses how its data moves. If a use isn't in the agreement, it doesn't happen.

D-05

Retention with an endpoint

Records are kept as long as operations, disputes, and the law require — then deleted or de-identified. Consent trails and billing records live on the schedule the agreement defines, because they're what dispute resolution runs on.

Traffic quality standards

No junk in the stream.

Our media is bid against billable outcomes, so junk volume costs us twice — once in media, once in trust. The standards below aren't aspirations; they're how the economics only work.

Q-01

No incentivized traffic

No sweepstakes, no rewards paths, no co-registration, no "answer this survey to continue." A consumer bribed into a funnel is not a consumer with a flooded basement. Incentivized volume is the fastest way to poison a buyer relationship, and it is banned outright.

Q-02

No misleading creative

No fake countdown timers, no fabricated urgency, no impersonating insurers, utilities, or government programs, no "crews in your area" claims that aren't true. Ad-platform policy teams and state AGs read these pages — we read them first, and creative that wouldn't survive that reading doesn't run.

Q-03

A real publisher vetting bar

Affiliate and publisher traffic runs on our tracking numbers, our attribution, and our consent standards — never their own. Landing pages and creative are reviewed before launch, every publisher is attributed per-source, and a disclosure violation ends the relationship regardless of the volume it was producing. Publishers who can't meet the bar don't run.

Q-04

Filtered before it bills

Duplicates, out-of-footprint calls, and non-service traffic are identified in disposition review and excluded from billing. The billable criteria in your agreement are the filter — what shouldn't bill, doesn't, and the disposition data feeds straight back into what media we buy next.

Dispute handling

Pull the telemetry. Read it together.

Disputes here work like a stewards' inquiry: nobody argues from memory, because the black box already knows. Every unit carries its source attribution, timestamps, consent trail, routing history, and — where lawfully recorded — the call itself.

R-01

The record decides

Flag a unit inside the dispute window defined in your agreement and we pull its record — same data on both screens. Most disputes end at the record, in minutes, because there's nothing left to argue about.

R-02

Credits, not attrition

If the record supports the dispute, the credit lands on the next invoice — no wearing you down, no "let me escalate that." If the record doesn't support it, you'll see exactly why, in the data, not in a paragraph of pushback.

R-03

Disputes make the stream better

Every disputed and low-quality disposition feeds back into media buying and publisher review. A dispute isn't friction to be managed — it's telemetry we'd pay for. Partners who dispute honestly make their own stream cleaner.

What we ask of partners

The bar runs both ways.

A consumer on one of our properties is trusting the whole chain — including the last link, which is you. So we hold partners to the same standard we hold our own pages.

Licensed

Licensed and insured

Proper licensing for the trade and the geography, insurance in force, verified at onboarding and kept current. We route emergencies to professionals, not to whoever bids — no exceptions, no "license pending."

Fast

Answer like it's an emergency

Live pickup, around the clock for emergency verticals. A homeowner standing in water does not leave a voicemail — they call the next result. If your intake can't answer, the stream can't route to you.

Decent

Treat the consumer well

Show up when promised, quote honestly, do the work you said you'd do. The consumer's experience with you lands on our brand and on every partner sharing the stream — we scale the partners who make it stronger.

Accountable

Keep the loop closed

Honest and timely dispositions, consumer data handled under applicable law, disputes raised through the window rather than deducted from the invoice. The records-first model only works when both sides feed it.

For reviewers

Kick the tires.

Slipstreams is early-stage and founder-operated, with one live vertical and a deliberate growth pace — which means the person answering your diligence questions is the person who built the consent flow. Under NDA, qualified partners and network compliance teams can review property domains and live consent flows, sample unit records with full consent trails, recording and retention practices, and the published policies on each property.

Diligence and partnerships: contact@slipstreams.com  ·  Privacy requests: privacy@slipstreams.com

Questions for compliance? Ask them.

contact@slipstreams.com