Privacy Policy
Last updated: June 6, 2026.
Plain-language summary
- Om primarily provides access to models, model-enabled workflows, APIs, and Data Generation
workflows. Some Om products and orders include model training, evaluation, or service
improvement as part of the service.
- Om may use Generated Data from Data Generation workflows to improve, train, fine-tune,
evaluate, and make available Om models or model-enabled services. Unless a written Om
agreement expressly says otherwise, we do not make your customer-specific raw Generated
Data or training dataset available to other customers as a standalone dataset or data
product.
- Data Generation is non-exclusive unless Om expressly agrees otherwise. If another customer
independently requests the same or similar protein sequence, target, SMILES, molecule,
interaction pair, or workflow, Om may generate or provide the same or similar predictions,
scores, rankings, data, or outputs for that customer without treating that as a disclosure
of your Customer Data or your customer-specific Generated Data.
- Customer-specific raw Generated Data and training datasets from Data Generation are not
published, resold, redistributed, licensed, or disclosed to other customers as standalone
datasets or data products unless a separate written Om agreement or order form expressly
says so.
- We do NOT use personal account or billing information for model training or sale.
- Subscription-gated Om Data, model-enabled services, Data Generation Slots, and
related plan entitlements are governed by your subscription, order form, checkout
flow, or written Om agreement. Subscription pricing and plan changes are
plan-based; paid Data Generation orders govern Generated Data for the ordered
protein_uuid, including updated snapshots or vintages Om makes available for
that same protein_uuid.
- If the applicable subscription or written license coverage ends, the related
subscription-gated entitlements, Data Generation Slots, plan quotas, plan-specific paid workflow pricing,
and plan-only Om-hosted or customer fine-tuned models end unless a separate written
Om agreement or order form expressly says otherwise. Separately funded Wallet Credits
and supported pay-as-you-go workflows remain governed by your wallet balance, account
standing, product availability, payment status, and Om Terms. Generated Data already
generated under a paid Data Generation order remains governed by that order and the
Om Terms.
1. Who We Are
Om Therapeutics, Inc., a Delaware C Corporation with its principal place of business at 3210 Merryfield Row, San Diego, CA 92121 USA ("Om," "we," "us") provides software, APIs, and related services that incorporate machine-learning ("ML") techniques. This Privacy Policy ("Policy") explains our global data-handling practices.
2. Scope
- Visit an Om website or app that links to this Policy.
- Create an account or subscription.
- Interact with the Diligence tool, API, SDKs, plug-ins, or any other product developed by Om Therapeutics, Inc.
- Purchase products or paid subscription plans that may be offered.
- Contact us or participate in events, surveys, or promotions.
3. Key Definitions
- Om: Om Therapeutics, Inc., a Delaware C Corporation with its principal place of business at 3210 Merryfield Row, San Diego, CA 92121 USA.
- Personal information: any data that identifies, relates to, describes, or can reasonably be linked to an individual.
- Service Data: text, files, prompts, and other content you submit or generate.
- Generated Data: datasets, files, reports, rankings, predictions, and other data outputs generated by Om for you through a Data Generation order, checkout flow, Data Generation Slot workflow, or written Om agreement.
- Model Training: using Service Data, Outputs, or Generated Data to develop, fine-tune, or evaluate Om ML systems where permitted by the applicable product flow, order, or written Om agreement.
- Subscription Plan: the subscription-gated entitlements, Data Generation Slots, plan quotas, plan-specific paid workflow pricing, plan-only model access, plan-only API or MCP access, Om-hosted model access, and related entitlements you purchase.
- Molecule Fulfillment: provider-backed search, quote, checkout, order, shipping, status, or related fulfillment workflows for physical molecules or related materials made available through the Services.
4. Information We Collect
Information We Collect
| Category | Examples | Source |
|---|---|---|
| Account Data | name, email, postal address, phone, company, job title, credentials | you |
| Payment Data | partial card details, billing address, tax/VAT numbers | payment processor |
| Service Data | protein sequences, molecular inputs, prompts, files, dataset access selections, outputs | you / automated collection |
| Molecule Fulfillment Data | SMILES strings, molecule identifiers, requested quantities, provider search results, quote details, shipping/contact details, fulfillment order status, and support communications about fulfillment | you / fulfillment providers / automated collection |
| Usage Data | IP address, device IDs, cookies, event logs, error reports | automated |
| Third-Party Data | SSO identity, marketing attribution, public records | business partners |
5. How and Why We Use Data
How and Why We Use Data
| Purpose | Legal/Lawful Basis |
|---|---|
| Operate, secure, and provide the Services (including Data Generation, subscriptions, and Generated Data delivery) | Contract |
| Facilitate Molecule Fulfillment workflows, including provider-backed search, quotes, orders, shipping, status, support, and compliance checks | Contract |
| Model Training and Service Improvement | Contract |
| Process payments and send transactional messages | Contract / Legal obligation |
| Prevent fraud, abuse, or security incidents | Legitimate interests |
| Marketing communications (opt-in where required) | Consent |
| Compliance with laws, audits, and requests from authorities | Legal obligation |
Lawful bases for EU/UK data subjects are detailed in Section 6.
5.1 Model-Training Policy
We use submitted sequences, molecular inputs, computational outputs, and Generated Data to provide, maintain, secure, troubleshoot, validate, and improve the Services and Om Platform and, where permitted by the applicable product flow or written Om agreement, to train, fine-tune, and evaluate our internal ML systems. For Data Generation and other products or written Om agreements that so provide, we may also use those inputs and outputs to improve, develop, train, fine-tune, evaluate, and make available Om models or model-enabled services. Unless a separate written Om agreement or order form expressly permits a specific publication or data-sharing exception, we do not make your customer-specific raw Generated Data or training dataset available to other customers as a standalone dataset or data product. If another customer independently requests the same or similar protein sequence, target, SMILES, molecule, interaction pair, or workflow, Om may generate or provide the same or similar predictions, scores, rankings, data, or outputs for that customer without treating that as a disclosure of your Customer Data or customer-specific Generated Data.
What we use for model training
- Protein sequences, targets, SMILES, molecules, interaction pairs, and computational requests you submit through Data Generation workflows and other products or written Om agreements that allow model training
- Computational outputs, predictions, scores, rankings, Generated Data, and interaction matrices we generate from those products, workflows, and orders
What we never use for model training or sale
- Your personal information (name, email, etc.)
- Payment information
- Any other account data
Note on support communications: We may use customer support communications internally to provide support, troubleshoot issues, improve product features, improve support quality, and improve the Services. We do not sell support communications. Where support communications or Service Data are used to improve the Services, including model-enabled systems, we use reasonable data-minimization, access-control, aggregation, and de-identification practices where appropriate and technically feasible.
If the same or similar protein sequence, SMILES, molecule, interaction pair, or workflow is independently requested by another customer or later appears in public, Om may screen, rescreen, score, or generate outputs for that independent request. We do not share personal account data in any dataset outputs.
6. Legal Bases (EU/EEA/UK GDPR and Comparable Laws)
Legal Bases
| Processing Purpose | Lawful Basis |
|---|---|
| Service provision and model training where applicable under the product or order | Art. 6(1)(b) - contract |
| Marketing | Art. 6(1)(a) - consent |
| Security and fraud | Art. 6(1)(f) - legitimate interests |
| Compliance | Art. 6(1)(c) - legal obligation |
Where a product flow, order, or written Om agreement provides for model training and evaluation, that processing is part of the contracted Services and is based on contractual necessity (GDPR Art. 6(1)(b)), not on separate consent under Art. 6(1)(a). Data Generation results may still be used internally to provide, maintain, secure, troubleshoot, validate, improve, train, fine-tune, and evaluate the Services and Om Platform, but the customer-specific raw Generated Data or training dataset is not published, licensed, or disclosed to other customers as a standalone dataset except where a written Om agreement expressly says otherwise.
7. Disclosures to Third Parties
- Service providers (cloud hosting, analytics, customer support) under strict contracts.
- Molecule Fulfillment providers, logistics providers, and related service providers when needed to search availability, prepare quotes, create orders, arrange shipment, provide order status, handle support, or satisfy compliance obligations. Fulfillment disclosures may include SMILES strings, molecule identifiers, quantities, quote/order details, shipping/contact details, billing or invoice status, and support context needed for the provider-backed workflow.
- Subscribers and licensees who access Om model-enabled services or Om Data outputs where permitted by the applicable product or agreement (no personal account data, and no customer-specific raw Generated Data or training dataset as a standalone dataset unless expressly agreed; independent same-or-similar customer requests may result in same-or-similar predictions, scores, rankings, data, or outputs).
- Affiliates and acquirers in corporate transactions.
- Authorities when legally required.
- Others with your explicit direction.
8. Your Rights and Choices
Rights and Choices
| Jurisdiction | Rights | How to Exercise |
|---|---|---|
| Global (all users) | Access, correction, deletion | support@omtx.ai |
| California / US state privacy laws (where applicable) | Request access, correction, deletion, portability, and opt-out or limit choices for covered personal information where applicable by law; rights depend on residency, verification, data type, and legal exceptions | support@omtx.ai |
| EEA/UK (GDPR) | Access, correction, deletion, portability; restrict or object to certain processing | Account privacy controls or email |
| Brazil (LGPD) | Confirm processing; anonymization; review automated decisions | support@omtx.ai |
| Canada (PIPEDA) | Access, correction; complain to OPC | support@omtx.ai |
8.1 Account Closure and Model Training
Account closure or subscription cancellation does not by itself change the rights and restrictions that applied to Generated Data already generated under a paid Data Generation order. You may continue using that Generated Data under the same Terms, license scope, and order-specific restrictions, and Om may continue to use data as described in the Terms and the applicable product flow, order, or written Om agreement, except where applicable law or a written Om agreement requires a different result. Personal account information can be deleted per this Policy.
8.2 Subscription Plans and Data Generation
- Subscription plans control subscription-gated Om workflows, model-enabled services, Data Generation Slots, plan-only API or MCP features, and related plan entitlements. Separately funded Wallet Credits control supported pay-as-you-go usage where available.
- A Data Generation Slot means generation work in process under a subscription plan, not a monthly publication, resale, or ownership quota.
- Subscription entitlements are governed by active subscription status, plan rights, checkout flows, order forms, or other written license coverage. Paid Data Generation order rights for Generated Data associated with the ordered
protein_uuid, including updated snapshots or vintages Om makes available for that sameprotein_uuid, are governed by the applicable paid order and Om Terms.
See the Terms of Service for licensing terms, Digital and Physical Derived Works, payment obligations, remedies for unauthorized or unpaid use, the 60-day cure period, and consequences of non-payment.
9. Security
We use reasonable administrative, technical, and organizational safeguards designed to protect personal information. No method of transmission or storage is completely secure.
10. International Transfers
We may transfer personal information across borders. Where required, we rely on appropriate safeguards such as standard contractual clauses or other lawful transfer mechanisms.
11. Data Retention
We retain personal information for as long as needed to provide the Services, comply with legal obligations, resolve disputes, and enforce agreements. Retention periods may vary by data type and jurisdiction.
12. Children's Privacy
The Services are not directed to children under 18, and we do not knowingly collect personal information from children.
13. Changes to This Policy
We may update this Policy from time to time. Updates become effective when published in our application. Continued use requires accepting the current legal version where applicable.
14. Contact
Om Therapeutics, Inc.
3210 Merryfield Row, San Diego, CA 92121 USA support@omtx.ai