Last updated 2026-09-25
Enterprise terms
The additional terms for organisations on the Enterprise tier — cloud or self-hosted. They apply together with the terms of service and the data processing agreement, and they exist so that most enterprise deals need one order form and zero redlines.
1How the documents fit together
An Enterprise subscription is formed by an order form — a short document both parties sign, or an agreed written offer you accept — under these enterprise terms, the terms of service and the data processing agreement.
Where the documents conflict: the order form controls over these terms, and these terms control over the terms of service. For the processing of personal data, the data processing agreement controls over everything except an order-form clause that explicitly amends it.
Enterprise is offered to businesses and public-sector bodies, not to consumers.
2What the order form fixes
- the deployment: our cloud, or self-hosted on your infrastructure (section 5);
- seats, workspaces, storage and credit allowances — Enterprise quotas are negotiated, not taken from the pricing page;
- price, currency, billing period and initial term;
- a service level agreement, if one is agreed (there is none by default);
- any agreed deviations from these terms, the terms of service or the data processing agreement.
Unless the order form says otherwise: the initial term is 12 months, renewing for successive 12-month periods; either party can decline renewal with 60 days' written notice before the term ends.
3Billing
- We invoice; you pay within 30 days of the invoice date, by bank transfer, in the order form's currency.
- Prices are exclusive of VAT and similar taxes; EU customers with a valid VAT ID are reverse-charged.
- Fees for a running period are non-refundable except where these terms or the order form say otherwise.
- Seats added mid-term are invoiced pro-rata for the remainder of the term.
4Enterprise on our cloud
The Enterprise tier on our cloud includes, beyond the product itself:
- enterprise SSO (OIDC) with forced-SSO enrolment and per-connection MFA requirements, verified against your identity provider;
- the organisation security audit trail;
- the data processing agreement countersigned, security questionnaires answered, and the sub-processor notice list (30 days before any addition);
- a named support contact and priority handling of incidents affecting your organisation.
5Self-hosted vitrinka
A self-hosted deployment runs entirely on your infrastructure. We supply the software and a signed licence file; your content never reaches us — there is nothing for us to process, which is why the data processing agreement does not apply to a purely self-hosted deployment, and why one is often the shortest path through procurement.
- We grant you a non-exclusive, non-transferable licence, for the term and seat count in the order form, to run vitrinka on infrastructure you control, recorded in a licence file we sign.
- Do not circumvent or tamper with license enforcement, remove notices, or make the service available to anyone but your own organisation and its contractors working for it.
- We provide releases and security updates for supported versions through the channel named in the order form, and support per section 4's support terms.
- Telemetry: a self-hosted deployment does not phone home. The licence is a signed file your deployment verifies offline, against our public key built into each release, and nothing is sent to us unless the order form says otherwise.
- On termination, the licence ends and you delete your copies; your data was always yours and stays with you.
6Confidentiality
Each party will use the other's confidential information — terms of the deal, technical and security details, anything marked or obviously confidential — only to perform the agreement, protect it with at least reasonable care, and disclose it only to people who need it and are bound to keep it. This does not cover information that is public, independently developed, or lawfully received elsewhere, and disclosure required by law is permitted after notice where notice is lawful. The duty runs for the agreement and five years after.
7Our indemnity to you
We will defend you against a third-party claim that vitrinka, used as agreed, infringes that party's intellectual property, and we will pay the damages and reasonable costs a court finally awards, or an agreed settlement — provided you tell us promptly, let us control the defence, and reasonably cooperate.
If such a claim looks likely, we may procure the right for you to keep using the service, or modify it to be non-infringing without material loss of function; if neither is commercially reasonable, we may terminate the affected subscription and refund prepaid fees for the period after termination. This section states our entire liability for IP infringement.
It does not cover claims arising from your content, your combination of the service with things we did not supply, or your use in breach of the agreement — for those, the terms of service's responsibility clause applies to you.
8Liability
The liability cap in the terms of service applies, with one enterprise adjustment: for breaches of the data processing agreement or of section 6 (confidentiality), the cap is twice the fees paid or payable in the 12 months before the event. The indemnity in section 7, and liability that cannot be limited under the applicable law, are uncapped.
9Termination
- Either party may terminate for material breach not cured within 30 days of written notice, or immediately if the other becomes insolvent.
- On termination of a cloud subscription, the export and deletion mechanics of the data processing agreement apply: your data is exportable before and for 30 days after the end, and is then deleted by key destruction.
- Sections that by nature survive — confidentiality, indemnity, liability, payment of accrued fees — survive.
10Talking to us
Enterprise deals start at hello@vitrinka.ai; contract questions go to legal@vitrinka.ai. Security documentation for your review is at /legal/security, the sub-processor register at /legal/subprocessors, and the data processing agreement at /legal/dpa.