Legal
Terms of Service
The agreement between you and Drug Catalog when you use the API, dashboard, MCP server, or any SDK we publish. Plain language wherever it's allowed to be.
Effective date: 3 June 2026
1. Acceptance and parties
These Terms of Service (the “Terms”) form a binding agreement between you (“you”, “Customer”) and the company operating Drug Catalog at drug-database.com (“we”, “us”, “Drug Catalog”), a company incorporated under Swiss law. By creating an account, generating an API key, or otherwise using the Service, you accept these Terms. If you do not accept them, do not use the Service.
If you accept these Terms on behalf of a company or other legal entity, you represent that you have authority to bind that entity, and “you” refers to that entity.
2. Eligibility
You must be at least 18 years old and capable of forming a legally binding contract. The Service is offered for business and professional use, not for personal consumer use. You must not be subject to sanctions that would prohibit us from providing the Service to you.
3. The Service
The Service is a worldwide drug master and interactions API. We aggregate, normalise, version, and serve data ingested from 44 public sources across Switzerland, the European Union and the United Kingdom, and the United States. The full source list, cadence, and per-source licensing notes are published at drug-database.com/docs.
The Service is delivered as REST endpoints under /v1, a GraphQL endpoint under /v1/graphql, an optional Model Context Protocol (MCP) server, FHIR R4 and HL7v2 adapters, and a dashboard hosted at drug-database.com.
We may add, modify, or deprecate endpoints. Breaking changes ship under a new major version (/v2) with at least eighteen months of overlap with the prior version.
4. Accounts and API keys
An account is created by signing up with a valid email address (the “owner email”) and a tenant name. Each account is provisioned one or more tenant-scoped API keys. API keys are shown once at creation and never again; we store only a SHA-256 hash. You are responsible for the security of any plaintext key value issued to you. Lost keys can be rotated but never recovered.
You are responsible for all activity that occurs under your API keys, including usage by your end-users, agents, and downstream systems.
5. Plans, quotas, and billing
The Service is offered in tiers — Developer (free), Starter, Growth, and Enterprise. Each tier carries a monthly request quota and a feature set published at drug-database.com/pricing. Quotas are metered per calendar month, per tenant, across all keys belonging to the tenant.
Paid plans are billed monthly in advance through Stripe. Card information is held by Stripe; we never see or store full payment instrument data. Usage above the included quota is either rate-limited or billed as overage, depending on the plan; the rules are stated in the plan description at checkout.
You can cancel a paid plan at any time from the dashboard. Cancellation takes effect at the end of the then-current billing period. We do not pro-rate refunds for partial months, except where required by law.
6. Acceptable use
You agree not to:
- resell, sub-license, or redistribute raw catalogue data in bulk beyond what the applicable upstream licence permits;
- scrape, mirror, or bulk-download the Service in ways that bypass quotas, rate limits, or authentication;
- reverse-engineer the Service for the purpose of building a competing data product (you may, of course, build any application on top of the API);
- upload, submit, or transmit through the Service any personal health information (PHI), patient names, medical record numbers, or other directly identifying data; the
/v1/prescriptions/validateendpoint accepts only bucketed context (age band, eGFR band, pregnancy flag, condition codes), and any other PHI sent to us will be rejected and may cause the request to be terminated; - use the Service in a way that infringes any third party’s intellectual property, privacy, or other rights;
- use the Service to develop a clinical decision support system, an electronic prescribing module, or any other product that interacts with patients without an appropriately qualified medical professional in the loop and without complying with the applicable medical-device regulations in your jurisdiction.
7. Source attribution and licensing
Drug Catalog ingests data from named public sources. Every API response carries a _meta.sources array identifying the upstream sources that contributed to the response. You must preserve and surface that attribution when you redistribute, display, or otherwise expose data sourced from the Service, in line with each source’s licence terms. Representative examples include:
- BAG-SL (Federal Office of Public Health, Switzerland) — public domain, attribution required;
- Swissmedic / AIPS monographs — public, redistribution allowed with attribution;
- NHS BSA dm+d — Open Government Licence v3.0, with NHS BSA acknowledgement in user-facing surfaces;
- FR BDPM (ANSM) — Licence Ouverte / Etalab v2.0;
- EMA SPOR / IDMP — public after free SPOR registration;
- FDA NDC, Orange Book, DailyMed, openFDA, UNII, DEA, HCPCS — US-government public domain;
- NLM RxNorm — public, UMLS terms apply;
- WHO ATC / DDD — licensed centrally by us from WHO CC Oslo, served as part of the Service; you may not re-distribute the raw codes as a separate downloadable dump.
Commercial sources (HCI Compendium / Documedis / hospINDEX, Vidal, Rote Liste / ABDA, BNF, USP-NF, KNMP G-Standaard, Austria-Codex, IFA PZN registry) are never aggregated into the shared catalogue. Where you hold your own licence with such a publisher, you may bring your own credentials (BYOL) for tenant-scoped passthrough; that data is not cached cross-tenant.
8. Intellectual property
We do not claim ownership of the upstream public data we ingest; the rights to that data rest with the originating authority (Swissmedic, BAG, EMA, NHS BSA, FDA, NLM, WHO CC Oslo, etc.). We do claim ownership of the Service itself: the schema design, the cross-jurisdictional normalisation, the staging and validation pipeline (the “watchtower”), the diff feed, the curated bridges between identifier systems, the SDKs we publish, the documentation, and the brand. You receive a non-exclusive, non-transferable, revocable licence to use the Service during the term, for your own internal and customer-facing applications.
9. Not medical advice
The Service is a reference data API. It is not a medical device, not a clinical decision support system, and not a substitute for professional medical judgment. Responses may be incomplete, out of date, or incorrect. Drug interactions, dosing, contraindications, and recall information are derived from public sources whose completeness and currency we cannot guarantee. Any clinical decision made on the basis of data returned by the Service must be reviewed by an appropriately qualified healthcare professional who is responsible for the patient.
You agree that you will not present the Service as a clinical authority to your end-users, and that any application you build on top of the Service which is capable of influencing patient care will carry your own equivalent disclaimer.
10. Warranty disclaimer
Except as expressly stated in a separately negotiated enterprise agreement, the Service is provided “as is” and “as available”, without warranties of any kind, whether express, implied, or statutory, including but not limited to warranties of merchantability, fitness for a particular purpose, accuracy, completeness, or non-infringement. We do not warrant that the Service will be uninterrupted, error-free, or that defects will be corrected.
11. Limitation of liability
To the maximum extent permitted by law, neither party will be liable for any indirect, incidental, special, consequential, punitive, or exemplary damages, or for lost profits, lost revenue, lost data, business interruption, or cost of substitute services, arising out of or related to these Terms or the Service, even if advised of the possibility of such damages.
Our aggregate liability for direct damages arising out of or related to these Terms is capped at the total fees actually paid by you to us under the affected plan in the twelve (12) months immediately preceding the event giving rise to the claim. For the Developer (free) tier, our aggregate liability is capped at one hundred Swiss francs (CHF 100).
The above limitations do not apply to liability that cannot be excluded under mandatory Swiss law, including liability for intentional misconduct or gross negligence.
12. Indemnification
By you. You will defend, indemnify, and hold us harmless from and against any third-party claim arising out of (a) your use of the Service in breach of these Terms, (b) data you submit to the Service in breach of Section 6, or (c) your application’s interaction with end-users.
By us. We will defend, indemnify, and hold you harmless from and against any third-party claim alleging that the Service, as provided by us and used by you in accordance with these Terms, infringes that third party’s intellectual property rights, except to the extent the claim arises from upstream public data we ingest, from your own modifications, or from your use in combination with software or data we did not supply.
13. Suspension and termination
We may suspend or terminate your access to the Service immediately if we reasonably believe you are in material breach of Section 6 (Acceptable Use) or Section 9 (Not medical advice), if you fail to pay invoiced amounts within thirty (30) days of the due date, or if continued service would expose us to legal or regulatory risk. We will use reasonable efforts to notify you before suspending, where the circumstances allow.
You may terminate these Terms at any time by cancelling all paid plans and deleting your account from the dashboard. Termination does not relieve you of accrued payment obligations.
Sections 7 (attribution), 8 (IP), 9 (not medical advice), 10 (disclaimer), 11 (liability), 12 (indemnity), 14 (governing law) and 16 (general) survive termination.
14. Governing law and jurisdiction
These Terms are governed by the substantive laws of Switzerland, without regard to conflict-of-laws principles and excluding the United Nations Convention on Contracts for the International Sale of Goods. The exclusive forum for any dispute arising out of or related to these Terms is the ordinary courts of the City of Zurich, Switzerland, subject to appeal to the Swiss Federal Supreme Court where the law allows.
15. Changes to these Terms
We may update these Terms from time to time. Material changes will be notified to the owner email on file and posted in the dashboard at least thirty (30) days before they take effect, except where shorter notice is required by law or for security reasons. Continued use of the Service after the effective date of a change constitutes acceptance of the change.
16. General
These Terms, together with the Privacy Policy, the Data Processing Agreement (where applicable), and any plan-specific terms accepted at checkout, are the entire agreement between you and us regarding the Service and supersede any prior agreements on the same subject matter. If any provision is found unenforceable, the remainder will continue in effect. Failure to enforce a provision is not a waiver of the right to do so later. You may not assign these Terms without our prior written consent; we may assign to an affiliate or in connection with a corporate transaction. Notices to us should be sent to legal@drug-database.com.
17. Contact
Questions about these Terms: legal@drug-database.com. Privacy questions: privacy@drug-database.com. Security disclosures: security@drug-database.com.