Legal packages
Versioned documents and acceptance
Legal records are versioned separately, but the customer completes at most one acceptance action per product activation.
Document roles
| Role | Examples | Acceptance |
|---|---|---|
| Public information | Impressum, general privacy notice | No consent; always accessible |
| Hosting contract | Hosting terms | Included in hosting package |
| Hosting annex | Acceptable Use, AVV, TOMs, subprocessors and an SLA only when the tariff promises one | Recorded with the same hosting click |
| Studio contract | AI Studio terms and AVV addendum | Included in Studio activation |
| Studio information/annex | Studio privacy notice, TOMs and recipient information | Versions recorded with Studio package |
| Internal compliance | B2B checkout checklist | Never customer-facing |
Hosting acceptance
The plan popup shows price and product information. Legal text appears only after Buy and before Stripe redirection. Core returns the currently effective package for the customer and locale. Portal presents the terms in one readable, scrollable dialog and requires a single checkbox.
On confirmation, Core stores every included document ID, version, locale, effective date, package purpose, customer, accepting user, timestamp and available request evidence. Stripe checkout starts only after that acceptance succeeds.
AI Studio acceptance
Studio is optional and separately activated. Before the first launch, the customer accepts one AI Studio package. It states that the customer connects its own authorized OpenAI/Codex account and that Mivama does not provide an OpenAI account, model, tokens or credits.
The supplemental privacy notice is acknowledged as information, not mislabeled as GDPR consent. If a new materially changed package requires acceptance, Core returns ineligible and Studio remains locked until accepted.
Publication lifecycle
A document can be Draft, Published or Superseded. Superseded means a newer version replaced it for new acceptances; the old version remains immutable and available for proving existing contracts. Never edit accepted content in place—publish a new version and preserve the archived text.
Published test documents may contain clearly marked placeholders. Before production, company identity, address, security contacts, venue, providers, backup expiry and all operational promises must be completed and reviewed by German IT/privacy counsel.
Source: mivama_core/legal.py, legal_documents/de and Portal legal/checkout components.