Contractual Documents¶
Overview of the current contractual and legal documents of MazeVault and whom they bind
Version: 1.0.0
Owner: Managing Director, MAZEVAULT s.r.o.
Last Updated: 2025-02-19
Review Cycle: After every 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 (hereinafter the "Provider"). Grants the license directly to the Customer.
- Partner – business partner (reseller) that offers and sells the Product and provides the Customer with support and operation within the scope of its agreement with the Customer.
- Customer – end business user that uses the Product for its own internal needs.
The license to use the Product is granted to the Customer directly by the Provider upon acceptance of the License Terms — it is a direct license, not a sublicense. 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 constitute the current binding wording:
| Document | What it governs | Current version |
|---|---|---|
| MazeVault License Terms | Direct license Provider ↔ Customer: scope and limitations of use, operating modes, liability, data protection, lifecycle | mazevault.com/licence · PDF |
| List of Required Software for Operation and Lifecycle | Technical, security and operational reference standards that the Customer must meet; supported and unsupported configurations | mazevault.com/software · PDF |
3. Support, Data Processing and Order (Agreed by the Customer with the Partner)¶
The commercial and operational relationship — conclusion of the contract, order, price list, support level and processing of personal data — is agreed by the Customer with its Partner. The contractual documents of the partner channel (framework cooperation agreement, order template, price list) are not part of the customer documentation. What matters for 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 through the Partner: Customer = controller, Partner = processor, Provider = conditional sub-processor. For transparency of the processing chain, see the Subprocessor List.
4. Compliance, Operational and Audit Documentation¶
Information pages for regulated Customers — they state exclusively what follows from legal regulations and the contractual documentation:
| Document | Area |
|---|---|
| Information for Regulated Entities — Act No. 264/2025 Coll. / NIS2 | Supplier's position, materials for assessment, contractual assurance of requirements |
| Information for Financial Entities — DORA | Position under DORA, register of information, Art. 30 mapping, exit |
| Personal Data Protection | Roles under GDPR, scope of processing by the Provider, data subject rights |
| Handling of Security Incidents and Vulnerabilities | Notification chain and time limits under the License Terms, SLA and DPA |
| Continuity of Product Provision and Lifecycle | Dependency on the license server, patches, end of support for versions |
| Compliance Evidence and Reporting | Built-in Product features: audit logs, compliance reports, Auditor role |
| Subprocessor and Supplier List | Sub-processors under the DPA and the Provider's suppliers |
5. Where Individual Areas Are Governed¶
| Area | Governed by | Responsibility |
|---|---|---|
| Scope of use, limitations, IP, liability, lifecycle | License Terms | Provider (license) |
| Technical/security minimum, supported configurations | List of Required Software | Customer (operation according to the standards) |
| Response times, incident classification, escalation | SLA (according to 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 management, infrastructure | License Terms + List of Required Software | Customer, unless agreed otherwise; loss of the master encryption key is unrecoverable without a valid customer copy |
6. Documentation Consistency Rules¶
- Product documentation must not convert the Provider's commitments into direct customer commitments beyond the License Terms.
- Response times, RTO/RPO and availability are stated as reference values unless incorporated by the relevant contract; binding availability is assumed only by the infrastructure operator (Partner or Customer), and the Customer's binding support level follows from the license variant and the agreement with the Partner.
- The publicly binding wording is always the current wording at the stated URLs (
mazevault.com/legal/…). - Generated documentation in
product/docs/site/is not edited manually; it is regenerated after the sources are modified.
Document Control¶
| Version | Date | Owner | Changes |
|---|---|---|---|
| 1.0.0 | 2025-02-19 | Managing Director, MAZEVAULT s.r.o. | First issue — overview of the contractual documentation for the direct license model (roles Provider / Partner / Customer) |