Zeldoc AI Platform - Terms and Conditions

1.Introduction and Parties

1.1 These Terms and Conditions ("Terms") govern access to and use of the Zeldoc AI Platform ("the Platform") provided by Zeldoc.ai ApS ("Zeldoc", "we", "us"), CVR no. 46329902, Åboulevarden 69, 8000 Aarhus C, Denmark.

1.2 By creating an account, accessing the Platform or entering into a written agreement, the Customer ("the Customer", "you") accepts these Terms in their entirety, cf. the Danish Contracts Act § 1 (acceptance of contract).

1.3 Zeldoc is an independent legal entity and the data controller for its own account, administration, technical and billing data, cf. GDPR Art. 4(7) (definition of data controller) and the Privacy Policy §5.1. For the processing of Customer data, Zeldoc is the processor on the Customer's behalf, cf. the Data Processing Agreement (DPA).

1.4 These Terms are governed by Danish law and constitute, together with the Subscription and the Privacy Policy, the complete agreement between the parties. The Privacy Policy can be read at zeldoc.ai/privacy.

2.Definitions

3.The Platform and Products

3.1 Product overview

The Platform consists of four integrated Products:

3.2 ZControl - Included foundation

ZControl is the foundation of the Platform and is included at no additional cost with all Products (ZCore, ZDev and ZRouter). ZControl is not sold separately, as it makes no sense without at least one of the other Products - there is nothing to administer if no Products are selected. ZControl includes as a minimum:

• User and role administration (RBAC)
• Access control for models per API key
• Usage and billing administration, including spend caps and top-ups of the prepaid balance

3.3 Product combinations

The Customer may freely combine Products, subject to the following:

• ZCore includes ZControl
• ZDev includes ZControl
• ZRouter includes ZControl and ZConnect
• ZConnect is included with ZRouter and requires an active ZRouter subscription (and thus ZControl)
• ZControl is not sold separately - it comes with at least one of the Products ZCore, ZDev or ZRouter

3.4 Model selection and data sovereignty matrix

The Customer selects via ZControl/ZRouter which models are used for inference. The choice has direct consequences for data sovereignty:

4.Access and Use

4.1 Account creation. Zeldoc provides an account to the Customer. The Customer designates an Account Administrator who has authority to manage users and Products via ZControl.

4.2 User licenses. The Subscription specifies the number of users ("Seats"). Each product may have different licensing models (user-based, usage-based, or a combination thereof).

4.3 Acceptable use. The Customer undertakes not to use the Platform for:

• unlawful purposes, including acts in violation of the Danish Penal Code or applicable EU legislation
• generating content that infringes third-party rights, including copyright, cf. the Danish Copyright Act, trademarks, cf. the Danish Trademarks Act, or confidentiality
• attempting to compromise the security or availability of the Platform, cf. the Danish Penal Code § 263 (unauthorized access to IT systems)
• extracting, reverse-engineering or reproducing the underlying technology of the Platform, cf. the Danish Trade Secrets Act (Act on the Protection of Trade Secrets)
• processing personal data in violation of the GDPR, including without a legal basis or in violation of data subjects' rights

4.4 Customer conduct. The Customer is responsible for the actions of its users on the Platform, cf. the Danish Contracts Act's rules on authority.

5.Data Sovereignty - Data Locality in the EU

5.1 Core products with data in the EU

For ZControl and for inference via ZCore, ZDev and ZRouter with local/EU-hosted models:

• Storage at Zeldoc: account/administration data, technical data, technical logs, session and security records, operational and usage metadata and backups — complete inventory cf. the Data Processing Agreement (DPA), Appendix A.3(b). Zeldoc's AI infrastructure (ZCore/ZDev) does not store content (prompts, outputs); such data is processed solely transiently during AI inference. Content is not stored by Zeldoc — storage takes place in the application layer chosen by the Customer, cf. the DPA, Appendix A.2(c) and A.3(c)
• Core inference is executed exclusively on servers within the European Union (currently Denmark), and Customer data is stored in the EU (currently Germany). Connections to the Platform pass through Cloudflare, which may terminate the encrypted connection (TLS) outside the EU
• Customer data is not transferred to, processed in or stored in countries outside the EU/EEA during core inference
• The core products can, in an alternative setup, be delivered entirely on EU hosting and EU-hosted models without US companies; the current delivery uses US companies for support functions, including Cloudflare for network and TLS termination
• No content storage during core inference: prompts, inference requests and outputs are processed transiently in memory on the inference servers in the EU, and the inference servers write neither swap, crash dumps nor KV cache to disk, cf. the Data Processing Agreement (DPA), Appendix A.2(a) and C.2
• Core inference is executed in the EU. For Cloudflare, which terminates the encrypted connection, and other operational subprocessors that are US companies, SCCs and/or the EU-US Data Privacy Framework apply as transfer mechanisms, cf. the Schrems II judgment (C-311/18) - see the subprocessor list at zeldoc.ai/subprocessors

