Trust & data posture

Every external record in CitedLeads arrives through a licensed provider adapter: a contractual path with defined usage terms, collection standards, and a contact at the other end. Provider work is gated on signed agreements (our internal G-LEGAL gate); until then the product runs on synthetic demo data and says so.

This is a deliberate constraint, not a missing feature. Licensed sourcing is what lets us answer “where did this come from” for every lead, and what makes suppression and deletion requests actually enforceable.

Every credit event (monthly grant, LTD pool release, reveal, support credit-back) is written to an append-only ledger you can inspect in the product. Balances are derived from the ledger, not stored beside it, so the number you see is always the sum of entries you can audit.

This exists because credit-metered pricing has a trust problem: buyers cannot verify what a vendor’s counter actually did. A visible ledger turns “trust us” into a record.

You can suppress any lead record. Suppressed records leave your views and monitoring immediately. Where our providers maintain suppression lists, we propagate deletion requests to them so a suppressed contact does not silently return through the next query.

Credit-ledger entries are preserved through suppression because they are the accounting record of what happened: they record the action, not the person.

Contact fields stay hidden by default and unmask only through the metered reveal path, and only for the organization that paid. Exports are minimized: you get the fields needed for the next approved workflow, not a bulk data dump.

Deterministic scoring means no opaque model decides what you see: the same input produces the same score, and the rubric is printed on every brief.

No scraping

no crawlers, no delegated worker clusters, no browser automation, no CAPTCHA bypass, no fake accounts.

No browser extensions

there is nothing to install, and nothing that rides on your browser session.

No cookies or session reuse

we do not collect your browsing data, and the product never touches your LinkedIn or any other personal-account session.

No credentials

CitedLeads never asks for a password or session token to another platform.

No outbound messaging

the product produces briefs and exports; it does not send messages on your behalf.

No phone reveals

contact reveals cover business email only.

In negotiationProvider contracts: in negotiation. The product is demo-mode until they are signed.

Pending reviewNamed sub-processor list and formal DPA: pending counsel review.

Not commissionedSecurity review artifacts (penetration test, formal SOC 2 posture): not yet commissioned; we say so rather than badge it.

PlannedPublic API: schema exists in the entitlement layer; documentation ships when the API ships.

Found a data or security issue? Reach us through the contact page. Deletion and suppression requests go through the same path while the formal DPA is pending.