Skip to content

Leadership and readiness

Data licensing subsidiary approvals: who can license which records

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

For data licensing subsidiary approvals, the licensor is the group entity that holds the rights in each record set, and that entity approves through its own board, managers or delegated officers. Find it by testing six things per record set: contract counterparty, privacy notice issuer, employer of the authors, system account holder, written intercompany transfers and trade secret owner. When the tests split, split the records or paper the rights first.

Provenance trail

Data licensing subsidiary

This page covers data licensing subsidiary approvals: who can license which records.Illustrative

Key takeaways

  • The licensor is the entity that holds the rights in each record set, and it approves through its own governance.
  • Six tests locate the rights: contract counterparty, notice issuer, employer of authors, account holder, written transfers and trade secret owner.
  • Shared services employers, parent-held tenants and acquired subsidiaries are where the tests most often split.
  • A parent's consent can be required by group policy but does not replace the subsidiary's own approval.
  • Record each answer as confirmed, inferred or unknown, and keep record sets with unknown core fields out of scope.

How do you determine which subsidiary may license particular business records?

The licensor for a record set is the entity that holds the rights in those records, and the approval must come from that entity's own decision makers. In practice you find it by running six tests on each record set: who is the counterparty to the contracts that govern the records, who gave the privacy notice, who employed the people who authored the content, who holds the system account, which written transfers exist between group companies, and who owns the trade secrets in the content.

When all six tests point to one subsidiary, that subsidiary licenses and its board, managers or delegated officers approve. When the tests point to different entities, the parent cannot simply sign for the group. Either the record set is split along entity lines, or the entities first put written intercompany arrangements in place, and each rights-holding entity approves its own part.

Six tests that point to the rights-holding entity

Run every test for every record set, and record the evidence, not just the answer. Each test reflects a different source of rights or obligations, so one entity can pass four tests and fail two.

Six tests that point to the rights-holding entity
TestQuestionEvidenceWhy it matters
Contract counterpartyWhich entity signed the customer, supplier or partner contracts whose data is in the records?Signed contracts and order forms showing the legal entity nameConfidentiality and data use terms bind the entity that signed them
Privacy notice issuerWhich entity told the people in the records how their data would be used?Privacy notices and collection forms in force when the data was collectedThe promises made at collection limit later uses
Employing entityWhich entity employed the staff who wrote notes, reports and tickets?Payroll and employment agreements by entityCopyright in employee work vests in the employer
System account holderWhich entity holds the subscription and admin rights for the source system?Vendor contract and tenant ownership recordsThe vendor's terms and export rights attach to the account holder
Written transfersHas any group company assigned or licensed rights in the records to another?Signed intercompany agreements and assignmentsA copyright transfer needs a signed writing
Trade secret ownerWhich entity holds title to the confidential methods, prices and know-how in the content?IP ownership records and intercompany IP agreementsFederal law ties trade secret ownership to title or license

The entity source and approval matrix: fields to fill for each record set

Build one row per record set, where a record set is a defined slice of one system, such as work orders in one field service tenant for one date range. Keep the fields below for every row. The matrix is the evidence pack a licensing review, an auditor or a future acquirer of one subsidiary will ask for.

At a glance

The entity source and approval matrix: fields to fill for each record set

The entity source and approval matrix: fields to fill for each record set
FieldWhat to recordSource of evidenceWho fills it
Record setSystem, tenant, object types and date rangeSystem inventory and export planData owner
Origin entityEntity whose operations created the recordsBusiness unit and branch mappingFinance or operations lead
Counterparty entityEntity named in governing customer and supplier contractsContract repository searchLegal or contracts manager
Notice entityEntity that issued the privacy notice at collection, with notice versionArchived notices and website historyPrivacy lead
Employer of authorsEntity that employed the staff who authored free textPayroll entity per role and periodHR
Account holderEntity holding the system subscription and admin rightsVendor contract and admin consoleIT
Intercompany instrumentsAssignments, licenses or services agreements touching the recordsSigned intercompany agreementsLegal
Approver and authorityPerson or body that approves for the rights-holding entity, and the source of that authorityBoard minutes, LLC agreement, delegation of authorityCompany secretary or counsel
Status and confidenceConfirmed, inferred or unknown for each field, with open question ownerMatrix review notesGovernance lead

Who signs for each entity, and on what authority?