5.2 ZRouter with external frontier models - EXCEPTION

Data leaves the EU. The Customer's prompts and inference data are transferred to the external model provider's infrastructure outside the EU (e.g. USA).

No Zero Data Retention. Zeldoc cannot guarantee that the external provider does not retain data. The external provider's own data retention policies apply.

GDPR third-country transfer. The transfer is covered by GDPR Art. 44-49 (transfer to third countries). Zeldoc ensures Standard Contractual Clauses (SCCs) and supplementary measures (encryption, data minimization), cf. Schrems II (C-311/18).

Customer obligations. The Customer must:

• Ensure a legal basis for the transfer of personal data to third countries
• Inform data subjects about the transfer, cf. GDPR Art. 13/14 (information to data subjects)
• Conduct a Transfer Impact Assessment for specific use cases
• Refrain from sending special categories of personal data (health data, criminal offences, etc.), cf. GDPR Art. 9 (special categories of personal data), through external frontier models without separate assessment

Zeldoc's measures. Zeldoc ensures:

• Operational and usage metadata per AI call (timestamp, model, token count, cost, pseudonymised key/team ID, status) is retained for 2 years for operation, billing and security. The content of the calls (prompts, files, outputs) is not stored - request/response storage is disabled
• Governance via ZControl (access management and model access per API key)
• Aggregated usage reporting and billing
• Encryption of data in transit (TLS 1.2+) between EU infrastructure and external provider

5.3 Consent

By activating ZRouter for external frontier models or ZConnect, the Customer expressly acknowledges that data leaves the EU at inference, and that Zeldoc cannot guarantee data sovereignty for these calls. The option is recorded in the Subscription, and enabling or disabling ZRouter and ZConnect is logged with a timestamp in the Platform.

5.4 Overview: Where does data leave the EU?

5.5 Data Processing Agreement

Zeldoc's Data Processing Agreement (DPA) (zeldoc.ai/dpa) forms an integral part of these Terms and governs Zeldoc's processing of personal data on your behalf. By accepting these Terms you accept the DPA.

6.Subscription, Pricing and Payment

6.1 Subscription structure. The Customer subscribes to selected Products via a written order confirmation, enrollment form or SaaS agreement. The Subscription runs on a monthly basis from the effective date. The Customer may terminate the subscription at any time with the notice specified in §11.1. There is no binding period. The number of user licenses (seats, ZDev) and the plan level (ZCore) may be increased at any time with immediate effect; increments are billed pro rata for the remainder of the month. Downgrades take effect from the next billing period.

6.2 Pricing model. The price consists - depending on Product and plan, cf. the order confirmation - of a fixed subscription fee per Product per month and/or usage-based billing for token costs. All prices are in EUR excluding VAT. The Subscription's scope of Usage (tokens) may be designed in one of the following ways:

