19 November 2026 · LicenseTrack Team

Privacy-Conscious Direct-Licence Recordkeeping for Composers

Set a clear purpose for each record, separate public identifiers from confidential details, choose a retention review date, and keep Reports of Use within their permitted limits. This guide distinguishes cited findings from assumptions and unresolved jurisdictional questions.

A direct music licence can leave you holding names, addresses, payment details, contact history, work information and royalty records. A useful recordkeeping system makes it clear why each item is held, who can see it, and when its purpose or legal retention need should be reviewed.

This guide turns a supplied research brief into practical workflow prompts. It is general educational information, not legal advice. The cited findings, the report’s assumptions, unverified areas and unresolved questions are labelled separately below. Whether a law applies to you depends on your circumstances and the relevant jurisdiction; this guide does not make a blanket claim of global compliance.

A practical starting point: map the record before collecting it

For each kind of information you request or receive, write down:

  1. What it is: for example, a licensee’s identity, a service address, a payment contact, a licence record or a Report of Use.
  2. Why you need it: connect the field to a stated activity such as negotiating or administering a licence, tracking royalties, making a payment, or resolving a contractual question.
  3. Who needs access: name the people or roles that need it for that activity. Keep especially restricted records separate from general client notes.
  4. What happens when the purpose ends: identify the contract end date, any post-termination audit or dispute period, and any applicable legal retention duty that needs checking.

This is an operational way to apply the report’s purpose-limitation and shortest-necessary-retention findings where GDPR applies; it is not a substitute for deciding which rules govern your records. GDPR requires a specific purpose to be communicated to individuals and personal data to be retained for the shortest time possible, subject to legal duties to keep it [1].

Tell customers what you are doing with their data

When you collect personal data in a setting where GDPR applies, the report says individuals should be told the specific purpose at collection [1]. Use a collection notice that is understandable and available when the customer provides the information. Check that it names:

  • Processing purposes: such as licensing, royalty tracking and payment.
  • The legal basis: state the basis you have selected for your organisation and explain it accurately.
  • The retention period: give the period you have determined, or explain how it is set if a fixed period cannot be stated.
  • Rights: include how people can ask to access, correct or erase their information, and explain that rights may have legal exceptions.
  • The data controller: identify the person or entity responsible for deciding why and how the information is processed.

The report describes contractual necessity and legitimate interests as possible lawful bases for direct-licensing records, not automatic answers. Which basis is appropriate, and how to document it, is specific to the entity and requires legal review [1]. Do not copy a basis from another composer’s notice without checking your own processing.

When a customer asks to access, correct or erase information

The report describes GDPR rights to access personal data, correct inaccuracies and request erasure, subject to exceptions such as legal obligations [1]. A practical handling log can record the request date, the records searched, the action taken, any information corrected or erased, and the reason any item was retained. Have a jurisdiction-specific process reviewed before relying on it; the supplied research does not establish response deadlines or a universal procedure.

An erasure request does not by itself settle whether a record must be deleted. Check applicable tax, audit, copyright-registration, renewal and other legal retention duties before acting. The report gives seven years for financial records only as an example if a jurisdiction requires that period; it is not a general retention rule for music records [1].

Separate public identifiers from confidential details

Some licensing information may be subject to a specific disclosure rule, while other information should be handled confidentially. Do not treat a public record as permission to publish every detail about a customer.

US Copyright Office finding: the report says the US Copyright Office requires a copyright owner’s identity and address to be passed into online public catalogues and direct feeds to music services. It also says the service address for notices must be entered on Form DCS in the Relationship line [2]. Apply that statement to the identified US recordation context; it does not establish a universal publication rule for every jurisdiction or every customer field.

BMI confidentiality finding: BMI identifies other details to keep confidential with the affiliated PRO, including an address beyond the service address, residence or other contact information, assignees, and heirs of deceased writers [3]. This is BMI’s stated treatment; do not present it as a universal rule for every composer or organisation.

As a practical control, label fields by their intended handling: for example, “recordation/service address” versus “private contact or payment information”. Before sending a record to a catalogue, feed, partner or customer, check which fields are required for that specific purpose and which are confidential under the applicable agreement or rule.

Keep Reports of Use within their permitted purpose

Reports of Use have specific restrictions in the statutory-licensing finding described in the research. Copyright owners, their agents and collectives must not give this information to people who are not entitled to it, or use it for anything outside royalty collection and distribution and compliance determination. Inspection is permitted only after a written agreement not to use the information for other purposes [4].

In practice, keep Reports of Use in a restricted location, give access only to people entitled to inspect them for those stated purposes, and record any inspection agreement before sharing. Do not reuse the report for marketing, unrelated research or general promotion. These controls are practical steps tied to the cited restriction, not an expansion of who is legally entitled to inspect a report.

The research establishes no universal minimum or maximum retention period for direct-licensing records. GDPR’s stated approach is to keep personal data for the shortest time possible while accounting for the processing reason and legal retention duties [1]. The report identifies these factors to review:

  • how long the licence runs;
  • any post-termination audit or dispute period in the contract;
  • applicable tax-record requirements; and
  • copyright registration or renewal duties in the relevant jurisdiction.

For each record category, note the event that starts a retention review, the contractual or legal reason for continued storage, and who will review it. Revisit the decision when the contract changes, a dispute closes, or a legal duty expires. Do not turn a retention example from one jurisdiction into a fixed music-industry period.

Use appropriate security, without inventing a technical standard

