Restricted beta status

Trust through explicit boundaries

LeadLeak should show why a record can be worked—and refuse when it cannot.

Current source work emphasizes tenant isolation, evidence preservation, explicit opt-in structure, fail-closed eligibility, immutable outcomes, and honest separation between built software and inactive integrations.

01

Organization-scoped access

Selected organization, active entitlement, active membership, required grant, and valid seat resolution are all required. One organization's access must never expose another's data.

02

Evidence before contact

Source, funnel, notice, consent, screening, suppression, policy, assignment, and audit context remain separate durable facts.

03

Fail-closed eligibility

Missing, pending, failed, unavailable, expired, suppressed, revoked, or policy-held records are not presented as callable.

04

Data minimization

Funnels use approved fields and reject prohibited sensitive data. Free text is not a license to collect health, financial-account, government-ID, or underwriting data.

05

Human review remains real

Structural validation is not legal, supervisory, privacy, compliance, product, or release approval.

06

No invented actions

The product must not claim it sent, called, booked, tracked, charged, or recovered revenue unless an authorized system actually performed and recorded that action.

Current boundary: source-only and synthetic readiness does not authorize real leads, live Sonera traffic, outreach, pixels, payments, customer operation, or deployment.