Each rights-holding entity approves through its own governance. For a Delaware corporation, the business and affairs of the company are managed by or under the direction of its board unless the statute or certificate provides otherwise, so a license from a subsidiary corporation needs either a board resolution or a documented delegation to an officer. For a Delaware LLC, management sits with the members unless the LLC agreement appoints managers, and the members or managers can delegate to officers unless the agreement says otherwise.

The parent's role is usually that of shareholder or sole member, plus whatever group policy requires. A group approval policy may say a parent committee must consent to any data license, and that consent is worth recording. It does not replace the subsidiary's own approval, and a parent officer who signs on behalf of a subsidiary should be able to point to written authority from that subsidiary.

Record the authority in the matrix row: the resolution or delegation, its date, its limits, and whether it covers licensing records to third parties or only ordinary commercial contracts.

Scope the approval as narrowly as the record set. A useful resolution names the entity, the record sets by matrix row, the permitted use, the counterparty or class of counterparty, any exclusions and the officer authorized to sign. A broad authority to enter into data agreements is better than nothing, but it invites later disputes about whether licensing to an AI developer was ever contemplated. When several subsidiaries license in one transaction, each should pass its own resolution covering its own rows, even if the boards share directors and meet on the same day.

Group arrangements that blur the answer

Groups share people, systems and brands, which is exactly where the six tests start pointing in different directions. These are the arrangements to check first:

At a glance

Group arrangements that blur the answer

  • Shared services employers: if a parent or a services company employs the staff who write notes for several subsidiaries, copyright in that free text vests in the employer, not the subsidiary that serves the customer.
  • Group-wide tenants: a CRM or ERP subscription held by the parent but used by every subsidiary puts the account holder test with the parent while the records belong to the subsidiaries' operations.
  • Common branding: California's privacy law counts an entity that controls or is controlled by a business, shares its branding and receives consumers' personal information from it within the business definition, which helps intra-group sharing but says nothing about licensing to an outside AI developer.
  • EU group transfers: the GDPR defines a group of undertakings and recognizes a possible legitimate interest in sharing personal data within a group for internal administrative purposes; licensing records to a third party is a different purpose and needs its own analysis.
  • Acquired subsidiaries: records created before an acquisition remain governed by the notices and contracts that entity used then, even after it adopts group branding and systems.
  • Updated privacy terms: FTC staff warned in 2024 that adopting more permissive data practices, including AI training or third-party sharing, through a surreptitious retroactive change to terms may be unfair or deceptive, so a new group-wide notice does not cleanly reach data collected under an old one.

Who owns each unresolved approval question?

Every unresolved field in the matrix needs a named owner, the evidence that would resolve it and a point of escalation. Without that, open questions drift and the record set either stalls or goes ahead on an assumption.

Review the open questions on a fixed cadence, weekly while a licensing project is active, and close each one by attaching the document that answers it to the matrix row. An answer given in a meeting is an inference until the document is filed. When the owner cannot find the evidence within an agreed period, escalate rather than extend, because the escalation point is the person who can decide to narrow the record set or accept the gap.

Who owns each unresolved approval question?
Open questionOwnerEvidence that resolves itEscalate to
Which entity signed older customer contracts?Contracts managerExecuted contracts or order forms for a sample of accountsGeneral counsel
Which notice applied to records from a given year?Privacy leadArchived notice versions and collection datesPrivacy counsel
Who employed field staff before a reorganization?HR leadPayroll entity history by roleCFO
Does the intercompany services agreement grant data rights?LegalSigned agreement and any IP clauseGeneral counsel
Who can approve for the subsidiary?Company secretaryBoard minutes, LLC agreement and delegation scheduleSubsidiary board or managers
Do any customers object to reuse?Account ownersContract terms and written objections on fileExecutive sponsor

Worked scenario (illustrative): a field services group with three operating companies

This scenario is illustrative; the group, entities and shares are invented. A holding company owns three operating subsidiaries: an HVAC services company, a plumbing company acquired two years ago and a commercial maintenance company. All three use one field service management tenant held by the parent, and a shared services subsidiary employs dispatchers and office staff for the whole group.

The matrix shows a mixed picture. Customer contracts and privacy notices are with each operating subsidiary. The tenant is held by the parent. Dispatcher notes were written by employees of the shared services company, while technician notes were written by each operating subsidiary's own staff. There is an intercompany services agreement, but it says nothing about rights in records.

