fremai Terms of Service

title: fremai Terms of Service author: fremverk date: 2026-08-13 version: “1.0” status: Published v1.0 lang: en #

Last updated: 2026-08-13

Effective Date: 2026-08-13 — Version: 1.0 (see the change log for the effective date of each amendment)

These Terms of Service (“ToS”) form the master agreement between fremverk ApS and the Customer for use of the fremai service at fremai.eu. The Acceptable Use Policy, Data Processing Agreement, Service Level Agreement, and Privacy Notice are incorporated by reference and form part of the same contract.

1. Parties #

This agreement is between:

fremverk ApS ("fremverk", “we”, “us”, “our”)
CVR: 39150689
VAT: DK39150689
Ringager 4C, 2. tv, 2605 Brøndby, Denmark
Contact: legal@fremai.eu for contractual notices, support@fremai.eu for service matters. General enquiries: info@fremverk.com.

and

the Customer (the legal entity that signs up for, or is invoiced for, the fremai service), identified by the organisation name, billing address, and VAT number provided at signup or in an ordering document.

fremai is a product brand of fremverk ApS. fremverk ApS is the sole legal signatory and contracting party.

1.1 Definitions #

• Customer — the legal entity identified at signup or in the Order Form that contracts with fremverk for use of the Service. Every account belongs to a Customer tenant, including a solo self-serve developer (a “team-of-one”).
• User — an individual authorised by the Customer to use the Service under the Customer’s tenant.
• Service — the fremai EU-sovereign, OpenAI-compatible AI-inference service described in §2.
• API Key — a customer inference credential in the sk-fremai-… format, or an OAuth-issued ephemeral credential, that authenticates requests to the Service.
• Backend — the third-party EU-sovereign inference provider that serves model completions as fremverk’s sub-processor (see DPA Annex B).
• Prompts and Completions — the request content the Customer sends to the Service and the model output returned; collectively, Customer Content.
• Usage Metadata — the billing- and operations-relevant metadata the Service records (token counts, model id, latency, HTTP status, cost, key id, timestamp). See §5 and DPA §4.
• Fees — the amounts payable by the Customer for the Service, per §4 and the published pricing at www.fremai.eu.
• Order Form — any ordering document or signup record recording the commercial terms.

2. The Service #

fremai is an EU-sovereign, OpenAI-compatible AI-inference service. A Customer points an OpenAI-compatible client at https://api.fremai.eu/v1 and consumes inference against a curated catalog of models served under their real upstream identifiers. The Service includes, without limitation:

• An OpenAI-compatible inference API at https://api.fremai.eu/v1 (chat completions, completions, embeddings, and other routes the Backend serves under OpenAI-compatible paths).
• A developer console at app.fremai.eu for signup, API-key issue/revoke, usage dashboards, budgets and alerts, billing, and team management.
• A public pricing page and model catalog at www.fremai.eu, and developer documentation at docs.fremai.eu.
• Per-key, per-user, per-team, and per-tenant budgets and rate limits; usage metering; and usage / billing export.

2.1 What the Service is NOT #

• fremai does not develop, train, or first place any model on the EU market. It resells access to models served by the Backend. fremai is a downstream distributor of GPAI-model access, not a provider of a general-purpose AI model or of a high-risk AI system under Regulation (EU) 2024/1689 (the “AI Act”). The Customer, as the party building an application on top of the models, is the deployer for AI-Act purposes and bears the deployer obligations (see §11).
• fremai does not inspect, moderate, or filter prompt or completion content (see §5 and AUP §5). This follows from the no-content posture in §5.

3. Accounts, keys, and access #

