Masked Lead Model
No names, emails, phones, street addresses, exact postcodes, or raw flexible fields.
Marketplace scenario and buyer offer viewsTrust and compliance
LeadCore must make trust visible before buyers and suppliers operate. The public site states the data boundary; the authenticated product enforces it through roles, service guards, and audit events.
Compliance Control Surface
No names, emails, phones, street addresses, exact postcodes, or raw flexible fields.
Marketplace scenario and buyer offer viewsSource channel, supplier identity, timestamp, country pack, and consent payload remain linked.
Lead submission audit panelPlatform, tenant, supplier, buyer, quality, billing, and collection roles receive separated account areas.
Role access portalPurchases, transfers, complaints, refunds, invoices, and collection actions require events.
Compliance control gridRetention, disclosure, complaint windows, tax behavior, and allowed lead types are configured per pack.
Country and industry scope setupLead purchase, supplier credit, tenant invoice, complaint, refund, dunning, and collection states are linked.
Settlement flow preview