The referral conversation with a privacy officer: a first-meeting agenda that settles which seat the privacy officer sits in, keeps every company's personal data out of the room, sends conflict and pay questions to their own counsel and ends in an introduction, an unpaid mention or no part

Short answer

Treat a privacy officer as someone whose duty runs to the organization they protect, not as a source of introductions. In a first meeting, settle which seat they occupy (inside one company, an outside officer for several clients, or a privacy lawyer), keep every company's personal data and compliance files out of the conversation, send the conflict and pay questions to their own counsel or employer, and agree one permitted next step: an introduction the CEO wants, an unpaid mention, or nothing.

Visual briefFull-size diagram
A vertical agenda strip of seven numbered items, seat, how you know the CEO, what SourceX publishes, conflict, pay, never in the room and next step, with the conflict and pay items tagged own counsel; beside it a locked box lists what stays out of the room, and three endings sit at the bottom: introduction, unpaid mention and no part.
The agenda on this page, shortened. Illustrative layout; no real meeting or company.

This page is for alliance managers at law and advisory firms, and for any partner whose network includes privacy professionals. It gives no legal advice and takes no position on whether any professional may accept a referral reward; their own counsel, employer or engagement terms answer that.

Who the privacy officer is, and what you are proposing

A privacy officer's job is defined by someone other than you. Under the EU's General Data Protection Regulation, the first listed task of a data protection officer is to inform and advise the controller or processor and its employees about their data protection obligations; the officer takes no instructions on how those tasks are performed and reports to the highest management level, and may take on other tasks only where they do not create a conflict of interests (paraphrase of Articles 38 and 39). Article 38(5) adds: "The data protection officer shall be bound by secrecy or confidentiality concerning the performance of his or her tasks, in accordance with Union or Member State law." In U.S. health care, HHS's summary of the HIPAA Privacy Rule says a covered entity must designate a privacy official responsible for developing and implementing its privacy policies and procedures (paraphrase).

Those duties shape every referral conversation. What you propose is narrow: that the privacy officer might mention SourceX to a CEO they know, or make an introduction that CEO wants. What you never propose is that they draw on what their role showed them.

SeatDuty runs toWhat they know about companiesWhere a referral role could collideWho reviews it first
Staff privacy officerTheir employerIts processing, systems and incidents, in depthTheir role is to advise the company on exactly the records a license would touchTheir employer's policy and, for the company itself, the CEO
Outside privacy officer for several clientsEach client under its contractEach client's processing, confidentiallyConfidentiality to every client; advising on privacy while gaining from a licenseTheir engagement terms and their own counsel
Privacy lawyer at a firmThe firm's clientsPrivileged and confidential client mattersProfessional rules on confidentiality and conflictsThe firm's ethics or general counsel

The privacy-role first-meeting agenda

Thirty minutes, seven items, in this order. Each item names who answers and what goes in your note. Nothing about a particular company's data is discussed at any point.

#MinutesQuestionWho answersWhat you record
13"Which seat are you in for this conversation?"The privacy officerStaff, outside officer or lawyer; no client names
24"Do you know any CEO you might mention this to through your privacy role, or some other way?"The privacy officerOnly the channel: through the role, or outside it
35What SourceX publishes about its process, read from its pagesYouWhich published pages you shared
45"Does any role you hold limit you from introducing a company, or from advising it afterward?"Their counsel, employer or engagement terms, laterThe question and who will answer it
55"Would any reward be acceptable under your rules or contracts?"The same reviewers, laterThe question; no answer from you
64What you will never ask them for (list below)YouThat the list was read
74Which of three endings fits, and who acts nextThe privacy officer, after reviewEnding, date, open questions

Item 2 decides most of the meeting. A CEO the officer knows only through their privacy role is a CEO whose company's processing they hold in confidence. Whether they may mention SourceX to that CEO at all is a question for their reviewer, and nothing they learned in the role travels into your note.

Item 3 stays on published sentences. SourceX's process page says: "You approve the scope and terms and sign before any data is delivered." Under the confirmations a company gives, it says: "You have the rights to license the data, personal data was collected lawfully (GDPR/CCPA), it hasn't been licensed for AI training before, and it wasn't created or altered with AI for the sale." A privacy officer will want more than that, which is the right instinct; their questions go to SourceX directly, by the company, once the CEO wants the conversation. You add nothing to SourceX's published words, and the reasons are set out in what partners should never promise about privacy.