• Signup and card gate. Self-serve signup is at app.fremai.eu. A verified payment card (via Mollie) is required before API Keys activate. On card verification fremverk grants a small free credit (currently €5, 30-day expiry; the exact token equivalent depends on the model). Enterprise accounts are onboarded manually and may bypass the card gate.
• API Keys. The Customer may hold multiple sk-fremai-… keys, each individually revocable with its own optional budget, rate limit, model subset, and expiry. The Customer is responsible for keeping keys confidential. fremverk may automatically revoke a key on detected leakage (e.g. a secret-scanning notification) or on a spend-velocity anomaly, and will alert the Customer.
• Authentication. Static sk-fremai-… keys are the drop-in path for OpenAI SDKs, LangChain, curl, and CI. OAuth (via the self-hosted Zitadel identity layer) is offered for agent clients and machine-to-machine use; OAuth-issued credentials are short-lived and rotated.
• Acceptable use. All use is subject to the AUP. fremverk may suspend or throttle keys, users, teams, or a tenant for AUP breach, non-payment, or to protect the shared Backend.

4. Fees, billing, and payment #

• Currency. Card and prepaid balances are always billed in EUR. The public price page is in EUR. DKK is available on enterprise invoices only (via Dinero) for Danish customers.
• Pricing. Per-token prices are published openly at www.fremai.eu, per model, for input and output tokens. The fremai price is the Backend token price plus a flat markup (currently +25%), recomputed on a regular cadence to absorb USD→EUR FX movement. fremverk may change published prices prospectively on notice per §8; changes do not apply retroactively to already-consumed usage.
• Metering. Customers are metered on the token usage the Backend reports for each request — the same figures fremverk is charged on. Where the Backend omits usage on some streaming paths, fremverk falls back to a local token count and reconciles against the Backend’s figures.
• Self-serve (prepaid). Usage debits a prepaid credit balance. Top-ups are made via Mollie. A key returns 402 Payment Required at zero balance. Free-credit grants (§3) expire per their stated term and are not redeemable for cash.
• Enterprise (postpaid). Metered monthly invoicing via Dinero, net-30 in arrears on actual usage, on a negotiated rate. Two invoicing shapes are offered: (a) advance monthly commit + arrears overage; or (b) pure net-30 arrears on actuals. Overage above a commit accrues and is billed in arrears — it does not hard-stop the Service.
• Credit limit. Each tenant carries a credit limit — the hard cap on unbilled accrued usage. It is the only control that throttles or stops the Service for commercial reasons, is set by creditworthiness, and is raisable. EU B2B VAT reverse-charge is applied on VIES-validated cross-border supplies; VAT treatment follows the customer’s validated region and is never defaulted to Denmark.
• No refunds. Except where required by mandatory law or expressly stated in an Order Form, prepaid credit and paid Fees are non-refundable. Unused free credit is never refundable.

5. Content handling — metadata-only, no training #

This is a defining term of the Service and a material commitment:

• Prompts and Completions are never persisted at the fremai layer and are never used to train, fine-tune, or improve any model, whether for fremverk, the Backend, or any third party. The Backend serves inference from ephemeral, zero-retention execution and returns the result; fremai proxies it without storing the content.
• fremai records Usage Metadata only (token counts, model, latency, status, cost, key id, timestamp) for billing, rate-limiting, security, and audit. Response caching that would store content is off by default.
• Because fremai does not read content, it does not moderate, filter, or scan prompts or completions. Abuse controls operate on metadata and the AUP, with account suspension as the backstop. Any content-inspection capability (e.g. an opt-in DLP tier) is an explicit, separately-disclosed opt-in and never the default path.

Full detail is in the Privacy Notice and DPA Annex A.

6. Availability and support #

The Service’s availability commitment, measurement method, exclusions, and service credits are set out in the SLA. During the Phase-1 single-backend period the Service is offered on a best-effort / beta basis (see SLA §2); availability tracks the Backend. Live status is at https://status.fremai.eu.

7. Intellectual property; Customer Content ownership #

• The Customer retains all rights in its Prompts and in the Completions returned to it, to the extent such rights subsist. fremverk claims no ownership of Customer Content and, per §5, retains none of it.
• fremverk (and its licensors, including the model developers and the Backend) retain all rights in the Service, the models, and the documentation. Nothing here transfers those rights to the Customer.
• The Customer is responsible for its use of Completions, including any obligation to mark or disclose AI-generated content under applicable law (§11). fremai does not strip provenance metadata a Backend emits.

