solutions / vendor-sharing
Vendor data sharing
Every integration is a copy of your data sitting inside someone else’s incident response plan.
The problem
A vendor asks for a customer export to enable one feature and receives the whole record because that was the easiest query to write. Multiply by forty integrations and the honest answer to "where is our customer data" becomes nobody knows. Contracts allocate liability; they do not reduce the copies.
What Divelai does
Put the sidecar on the egress path and apply a per-destination policy. The billing vendor gets real invoice amounts and tokenised names. The support tool gets names and tokenised card data. Each integration’s data-flow map is generated from what actually crossed the wire, not from what the integration document claimed.
What this does not solve
This governs data leaving through paths you route. A vendor with direct database credentials, or an employee with an export button, is outside the request path — pair Divelai with access controls at the source.
# Per-destination policy. destinations: - host: "api.billing-vendor.example" allow: [invoice.amount, invoice.date] tokenise: [pii.person, pii.email] redact: [pci.pan, phi.*] - host: "api.support-tool.example" allow: [pii.person, pii.email] redact: [pci.pan, pii.national_id] default: deny