Items 4 and 5 end with a question, not an answer. You can supply the facts a reviewer needs. Section 4 of SourceX's terms says the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation", so a company receives the same amount whether or not anyone introduced it. The sample Channel Partner Agreement names the Partner as an individual or an entity, so a firm can sign. What the published terms do not settle is how SourceX treats a partner who wants no reward; SourceX decides that, and a privacy officer who would only take part unpaid should ask SourceX in writing first. For a multi-country network, the jurisdiction review register lists whom each person should ask.

What never enters the room

Your agreement with SourceX already draws the line. Section 4.2 of the sample Channel Partner Agreement says: "This Agreement gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems." For a meeting with a privacy officer, read it wider:

  • Personal data in any form, including samples, screenshots or "anonymized" extracts.
  • Records of processing, data maps, impact assessments, retention schedules and consent records.
  • Incident and breach history, regulator correspondence and audit findings.
  • The names of an outside officer's clients, unless that client has agreed.
  • Legal advice given to any company, and anything privileged.
  • Any view on whether a company's records could be licensed; that is for the company's counsel and SourceX's rights review.

Confidentiality, conflict and compensation questions for their own counsel

Hand the privacy officer these questions to take away. You do not answer them, and the meeting note records only that they were asked.

AreaQuestion for their reviewer
ConfidentialityDoes the duty attached to my role cover the fact that I know this CEO, or only what the role showed me about the company?
ConfidentialityIf the CEO asks me afterward whether to go ahead, am I advising as the company's privacy officer or as the person who mentioned it?
ConflictWould introducing a company, paid or unpaid, conflict with tasks I perform for it or for another client?
ConflictMust I disclose the introduction to my employer, client or firm, and in what form?
CompensationDo my contract, employer policy or professional rules allow a reward from a third party in this situation?
CompensationIf not, may I still mention SourceX unpaid, and what record should I keep?

Three meetings, three endings (Illustrative)

Generic people and companies; no real cases.

A. An introduction. An outside privacy officer serving several mid-sized firms knows the CEO of a 260-person claims administrator from a regional business council, not from any engagement. Their counsel confirms there is no client relationship with the company and clears the role. The officer asks the CEO, who wants the conversation; the officer's firm signs the Channel Partner Agreement before submitting anything.

B. An unpaid mention. A staff privacy officer at a 400-person logistics company thinks its dispatch history might interest SourceX. Their employer's policy rules out any personal reward. They tell the CEO that SourceX exists and point to the published criteria; if the CEO wants to explore it, the company applies on its own and the privacy officer advises internally, as their role already requires.

C. No part. A privacy lawyer is advising a client through a data incident. The client is in a sensitive period and the lawyer's ethics counsel advises against any referral role. The alliance manager records "no part, dated", contacts nobody at the company, and follows the reasoning in why a crisis is usually a poor moment for outreach.

The five-line note that closes the meeting

Close the meeting with a five-line note that both of you can read:

  1. Date and the privacy officer's seat.
  2. The ending chosen, or "pending review".
  3. Who decides what: their reviewer on role and pay; the company's CEO on whether the company talks to SourceX.
  4. Open questions, each with the person who will answer it.
  5. A line confirming no company data, client names or advice were discussed.

A company only becomes worth an introduction if it could pass SourceX's screen: 50 or more full-time employees at peak with contractors excluded, years of records it created itself, the rights to license them without breaching client confidentiality, employee privacy or third-party contracts, and a CEO who decides. Personal consumer data, scraped data and material that belongs to the company's clients are usually not a fit, which a privacy officer will grasp faster than most. On location: Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Whoever submits must sign the Channel Partner Agreement first, and credit then depends on dated records, never on a link click.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When the privacy officer's reviewer has cleared a route and the CEO wants the conversation, register whoever will sign as partner, compare the company with who qualifies, read the terms and find related professional guides in the guides library.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can a privacy officer tell me whether a company's records could be licensed?

They should not, and you should not ask. Whether records can be licensed is settled by the company's own counsel and SourceX's rights review, and what a privacy officer knows about a company's processing came to them through their role. The meeting stays on roles, rules and routes.

If the privacy officer cannot take a reward, can I take it instead?

Credit follows the dated record of who made the introduction, so a reward is not something to hand across. An arrangement in which you submit and collect in place of someone whose role bars them is exactly the kind of plan to put to both of your counsel before anyone contacts the CEO.

Should the privacy officer be in the room when the CEO discusses SourceX?

That is the CEO's choice. A company's privacy officer is a natural adviser to the CEO on personal data questions, and SourceX's published process puts scope and terms in the company's hands before any data moves. The partner's job is to stay out of that internal conversation.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/how-it-works
  4. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  5. eur-lex.europa.eu/eli/reg/2016/679/oj/eng
  6. hhs.gov/hipaa/for-professionals/privacy/laws-regulat…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment