Consent, Privacy and Revocation in Private B2B Networks
Private B2B networks need explicit, current and purpose-bound controls for interest, identity disclosure and revocation.
Consent in a private B2B network should be specific, informed, current and tied to a defined disclosure purpose. Expressing interest is not the same as permitting identity disclosure. The platform should fail closed, record who consented to what and when, support revocation before disclosure and clearly explain which information cannot be recalled after another authorised participant has received it.
Core privacy and consent controls
Technical enforcement, transparent records and participant responsibility must work together.
| Dimension | What to examine | Decision rule |
|---|---|---|
| Purpose limitation | State the opportunity and data involved in each consent request. | Reject broad or ambiguous permission. |
| Separate decisions | Keep opportunity interest distinct from identity-disclosure consent. | Require both where the workflow needs both. |
| Current group | Recalculate consent when a participant joins, leaves or changes role. | Invalidate stale consent after material group changes. |
| Revocation | Allow withdrawal before disclosure and record the effect immediately. | Explain that already received information cannot be technically unseen. |
Example: a new participant changes the disclosure group
Three companies consent to a controlled introduction, then a logistics partner is proposed as a fourth participant.
The prior consent does not automatically cover the new group. Disclosure remains blocked until everyone makes a current decision.
Illustrative scenario, not a customer claim or guaranteed outcome.FoundBefore's current boundary
FoundBefore's controlled model treats consent as a current per-opportunity condition and supports anonymised review before disclosure.
Participants must protect legitimately received information and follow applicable law and agreements.
Limits and responsibilities
- Revocation cannot erase human memory or external copies.
- Consent is not a substitute for a lawful processing basis.
- Platform controls do not replace participant security practices.
FoundBefore does not guarantee a match, buyer, supplier, partnership or completed deal. Identity disclosure requires mutual consent, and the controlled pilot does not replace procurement, contracting or human review.
Trustworthy private networks separate interest, disclosure permission and revocation, and clearly state the limits of each control.