Research Use Terms
Effective September 2026. These terms state the core scientific-use boundary for the public GaiaLab research platform. Paid or institutional agreements may add or replace terms for a specific engagement.
1. Permitted use
You may use GaiaLab to explore biological evidence, generate research hypotheses, inspect source-linked reasoning, compare research records, and support experimental planning subject to applicable law and third-party source terms.
2. Scientific responsibility
Outputs can be incomplete, uncertain, incorrect, outdated, or dependent on external source availability. Users are responsible for independent scientific review and experimental validation before relying on an output.
3. Prohibited data in the public workflow
Do not submit PHI, directly identifiable patient information, regulated clinical data, credentials, unlawful content, or confidential trade-secret datasets through the general public workflow. Contact GaiaLab before any proposed confidential institutional use.
4. Evidence and third-party sources
GaiaLab integrates and cites third-party scientific information. Those underlying sources remain subject to their own ownership, licenses, access conditions, and attribution requirements. GaiaLab's value is the research workflow, evidence organization, analysis record, provenance, and synthesis—not ownership of public third-party scientific facts.
5. No guarantee of biological efficacy
A hypothesis, score, ranking, citation, timestamp, prediction record, or proof-of-anteriority artifact does not establish biological truth, efficacy, safety, clinical utility, novelty, patentability, or regulatory acceptance.
6. Proof of anteriority
Cryptographic or timestamp evidence can establish that a particular digital commitment existed by a particular time when verification succeeds. It does not prove that the scientific claim is correct or effective.
7. Availability
GaiaLab may change providers, data-source availability, models, limits, interfaces, or experimental features. Versioned evidence records should be used when reproducibility matters.
8. Institutional engagements
Validation pilots and enterprise engagements should define scope, permitted data, success criteria, confidentiality, retention, support, security responsibilities, and deliverables in a separate written agreement.
9. Contact
Questions about institutional use: partnerships@gailabai.com. Security reports: security@gailabai.com.