Where GDPR applies, organisations must use appropriate technical and organisational measures to protect personal data against unauthorised or unlawful processing and accidental loss, destruction or damage [1]. The research also reports CISAC’s confidentiality and security commitment in relation to its own obligations [5], and BMI’s use of the phrase “commercial-grade” security [3].

The sources supplied do not prescribe an encryption algorithm, key-management protocol or certification. The report treats “commercial-grade” as qualitative, requiring interpretation in the relevant security and legal context [1][3][5]. Do not claim that one product setting, certificate or checklist guarantees compliance.

As a starting review—not a source-prescribed standard—consider whether access is limited to people who need the data, whether accounts and devices are protected, whether copies and exports are controlled, whether recoverable backups are suitable, and whether information is removed when no longer needed. Ask a qualified security or legal professional to assess the measures appropriate to your risks and obligations.

Check the jurisdictions without assuming a global rule

The report says GDPR may apply to an organisation outside the EU when it processes EU residents’ personal data in connection with offering goods or services to them or monitoring their behaviour [1][5]. That is a conditional scope description; it does not establish that every composer with an overseas customer is automatically subject to GDPR.

The report says UK GDPR remains largely aligned with EU GDPR after Brexit, and that ICO guidance specific to direct licensing was not found [5]. The absence of located direct-licensing guidance is a research finding, not confirmation that no other relevant UK guidance exists.

The report describes CISAC’s own position: CISAC states that it is subject to GDPR and, as a French-based organisation, the French Data Protection Act, which supplements GDPR; CISAC also states a commitment to appropriate confidentiality and security [5]. This organisation-specific account is not a rule that every composer is subject to the French Act.

The report did not establish whether CCPA applies to independent composers. It says applicability depends on factors including revenue, data volume and customer profile, and calls for separate legal review. PIPEDA in Canada and Australia’s Privacy Act were not researched in the supplied run and are marked unverified. The report’s suggestion that local storage combined with customers abroad may create multi-jurisdiction exposure is explicitly an assumption, not a confirmed rule for every cross-border licence.

Before adopting a cross-border process, list where you are based, where customers are located, what data you hold, and whether you offer services to or monitor people in another jurisdiction. Use that map to ask a qualified adviser which laws and transfer rules apply; do not use this guide as a global compliance determination.

What the report says about BMI and cross-border data

BMI states that it participates in the EU-US Data Privacy Framework, the UK Extension to that framework, and the Swiss-US Data Privacy Framework, and that it certified to the US Department of Commerce that it adheres to the framework principles [6]. These are BMI’s statements about its own participation, not a certification or transfer route available to every composer.

BMI says it may identify affiliates and their companies as royalty-payment sources when remitting to affiliates and music-licensing organisations outside the US. It may also disclose affiliate and work information to standards registries and other music-licensing organisations around the world to help identify works for licensing and administration. The report says third parties receiving personal information under the framework must meet the same obligations [6]. Treat these as the described BMI framework practices, not a general permission to disclose a composer’s customer records.

Composer’s recordkeeping checklist

Use this as a review prompt for a direct-licensing workflow. The legal requirements depend on the laws and agreements that apply to you.

  • I can explain why each personal-data field is needed for licensing, royalty tracking, payment or another clearly stated purpose.
  • My collection notice names the purposes, selected legal basis, retention period, access/correction/erasure rights and data-controller identity [1].
  • I have not treated contractual necessity or legitimate interests as a default; the selected basis and its documentation have had entity-specific legal review [1].
  • I have separated copyright-owner identity and address or service-address fields used for the identified US Copyright Office requirements from other confidential customer information [2][3].
  • I know which fields BMI identifies for confidential treatment with an affiliated PRO, and I have not presented that BMI-specific treatment as a universal rule [3].
  • Reports of Use are restricted to entitled people and to royalty collection/distribution and compliance determination; any inspection has the required written use-limitation agreement [4].
  • Each record category has a retention review tied to contract duration, post-termination audit/dispute periods, applicable tax duties and copyright registration/renewal obligations. I have not invented a universal period [1].
  • Any seven-year financial-record period is used only if the relevant jurisdiction requires it [1].
  • I have reviewed appropriate technical and organisational protections without claiming that the report prescribes an algorithm, key-management protocol or certification [1][3][5].
  • I have a way to receive, assess and document access, correction and erasure requests, including any legal-obligation exception [1].
  • I have mapped relevant jurisdictions and kept the report’s CCPA uncertainty, unverified PIPEDA/Australia areas and cross-border assumption unresolved until checked [1][5].
  • I have kept BMI’s and CISAC’s organisation-specific statements separate from rules that may apply to my own organisation [5][6].

Source and evidence limits

This guide was prepared from the supplied excerpt of Privacy Obligations for Storing Direct Music-Licensing Records: Authoritative Guidance Brief. The supplied copy stops midway through “Customer Rights and Transparency” and does not contain the report’s complete remainder or reference list. Citation markers [1]–[6] are preserved against the claims visible in that excerpt, but the bibliographic entries and omitted findings could not be reproduced or checked here. No missing findings or sources have been inferred.

This guide is general educational information, not legal advice. Confirm current law, contract terms and organisation-specific duties with a qualified adviser in each relevant jurisdiction before deciding what to collect, disclose, retain or erase.

LicenseTrack plans

Start using the live workflow

Compare the current subscription plans and see what is included before creating your account.

View plans and pricing