The decision follows the evidence. Each operating subsidiary licenses its own work orders and approves through its own board. The parent, as account holder, confirms in writing that its vendor terms allow the export and that it claims no rights in the records. The shared services company signs a short written assignment or license of its rights in dispatcher notes to each operating subsidiary before anything is licensed out, because copyright in that text sits with the employer.

The exception is the acquired plumbing company. Its records from before the acquisition, roughly 40 percent of its history in this illustration, were collected under its old privacy notice and customer terms, one of which restricted sharing beyond service delivery. Those records stay out of scope until counsel has reviewed the old terms, and the matrix carries them as a separate row with an unknown status.

Which assumption flips the decision, and how to record uncertainty

The assumption that most often flips the decision is that the entity named on the invoice is the entity that holds all rights in the records. It frequently holds the customer relationship but not the account, not the employment of the authors, or not the IP. Test that assumption first for every record set.

Record confidence per field as confirmed, inferred or unknown. Confirmed means a document was found and filed. Inferred means the answer follows from patterns, such as a branch mapping, without a document for this record set. Unknown means nobody has looked or the evidence conflicts.

Use the confidence to decide scope rather than to argue about it. A record set with any unknown in the counterparty, notice or approver fields stays out. Inferred fields can proceed only when the owner of the open question accepts the residual risk in writing and the inference is described in the license file. If the six tests split between entities, show the split in the matrix instead of choosing the most convenient entity.

Presenting a group's records for a SourceX assessment

SourceX runs the rights review, contracting, preparation and delivery when a company licenses selected operational records directly to SourceX, and in a group that review starts from the entity question. In a group, the company that approves the scope and terms and signs the agreement before any data is delivered should be the rights-holding entity the matrix identifies, not simply the parent that first made contact.

The first step is a short company assessment that needs no data upload, so it can begin while the matrix is still being filled. Bringing the matrix, even with open questions marked, makes the rights review faster and keeps each subsidiary's records with the entity that can actually license them.

Frequently asked questions

Can a parent company license its subsidiaries' records?

Only if it holds the rights or has written authority from each subsidiary that does. Ownership of the subsidiary's shares does not by itself make the parent the owner of the subsidiary's contracts, notices or copyrights. Most groups have each subsidiary license its own records or grant the parent written rights first.

What if the records sit in a system the parent pays for?

The parent then holds the account and must confirm the vendor terms allow the export, but the records usually still belong to the operating subsidiaries whose work created them. Record both entities in the matrix and get the parent's written confirmation that it claims no rights in the records.

Who approves a data license for a subsidiary LLC?

Under Delaware's default rule, the members manage an LLC unless the LLC agreement appoints managers, and they can delegate to officers. Check the LLC agreement and any delegation schedule, and record the authority in the approval field of the matrix.

Does a new group privacy notice cover records collected earlier?

Not automatically. Records collected under an earlier notice are generally governed by what that notice said, and FTC staff have warned that quietly expanding data uses through retroactive changes may be unfair or deceptive. Counsel should review older records before they are licensed.

What is an entity source and approval matrix?

It is a table with one row per record set that records which group entity created the records, signed the governing contracts, issued the privacy notice, employed the authors, holds the system account and approves the license, with evidence and confidence for each answer.

Sources

  • Federal trade secret law defines the owner of a trade secret as the person or entity holding rightful legal or equitable title to, or a license in, it. Source
  • Under the Copyright Act the employer is the author and owner of a work made for hire unless a signed writing says otherwise, and a transfer of copyright ownership needs a signed writing. Source
  • Delaware law places the business and affairs of a corporation under the management or direction of its board of directors unless the statute or certificate of incorporation provides otherwise. Source
  • Delaware LLCs are managed by their members unless the LLC agreement provides for managers, and management powers can be delegated to officers or agents unless the agreement says otherwise. Source
  • The GDPR defines a group of undertakings as a controlling undertaking and its controlled undertakings, and Recital 48 recognizes a possible legitimate interest in transmitting personal data within a group for internal administrative purposes. Source
  • The California Consumer Privacy Act treats an entity that controls or is controlled by a business, shares common branding with it and receives consumers' personal information from it as part of the business definition. Source
  • FTC staff warned in 2024 that adopting more permissive data practices, such as sharing data with third parties or using it for AI training, through a surreptitious retroactive change to terms or a privacy policy may be unfair or deceptive. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies