Check a Partner’s Authority to Share Contact Details

Review purpose, source rights, notice and downstream controls before accepting partner contact data, without assuming consent or unrestricted reuse.

10/23/20263 min read

Cedar-to-Birch transfer is held because authority for disclosure and promotion is unresolved.
Cedar-to-Birch transfer is held because authority for disclosure and promotion is unresolved.

A partner offers to send you a spreadsheet of its customers who might need your service. The commercial relationship may be genuine, but the proposed transfer still needs a defined purpose and authority. A partnership agreement does not automatically tell you what individuals were told, what data may be shared, or how your organization may use it afterward.

Review the proposed sharing before receiving the file where possible. The practical output is a purpose-and-authority checklist covering both the partner's disclosure and your intended use. Do not assume the same permission or basis resolves both sides.

Describe the transfer precisely

Identify the supplying organization, receiving organization, data categories, people affected, purpose, intended channel, storage location, access group, and onward sharing. Distinguish a one-person requested introduction from a recurring bulk transfer of customer records.

The ICO's data-sharing code addresses fair, lawful and accountable sharing, and notes that consent is not the basis for every sharing activity. The code is under review following legislative changes. A qualified reviewer should determine current requirements and the appropriate basis for the actual arrangement; neither assume consent nor assume it is always the only possible route.

Do not request unnecessary sample rows to prove that the partner has valuable contacts. Begin with process documentation and synthetic examples when those are sufficient for evaluation.

Ask the partner for evidence, not reassurance

A useful checklist asks what was collected, for what original purpose, what people were told about the proposed recipient and use, what restrictions apply, and how current preferences are enforced. Request the relevant notice or agreement version through the authorized owner.

Also establish how corrections, objections, deletion decisions, and complaints will flow between organizations. A transfer that is accurate on day one can become unsafe if neither party knows how to propagate a later change. Define accountable contacts and secure routes for those updates.

Check source restrictions and onward-sharing limits. The partner may itself have obtained the data under a license that restricts redistribution. Its willingness to share does not prove that it has authority to do so.

A fictional sharing review

Fictional Cedar Maintenance proposes giving partner Birch Scheduling the work emails of customers who attended a service review. The stated goal is to promote Birch's scheduling product. The review discovers that the service-review notice described Cedar's maintenance administration but did not establish the proposed partner marketing use.

  • Proposed data: named customer contacts and work emails.

  • Original purpose: Cedar's service review.

  • New recipient and purpose: Birch's promotional outreach.

  • Evidence gap: authority and transparency for that transfer and use are not established.

  • Decision: do not accept an active marketing file; seek qualified review and consider an appropriately authorized alternative.

One alternative might be a recipient-requested introduction through an approved process. Another may be no transfer. The example does not authorize the partner to send a new promotional message merely to obtain permission for your company.

Control an approved transfer at both ends

If the arrangement is approved, specify the minimum fields, recipient roles, transmission method, retention, and permitted actions. Verify the recipient before sending and avoid broad shared links. Document the received version and restrictions so the file cannot become an unrestricted prospect list later.

Keep the shared source label and evidence references in your system. Do not relabel the records as directly collected. Separate technical receipt from activation: a file can arrive successfully while its records remain ineligible for a particular campaign.

Test the correction and stop process with synthetic records. Confirm that a restriction received by the partner reaches your active systems and that your organization can return a relevant update without disclosing unrelated contacts.

The final decision should explain what may be shared, why, with whom, for which purpose, under which conditions, and who verifies ongoing controls. A trusted partnership is a reason to have a clear process, not a reason to skip it. If either side cannot explain the authority or boundaries, keep the transfer or intended use paused.

If you are also choosing research access, ask about Leads Automation’s independent Sales Navigator offer at US$15/month on WhatsApp. Confirm the available plan, eligibility and terms before ordering; this is not LinkedIn’s official price or an assurance that any particular integration is included.

Sources and scope

Related guides