Bee360 SaaS Trust & Compliance
Our Standardized Terms and Policies
As a SaaS provider serving a large number of customers, we have tailored our legal framework specifically to our standardized software and scalable operations. As a result, we are unable to accommodate individual contractual modifications or custom agreements.
Instead, we have carefully designed standardized terms that ensure compliance with relevant regulatory requirements while reflecting the specifics of our services.
Bee360 Service Status
Book a Consultation
Legal Documents
| Document | Description | Download |
|---|---|---|
| General SaaS Terms and Conditions | Bee360's General SaaS Terms and Conditions (GTC) govern the provision and use of Bee360's cloud-based software as a service (SaaS). These terms outline the rights and obligations of both Bee360 and the customer, covering key areas such as scope of service, usage rights, fees, data protection, liability, and termination conditions. The GTC ensure a secure, transparent, and legally compliant framework for customers using Bee360's software solutions to manage their business operations efficiently. By using Bee360, customers agree to comply with these terms, which apply exclusively and supersede any conflicting customer conditions. | |
| Special Contractual Terms and Conditions for Services | Bee360's Special Contractual Terms and Conditions for Services (BVB-SERVICES) govern the provision of services related to the Bee360 Software-as-a-Service (SaaS) solution. They supplement the General SaaS Terms and Conditions (GTC) and define specific agreements regarding service delivery, usage rights for work results, remuneration, customer cooperation obligations, and service acceptance. These terms provide a transparent and legally secure framework for using Bee360-related services. In the event of conflicts with the GTC, the BVB-SERVICES take precedence. | |
| Service Level Agreement | Bee360's Service Level Agreement (SLA) defines the provider's commitments regarding service availability, performance standards, incident response, and reporting. It ensures transparency in service expectations and supplements the General SaaS Terms and Conditions (GTC) to provide a structured framework for service reliability and accountability. | |
| Support Guide | Bee360's Support Guide describes the support services available to customers using the Bee360 Software-as-a-Service (SaaS) solution. It defines the scope of standard support, response times, support case management, and escalation procedures. The guide also includes best practices for efficient collaboration, roles and responsibilities within the support team, and the process for reporting and resolving issues. It additionally covers maintenance windows and provides clarity on included and excluded support services, ensuring transparency and efficiency in customer support interactions. | |
| Technical System Requirements | Bee360's SaaS Technical System Requirements document outlines the technical, infrastructure, and organizational prerequisites needed to deploy and operate Bee360 in a customer environment. It details required system components, integration with identity providers, browser and mail server requirements, internet connectivity, and data handling considerations. It also specifies content-related and organizational prerequisites, ensuring smooth deployment and operation. Customers must ensure compliance with these requirements to enable seamless integration and optimal performance of Bee360. | |
| Data Processing Agreement | Bee360's Data Processing Agreement (DPA) governs the processing of personal data by Bee360 on behalf of the customer, ensuring compliance with applicable data protection laws, including the General Data Protection Regulation (GDPR). It outlines the roles and responsibilities of both parties, security measures, sub-processors, data transfer mechanisms, incident response, and data retention policies. The agreement provides a structured framework for safeguarding personal data, ensuring transparency, and defining compliance obligations between Bee360 and its customers. | |
| DORA Addendum | Bee360's DORA Addendum supplements the General SaaS Terms and Conditions (GTC) to ensure compliance with the Digital Operational Resilience Act (DORA). It establishes contractual provisions related to ICT service obligations, data protection, incident response, cooperation with regulatory authorities, and termination rights in the event of non-compliance. This addendum ensures that Bee360 meets the regulatory requirements for financial entities subject to DORA while maintaining operational resilience and security standards. | |
| ISO Certification | Bee360 is ISO 27001:2022 certified, meeting all requirements for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS). This ensures that Bee360's services have the necessary security controls and management program in place, as defined by the ISO/IEC 27001 standard. |
Frequently Asked Questions
Bee360 is licensed as a single enterprise subscription. The price follows the size of the IT budget managed in the platform, not the number of users, applications or projects — every tier includes the full functional scope and unlimited users.
Budget ranges are grouped into size tiers, and the applicable tier is determined together with you during the assessment. The reason for this model is deliberate: pricing per user or per capability makes organizations ration access to the very platform that only creates value when the right people use it. Where the IT budget alone does not reflect the scope to be managed, related budgets such as research and development, including personnel costs, are taken into account when the tier is identified. Bee360 is owner-managed and has been on the market since 2003, with no external capital involved — which is why we can price for a long-term relationship rather than a funding round.
Evaluation runs as a guided Quick Start on a live system with your own data and full functional access, rather than as a self-service trial account — it is chargeable and converts into a regular license afterwards.
The reason is simple: a governance platform shows its value on your portfolio, your costs and your capacity, not on demo data, and unguided access to an empty system tends to leave people without orientation. A Quick Start is usually preceded by a discovery conversation and a workshop with the leadership team to establish where the pressure actually is. We recommend proving the value across the organization rather than in one isolated team, because the effects that matter — prioritization, capacity, cost transparency — only appear where the decisions are made. A sandbox environment alongside the productive environment can be included.
The standard contract is an annual subscription that renews automatically unless it is cancelled; multi-year terms can be agreed where you want planning certainty, and the applicable notice period is set out in the contract documents.
A longer commitment is an option, not a precondition for using the platform. The renewal period and the notice period are stated in the contract documents and confirmed in each case. We share the full contract set — general terms, service level agreement and data processing agreement — for review before signature, so the commercial and legal terms are on the table before a decision is made.
SaaS is the standard delivery model, and an on-premises installation in your own environment is available as well — typically where regulatory requirements call for it — at an additional cost quoted individually.
Staying close to the SaaS standard is what keeps the platform continuously upgradeable, which is why we recommend it wherever the regulatory situation allows. For an on-premises deployment Bee360 provides the installation documentation and our DevOps team sets the system up together with your infrastructure team. Organizations under strict regulatory supervision are among those running Bee360 on their own infrastructure today.
Bee360 provides a standard data processing agreement (DPA, German AVV) as part of its contract documents; it is supplied on request alongside the general terms and the service level agreement, for review before signature.
The general terms set out what is stored, where, for how long, and when it is deleted. Optional integrations are deliberately built so that no additional processing agreement with Bee360 is needed: translation and AI features run through your own provider subscription and under your own terms, which keeps the decision about which AI provider processes your data with you rather than with us.
