Terms of service
The rules for using private security inference: contract, access, authorised use, verification, billing, your data and your responsibilities.
Last updated 18 November 2026.
Scope and provider
These terms govern the use of the private security inference service provided by W&M IT-Solutions UG (haftungsbeschränkt), Kaiserin-Augusta-Allee 111, 10553 Berlin, Germany (the provider). The service provides private model APIs for authorised security work.
The acceptable use policy, the data processing agreement and, where agreed, an individual order form are part of these terms. Conflicting terms of the customer do not apply.
The service is in development and not generally available yet. Features, models, hardware and prices are provisional until the launch benchmarks are complete.
Contract structure and conclusion
This website does not conclude contracts. Access is granted individually after a waitlist request.
When the provider activates the customer’s account, a framework contract on the basis of these terms is concluded. The framework contract is free of charge and runs for an indefinite period.
Each deploy of an instance is a separate paid order under the framework contract. Before the deploy, the customer sees the model, the variant, the country, the hourly price and, for Pro and Frontier, the reservation. The customer can correct these entries with the back button or by changing the selection. By clicking the deploy button, which states that the order is subject to payment, the customer places the order. The provider accepts it by starting the instance.
The provider stores the contract text. The terms that apply to an order can be viewed in the account at any time and are sent to the customer by email when the account is activated and whenever they change.
The binding language of the contract is English. A German translation may be provided later. Where a German version is declared binding, both versions have equal effect.
Customers and accounts
Customers can be businesses and consumers. A consumer is a natural person who uses the service for purposes that are mainly neither commercial nor self-employed. Provisions that apply only to consumers or only to businesses say so.
Consumers must be at least 18 years old. A business customer is represented by a person who is authorised to act for it.
The customer gives accurate contact details and, for businesses, company details including a valid VAT identification number where one exists, and keeps them up to date. A customer may authorise its own staff to use its account and is responsible for their use.
Access and API keys
Each instance has its own API key, which is checked on the instance. The provider stores only a hash of the key.
The customer keeps API keys confidential and is responsible for all use of an instance under its key. If a key may have been exposed, the customer stops the instance without delay.
The provider may limit the number of concurrent instances per customer, depending on available GPU capacity.
The service
The customer selects a model, a variant and a country and starts an instance. Each instance runs one model on its own dedicated GPU with a GPU provider based in the European Union and offers an OpenAI-compatible API over TLS. The instance always runs in the country the customer selected. If no capacity is available there, the deploy fails or the customer chooses another country. The provider never moves an instance to another country on its own.
The customer uses the API while the instance is running. Stopping an instance ends that order and deletes the instance.
If a health check fails, the provider redeploys the instance or takes the steps the situation requires. A redeployed instance keeps its endpoint, API key, model version and country, and the customer is informed by email.
There is no entitlement to a particular GPU being available at a particular time. A deploy that fails before the first successful health check is free of charge. Reserved capacity, in particular for Frontier models, is available only under an individual order form with its own term and price.
Models, licences and variants
The service uses open-weight models and security derivatives of them. The adaptation of the weights for security tasks is carried out by the model developers or by specialised third parties, not by the provider. The provider selects, operates and serves these models.
The licences of the models and derivatives apply in addition to these terms. The licence of each model is named on the models page and shown again at the deploy. Where a licence or a usage policy of a model contains special conditions, the customer has to confirm them before the deploy.
Each model class is offered as a Blue Team and a Red Team variant where the licence of the model allows it. A model whose licence does not allow a Red Team variant is offered as a Blue Team variant only.
Verification
Blue Team variants need no verification.
Red Team variants of Entry and Basic require a verified email address, a stored payment method and a one-time description of the intended use.
Red Team variants of Pro and Frontier require full verification. Frontier is available to business customers only. Full verification consists of an identity check with an identity document and a selfie, which is matched with the document photo (biometric check), company details for business customers, a description of the intended use, and evidence of a legitimate reason or professional background. The identity check is carried out by Stripe as service provider. A person at the provider reviews the intended use and the evidence.
The biometric check requires the customer’s express consent. It is necessary to establish reliably who uses the most capable Red Team models. A customer who does not consent cannot use Red Team variants of Pro and Frontier. All other models remain available.
Full verification is renewed once a year. The customer confirms its details and its intended use. A new identity check is required only if the person, the company or the intended use changes, or if there are indications of misuse.
The provider may ask for further evidence, may refuse access, and may withdraw access to a Red Team variant if the verification is not or no longer met or if these terms are breached.
Use for third parties
Business customers may integrate Blue Team variants into their own products and services. They bind their users to rules that are at least as strict as the acceptable use policy and are responsible for their users as for their own conduct.
Red Team variants may be used only by the customer’s own staff and by service providers working on its behalf. Making a Red Team variant available to other third parties, in particular through the customer’s own product, requires the provider’s prior consent in text form.
Within an engagement, people of the customer’s client may work on an instance together with the customer as part of its team. The customer is responsible for them and does not hand over API keys to them permanently.
Sanctions and export control
The customer confirms that neither it nor any person controlling it appears on a sanctions list of the European Union, the United Nations, Germany or the United States, and that it is not located in or acting for a country or region that is subject to a comprehensive embargo.
The customer does not use the service in breach of sanctions or export control law, in particular the EU Dual-Use Regulation and the German Foreign Trade and Payments Act, and does not give access to the service or its outputs to sanctioned persons or for prohibited end uses. Intrusion software and cyber-surveillance items can be subject to export controls, and the customer is responsible for checking these rules for its own use.
The provider may refuse, suspend or end access where sanctions or export control law requires it or where there are indications of a breach, and may ask the customer for the information needed to check this.
Misuse
The provider reviews suspected misuse on the basis of information it legitimately has, such as account, verification and billing data, deploy confirmations, usage metadata, reports from third parties and information from authorities. The provider has no technical access to running instances and cannot read prompts or outputs.
In case of concrete indications of misuse, the provider may suspend the instance or the account immediately. It informs the customer of the suspension and its reason without delay, unless it is legally prevented from doing so. The customer can respond and provide evidence within 7 days. The provider then lifts the suspension or ends access.
In case of clear and serious misuse, in particular content relating to child sexual abuse, the provider may end access immediately without a prior hearing.
Where the law requires it, or where there are concrete indications of a criminal use of the service, the provider may report to the competent authorities and cooperate with them within the law.
Prices and payment
The hourly price shown at the deploy applies to that instance. Prices shown on the website are indicative starting prices per hour and may change before launch. The provider may change prices for future deploys and announces changes on its website in advance.
Prices are in euros. For business customers they exclude VAT. Business customers in another EU member state with a valid VAT identification number are invoiced under the reverse charge procedure. For consumers, prices include the VAT of the member state in which the consumer lives, and the price including VAT is shown before the deploy.
Payments are processed by Stripe as payment provider. The customer accepts Stripe’s terms for payments. The provider does not store complete payment card data. A deploy requires a stored payment method. The provider issues an invoice for every charge.
Where an invoice is issued separately, it is payable within 14 days of receipt without deduction. In case of late payment, statutory default interest applies.
Business customers may set off only claims that are undisputed or have been finally established by a court.
Billing of instances
Charges follow each started hour of a healthy instance. Every started hour counts as a full hour. Billing begins at the first successful health check. Time before the instance is healthy, including a failed deploy, is not billed.
Time during which an instance is not healthy for reasons within the provider’s or its GPU provider’s sphere is not billed. If an instance ends for such a reason, billing ends at the last successful health check.
Entry and Basic are pay as you go. No amount is reserved or paid in advance. The hours used are charged when the instance ends, at the latest at the end of each calendar month, and in addition whenever the open amount reaches €250.
For Pro and Frontier, the customer chooses a planned running time at the deploy. The planned running time multiplied by the hourly price is reserved on the customer’s payment method and shown before the deploy. A reservation is not a payment. Only the actual usage is charged, and the reservation is released. When a reservation is used up or expires, a new reservation is made automatically. If it fails, the customer is warned by email and the instance is stopped after a short grace period stated in the warning. Depending on the bank, a reservation can reduce the available credit until it is released.
If a charge fails, the provider informs the customer by email. The customer has 3 days to update its payment method. During this period no new instances can be deployed. After it, running instances are stopped and deleted. The claim for the hours used remains.
The customer can set a monthly spending limit in its account. It is warned when 80 per cent of the limit is reached and can choose that its instances are stopped when the limit is reached. Without such a setting, the customer is responsible for stopping its instances.
Right of withdrawal for consumers
Consumers have a statutory right of withdrawal. The details, including the model withdrawal form, are set out in the withdrawal notice.
An instance starts immediately after the deploy. Before every deploy, the consumer can expressly request that the service starts before the end of the withdrawal period and confirm that it knows it loses its right of withdrawal once the service has been fully provided. If the consumer withdraws after such a request, it pays a proportionate amount for the hours provided until the withdrawal.
Data protection
Prompts and outputs are never stored and never used to train models. They exist only in the memory of the instance while they are processed. Request logging is switched off, and no content is written to logs or disks. Inference traffic goes directly to the instance and does not pass through the provider’s control plane, which can only start, stop, redeploy and delete the instance and check its health. The provider has no technical access to running instances.
A data processing agreement (AVV / DPA) with a list of subprocessors is part of onboarding. The provider announces new subprocessors at least 30 days in advance by email. The customer can object, and if no solution is found, it can terminate the framework contract without disadvantage before the change takes effect.
The provider informs the customer without undue delay, at the latest within 48 hours of becoming aware of it, about a security incident that affects the customer’s instances or data.
The customer processes personal data in prompts and outputs only where it is allowed to.
Details are described under Security & privacy and in the privacy policy. Where they differ, the data processing agreement and these terms are binding.
Customer content, outputs and feedback
The customer keeps its rights to the prompts it sends and to the outputs it receives, and is responsible for having the right to use the content it processes with the service.
The customer may use outputs to train or distil its own models unless the licence of the model used restricts this. Such restrictions are shown at the deploy.
Model outputs can be inaccurate or incomplete. The customer reviews outputs before relying on them, in particular before acting on a finding, running generated code or using an exploit. Outputs must not be the sole basis of safety-critical decisions, such as automated changes to production systems without human review.
Feedback the customer gives about the service may be used by the provider without restriction and without compensation. This does not include customer data, prompts, outputs or other confidential content that the feedback contains.
Intellectual property
The provider keeps all rights to the service, the website and the brand. The models and their adapted weights are subject to the rights and licences of their developers. The customer receives a non-exclusive, non-transferable right to use the service for the duration of the contract.
The customer does not copy, extract, reverse engineer or redistribute model weights from an instance, and does not circumvent technical protections of the service.
The provider names a customer as a reference only with the customer’s express consent.
Confidentiality
Both parties keep confidential the information they receive from the other party that is marked as confidential or is evidently confidential, in particular verification details, details of engagements, evidence of authorisation, individual prices and security information about the service. They use it only for the contract.
This does not apply to information that is or becomes public without a breach, that the receiving party already had or developed independently, or that has to be disclosed by law or by order of an authority or court. Where the law allows, the provider informs the customer before it discloses the customer’s information to an authority.
The obligation continues for 3 years after the end of the framework contract.
Security responsibilities
The provider is responsible for the instance and the infrastructure below it: the dedicated GPU, the encrypted endpoint, the check of API keys, the configuration that keeps prompts and outputs out of logs and disks, and the deletion of the instance when it is stopped.
The customer is responsible for everything on its side: the custody of its API keys, the tools, agents and networks that call the instance, which data it sends, and the legal basis for processing that data.
An instance is deleted completely when it is stopped. The customer saves the outputs and results it still needs and keeps its own backups. The provider cannot restore a deleted instance.
Availability, model versions and changes
The service is provided without a guaranteed availability. The provider works to keep instances running with reasonable care, and maintenance may cause short interruptions. Individual service levels can be agreed in an order form. Statutory rights of consumers remain unaffected.
A running instance always keeps the model version it was deployed with. New model versions and the withdrawal of models, hardware or countries apply only to new deploys and are announced at least 30 days in advance.
If a running instance has to be stopped for legal, security or licensing reasons, the provider informs the customer without delay. Only the hours up to the stop are billed.
AI regulation
The customer is responsible for the obligations that arise from its own use of the models under the EU AI Act and other law, in particular as deployer or as provider of its own AI system.
Practices prohibited under Article 5 of the EU AI Act are not allowed. Use in a high-risk area under Annex III of the EU AI Act requires a prior agreement with the provider.
Term and termination
The customer can terminate the framework contract at any time without notice, in particular with the button “Cancel contract here” in its account. The provider confirms the termination by email.
The provider can terminate the framework contract with 30 days’ notice. Both parties can terminate for good cause without notice. Good cause for the provider exists in particular in case of serious or repeated breaches of the acceptable use policy, a breach of sanctions or export control law, or a payment default that is not remedied.
On termination, running instances are stopped and deleted, and the hours used up to that point are charged. The provider deletes the account data in line with the retention periods in the privacy policy. Invoices are kept for as long as the law requires.
The provider may also limit or suspend use that endangers the stability or security of the platform or of other customers, for example through abnormal load or attempts to attack the service. A customer whose access was ended for good cause cannot open a new account, including under another name.
Liability
The provider is liable without limitation for intent and gross negligence, for injury to life, body or health, under the Product Liability Act, and where it has given a guarantee.
In case of slight negligence, the provider is liable only for the breach of an essential contractual obligation, meaning one on which the customer may regularly rely and whose breach endangers the purpose of the contract, and then only for the foreseeable damage typical for this type of contract. Liability for loss of data is limited to the typical effort of restoring it from backups the customer should have made.
Statutory rights of consumers, in particular under mandatory consumer protection law, remain unaffected.
The provider does not guarantee that model outputs are correct, complete or suitable for a particular purpose. The customer is responsible for what it does with the outputs and for the authorisation of its tests.
A business customer indemnifies the provider against claims of third parties that arise from a use of the service that breaches these terms or the acceptable use policy, to the extent the customer is responsible for the breach.
Force majeure
Neither party is liable for delays or failures caused by events beyond its reasonable control, such as natural disasters, war, terrorism, strikes, orders of authorities, failures of public networks or internet backbones, or cyberattacks despite reasonable protective measures. Failures of the provider’s own suppliers count only if they are themselves caused by such an event.
The affected party informs the other party without delay. Hours during which an instance is not healthy because of such an event are not billed.
Changes to these terms
The provider may change these terms with effect for the future, for example when features change or the service becomes generally available. Changes to the main obligations of the parties are not made in this way.
Business customers are informed of changes by email at least 30 days before they take effect. If a business customer does not object before then, the changes are deemed accepted. The provider points this out in the notice. If the customer objects, either party can terminate the framework contract with effect from the date of the change.
Consumers are informed of changes by email and asked for their consent in their account at the next login or deploy. Without consent, the previous terms continue to apply, and the provider can terminate the framework contract with 30 days’ notice.
Governing law and venue
These terms and the contract are governed by the law of the Federal Republic of Germany. The UN Convention on Contracts for the International Sale of Goods does not apply.
For consumers, the mandatory consumer protection provisions of the country where the consumer habitually resides remain unaffected.
If the customer is a merchant, a legal entity under public law or a special fund under public law, the place of jurisdiction for all disputes is Berlin, and the provider may also sue at the customer’s registered office. For consumers, the statutory places of jurisdiction apply.
The provider is neither obliged nor willing to take part in dispute resolution proceedings before a consumer arbitration board.
Both parties first try to resolve a dispute in good faith before they go to court.
General provisions
These terms, the acceptable use policy, the data processing agreement and any order form are the entire agreement between the provider and the customer about the service. An order form takes precedence over these terms, and individual agreements in text form take precedence over both.
If a provision is or becomes invalid, the other provisions remain valid. The statutory rules apply in place of the invalid provision.
The customer may transfer the contract to a third party only with the provider’s consent in text form. The provider may transfer the contract to a successor in business and informs the customer of this.
Notices are given electronically, in particular by email to the address the customer gave.
Contact
Questions about these terms: contact@inkyinfinit.com. Provider details are in the imprint.