• Included token pool (ZCore): A specified number of tokens per month and a throughput level (tokens and requests per minute) are included in the subscription fee (ZCore Starter, Small, Medium and Large). Usage beyond the pool is metered monthly in EUR at Zeldoc's published local rate (currently USD 1.50 per 1M input tokens and USD 6.00 per 1M output tokens). A spend cap is on by default: the Customer's bill cannot exceed the plan price plus add-ons unless the Customer raises the cap in ZControl. Only the models zeldoc/zcore and zeldoc/task count against the pool; embeddings and transcription run under fair use. As add-ons the Customer may choose ZCore Extra (a prepaid token block at the plan's throughput, fixed monthly amount) or ZCore Unlimited (no token meter within fair use, for a surcharge equal to the plan price).
• Per user with included agent credits (ZDev): ZDev is billed per user per month. Go and Pro include a fixed number of agent credits per month; Max provides unlimited usage under Zeldoc's fair-use policy. Usage beyond the included amount is handled under the fair-use policy, cf. §7.4.
• Prepaid balance (ZRouter and ZConnect): No tokens are included. Usage with external frontier models is drawn from a prepaid balance that the Customer tops up in ZControl. The plan's admin fee (Business: 8% of each top-up; Enterprise: by agreement) is deducted at top-up, after which usage is metered at the provider's token prices against the balance, cf. §7.4.

Usage not covered by the subscription fee is billed as set out above and in §7.4.

6.3 Billing. The subscription fee and metered usage (ZCore beyond the included pool) are billed monthly in arrears. Top-ups of the prepaid balance (credits for ZRouter/ZConnect) are purchased in advance by card in ZControl; a receipt/invoice is issued automatically for each purchase, and the plan's admin fee is deducted at purchase. The minimum top-up amount is EUR 100. The Customer may enable auto-recharge with a self-chosen threshold and amount. Enterprise customers may instead be invoiced for top-ups by agreement. Payment term: 30 days net, cf. the Danish Interest Act (interest on late payment).

6.4 Price adjustment. Zeldoc may adjust the subscription fee with 1 month's written notice. The Customer may terminate the agreement with 1 month's notice if the Customer does not wish to accept the price adjustment, however no later than the effective date of the price adjustment. Usage-based billing may be adjusted continuously in line with actual token costs.

6.5 Refund policy. Subscription fees are non-refundable. Usage costs are billed solely for actual usage. Prepaid credits are non-refundable and expire 12 months after the date of purchase; unused credits lapse on expiry and on termination of the subscription without refund. Credits are consumed oldest-first. Zeldoc generally does not offer a Service Level Agreement (SLA) - consistent with the practice of leading AI providers such as OpenAI and Anthropic, which do not offer SLAs. SLA may be offered in special cases for enterprise agreements.

7.ZConnect and ZRouter - External Frontier Models (Special Terms)

7.1 Description

ZConnect is included with ZRouter without a separate subscription and gives the Customer's users access to the Claude Office plugin through ZRouter. Usage is drawn from the Customer's prepaid ZRouter balance at the provider's token prices plus the plan's admin fee. ZConnect does not offer data sovereignty for external calls.

ZRouter is the underlying routing layer that enables this access. Both ZRouter (when routing to external frontier models) and ZConnect are subject to the same data sovereignty exceptions in §5.2.

7.2 Data transfer outside the EU

When using ZRouter with external frontier models or ZConnect, the Customer's prompts and inference data leave the EU data region and are transferred to the external model provider's infrastructure (e.g. Anthropic in the USA). Zeldoc ensures:

• Operational and usage metadata per AI call (timestamp, model, token count, cost, pseudonymised key/team ID, status) is retained for 2 years for operation, billing and security. The content of the calls (prompts, files, outputs) is not stored - request/response storage is disabled
• Governance via ZControl (access management and model access per API key)
• Aggregated billing and usage reporting
• Encryption in transit (TLS 1.2+)

7.3 Consent and Customer responsibility

Upon activation, the Customer expressly acknowledges that:

• Data leaves the EU at inference via external models
• Zeldoc cannot guarantee Zero Data Retention for external calls
• The external model provider's own policies apply to data retention
• The Customer is responsible for ensuring a legal basis for the transfer, cf. GDPR Art. 44-49 (transfer to third countries)
• The Customer is responsible for informing data subjects, cf. GDPR Art. 13/14 (information to data subjects)

7.4 Usage billing

Usage with external frontier models (token costs at the external provider via ZRouter/ZConnect) is not included in any subscription and is drawn from the Customer's prepaid balance. Credits are purchased in advance by card in ZControl (Enterprise customers may instead be invoiced by agreement) with a minimum top-up amount of EUR 100, and a receipt/invoice is issued automatically for each purchase. At each purchase the plan's admin fee (Business: 8%; Enterprise: by agreement) is deducted, and the remainder is converted to token credits at the day's exchange rate - the Customer bears no currency risk thereafter. Usage is metered at the provider's token prices (passthrough) against the balance. The prepaid balance constitutes the Customer's spend cap; Zeldoc alerts the Customer when 80% of the balance has been used, and the Customer may enable auto-recharge with a self-chosen threshold and amount. Prepaid credits are non-refundable and expire 12 months after the date of purchase; unused credits lapse on expiry and on termination of the subscription without refund. Credits are consumed oldest-first.

Usage billing may also apply to local/EU models: ZCore usage beyond the included token pool is metered at the published local rate, cf. §6.2, unless ZCore Unlimited has been added. ZDev is governed by the fair-use policy; where usage consistently exceeds fair use, Zeldoc may suggest an upgrade, lower the rate limit or agree supplementary passthrough billing for usage beyond the included amount.

Usage above the plan's throughput (tokens and requests per minute) is rate-limited until the next minute. Usage that does not constitute fair usage, including unreasonably high usage, automated or scripted bulk generation, use for purposes other than intended, and reselling access, may result in reduced speed, throttling/rate limiting, supplementary billing or temporary suspension of access until the 1st of the following month, cf. §6.2.

8.Intellectual Property

8.1 The Platform. Zeldoc retains all intellectual property rights to the Platform and Products, including software, infrastructure, user interfaces and documentation, cf. the Danish Copyright Act.

8.2 Customer data. The Customer retains all rights to Customer data. Zeldoc processes Customer data as processor on behalf of the Customer, who is the controller, in accordance with the Privacy Policy and the Data Processing Agreement (DPA), cf. GDPR Art. 28 and §5.5. The scope of storage and retention periods are stated in the DPA, available at zeldoc.ai/dpa, and in the subprocessor list at zeldoc.ai/subprocessors.

8.3 Generated content. Content generated through the Platform ("Outputs") belongs to the Customer, provided that the Customer has the rights to the prompts and inputs that led to the generation. Zeldoc makes no claims to Outputs.

8.4 Open-source models. Zeldoc's Products are built on open-source models and technologies. Open-source models are licensed under various license models, each with different terms for use, modification and distribution. Zeldoc endeavors to use only models with licenses that permit commercial use and generation of Outputs without restrictions. Zeldoc maintains an internal updated list of used models and their licenses.

8.5 Outputs and third-party rights. AI-generated Outputs may contain content reproduced from the model's training data. This is a general issue for all AI models - including closed frontier models (e.g. OpenAI GPT, Anthropic Claude) - and is not specific to open-source models. Zeldoc provides no warranty that Outputs are free of third-party rights, regardless of which model is used. The Customer should assess the specific use case and, in case of doubt, obtain independent legal advice.

8.6 Feedback. If the Customer provides feedback, suggestions or ideas to Zeldoc, Zeldoc may freely use these to improve the Platform without compensation or obligation.

9.Confidentiality and Security

9.1 Mutual confidentiality. Both parties protect each other's confidential information, including technical specifications, prices and trade secrets, cf. the Danish Trade Secrets Act (Act on the Protection of Trade Secrets).

9.2 Security standards. Zeldoc maintains industry best practices for information security, including:

• Encryption in transit (TLS 1.2+)
• Access control via ZControl
• Logging of access to systems; technical logs retained for 90 days
• Regular security reviews and vulnerability scanning

9.3 Data use. Zeldoc does not use Customer data to train, fine-tune or improve models.

9.4 Incident handling. Zeldoc informs the Customer of security incidents that may affect Customer data without undue delay - no later than 48 hours after discovery, cf. GDPR Art. 33 (breach notification).

10.Disclaimer and Limitation of Liability

10.1 "As-Is". The Platform is provided "as is". Zeldoc does not warrant that Outputs are correct, complete or fit for a particular purpose. AI-generated content may contain errors ("hallucinations").

10.2 Limitation of liability. Zeldoc's total liability under these Terms is limited to the amount the Customer has paid for the relevant Product in the 12 months preceding the event that gave rise to the claim, cf. the Danish Contracts Act § 36 (reasonableness).

10.3 Exceptions. The limitation of liability does not apply to:

• Zeldoc's gross negligence or wilful damage, cf. the Danish Liability for Damages Act
• Breach of confidentiality obligations
• Claims for damages that cannot be excluded by law, cf. the Danish Sale of Goods Act (Purchase Act) § 22 by analogy

10.4 Indirect damages. Neither party is liable for indirect damages, lost profits, lost data or business interruption, except where the law requires otherwise, cf. the Danish Liability for Damages Act's general rules.

10.5 AI-specific allocation of responsibility. The Customer acknowledges that:

• AI models are stochastic and may produce variable output
• The Customer is responsible for validating Outputs before use in critical decisions
• Zeldoc is not responsible for decisions made based on Outputs
• If the Platform constitutes a high-risk AI system, cf. the EU AI Act (Regulation 2024/1689), the special requirements of the AI Act apply, and the parties enter into a separate agreement on roles and responsibilities

11.Termination

11.1 Termination by the Customer. The Customer may terminate the subscription with 1 month's written notice. There is no binding period, cf. §6.1.

11.2 Termination by Zeldoc. Zeldoc may terminate the agreement with 1 month's written notice, or immediately upon:

• The Customer's material breach (if not remedied within 30 days of written demand), cf. the Danish Contracts Act § 23 (breach)
• The Customer's bankruptcy or insolvency, cf. the Danish Bankruptcy Act
• If continued operation would result in non-compliance with applicable law

11.3 Data upon termination. Upon termination, the Customer chooses whether associated tenant data is returned or deleted - no later than 30 days after termination, cf. the Data Processing Agreement (DPA), Clause 11.2 and Appendix C.4. Usage data and invoices can be retrieved in ZControl; other tenant data is provided on request in a common, machine-readable format. Statutory retention (e.g. the Bookkeeping Act) is excepted. Content (prompts, outputs) is not stored by Zeldoc and therefore requires no deletion upon termination; storage takes place in the application layer chosen by the Customer, cf. the DPA, Appendix A.3(c). The Customer's user and administration data (name, email), for which Zeldoc is the data controller, is deleted 30 days after the termination date, unless otherwise required by law (e.g. the Bookkeeping Act's retention of billing data), cf. GDPR Art. 5(1)(e).

