Rights and contracts
The employee-company data rights distinction: whose yes settles what
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
An employee's consent settles only what that employee personally holds: their own personal data, voice or likeness, and any work they own outright. It cannot make the company the owner of its records, authorize anyone to sign for the company, or clear content customers and vendors supplied. Those need ownership evidence, an officer the board has authorized, and the third party's own permission, each recorded separately.
License terms
Employee company data rights
Key takeaways
- Ownership, signing authority, individuals' rights and third-party rights are four questions with four different deciders.
- An employee's consent adds nothing to work product the company already owns, and it cannot authorize a license.
- A chief executive's signature binds the company but cannot waive employees' personal rights or clear customer content.
- Apache's contributor agreements model the split: an individual signs only for what the individual holds, and a corporate form is signed by someone with authority.
- In the EU, employee consent is a weak basis and can be withdrawn, so decide the basis for staff data with counsel before collecting forms.
Does an employee's consent settle whether the company can license its records?
No. A consent form signed by an employee reaches only the rights that employee holds personally, such as their personal data, their recorded voice or face, and work they own outright. The company's ownership of its records, the power to sign for the company and the content customers and vendors supplied all sit outside it. Each of those has its own decider, and a stack of signed forms answers none of them.
The confusion runs both ways, and both directions cost time in a licensing review. A head of sales collects consent forms from the team and forwards them as proof that everyone is on board; a chief executive signs a license and assumes the people in the records are covered by the company's signature. The first mistakes individual permission for organizational authority. The second mistakes organizational authority for individual permission.
The decision this page supports is narrow: before a company offers records for licensing, which permission does each record family need, whose signature supplies it, and what goes on file? The evidence is mostly documents the company already holds: employment and IP terms for the years the records were made, the board resolution or bylaws that say who may sign, the privacy notice and lawful-basis decision for staff data, and the customer and vendor contracts the records arrived under. Qualified counsel resolves any question those documents leave open.
Four permission questions that travel together but are settled apart
Ownership, authority, individual rights and third-party rights are four separate questions, and a license usually needs all four answered. They are settled by different people, under different documents, and an answer to one never carries over to another.
Ownership asks whether the company holds the rights in the records. For copyright in work made on the job, U.S. law answers through the employment relationship rather than through anyone's consent: under 17 U.S.C. section 201(b), for a work made for hire "the employer or other person for whom the work was prepared is considered the author", and owns the rights unless the parties have agreed otherwise in a signed written instrument (paraphrased). An employee who wrote a runbook in the course of the job has no copyright in it to give or withhold.
Authority asks who may bind the company. Delaware's corporation law is one common example. Section 141(a) reads: "The business and affairs of every corporation organized under this chapter shall be managed by or under the direction of a board of directors". Section 142(a) gives officers "such titles and duties as shall be stated in the bylaws or in a resolution of the board of directors". A license signed by someone without that delegation is a problem no number of employee signatures can repair.
Individual rights ask what the people inside the records can still control: their personal data, and in some places their voice and likeness. Third-party rights ask what customers, vendors and partners supplied under their own contracts. Neither the chief executive nor an employee can grant those on someone else's behalf.
Open source already runs a two-signature system
The Apache Software Foundation keeps individual and corporate permission apart, and its contributor agreements show the pattern a data license needs. An individual signs for what the individual holds; a company signs, through someone with authority, for what the company holds; and neither signature stands in for the other.
Section 4 of Apache's Individual Contributor License Agreement (version 2.2, read on 2026-10-28) makes the individual's limits explicit: "If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to the Foundation, or that your employer has executed a separate Corporate CLA with the Foundation." The individual's signature is good only for rights the individual actually has.
The foundation's guidance on the corporate form states the other half: "The CCLA legally binds the corporation, so a person with authority to enter into legal contracts on behalf of the corporation must sign it." It adds that a Corporate CLA "does not remove the need for every developer to sign their own ICLA as an individual". The corporate agreement then names the people it covers on a schedule of designated employees, with the note that "authorization is not tied to particular Contributions".
Translate that to data licensing and the record a company needs becomes clear. The company license, signed by an authorized officer, covers what the company owns. A separate individual instrument covers only what an individual personally holds, such as a release for their recorded voice or an assignment of a template they wrote before joining. A consent form asking employees to approve the licensing of company records sits in neither box.
One permission, one signer: the officer, employee and third-party matrix
Each permission a license needs has one kind of signature that can supply it, and a record that proves it. Read the matrix by row: find the permission, see which signature settles it, and file the document in the last column before anyone relies on the answer.
Two rows carry most of the confusion. In the first, an employee's consent adds nothing because the employee has nothing to give. In the third, the company's signature adds nothing because the right belongs to the person, and in the European Union an employee's consent is itself a weak instrument, as the next sections explain. The matrix, with the record that should be on file for each row:
| Permission the license needs | Authorized officer's signature | Employee's consent or release | Third party's written permission | Record that proves it |
|---|---|---|---|---|
| License work product the company owns | Settles it, once ownership is shown | Adds nothing: the employee has no right in it to give | Not needed | Employment and IP terms for the record dates, authors matched to the roster |
| Bind the company to the license | Settles it, if the board or bylaws gave that officer the power | Does not settle it, however senior the employee | Not needed | Board resolution or delegation naming the signer and the scope |
| Use an employee's personal data inside the records | Does not settle it | Only for that person, only where consent is a valid basis, and only until withdrawn | Not needed | Privacy notice, lawful-basis decision, exclusion and de-identification rules |
| Use an employee's voice or likeness in recordings | Does not settle it | A specific written release settles it for that person, where the law allows | Not needed | Signed release naming AI training, or an exclusion by recording |
| License work the employee owns personally | Does not settle it | Only an assignment or license from the employee, not a consent | Not needed | Signed assignment or license naming the work |
| License content a customer or vendor supplied | Settles it only if the contract already permits the use | Does not settle it | Settles it | The contract clause, or a signed permission naming the use |
Which records need one signature, and which need three?
Most business records need only the company's signature once personal details are handled, but a few record families need two or three signatures, and some need a signature the company cannot give at all. Sort record families before collecting anything, so each signature is requested only where it does work.
The six families below are the ones the figure places, from a single signature to all three:
- Company alone: runbooks, procedures and internal reports written on the job, with personal details removed before delivery.
- Company and third party: drawings or specifications a customer supplied, stored in project folders under that customer's contract.
- Company and employee: recorded internal training sessions, where a presenter's voice and face are the content.
- All three: recorded sales or support calls, which hold the company's work, the employee's voice and the customer's voice.
- Employee alone: a template or tool an employee wrote before joining and brought along; the company needs an assignment or license, not a consent.
- Third party alone: a vendor's licensed industry report saved to a shared drive, which the company has no right to pass on.
Is collecting consent from every employee the safe default?
No. Blanket consent forms feel thorough, but they fail four ways: they cannot supply ownership or authority, they are a weak legal basis for staff data in the European Union, they can be withdrawn, and they say nothing about customer content.
The first failure follows from the matrix. Consent from the author of a runbook the company already owns adds nothing, and consent from a manager who has no delegation does not authorize the license.
The second is regulatory. The European Data Protection Board's guidelines on consent (05/2020) treat employment as a standard case of imbalance of power, in which an employee can rarely refuse an employer's request without "fear or real risk of detrimental effects", so consent is valid only where refusing carries no consequence at all (paraphrased). The guidelines' own example is a filming session: "Those who do not want to be filmed are not penalised in any way but instead are given equivalent desks elsewhere in the building for the duration of the filming." Few licensing projects can promise that kind of neutrality.
The third is fragility. The same guidelines say, in paraphrase, that a controller whose processing rested on consent cannot switch to another lawful basis such as legitimate interests after the consent is withdrawn or proves invalid. A company that collects consent it does not need can end up bound by it. Decide the basis for staff data with counsel first, and ask individuals only for the instruments the matrix calls for.
The fourth is scope: no employee can consent for a customer. Removing names, or exporting the records with an administrator's access, does not change any of this. De-identification lowers what can be learned about a person; it does not move ownership, create authority or clear a customer's contract.
A review log for one request, entry by entry (illustrative)
A review log turns the matrix into decisions someone can check later: for each question, who decided, which document governed, what evidence settled it, what stayed out and how the exclusion reached the delivery. The company, names, dates and outcomes below are invented to show the format.
At a glance
A review log for one request, entry by entry (illustrative)
The request: a regional insurance brokerage plans to license five years of account-management records, covering CRM notes, email threads, recorded client calls and internal training videos. Its head of sales has already collected consent forms from the account team and forwarded them with a note that everyone agrees. The log the general counsel opens:
- Entry 1, authority. Question: who signs? Decided by the board, which passed a resolution authorizing the chief executive to sign data licenses for the four named record families. Evidence: the resolution and the bylaws section it relies on. The sales head's note is filed as input, not approval. Carried into delivery: the Confirmation lists only the families the resolution names, less those excluded below.
- Entry 2, ownership. Question: does the company own the CRM notes and emails? Decided by the general counsel on the employment and IP terms in force for each year, with authors matched to the payroll roster. Two outside sales contractors had no assignment clause, so their notes are held out. Carried into delivery: an author filter on the contractor list, with the excluded count in the manifest.
- Entry 3, staff personal data. Question: on what basis may staff details appear? Decided by the privacy lead with counsel, who chose not to rely on the consent forms and set de-identification rules instead; personal messages and the records of staff based in the Dublin office are excluded. Carried into delivery: the de-identification specification in the processing route and an office-location filter.
- Entry 4, recorded client calls. Question: may the client side be licensed? Decided by counsel and the contract owners: client contracts and call notices do not cover the use, so every recorded call is excluded rather than trimmed. Carried into delivery: a filter on recording type and an excluded count.
- Entry 5, training videos. Question: may presenters' voices and faces be used? Decided presenter by presenter: six signed a specific release naming AI training and two declined. Carried into delivery: the two presenters' video IDs excluded.
- Entry 6, a withdrawal. One account manager writes to withdraw her consent form. The company never relied on the forms, but they created an expectation, so counsel excludes her authored notes rather than argue the point. Carried into delivery: her author ID added to the exclusion filter. Lesson recorded: decide the basis before collecting forms.
How the decisions carry into SourceX's Dataset Deal Confirmation
The log is the evidence SourceX's rights check asks about, and its exclusions belong inside the dataset definition rather than beside it. SourceX's guidance treats the supplier as the company that holds the records, acting through its authorized signer, not an individual employee, which is entry 1 of the log.
Its FAQ says, in its own words, that "owning your records doesn't automatically give you the right to license personal information or data that belongs to customers, vendors or other third parties", that SourceX checks permissions with the supplier before any deal, and that it does not give legal advice, so uncertain questions go to the company's own counsel. On SourceX's how-it-works page, a supplier confirms that it holds the right to license the data, that any personal data in it was gathered lawfully and that no earlier AI training license covers it; records already licensed for that purpose are not eligible.
The Dataset Deal Confirmation both sides sign fixes the exact dataset, its rights, the processing route and the deadlines, so the record families the log excludes are simply not part of the dataset it names. A first step needs no files: a short company assessment checks fit, and it is not an offer and promises no payment.
What this matrix cannot settle
It cannot tell a company whether a particular document permits a particular use; that takes qualified counsel reading the actual agreements under the law that applies. The copyright and corporate rules quoted here are U.S. examples, Delaware's among many state corporation laws, and the consent guidance is European; other jurisdictions answer each row differently.
Rows three and four depend most on location. Works councils and collective agreements can add consultation duties, some states give people rights in their voice or likeness, and recording laws can require every party's consent to a call, so this site's guides to employee-authored records and to voice and likeness rights go further on those rows. The matrix also assumes the company's own records are accurate about who wrote what; where authorship is unclear, the record stays out until someone can place it.
Finally, the matrix is about permission, not value. A record family can clear every row and still not suit any buyer, and a narrow dataset with clean permissions usually survives review better than a broad one resting on consent forms.
Frequently asked questions
If every employee signs a consent form, can the company license its records?
Not on that basis alone. The forms do not show the company owns the records, do not authorize anyone to sign for it and do not cover customer or vendor content. They can also create obligations if staff later withdraw, so counsel should decide whether any individual instrument is needed before forms go out.
Can the chief executive sign away employees' privacy rights?
No. An authorized officer can bind the company to a license, but personal data inside the records still needs a lawful basis, notice and, often, exclusion or de-identification. Those decisions are recorded separately from the signature.
When does an individual employee's signature actually matter?
When the employee personally holds the right: a release for a recorded voice or face, or an assignment of work the employee owns, such as a template written before joining. In those cases the instrument is specific to that person and that material.
Does de-identifying staff remove the need for these decisions?
It reduces what can be learned about individuals, but it does not change who owns the records, who may sign or what a customer contract allows. Ownership, authority and third-party rows still need their own evidence.
Who should keep the review log?
Usually the general counsel or the person running the rights review, with entries from the privacy lead and the contract owners. The log should name the decider, the governing document, the evidence and how each exclusion is applied at extraction.
Sources
- 17 U.S.C. 201(b): for a work made for hire, the employer or other person for whom the work was prepared is considered the author and owns the rights unless a signed written instrument says otherwise. Source
- Delaware General Corporation Law 141(a) and 142(a): a board manages or directs the corporation's business, and officers hold the titles and duties stated in the bylaws or a board resolution. Source
- Apache ICLA v2.2 section 4: an individual contributor represents employer permission, an employer waiver or a separate Corporate CLA where the employer has rights in the contributor's work. Source
- Apache Corporate CLA: the corporation represents that designated employees on Schedule A may submit on its behalf; authorization is not tied to particular contributions. Source
- Apache guidance: a Corporate CLA does not remove the need for each developer's ICLA, and must be signed by a person with authority to contract for the corporation. Source
- EDPB Guidelines 05/2020: employment is an imbalance of power in which employee consent is rarely freely given; a controller cannot switch to another lawful basis after consent is withdrawn or invalid. Source
- SourceX FAQ: owning records does not automatically give the right to license personal information or third parties' data; SourceX checks permissions and does not give legal advice. Source
- SourceX how-it-works: suppliers confirm rights to license, lawful collection of personal data and no prior AI training license; the Dataset Deal Confirmation fixes the exact dataset, rights, processing route and deadlines. Source
- SourceX guidance: in a SourceX transaction the supplier is the company that holds the records, acting through its authorized signer, not an individual employee. Source
See if your company qualifies
A short company assessment. No data uploads are needed.