Contractual Documents¶
Overview of the current MazeVault contractual and legal documents and who they bind
Version: 2.0.0
Owner: Legal / CISO / DPO
Last Updated: 2026-10-12
Review Cycle: After each change to the contractual documentation
1. Roles and relationships¶
- Provider – MAZEVAULT s.r.o., author and holder of the economic copyright to the MazeVault software (the “Provider”). Grants the licence directly to the Customer.
- Partner – a reseller that promotes, sells and provides the Customer with support and operation to the extent of its agreement with the Customer.
- Customer – the end business user that uses the Product for its own internal needs.
The licence to use the Product is granted to the Customer directly by the Provider upon acceptance of the License Terms — this is a direct licence, not a sublicence. Technical support to the Customer is provided by the Partner; the Provider provides upstream (product) support to the Partner.
2. Documents directly for the Customer (public)¶
These documents are publicly available and always represent the current binding wording:
| Document | What it governs | Current version |
|---|---|---|
| MazeVault License Terms | Direct Provider ↔ Customer licence: scope and limits of use, operating modes, liability, data protection, lifecycle | mazevault.com/licence · PDF |
| List of Software Required to Operate and Maintain the Applications | Technical, security and operational reference standards the Customer must meet; supported and unsupported configurations | mazevault.com/software · PDF |
3. Support, data processing and ordering (arranged by the Customer with the Partner)¶
The commercial and operational relationship — contract conclusion, ordering, price list, support level and personal-data processing — is arranged by the Customer with its Partner. The partner-channel contractual documents (framework cooperation agreement, order template, price list) are not part of the customer documentation. What matters to the Customer is their framework:
- Support (SLA) – the Customer’s support level follows from the license variant (PoC / Small Business / Enterprise) and the agreement with the Partner. The Provider provides upstream (product) support to the Partner, not a direct SLA to the Customer.
- Personal-data processing (DPA) – concluded via the Partner: Customer = controller, Partner = processor, Provider = conditional sub-processor. For the processing-chain transparency see the Subprocessor list.
4. Compliance, operational and audit documentation¶
Current internal MazeVault documents referenced by the compliance and operational framework — direct links:
| Document | Area |
|---|---|
| NIS2 / Czech Cybersecurity Act Compliance | NIS2 / Act No. 264/2025 Sb. |
| DORA Compliance Mapping | DORA (EU 2022/2554) |
| GDPR Compliance | GDPR (EU 2016/679) |
| Incident Response Plan | Detection, response, recovery; NUKIB/DPA notification |
| Business Continuity & Disaster Recovery | BCP/DRP, RTO/RPO targets, DR testing |
| Compliance Evidence & Reporting | Audit logs, compliance reports, Auditor role |
| Subprocessor list | Transparency of the personal-data processing chain under GDPR/DORA |
5. Where each area is governed¶
| Area | Governed by | Responsibility |
|---|---|---|
| Scope of use, restrictions, IP, liability, lifecycle | License Terms | Provider (licence) |
| Technical/security minimum, supported configurations | Required Software list | Customer (operation per standards) |
| Response times, incident classification, escalation | SLA (per variant + agreement with the Partner) | Partner → Customer; Provider → Partner (upstream) |
| Personal data processing | DPA | Partner (processor), Customer (controller), Provider (conditional sub-processor) |
| Backups, encryption key custody, infrastructure | License Terms + Required Software list | Customer, unless otherwise agreed; loss of the master encryption key is unrecoverable without a valid customer-held copy |
6. Documentation consistency rules¶
- Product documentation must not convert the Provider’s obligations into direct customer obligations beyond the License Terms.
- Response times, RTO/RPO and availability are stated as reference unless incorporated by the applicable agreement; the Customer’s binding level follows from the license variant and the agreement with the Partner.
- The publicly binding version is always the current wording at the stated URLs (
mazevault.com/legal/…). - Generated documentation under
product/docs/site/is not edited manually; it is regenerated after source updates.
Document Control¶
| Version | Date | Owner | Changes |
|---|---|---|---|
| 2.0.0 | 2026-10-12 | Legal / CISO / DPO | Reworked to the current contractual structure and the direct licence model (Provider / Partner / Customer roles); removed the LEG-* scheme and annex numbering; added links to public URLs. Removed the partner-channel contractual documents table (framework cooperation agreement, order template, price list, direct SLA/DPA instruments) from the customer documentation and replaced it with a brief note that support, ordering and data processing are arranged by the Customer with the Partner. Compliance, operational and audit documentation listed as direct links (NIS2, DORA, GDPR, Incident Response Plan, Business Continuity & DR, Compliance Evidence, Subprocessor list) |
| 1.0.0 | 2026-07-19 | Legal / CISO / DPO | Initial registry (superseded; reflected an earlier contractual structure) |