12.Audit Access

12.1 The Customer may once a year request Zeldoc's written documentation (self-declaration) of compliance with the data locality and security terms, cf. GDPR Art. 28(3)(h) (audit access).

12.2 Upon reasoned suspicion of a breach, the Customer may, with 30 days' written notice, have an independent third party review Zeldoc's relevant systems and procedures. Such a review must not disrupt operations and must be conducted under confidentiality obligations, cf. GDPR Art. 28(3)(h) (audit access).

13.Governing Law and Jurisdiction

13.1 Choice of law. These Terms are governed by Danish law, with the exception of international private law rules on choice of law.

13.2 Jurisdiction. Disputes are resolved by the ordinary Danish courts, in the first instance the Court of Aarhus (Retten i Århus), Denmark.

13.3 Mediation. The parties endeavor to resolve disputes through negotiation before legal proceedings.

13.4 EU AI Act. The parties acknowledge that the Platform may be covered by the EU AI Act (Regulation (EU) 2024/1689). Zeldoc documents the Platform's risk classification and the relevant compliance measures. If the Platform constitutes a high-risk AI system, the parties enter into a separate agreement on roles, responsibilities and documentation, cf. AI Act Art. 16-29 (provider obligations).

14.Changes to Terms

14.1 Zeldoc may change these Terms with 30 days' written notice. In the case of material changes, including price adjustments cf. §6.4, the Customer is entitled to terminate the subscription without notice before the change takes effect, cf. the Danish Contracts Act § 36 (unreasonable terms).

14.2 Changes to usage billing (token prices) may be made without prior notice in line with underlying cost changes.

15.Miscellaneous

15.1 Entire agreement. These Terms, together with the Subscription and the Privacy Policy, constitute the complete agreement between the parties.

15.2 Assignment. The Customer may not assign rights or obligations without Zeldoc's written consent. Zeldoc may assign rights to an affiliated company.

15.3 Force Majeure. Neither party is liable for delay or non-performance caused by circumstances beyond their reasonable control (including war, natural disasters, internet blackouts), cf. general principles of contract law.

15.4 Notices. Written notices are sent to the addresses/email addresses specified in the Subscription.

15.5 Severability. If a provision is found to be invalid, it does not affect the other provisions, which remain in force, cf. the Danish Contracts Act § 36 (unreasonable terms).