8. Changes to the Service and to these terms #

fremverk may modify the Service and these ToS. For material adverse changes to these ToS or the incorporated documents, fremverk gives at least 30 days’ prior notice by email to the tenant’s billing contact and by posting to the trust center; changes to sub-processors follow the dedicated notice and objection procedure in DPA §10. Continued use after the notice period constitutes acceptance. Non-material or legally-required changes may take effect on shorter notice.

9. Term, suspension, and termination #

• These ToS run for the subscription term and renew per the Order Form or the self-serve plan.
• fremverk may suspend access for AUP breach, non-payment, security risk, or legal requirement, with notice where practicable and immediately where necessary to protect the Service or third parties.
• Either party may terminate per the Order Form or, for self-serve, at any time by closing the account. On termination, API Keys are deactivated and prepaid credit is forfeited except where mandatory law requires otherwise. Data handling on termination follows DPA §9.

10. Warranties, liability, and indemnity #

• The Service is provided “as is” and “as available” to the extent permitted by law. fremverk does not warrant that model outputs are accurate, complete, fit for a particular purpose, or free of errors. The Customer is responsible for evaluating Completions before relying on them.
• To the maximum extent permitted by law, neither party is liable for indirect, incidental, or consequential loss, or for lost profits, revenue, or data. fremverk’s aggregate liability under this agreement is capped at the Fees paid by the Customer for the Service in the 12 months before the event giving rise to the claim.
• Raised cap for personal-data breaches. For claims arising from fremverk’s breach of the DPA security annex that results in a Personal Data Breach, the cap above is raised to two times the annual Fees, without prejudice to any statutory liability that cannot be limited. fremverk applies the same raised cap across its products; the higher figure reflects that a data-protection failure is the failure mode with consequences beyond the Fees paid.
• These limits do not exclude liability that cannot be excluded under mandatory law (including gross negligence, wilful misconduct, and liability under GDPR to data subjects).
• The Customer indemnifies fremverk against third-party claims arising from the Customer’s use of the Service in breach of the AUP or applicable law.

11. AI Act and lawful-use obligations #

• fremai’s role is a downstream distributor of GPAI-model access (§2.1). The Customer is the deployer and bears the deployer-facing AI-Act duties for its own application — including, where applicable, the Art. 50(1) “you are interacting with an AI” disclosure and Art. 50(4) deepfake / public-interest-text labelling. fremai surfaces this guidance in the documentation but does not and cannot enforce it, because it does not inspect content.
• Prohibited practices (AI Act Art. 5) are prohibited by the AUP; because fremai does not inspect content, enforcement is contractual and act-on-report.
• Value-chain cooperation. Where the Customer builds a high-risk AI system on fremai, fremverk will, on reasonable request, provide the information and technical cooperation reasonably needed for the Customer’s conformity work, and will pass through upstream GPAI documentation obtained from the Backend to the extent it is available and fremverk is permitted to share it.

12. Confidentiality and data protection #

Each party protects the other’s confidential information. Processing of personal data in connection with the Service is governed by the DPA, under which fremverk acts as the Customer’s processor and the Customer is the controller.

13. Governing law and disputes #

These ToS are governed by the laws of Denmark, excluding its conflict-of-laws rules and the UN Convention on Contracts for the International Sale of Goods. The courts of Denmark (the City Court of Copenhagen as court of first instance) have exclusive jurisdiction, without prejudice to any mandatory consumer-protection venue rules that may apply to an individual acting as a consumer.

14. General #

Notices to fremverk go to legal@fremai.eu, with a copy to info@fremverk.com. Notices to the Customer go to the billing contact of record. If any provision is held unenforceable, the remainder stays in force. fremverk may assign this agreement to an affiliate or successor of the fremverk business. These ToS, together with the incorporated documents and any Order Form, are the entire agreement for the Service.

Change log #