How to distinguish de-identification from permission to license

Understanding the difference between de-identification and permission to license

When referring a business to SourceX, it's important to understand two distinct concepts: data de-identification and the company's permission to license its proprietary operational data. These are often confused, but they address different aspects of data readiness and legality.

What is de-identification?

De-identification is the process of removing or obscuring personally identifiable information (PII) from a dataset. This includes names, addresses, account numbers, or any other data points that could directly or indirectly link back to an individual. The goal is to protect privacy and comply with regulations related to personal data.

Key characteristics of de-identification:

Focus: Removing PII from a dataset. Purpose: Privacy protection and regulatory compliance (e.g., GDPR, CCPA). Process:* Technical methods to alter or aggregate data.

What is permission to license?

Permission to license, in the context of SourceX, refers to a company's legal right and authority to share its proprietary operational data. This data typically consists of internal processes, historical records, standard operating procedures (SOPs), knowledge bases, and other non-personal, company-specific information that holds value for AI training and analysis.

Key characteristics of permission to license:

Focus: Legal authority and ownership rights over operational, non-personal company data. Purpose: Monetizing proprietary business insights for AI buyers. Process:* Internal company approvals, legal review of data ownership, and contractual agreements.

Why the distinction matters for SourceX referrals

SourceX's referral program is built around connecting businesses that own valuable proprietary operational data with AI buyers. This means the primary focus is on the company's ability to license data it has created or lawfully possesses, rather than its ability to de-identify data containing PII.

When assessing a potential referral, SourceX looks for companies with:

Original documentation: SOPs, internal knowledge bases, project histories, QA records, support workflows and similar material the company created itself. Rights to license: The company owns the material, or can license it without breaching client confidentiality, employee privacy or third-party contracts. An authorized sponsor:* An owner, executive or someone they designate who can approve a discussion.

Learn more about who qualifies for referral.

SourceX does not engage with personal consumer data, scraped data, or data the company does not control. The company controls whether to proceed, what scope to offer and the terms it accepts. You do not need to export, upload or describe confidential records when making an introduction.

Therefore, while de-identification is crucial for handling personal data, it is generally not the primary concern for the types of operational data SourceX facilitates. The essential factor is that the referred company has clear permission to license its own proprietary, non-PII operational data to SourceX for buyer programs.

Illustrative: A company that has developed unique internal project management methodologies documented over years has the permission to license these internal guides. Its ability to de-identify customer support tickets would be a separate, irrelevant consideration for SourceX's primary data needs.

Focus your efforts on identifying companies with robust, proprietary operational data and the clear authority to license it. If you're unsure if a company fits, try the company fit checker.

Rewards are calculated as 25% of SourceX's eligible collected platform fees, capped at $100,000 per referred company. A lead, meeting or signed agreement alone does not trigger payment. See the program terms.