To ensure the fastest possible onboarding and the highest level of service security, FacilityBot utilizes a standardized Software Service Agreement (SSA). This document addresses the most common questions from legal and procurement teams regarding our terms.
1. Why is FacilityBot’s standard agreement preferred over a generic vendor template?
FacilityBot is a multi-tenant Cloud SaaS platform, not a professional services firm. Generic “Services Agreements” often fail to account for the technical realities of cloud hosting. Our SSA is purpose-built to address:
- Continuous Updates: Our software is updated regularly; our terms ensure you always have access to the latest version without needing contract amendments.
- Security & Uptime: Our agreement includes specific commitments regarding Hosted Services availability and the protection of the Platform (Clause 4.5).
- Regulatory Alignment: Our terms are structured to comply with data protection standards that generic “goods and services” templates often overlook.
2. Who owns the data uploaded to FacilityBot?
You do. Under Clause 10 of our agreement (Intellectual Property Rights), it is explicitly stated that nothing in the agreement shall operate to assign or transfer any Intellectual Property Rights from the Customer to the Provider. Your “Customer Data” remains your property, and we only process it to the extent necessary to provide the service.
3. What happens to our data if we terminate the service?
We believe in data portability. Upon termination (Clause 18), your access to the Hosted Services will cease, but our “Effects of Termination” (Clause 19) ensures that the wind-down is handled professionally. We recommend exporting your data via our built-in CSV export tools prior to the end of your term to ensure a smooth transition.
4. Why is there a fee for using a Customer’s legal template?
Our pricing is optimized for high-efficiency, standardized delivery. When a client requests the use of their own legal template, it moves the engagement from a “standardized service” to a “bespoke partnership,” which incurs significant overhead:
- Technical-Legal Mapping: Generic vendor templates are rarely designed for multi-tenant SaaS. We must perform a manual audit to ensure the contract does not promise technical impossibilities—such as granting physical access to AWS data centers (which we do not own) or “Work for Hire” clauses that conflict with our proprietary source code.
- Operational Risk & Compliance: SaaS scales because every customer operates under the same rules. Custom templates often require “manual exceptions” in our data handling, backup cycles, or notification protocols. These exceptions increase our operational risk and require manual monitoring by our engineering team.
- Insurance & Liability Alignment: Our corporate insurance and risk profiles are calibrated to our standard Software Service Agreement. Deviating from these terms requires a specialized risk assessment to ensure the contract remains insurable.
To keep our subscription fees low for the vast majority of our users who utilize our standard terms, we apply a Legal Review Fee of USD 3,000. This fee helps offset the direct costs of external counsel and the internal technical resources required to negotiate and maintain a non-standard agreement.
