- HIPAA reaches genetic information only when a covered entity or business associate holds it. A genetics company that sells tests straight to consumers is often outside HIPAA and answers to state law and its own consent terms instead.
- De-identifying a genome is not the same as deleting names. NIH says genomic data "can be re-identified", and HHS says de-identified data "retains some risk of identification".
- The Justice Department rule at 28 CFR part 202 bars US persons from knowingly giving six countries of concern or covered persons access to human genomic data on more than 100 US persons (more than 1,000 for other 'omic data), or to biospecimens that could yield it, through a license, vendor, employment or investment deal, even when the data is de-identified.
- Published genetic data deals give whole-deal figures, such as the $20 million GSK paid 23andMe upfront for a one-year license to summary data in 2023. No buyer has published a per-genome price.
Who may license genomic data, and under which rule?
The answer depends first on who holds the data and how it was collected. The same exome can sit in a hospital chart, a consumer genetics account and a research biobank, and each copy carries different rules. Each row below names a kind of holder, the rule that governs it, the operative words and what they mean for a license. The consent the donor signed sits on top of every row: no rule below lets a holder use data in a way its own consent terms ruled out.
| Holder and rule or law | Operative words (quoted) | Plain meaning for a license | Source and date read |
|---|---|---|---|
| Hospital, health system or clinical lab that is a HIPAA covered entity: 45 CFR 164.514 (de-identification) | Health information is not identifiable if there is "no reasonable basis to believe that the information can be used to identify an individual"; an expert must find "the risk is very small" | The holder may license genomic data without patient authorization only once it meets this standard, by expert determination or by safe harbor plus no actual knowledge of identifiability | eCFR, current text, read 20 November 2026 |
| The same holder: 45 CFR 164.502(a)(5)(ii) and 164.508(a)(4) (sale of PHI) | "a covered entity must obtain an authorization for any disclosure of protected health information which is a sale of protected health information" | Licensing identifiable genetic results for payment needs each patient's signed authorization, and it must say the holder is paid | eCFR, read 20 November 2026 |
| Consumer genetics company with California customers: California Genetic Information Privacy Act, Civil Code 56.18 to 56.186 | Separate express consent for "Each transfer or disclosure of the consumer's genetic data or biological sample to a third party other than to a service provider" | A direct-to-consumer company needs a separate yes for each transfer, naming the recipient. Deidentified data is outside the act only if the company takes reasonable measures, commits publicly not to re-identify it and binds recipients by contract. Data used "exclusively for scientific research" by an investigator at an institution with an HHS assurance, in compliance with the Common Rule and FDA human-subject rules, is outside it, as is PHI held by HIPAA covered entities and business associates | California Legislative Information, read 20 November 2026 |
| Anyone who holds genetic test information subject to Illinois law: Illinois Genetic Information Privacy Act, 410 ILCS 513, sections 15, 31.7 and 40 | Section 15(a): genetic testing information "may be released only to the individual tested and to persons specifically authorized, in writing"; section 31.7: a HIPAA "covered entity may, without a genetic information test subject's consent, create, use, and disclose de-identified information" | Section 15(a) is not limited by its words to results that identify the person. The consent-free route for de-identified data is written for HIPAA covered entities and business associates, and the recipient "shall not re-identify" it. A holder outside HIPAA, such as a direct-to-consumer company, has no such route in the text. Anyone "aggrieved" may sue (section 40) | Illinois General Assembly, current text, read 20 November 2026 |
| Consumer health data holder outside HIPAA: Washington My Health My Data Act, RCW 19.373 | "it is unlawful for any person to sell or offer to sell consumer health data concerning a consumer without first obtaining valid authorization from the consumer" | Covers Washington residents and data collected there, including genetic data. A sale needs a signed authorization, separate from the consent to collect, naming the purchaser and expiring "one year" after signing; sharing needs separate consent. A violation is "an unfair or deceptive act" under the Consumer Protection Act. HIPAA PHI and Common Rule data are exempt | Washington State Legislature, read 20 November 2026 |
| University, biobank or institution doing federally supported research: Common Rule, 45 CFR 46 | "Broad consent for the storage, maintenance, and secondary research use of identifiable private information or identifiable biospecimens" | Identifiable genomic data used again for research needs consent, broad consent, an exemption or an IRB waiver. For research involving biospecimens, consent forms should, when appropriate, say whether research "might include whole genome sequencing" and whether donors share in "commercial profit" | eCFR, read 20 November 2026 |
| NIH-funded investigators and institutions generating large-scale genomic data (applications due from 25 January 2015), and approved users of NIH controlled-access data: NIH Genomic Data Sharing Policy | Approved users agree to "Not selling any of the data obtained from NIH-designated data repositories" and "Using the data only for the approved research" | The policy binds those funded or approved under it, not every genomic data holder. Controlled-access data may not be resold, and use is limited to the approved project and its data use limitations. A submitting institution's own copy follows its consents and Institutional Certification | NIH, NOT-OD-14-124, read 20 November 2026 |
| Any US holder with a foreign licensee: Justice Department rule, 28 CFR part 202 | Bulk human genomic data means "more than 100 U.S. persons", counted "regardless of whether the data is anonymized, pseudonymized, de-identified, or encrypted" | No access for China, Cuba, Iran, North Korea, Russia, Venezuela or covered persons. Bulk counts data going to one foreign person in a deal or over 12 months. A bulk license to any other foreign person must bar onward transfer to them, with suspected breaches reported within 14 days. A license to a US company is outside the prohibitions unless the licensee is a designated covered person or the licensor knows or should know the deal gives such access | eCFR and justice.gov, read 20 November 2026 |
| Holder of data about people in the EU: GDPR, Articles 6, 9 and 44 | Processing of "genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health" is prohibited unless an exception applies; member states "may maintain or introduce further conditions" | Licensing EU data subjects' genomes needs an Article 6 basis and an Article 9(2) condition, such as explicit consent for specified purposes or research under Article 89(1), plus any member state conditions under Article 9(4), and a Chapter V transfer mechanism when the licensee is outside the EEA. Data de-identified to HIPAA's standard is not anonymous for that reason alone | EUR-Lex, read 20 November 2026 |
| Employers and health insurers: GINA | GINA exists "To prohibit discrimination on the basis of genetic information with respect to health insurance and employment." | GINA limits how insurers and employers use genetic information. It is not a general rule on licensing genetic data | EEOC and HHS, read 20 November 2026 |
Sources: 45 CFR 164.514, 164.508, California Civil Code 56.181, 410 ILCS 513, RCW 19.373, 45 CFR 46.116, the NIH Genomic Data Sharing Policy, 28 CFR part 202, GDPR and GINA, each read on 20 November 2026. This page is general information, not legal advice.
On the last row: the GDPR's Recital 26 says pseudonymized data that "could be attributed to a natural person by the use of additional information" is information on an identifiable person, and whether data is anonymous depends on "all the means reasonably likely to be used" to identify someone. A genome with names removed is judged by that test, not by HIPAA's.
Can genomic data be licensed for AI training?
Yes, but only where the training use fits inside what the donors agreed to and what the holder's rules permit. A consent form written for research on a named disease may or may not stretch to a commercial company training a foundation model. Where the form is silent on commercial use or on AI, the point is unsettled for that holder, and the institution's IRB or privacy counsel decides, not the buyer.
Format matters as much as permission. Some published genetic data deals have licensed summary results rather than individual genomes. When 23andMe extended its GSK collaboration in October 2023, its release said GSK would get "access to de-identified, summary data from global genome- and phenome-wide analysis of the 23andMe database". Summary statistics raise different consent and de-identification questions from individual-level genotypes.
Is de-identified genomic data still identifiable?
It can be, and the agencies say so. NIH writes that it obtained a Certificate of Confidentiality for its dbGaP repository "as an additional precaution because genomic data can be re-identified". The HHS Office for Civil Rights guidance on de-identification says both HIPAA methods "yield de-identified data that retains some risk of identification".
HIPAA's safe harbor list does not name genomes. It names 18 identifier types, ending with "Any other unique identifying number, characteristic, or code", and adds a condition: the holder must not have "actual knowledge" that the rest could identify someone. Whether a genome is itself a unique characteristic under that catch-all is not settled by the text, and we found no HHS statement that a genome stripped of names meets safe harbor. For individual-level genomic data, expert determination is the method that weighs that risk directly. The HIPAA de-identification guide explains both methods.
Two other rules make the answer matter less. The Justice Department rule counts genomic data "regardless of whether the data is anonymized, pseudonymized, de-identified, or encrypted". California treats deidentified data as outside its genetic privacy act only if the company "Publicly commits" not to re-identify it and binds recipients by contract to the same.
Can genetic testing companies sell or license customers' genetic data?
Only with the consents their state laws require, and HIPAA is often not the rule that applies. Under 45 CFR 160.103 a health care provider is a covered entity only if it "transmits any health information in electronic form in connection with a transaction covered by this subchapter", such as billing a health plan. A company that sells saliva kits to consumers for cash is not a covered entity unless it conducts those transactions. HIPAA can still reach it if it handles PHI as a business associate of a covered entity. Each company's status is a fact question.
California requires a "Direct-to-consumer genetic testing company" to get separate express consent for each use "beyond the primary purpose of the genetic testing" and each named third-party transfer. Express consent "cannot be inferred from inaction", and revocations must be honored within 30 days.
Illinois is stricter than HIPAA alone suggests, as the table shows. Section 40 sets liquidated damages of "$2,500 or actual damages, whichever is greater" for each negligent violation and "$15,000 or actual damages" for each intentional or reckless one, plus fees. Public Act 104-642 extends these rules to biomarker testing from 1 January 2027. Public Act 104-417, effective 15 August 2025, is a revisory act "not intended to make any substantive change in the law".
Other state laws we read on official sites: Montana's Genetic Information Privacy Act requires "separate express consent" before a transfer of genetic data to a third party, naming it, and express consent for any "sale or other valuable consideration" (MCA 30-23-104). Texas's Genomic Act of 2025, in force since 1 September 2025, bars facilities and companies that sequence or research the human genome in Texas from storing Texans' "genome sequencing data" in a foreign-adversary country or transferring it to a foreign adversary in a bankruptcy, with a civil penalty of $10,000 per violation. California's consumer privacy act lists "A consumer's genetic data" as sensitive personal information, and Connecticut's privacy act, as amended from 1 July 2026, counts genetic or biometric data "or information derived therefrom" as sensitive data, which a controller may not process without the consumer's consent. Washington's rule is in the table. Other states have genetic privacy laws too, so this list may be incomplete.
What happened to 23andMe genetic data when the company was sold?
The sale moved the business, not a dataset, and the buyer took on the company's privacy commitments. Figures are the sources' own numbers; the $305 million bought substantially all assets and the $300 million was an equity investment, so neither is a price for genetic data. Origin's biotech, CRO and lab data guide covers lab data generally.
| Date | What happened | Figure, as stated | Status as of 20 November 2026 |
|---|---|---|---|
| 25 July 2018 | GSK and 23andMe announce a drug discovery collaboration; GSK says research participation "requires customers to affirmatively consent to participate" | GSK release: "a $300M equity investment" (an investment, not a data price) | GSK described "a four-year collaboration with the option to extend for a fifth year"; the October 2023 license in the next row followed |
| 30 October 2023 | New non-exclusive data license: GSK gets de-identified summary data for 12 months | 23andMe release: "$20 million upfront payment for a one year, non-exclusive data license" (company figure) | The 12-month term has passed; we found no announcement of a renewal |
| 13 June 2025 | Agreement to sell substantially all assets to TTAM Research Institute, a nonprofit led by a 23andMe co-founder; Regeneron named backup bidder | 23andMe release: "a purchase price of $305 million" (company figure, whole business) | Completed |
| 27 June 2025 | Federal bankruptcy court in the Eastern District of Missouri approves the sale | Missouri Attorney General: "the $305 million sale" | Approved |
| 14 July 2025 | TTAM says it completed the acquisition of the Personal Genome Service and Research Services business lines | None given | Completed; TTAM said 23andMe "is continuing to operate" as part of TTAM |
Sources: GSK's release of 25 July 2018, 23andMe, 30 October 2023, 23andMe, 13 June 2025, the Missouri Attorney General, 2 July 2025 and TTAM, 14 July 2025, read on 20 November 2026.
The commitments matter to any holder thinking about a future sale. 23andMe's release said TTAM committed to honor policies that let individuals "delete their account and genetic data and opt-out of research in perpetuity", and to continue "allowing de-identified data to be used for scientific and biomedical research to research scholars at academic universities and other nonprofits". The Missouri Attorney General listed conditions in the sale: TTAM "is barred from licensing, disclosing, or sharing customer data" with anyone connected to countries of concern or covered persons, and "Any future sale of the genetic data must include the full adoption of TTAM's privacy commitments".
How do sequencing data licensing projects work?
One structure, the one the Truveta Genome Project describes, pairs health systems that enroll and consent patients with partners that sequence the samples and use the linked data. The rights split, the exclusivity and the payment are set in contracts that are rarely published.
The Truveta Genome Project is a current example as its participants describe it. Regeneron said in January 2025 that the project would extend its database "through genetic sequencing of up to ten million additional patient volunteers, all with linked electronic health records". Truveta wrote on 20 October 2026 that "our health system members lead participant enrollment and informed consent" and that "we have moved from planning to enrolling participants and collecting samples". Neither company published per-participant payments or the data rights split.
Each participant in such a project signs a research consent written for it, so later licensing questions are answered by that consent. A holder with archived samples and no such consent is in a weaker position, and the federal rules on secondary research use decide what it may do.
What should a genomic data license say?
We help you license your data. Origin Data Partners is an independent data partner that helps business owners value and license their company records: the company pays Origin nothing, and a buyer may pay Origin when a deal completes. These are the clauses that carry the rules above into a contract; your counsel decides the wording.
- Consent provenance: which consent form version covers each record, and which records are excluded.
- Use limits that travel with the data, including any IRB or NIH data use limitations.
- No re-identification and no linkage, binding the recipient's contractors too.
- Onward transfer: no access for countries of concern or covered persons, and the clause 28 CFR 202.302 requires when bulk data goes to any foreign person.
- Withdrawal and deletion: how a later revocation reaches data already delivered and models already trained.
When you know what you hold and under which consent, check what your data may be worth. For the documents buyers ask a health data holder to produce, see health data licensing requirements.
How we checked this
We read every source on this page on 20 November 2026, using official texts: the eCFR, six state legislatures' sites, EUR-Lex, NIH notices, the EEOC and HHS. Changes we found: the Illinois amendments of 2025 and 2027; NIH's April 2025 bar on access from countries of concern and its December 2025 proposal to revise the Genomic Data Sharing Policy, not final; the Justice Department rule, in force since 8 April 2025, with compliance-program and audit duties for restricted transactions from 6 October 2025; an HHS Privacy Rule final rule of 19 November 2026, effective 19 January 2027, which adds a sale exception for disclosures to a person an individual designates and leaves the de-identification methods unchanged; and planned Common Rule changes at the proposed rule stage. On 21 October 2026 the Council of the EU agreed its position on GDPR changes: it "maintains the current definition of personal data", adds a provision on pseudonymization, backs a definition of scientific research and adds safeguards to a proposed exception for processing sensitive data to develop and run AI systems. It is not law; talks with Parliament are pending. Market facts come from company releases and the Missouri Attorney General.
What we could not settle or did not cover: whether a whole genome stripped of names can meet HIPAA safe harbor; the terms of any license TTAM has signed; whether the 2023 GSK license was renewed; genetic privacy laws in states not named here; FTC enforcement; children's data rules; withdrawal from biobanks; tribal and Indigenous data governance; the BIOSECURE Act; and the European Health Data Space Regulation.
Origin Data Partners works with companies that own data and helps get it bought. We are independent of the services on this page, and a buyer may pay us when a deal closes (how Origin is paid). See what your data is worth.
Common questions
Do DNA companies sell data, and under what consent?
Some license it, usually de-identified or as summary results, and only under research consents customers opted into. GSK said in 2018 that 23andMe research participation "requires customers to affirmatively consent to participate". In California a direct-to-consumer company needs separate express consent for each transfer to a third party, naming that party. Read the company's research consent and privacy notice, not only its terms of service, to see what you agreed to.
Which laws apply to genetic data besides HIPAA?
Several, depending on who holds it and where donors live. State laws such as California's Civil Code 56.18 to 56.186, Illinois's 410 ILCS 513 and Montana's Genetic Information Privacy Act; Washington's My Health My Data Act; the Common Rule for federally supported research; NIH's Genomic Data Sharing Policy for large-scale data from NIH-funded research; the Justice Department rule at 28 CFR part 202 for foreign access; GINA for insurers and employers; and the GDPR for people in the EU.
Does GINA stop a company from licensing genetic data?
No. GINA was passed "To prohibit discrimination on the basis of genetic information with respect to health insurance and employment." HHS describes it the same way: it protects people from discrimination in health coverage and employment. It does not set general rules on licensing, consent or de-identification. Those come from HIPAA, state genetic privacy laws, consent terms and, for foreign access, the Justice Department rule.
Can a hospital license exome or genome data it generated in clinical care?
Only after de-identification under 45 CFR 164.514, or with each patient's HIPAA authorization if identifiable data is sold. For genomes, holders usually need an expert determination, because safe harbor's catch-all for "Any other unique identifying number, characteristic, or code" leaves the status of a genome unsettled. Illinois lets a covered entity release data de-identified to HIPAA's standard without consent and bars the recipient from re-identifying it.
Does the DOJ rule stop us licensing genomic data to a US AI company?
Not by itself. The rule at 28 CFR part 202 targets access by six countries of concern and covered persons. A license to a US company is outside its prohibitions unless the licensee has been designated a covered person or the licensor knows or should know the deal gives such access. Thresholds count de-identified data: more than 100 US persons for human genomic data going to the same foreign person over 12 months.
What happens to licensed genetic data if a customer revokes consent?
Under California's Genetic Information Privacy Act, a direct-to-consumer company must honor a revocation "as soon as practicable, but not later than 30 days" after it, and destroy a stored sample within 30 days of receiving a revocation of consent to store it. Whether data already delivered to a licensee must be deleted, and what happens to a model trained on it, depends on the license. Write it into the contract before delivery.
Can approved users of dbGaP data use it to train an AI model?
Only if the approved research described that use and the dataset's data use limitations allow it. Under NIH's Data Use Certification, users agree to use data "only for the approved research", not to sell it, and not to try to identify participants. Since April 2025 NIH also bars access by institutions in countries of concern. A commercial model trained for resale is a separate question that the approved project would need to cover.
Sources and further reading
- eCFR: 45 CFR 164.514, de-identification of protected health information
- eCFR: 45 CFR 164.502, including (a)(5)(ii), sale of protected health information
- eCFR: 45 CFR 164.508, uses and disclosures for which an authorization is required
- eCFR: 45 CFR 160.103, definitions (covered entity, business associate, health information)
- eCFR: 45 CFR 46.116, informed consent and broad consent
- NIH: Genomic Data Sharing Policy, NOT-OD-14-124
- NIH: NOT-OD-25-083, access to controlled-access data by countries of concern
- EEOC: Genetic Information Nondiscrimination Act of 2008
- HHS: Genetic Information (HIPAA and GINA)
- HHS Office for Civil Rights: guidance on HIPAA de-identification methods
- Illinois General Assembly: Genetic Information Privacy Act, 410 ILCS 513
- Illinois General Assembly: Public Act 104-0417, First 2025 General Revisory Act (full text)
- Illinois General Assembly: Public Act 104-0642 (SB 2886), biomarker testing
- California Legislative Information: Civil Code 56.18, Genetic Information Privacy Act definitions
- California Legislative Information: Civil Code 56.181, consent and transfer rules
- California Legislative Information: Civil Code 1798.140, CCPA definitions (sensitive personal information, neural data)
- Washington State Legislature: My Health My Data Act, RCW 19.373
- Montana Code Annotated 2025: 30-23-104, consumer genetic or neurotechnology data, consent
- Texas Legislature: HB 130 (89th Legislature), Texas Genomic Act of 2025, enrolled text
- Connecticut General Assembly: Public Act 25-113 (SB 1295), amending the Connecticut Data Privacy Act (PDF)
- eCFR: 28 CFR part 202, access to US sensitive personal data by countries of concern
- US Department of Justice, National Security Division: Data Security Program
- EUR-Lex: Regulation (EU) 2016/679 (GDPR)
- Council of the EU: Council agrees position on the digital rulebook (21 October 2026)
- Reginfo.gov: HHS Unified Agenda entry RIN 0937-AA16 (Common Rule revisions)
- Federal Register: HIPAA Privacy Rule final rule of 19 November 2026 (FR Doc. 2026-23429, full text)
- GSK: GSK and 23andMe sign agreement on genetic insights for new medicines (25 July 2018)
- 23andMe: collaboration extension with a new data licensing agreement with GSK (30 October 2023)
- 23andMe: agreement for sale of business to TTAM Research Institute (13 June 2025)
- TTAM Research Institute completes the acquisition of 23andMe assets (14 July 2025)
- Missouri Attorney General: privacy protections in the sale of 23andMe (2 July 2025)
- Regeneron: collaboration with Truveta and US health systems (13 January 2025)
- Truveta: Truveta Genome Project, the next chapter (20 October 2026)
