[IMP] legal/terms: update Odoo Enterprise for online use + data protection
Also removed the `online.rst` draft contract, which was never officially in use, and is now superseded by the unified Enterprise Agreement.
This commit is contained in:
parent
d720e8db89
commit
4ae3fa7fd5
@ -7,7 +7,6 @@ Terms and Conditions
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
terms/online
|
||||
terms/odoo_sh_terms
|
||||
terms/enterprise
|
||||
terms/partnership
|
||||
|
@ -5,15 +5,17 @@
|
||||
Odoo Enterprise Subscription Agreement
|
||||
======================================
|
||||
|
||||
.. note:: Version 7.1 - 2018-03-16
|
||||
.. note:: Version 8.0 - 2018-05-22
|
||||
|
||||
.. v6: add "App" definition + update pricing per-App
|
||||
.. v7: remove possibility of price change at renewal after prior notice
|
||||
.. 7.1: specify that 7% renewal increase applies to all charges, not just per-User.
|
||||
.. v8.0: adapt for "Self-Hosting" + "Data Protection" for GDPR
|
||||
|
||||
By subscribing to the Odoo Enterprise services (the "Services") provided by Odoo SA and its
|
||||
affiliates (collectively, "Odoo SA") in relation with Odoo Enterprise Edition or
|
||||
Odoo Community Edition (the "Software"), you (the "Customer") are agreeing to be bound by the
|
||||
affiliates (collectively, "Odoo SA") in relation with Odoo Enterprise Edition or Odoo Community
|
||||
Edition (the "Software"), hosted on Odoo SA's Cloud platforms (the "Cloud Platform") or
|
||||
on-premises ("Self-Hosting"), you (the "Customer") are agreeing to be bound by the
|
||||
following terms and conditions (the "Agreement").
|
||||
|
||||
.. _term:
|
||||
@ -21,10 +23,10 @@ following terms and conditions (the "Agreement").
|
||||
1 Term of the Agreement
|
||||
=======================
|
||||
|
||||
The duration of this Agreement (the “Term”) shall be minimally one year and as specified in writing
|
||||
at the signature of this Agreement, beginning on the date of the signature.
|
||||
The duration of this Agreement (the “Term”) shall be specified in writing at the signature of this
|
||||
Agreement, beginning on the date of the signature.
|
||||
It is automatically renewed for an equal Term, unless either party provides a written notice of
|
||||
termination minimum 30 days before the end of the Term by registered mail to the other party.
|
||||
termination minimum 30 days before the end of the Term to the other party.
|
||||
|
||||
.. _definitions:
|
||||
|
||||
@ -39,8 +41,7 @@ User
|
||||
|
||||
App
|
||||
An "App" is a specialized group of features available for installation in the Software,
|
||||
and listed in the public Pricing section of `Odoo SA's website <https://www.odoo.com>`_ at the
|
||||
signature of this Agreement.
|
||||
and listed in the public Pricing section of `Odoo SA's website <https://www.odoo.com>`_.
|
||||
|
||||
Bug
|
||||
Is considered a Bug any failure of the Software that results in a complete stop, error
|
||||
@ -51,18 +52,24 @@ Bug
|
||||
accounting requirements anymore).
|
||||
|
||||
Covered Versions
|
||||
All Services provided under this Agreement are applicable only to the Covered Versions of
|
||||
Unless specified otherwise, the Services provided under this Agreement are applicable only
|
||||
to the Covered Versions of
|
||||
the Software, which include the 3 (three) most recently released major versions.
|
||||
|
||||
To be covered by the current Agreement, Customer’s installations have to run the most recent
|
||||
To be covered by the current Agreement, the Customer has to run the most recent
|
||||
Covered Version at the time of this Agreement’s signature. When this is not the case,
|
||||
additional costs are applicable, as described in :ref:`charges`.
|
||||
|
||||
|
||||
.. _enterprise_access:
|
||||
|
||||
3 Access to Odoo Enterprise Edition
|
||||
===================================
|
||||
3 Access to the Software
|
||||
========================
|
||||
|
||||
The Customer can use the Software hosted on the Cloud Platform, or choose the Self-Hosting option.
|
||||
The Cloud Platform is hosted and fully managed by Odoo SA, and accessed remotely by the Customer.
|
||||
With the Self-Hosting option, the Customer instead hosts the Software on computer systems of their
|
||||
choice, that are not under the control of Odoo SA.
|
||||
|
||||
For the duration of this Agreement, Odoo SA gives the Customer a non-exclusive, non-transferable
|
||||
license to use (execute, modify, execute after modification) the Odoo Enterprise Edition software,
|
||||
@ -78,7 +85,7 @@ of the Customer, and to deal with all collected data in compliance with its offi
|
||||
Policy, published at https://www.odoo.com/privacy.
|
||||
|
||||
Upon expiration or termination of this Agreement, this license is revoked immediately and the
|
||||
Customer agrees to stop using the Odoo Enterprise Edition software.
|
||||
Customer agrees to stop using the Odoo Enterprise Edition software and the Cloud Platform.
|
||||
|
||||
Should the Customer breach the terms of this section, the Customer agrees to pay Odoo SA an extra
|
||||
fee equal to 300% of the applicable list price for the actual number of Users and installed Apps.
|
||||
@ -86,8 +93,8 @@ fee equal to 300% of the applicable list price for the actual number of Users an
|
||||
|
||||
.. _services:
|
||||
|
||||
4 Included Services
|
||||
===================
|
||||
4 Services
|
||||
==========
|
||||
|
||||
4.1 Bug Fixing Service
|
||||
----------------------
|
||||
@ -101,7 +108,8 @@ The Customer understands that Bugs caused by a modification or extension that is
|
||||
official Software will not be covered by this service.
|
||||
|
||||
As soon as the Bug is fixed an appropriate remedy will be communicated to the Customer.
|
||||
If the bug has been addressed in a more recent revision of the Covered Version of the
|
||||
|
||||
For Self-Hosting, if the bug has been addressed in a more recent revision of the Covered Version of the
|
||||
Software used by the Customer, the Customer agrees to update its systems to that revision in order
|
||||
to obtain the correction. The Customer will not be asked to upgrade to a more recent Covered
|
||||
Version of the Software as a remedy to a Bug.
|
||||
@ -113,11 +121,16 @@ Both parties acknowledge that as specified in the license of the Software and in
|
||||
section of this Agreement, Odoo SA cannot be held liable for Bugs in the Software.
|
||||
|
||||
|
||||
4.2 Security Advisories Service
|
||||
-------------------------------
|
||||
4.2 Security Updates Service
|
||||
----------------------------
|
||||
|
||||
.. _secu_self_hosting:
|
||||
|
||||
Self-Hosting
|
||||
++++++++++++
|
||||
|
||||
For the duration of this Agreement, Odoo SA commits to sending a "Security Advisory" to the Customer
|
||||
for any security Bug that are discovered in the Covered Versions of the Software, at least 2 weeks
|
||||
for any security Bug that is discovered in the Covered Versions of the Software, at least 2 weeks
|
||||
before making the Security Advisory public, unless the Bug has already been disclosed publicly by a
|
||||
third party.
|
||||
Security Advisories include a complete description of the Bug, its cause, its possible impacts
|
||||
@ -127,6 +140,16 @@ The Customer understands that the Bug and the information in the Security Adviso
|
||||
as Confidential Information as described in :ref:`confidentiality` during the embargo period prior to
|
||||
the public disclosure.
|
||||
|
||||
.. _secu_cloud_platform:
|
||||
|
||||
Cloud Platform
|
||||
++++++++++++++
|
||||
|
||||
Odoo SA commits to apply the security remedies for any security Bug discovered in a version of
|
||||
the Software hosted on the Cloud Platform, on all systems under its control, as soon as
|
||||
the remedy is available, without requiring any manual action of the Customer.
|
||||
|
||||
|
||||
.. _upgrade:
|
||||
|
||||
4.3 Upgrade Services
|
||||
@ -141,7 +164,9 @@ For the duration of this Agreement, the Customer can submit upgrade requests thr
|
||||
channel (typically Odoo SA's upgrade service website), in order to convert a database of the Software
|
||||
from one Covered Version of the Software to a more recent Covered Version (the "Target Version").
|
||||
|
||||
Upgrade requests must include a complete backup copy of the Customer's database and the
|
||||
For the Cloud Platform, upgrade requests are submitted directly from the control panel of the
|
||||
Cloud Platform, and do not require any data upload. For Self-Hosting,
|
||||
upgrade requests must include a complete backup copy of the Customer's database and the
|
||||
associated data (typically obtained from the Backup menu of the Software). Where necessary for data
|
||||
security or regulation reasons, the Upgrade Service includes an optional tool to anonymize
|
||||
identifiable data inside a database before submitting the upgrade request, and a tool to restore
|
||||
@ -177,6 +202,52 @@ technical adaptation of third-party modules installed in the Customer's database
|
||||
corresponding data in order to be compatible with the Target Version. The Customer will receive an
|
||||
upgraded version of all installed third-party modules along with the upgraded database.
|
||||
|
||||
|
||||
.. _cloud_hosting:
|
||||
|
||||
4.4 Cloud Hosting Services
|
||||
--------------------------
|
||||
|
||||
For the duration of this Agreement, when the Customer chooses to use the Cloud Platform,
|
||||
Odoo SA commits to providing at least the following services:
|
||||
|
||||
- Choice of multiple hosting regions (minimum 3: Europe, America, Asia/Pacific)
|
||||
- Hosting in Tier-III data centers or equivalent, with 99.9% network uptime
|
||||
- Grade A SSL (HTTPS) Encryption of communication
|
||||
- Fully automated, verified backups, replicated in multiple regions
|
||||
- Disaster Recovery Plan, tested regularly
|
||||
|
||||
The details of the Cloud Hosting Services are described on the Service Level Agreement page at
|
||||
https://www.odoo.com/cloud-sla.
|
||||
|
||||
|
||||
.. _support_service:
|
||||
|
||||
4.4 Cloud Hosting Services
|
||||
--------------------------
|
||||
|
||||
Scope
|
||||
+++++
|
||||
|
||||
For the duration of this Agreement, the Customer may open an unlimited number of support tickets
|
||||
free of charge, exclusively for questions regarding Bugs (see 4.1 Bug Fixing Service) or guidance
|
||||
with respect to the use of the standard features of the Software and Services
|
||||
(functionalities, intended use, configuration, troubleshooting).
|
||||
|
||||
Other assistance requests, such as questions related to development, customizations,
|
||||
installation for Self-Hosting, or services requiring to access the Customer's database,
|
||||
may be covered through the purchase of a separate Service Pack.
|
||||
In case it’s not clear if a request is covered by this Agreement or a Service Pack,
|
||||
the decision is at the discretion of Odoo SA.
|
||||
|
||||
Availability
|
||||
++++++++++++
|
||||
|
||||
Tickets can be submitted online at https://www.odoo.com/help, or by phone directly to the
|
||||
various offices, subject to local opening hours.
|
||||
|
||||
|
||||
|
||||
.. _charges:
|
||||
|
||||
5 Charges and Fees
|
||||
@ -187,8 +258,7 @@ upgraded version of all installed third-party modules along with the upgraded da
|
||||
5.1 Standard charges
|
||||
--------------------
|
||||
|
||||
The standard charges for the Odoo Enterprise subscription, the Bug Fixing Service, Security Advisories
|
||||
Service and the Upgrade Service are based on the number of Users, the installed
|
||||
The standard charges for the Services are based on the number of Users, the installed
|
||||
Apps, the Software version used by the Customer, and specified in writing at the signature of the Agreement.
|
||||
|
||||
When during the Term, the Customer has more Users or more installed Apps than specified at the time
|
||||
@ -247,8 +317,6 @@ is legally obliged to pay or collect Taxes for which the Customer is responsible
|
||||
6.1 Customer Obligations
|
||||
------------------------
|
||||
|
||||
.. FIXME: removed the clause about
|
||||
|
||||
The Customer agrees to:
|
||||
|
||||
- pay Odoo SA any applicable charges for the Services of the present Agreement, in accordance with
|
||||
@ -259,11 +327,22 @@ The Customer agrees to:
|
||||
- take all measures necessary to guarantee the unmodified execution of the part of the Software
|
||||
that verifies the validity of the Odoo Enterprise Edition usage, as described
|
||||
in :ref:`enterprise_access` ;
|
||||
- grant Odoo SA the necessary access to verify the validity of the Odoo Enterprise Edition usage
|
||||
upon request (e.g. if the automatic validation is found to be inoperant for the Customer);
|
||||
- appoint 1 dedicated Customer contact person for the entire duration of the Agreement;
|
||||
|
||||
When the Customer chooses to use the Cloud Platform, the Customer further agrees to:
|
||||
|
||||
- take all reasonable measures to keep their user accounts secure, including by choosing
|
||||
a strong password and not sharing it with anyone else;
|
||||
- make a reasonable use of the Hosting Services, to the exclusion of any illegal or abusive
|
||||
activities, and strictly observe the rules outlined in the Acceptable Use Policy
|
||||
published at https://www.odoo.com/acceptable-use.
|
||||
|
||||
When the Customer chooses the Self-Hosting option, the Customer further agrees to:
|
||||
|
||||
- take all reasonable measures to protect Customer’s files and databases and to ensure Customer’s
|
||||
data is safe and secure, acknowledging that Odoo SA cannot be held liable for any data loss;
|
||||
- grant Odoo SA the necessary access to verify the validity of the Odoo Enterprise Edition usage
|
||||
upon request (e.g. if the automatic validation is found to be inoperant for the Customer);
|
||||
|
||||
|
||||
.. _no_soliciting:
|
||||
@ -312,9 +391,71 @@ The Receiving Party may disclose Confidential Information of the Disclosing Part
|
||||
compelled by law to do so, provided the Receiving Party gives the Disclosing Party prior notice of
|
||||
the compelled disclosure, to the extent permitted by law.
|
||||
|
||||
|
||||
.. _data_protection:
|
||||
|
||||
6.5 Data Protection
|
||||
-------------------
|
||||
|
||||
Definitions
|
||||
"Personal Data", "Controller", "Processing" take the same meanings as in the
|
||||
Regulation (EU) 2016/679 and the Directive 2002/58/EC,
|
||||
and any regulation or legislation that amends or replaces them
|
||||
(hereafter referred to as “Data Protection Legislation”)
|
||||
|
||||
Processing of Personal Data
|
||||
+++++++++++++++++++++++++++
|
||||
|
||||
The parties acknowledge that the Customer's database may contain Personal Data, for which the
|
||||
Customer is the Controller. This data will be processed by Odoo SA when the Customer instructs so,
|
||||
by using any of the Services that require a database (e.g. the Cloud Hosting Services or
|
||||
the Database Upgrade Service), or if the Customer transfers their database or a part of
|
||||
their database to Odoo SA for any reason pertaining to this Agreement.
|
||||
|
||||
This processing will be performed in conformance with Data Protection Legislation.
|
||||
In particular, Odoo SA commits to:
|
||||
|
||||
- (a) only process the Personal Data when and as instructed by the Customer, and for the purpose of
|
||||
performing one of the Services under this Agreement, unless required by law to do so,
|
||||
in which case Odoo SA will provide prior notice to the Customer, unless the law
|
||||
forbids it ;
|
||||
- (b) ensure that all persons within Odoo SA authorised to process the Personal Data have committed
|
||||
themselves to confidentiality ;
|
||||
- (c) implement and maintain appropriate technical and organizational measures to protect
|
||||
the Personal Data against unauthorized or unlawful processing and against accidental loss,
|
||||
destruction, damage, theft, alteration or disclosure ;
|
||||
- (d) forward promptly to the Customer any Data Protection request that was submitted
|
||||
to Odoo SA with regard to the Customer's database ;
|
||||
- (e) notify the Customer promptly upon becoming aware of and confirming any accidental,
|
||||
unauthorized, or unlawful processing of, disclosure of, or access to the Personal Data ;
|
||||
- (f) notify the Customer if the processing instructions infringe applicable Data Protection
|
||||
Legislation, in the opinion of Odoo SA;
|
||||
- (g) make available to the Customer all information necessary to demonstrate compliance with the
|
||||
Data Protection Legislation, allow for and contribute reasonably to audits, including
|
||||
inspections, conducted or mandated by the Customer;
|
||||
- (h) permanently delete all copies of the Customer's database in possession of Odoo SA,
|
||||
or return such data, at the Customer’s choice, upon termination of this Agreement,
|
||||
subject to the delays specified in Odoo SA's
|
||||
`Privacy Policy <https://www.odoo.com/privacy>`_ ;
|
||||
|
||||
With regard to points (d) to (f), the Customer agrees to provide Odoo SA with accurate contact
|
||||
information at all times, as necessary to notify the Customer's Data Protection responsible.
|
||||
|
||||
Subprocessors
|
||||
+++++++++++++
|
||||
|
||||
The Customer acknowledges and agrees that in order to provide the Services, Odoo SA may use
|
||||
third-party service providers (Subprocessors) to process Personal Data. Odoo SA commits to only
|
||||
use Subprocessors in compliance with Data Protection Legislation. This use will be covered by a
|
||||
contract between Odoo SA and the Subprocessor that provides guarantees to that effect.
|
||||
Odoo SA's Privacy Policy, published at https://www.odoo.com/privacy provides up-to-date information
|
||||
regarding the names and purposes of Subprocessors currently in use by Odoo SA for the
|
||||
execution of the Services.
|
||||
|
||||
|
||||
.. _termination:
|
||||
|
||||
6.5 Termination
|
||||
6.6 Termination
|
||||
---------------
|
||||
|
||||
In the event that either Party fails to fulfill any of its obligations arising herein, and if such
|
||||
@ -345,10 +486,10 @@ Surviving Provisions:
|
||||
For the duration of this Agreement, Odoo SA commits to using commercially reasonable efforts to
|
||||
execute the Services in accordance with the generally accepted industry standards provided that:
|
||||
|
||||
- the Customer’s computing systems are in good operational order and the Software is installed in a
|
||||
suitable operating environment;
|
||||
- the Customer provides adequate troubleshooting information and access so that Odoo SA can
|
||||
identify, reproduce and address problems;
|
||||
- the Customer’s computing systems are in good operational order and, for Self-Hosting, that
|
||||
the Software is installed in a suitable operating environment;
|
||||
- the Customer provides adequate troubleshooting information and, for Self-Hosting, any access
|
||||
that Odoo SA may need to identify, reproduce and address problems;
|
||||
- all amounts due to Odoo SA have been paid.
|
||||
|
||||
The Customer's sole and exclusive remedy and Odoo SA's only obligation for any breach of this warranty
|
||||
|
@ -1,614 +0,0 @@
|
||||
.. _online_terms_of_sale:
|
||||
|
||||
==============================
|
||||
Odoo Online Terms & Conditions
|
||||
==============================
|
||||
|
||||
.. note:: Version 1 - Last revision: July 12, 2017.
|
||||
|
||||
By subscribing to the Odoo Online services (the "Services") provided by Odoo SA and its
|
||||
affiliates (collectively, "Odoo SA") in relation with Odoo Enterprise Edition or
|
||||
Odoo Community Edition (the "Software"), you (the "Customer") are agreeing to be bound by the
|
||||
following terms and conditions (the "Agreement").
|
||||
|
||||
.. _term_online:
|
||||
|
||||
1 Term of the Agreement
|
||||
=======================
|
||||
|
||||
The duration of this Agreement (the “Term”) shall be minimally one month and as
|
||||
specified in writing at the signature of this Agreement, beginning on the date
|
||||
of the signature. It is automatically renewed for an equal Term, unless either
|
||||
party provides a written notice of termination minimum 30 days before the end
|
||||
of the Term by registered mail to the other party.
|
||||
|
||||
|
||||
.. _definitions_online:
|
||||
|
||||
2 Definitions
|
||||
=============
|
||||
|
||||
User
|
||||
Any active user account with access to the Software in creation and/or edition mode.
|
||||
Deactivated user accounts and accounts used by external people (or systems) who only have
|
||||
limited access to the Software through the portal facilities (known as "portal Users") are not
|
||||
counted as Users.
|
||||
|
||||
Bug
|
||||
Is considered a Bug any failure of the Software that results in a complete stop, error
|
||||
traceback or security breach, and is not directly caused by a defective installation or
|
||||
configuration. Non-compliance with specifications or requirements will be considered as Bugs at
|
||||
the discretion of Odoo SA (typically, when the Software does not produce the results or
|
||||
performance it was designed to produce, or when a country-specific feature does not meet legal
|
||||
accounting requirements anymore).
|
||||
|
||||
.. _enterprise_access_online:
|
||||
|
||||
3 Access to source code
|
||||
=======================
|
||||
|
||||
For the duration of this Agreement, Odoo SA gives the Customer a non-exclusive,
|
||||
non-transferable license to use (execute, modify, execute after modification)
|
||||
the Odoo software, under the terms set forth in :ref:`appendix_a_online`.
|
||||
|
||||
The Customer agrees to take all necessary measures to guarantee the unmodified
|
||||
execution of the part of the Software that verifies the validity of the usage
|
||||
and collects statistics for that purpose, including but not limited to the
|
||||
running of an instance, the applications installed and the number of Users.
|
||||
|
||||
Odoo SA commits not to disclose individual or named figures to third parties without the consent
|
||||
of the Customer, and to deal with all collected data in compliance with its official Privacy
|
||||
Policy, as published on `Odoo SA's website <https://www.odoo.com>`_.
|
||||
|
||||
Upon expiration or termination of this Agreement, this license is revoked immediately and the
|
||||
Customer agrees to stop using the software.
|
||||
|
||||
Should the Customer breach the terms of this section, the Customer agrees to
|
||||
pay Odoo SA an extra fee equal to 300% of the applicable list price for the
|
||||
actual number of Users for one year.
|
||||
|
||||
|
||||
.. _services_online:
|
||||
|
||||
4 Service Level
|
||||
===============
|
||||
|
||||
4.1 Bug Fixing Service
|
||||
----------------------
|
||||
|
||||
For the duration of this Agreement, Odoo SA commits to making all reasonable efforts to remedy any
|
||||
Bug of the Software submitted by the Customer through the appropriate channel (typically, Odoo SA's
|
||||
service desk email address or website form), and to start handling such Customer submissions
|
||||
within 2 business days.
|
||||
|
||||
The Customer understands that Bugs caused by a modification or extension that is not part of the
|
||||
official Software will not be covered by this service.
|
||||
|
||||
Both parties acknowledge that as specified in the license of the Software and in the :ref:`liability_online`
|
||||
section of this Agreement, Odoo SA cannot be held liable for Bugs in the Software.
|
||||
|
||||
4.2 Support Service
|
||||
-------------------
|
||||
|
||||
Support Scope
|
||||
+++++++++++++
|
||||
|
||||
For the duration of this Agreement, Odoo SA offer a support service, with an
|
||||
unlimited number of tickets for bugs and functional questions: how to use and
|
||||
configure Odoo for your specific needs.
|
||||
|
||||
This support service does not include support to customize Odoo, develop new
|
||||
modules, or perform specific actions on your database on your behalf. (e.g.
|
||||
recording data, or configuring the system for you) Those services can be
|
||||
offered in extra through our Success Pack service offer.
|
||||
|
||||
Support Service
|
||||
+++++++++++++++
|
||||
|
||||
Support issues should be submited online on https://odoo.com/help In case of
|
||||
emergency, you can call our support teams directly for a real time answer.
|
||||
|
||||
Our support teams are split across 3 continents in India (Ahmedabad), Belgium
|
||||
(Brussels) and United States (San Francisco) in order to cover 20 hours per
|
||||
open day. (monday to friday, excluding legal holidays in the respective
|
||||
countries)
|
||||
|
||||
No guarantees are provided on the time to qualify or close a support ticket,
|
||||
it's based on our best efforts. But 95% of the tickets are qualified within 2
|
||||
open days, and 90% of the critical bugs (when a user can not work on the system
|
||||
anymore) are processed within 2 hours.
|
||||
|
||||
The Odoo portal allows you to track you support tickets.
|
||||
|
||||
|
||||
4.3 Service Availability
|
||||
------------------------
|
||||
|
||||
Customer databases are hosted in the closest Odoo data center (EMEA: France,
|
||||
Americas: Canada, APAC: Hong Kong or Taiwan). Each customer instance is replicated
|
||||
in real-time on a hot-standby system located in the same data center.
|
||||
|
||||
We work with different hosting providers worldwide (and we can switch at anytime),
|
||||
but they always deliver at least 99.9% uptime guarantee. These metrics refer to
|
||||
the availability of the platform itself for all customers. Individual databases
|
||||
may be temporarily unavailable for specific reasons, typically related to the
|
||||
customer's actions, customizations or upgrades.
|
||||
|
||||
Our data centers are Tier-III certified or equivalent, with N+1 redundancy for
|
||||
power, network and cooling.
|
||||
|
||||
4.4 Backups & Recovery
|
||||
----------------------
|
||||
|
||||
Every database has 14 full snapshot backups for up to 3 months: 1/day for 7
|
||||
days, 1/week for 4 weeks, 1/month for 3 months. Every backup is replicated on
|
||||
at least 3 different machines in different data centers.
|
||||
|
||||
Users can download manual backups of their live data at any time.
|
||||
|
||||
For a permanent disaster impacting one server only, our Disaster Recovery Plan
|
||||
has the following metrics:
|
||||
- RPO (Recovery Point Objective) = 5 minutes, i.e. can lose maximum 5 minutes of work
|
||||
- RTO (Recovery Time Objective) = 30 minutes, i.e the service will be back online after maximum 30 minutes (Standby promotion time + DNS propagation time included)
|
||||
|
||||
For data center disasters (one entire data center is completely and permanently
|
||||
down), Disaster Recovery Plan has these metrics:
|
||||
- RPO (Recovery Point Objective) = 24h, i.e. you can lose maximum 24h of work if the data cannot be recovered and we need to restore the last daily backup
|
||||
- RTO (Recovery Time Objective) = 24h, i.e. the service will be restored from the backup within 24 hours in a different data center
|
||||
|
||||
4.5 Security
|
||||
------------
|
||||
|
||||
Database Security
|
||||
+++++++++++++++++
|
||||
|
||||
Customer data is stored in a dedicated database - no sharing of data between
|
||||
clients. Data access control rules implement complete isolation between customer
|
||||
databases running on the same cluster, no access is possible from one database
|
||||
to another.
|
||||
|
||||
Password Security
|
||||
+++++++++++++++++
|
||||
|
||||
Customer passwords are protected with industry-standard PBKDF2+SHA512
|
||||
encryption (salted + stretched for thousands of rounds).
|
||||
|
||||
Odoo staff does not have access to your password, and cannot retrieve it for
|
||||
you, the only option if you lose it is to reset it Login credentials are always
|
||||
transmitted securely over HTTPS.
|
||||
|
||||
System Security
|
||||
+++++++++++++++
|
||||
|
||||
All web connections to client instances are protected with state-of-the-art
|
||||
256-bit SSL encryption. All our SSL certificates use robust 2048-bit modulus
|
||||
with full SHA-2 certificates chains. Our servers are kept under a strict
|
||||
security watch, and always patched against the latest SSL vulnerabilities,
|
||||
enjoying Grade A SSL ratings at all times.
|
||||
|
||||
All Odoo online servers are running hardened Linux distributions with
|
||||
up-to-date security patches. Installations are ad-hoc and minimal to limit the
|
||||
number of services that could contain vulnerabilities (no PHP/MySQL stack for
|
||||
example)
|
||||
|
||||
Only a few trusted Odoo engineers have clearance to remotely manage the servers
|
||||
- and access is only possible using SSH key pairs (password authentication
|
||||
disallowed)
|
||||
|
||||
Firewalls and intrusion counter-measures help prevent unauthorized access.
|
||||
Automatic Distributed Denial of Service (DDoS) mitigation is implemented in EU
|
||||
and US data centers, and coming soon in Asia.
|
||||
|
||||
Staff Access
|
||||
++++++++++++
|
||||
|
||||
Odoo helpdesk staff may sign into your account to access settings related to
|
||||
your support issue. For this they use their own special staff credentials, not
|
||||
your password (which they have no way to know).
|
||||
|
||||
This special staff access improves efficiency and security: they can
|
||||
immediately reproduce the problem you are seeing, you never need to share your
|
||||
password, and we can audit and control staff actions separately!
|
||||
|
||||
Our Helpdesk staff strives to respect your privacy as much as possible, and
|
||||
only access files and settings needed to diagnose and resolve your issue
|
||||
|
||||
Physical Security
|
||||
+++++++++++++++++
|
||||
|
||||
The Odoo Online servers are hosted in several data centers worldwide, that must
|
||||
all satisfy with our minimum physical security criterions:
|
||||
- Physical access to the data center area where Odoo servers are located is restricted to data center technicians only
|
||||
- Security cameras are monitoring the data center locations
|
||||
|
||||
Credit Cards Safety
|
||||
+++++++++++++++++++
|
||||
|
||||
When you sign up for a paid Odoo Online subscription, we do not store your
|
||||
credit card information. Your credit card information is only transmitted
|
||||
securely between you and our PCI-Compliant payment acquirers: Ingenico and
|
||||
Paypal (even for recurring subscriptions)
|
||||
|
||||
Software Security
|
||||
+++++++++++++++++
|
||||
|
||||
The codebase of Odoo is laregely distributed and, thus, is continuously under
|
||||
examination by Odoo users and contributors worldwide. Community bug reports are
|
||||
therefore one important source of feedback regarding security. We encourage
|
||||
developers to audit the code and report security issues.
|
||||
|
||||
Odoo SA commits to sending a "Security Advisory" to the Customer for any
|
||||
security Bug that are discovered in the Software, at least 2 weeks before
|
||||
making the Security Advisory public, unless the Bug has already been disclosed
|
||||
publicly by a third party.
|
||||
|
||||
Security Advisories include a complete description of the Bug, its cause, its
|
||||
possible impacts on the Customer's systems, and the corresponding remedy for
|
||||
each Covered Version.
|
||||
|
||||
The Customer understands that the Bug and the information in the Security
|
||||
Advisory must be treated are Confidential Information as described in
|
||||
:ref:`confidentiality_online` during the embargo period prior to the public
|
||||
disclosure.
|
||||
|
||||
The Odoo R&D processes have code review steps that include security aspects,
|
||||
for new and contributed pieces of code. Odoo is designed in a way that prevents
|
||||
introducing most common security vulnerabilities:
|
||||
|
||||
- SQL injections are prevented by the use of a higher-level API that does not require manual SQL queries
|
||||
- XSS attacks are prevented by the use of a high-level templating system that automatically escapes injected data
|
||||
- The framework prevents RPC access to private methods, making it harder to introduce exploitable vulnerabilities
|
||||
- See also the OWASP Top Vulnerabilities section to see how Odoo is designed from the ground up to prevent such vulnerabilities from appearing.
|
||||
|
||||
Odoo is regularly audited by independent companies that are hired by our
|
||||
customers and prospects to perform audits and penetration tests. The Odoo
|
||||
Security Team receives the results and takes appropriate corrective measures
|
||||
whenever it is necessary. We can't however disclose any of those results,
|
||||
because they are confidential and belong to the commissioners.
|
||||
|
||||
Odoo also has a very active community of independent security researchers, who
|
||||
continuously monitor the source code and work with us to improve and harden the
|
||||
security of Odoo. Our Security Program is described on our Responsible
|
||||
Disclosure page: https://www.odoo.com/page/responsible-disclosure.
|
||||
|
||||
.. _upgrade_online:
|
||||
|
||||
4.6 Upgrade Services
|
||||
--------------------
|
||||
|
||||
.. _upgrade_odoo_online:
|
||||
|
||||
Upgrade Service for the Software
|
||||
++++++++++++++++++++++++++++++++
|
||||
|
||||
For the duration of this Agreement, the Customer can submit upgrade requests,
|
||||
in order to convert a database of the Software from one Covered Version of the
|
||||
Software to a more recent Covered Version (the "Target Version").
|
||||
|
||||
This service provided through an automated platform in order to allow the Customer to perform
|
||||
unattended upgrades once a previous version of the Customer's database has been successfully
|
||||
upgraded for a Covered Version.
|
||||
The Customer may submit successive upgrade requests for a database, and agrees to submit at least
|
||||
1 upgrade request for testing purposes before submitting the final upgrade request.
|
||||
|
||||
It is the sole responsibility of the Customer to verify and validate the upgraded database in order
|
||||
to detect Bugs, to analyze the impact of changes and new features implemented in the Target Version,
|
||||
and to convert and adapt for the Target Version any third-party extensions of the Software that
|
||||
were installed in the database before the upgrade (except where applicable as foreseen in section
|
||||
:ref:`upgrade_extra_online`).
|
||||
|
||||
The Customer may submit multiple upgrade requests for a database, until an
|
||||
acceptable result is achieved.
|
||||
|
||||
.. _upgrade_extra_online:
|
||||
|
||||
Upgrade Service for customizations
|
||||
++++++++++++++++++++++++++++++++++
|
||||
|
||||
For the duration of this Agreement, the Customer may request optional upgrade
|
||||
services for third-party extension modules of the Software, in addition to the
|
||||
regular Upgrade Services.
|
||||
|
||||
This optional service is subject to additional fees
|
||||
(as described in charges_online_) and includes the technical adaptation of third-party
|
||||
modules installed in the Customer's database and their corresponding data in
|
||||
order to be compatible with the Target Version. The Customer will receive an
|
||||
upgraded version of all installed third-party modules along with the upgraded
|
||||
database.
|
||||
|
||||
.. _charges_online:
|
||||
|
||||
5 Charges and Fees
|
||||
==================
|
||||
|
||||
.. _charges_standard_online:
|
||||
|
||||
5.1 Standard charges
|
||||
--------------------
|
||||
|
||||
The standard charges for the Odoo Online subscription, the Bug Fixing Service, Security Advisories
|
||||
Service and the Upgrade Service are based on the number of Users and applications used by
|
||||
the Customer, and specified in writing at the signature of the Agreement.
|
||||
|
||||
When during the Term, the Customer has more Users or applications than
|
||||
specified at the time of signature of this Agreement, the Customer agrees to
|
||||
pay an extra fee equivalent to the applicable list price (at the beginning of
|
||||
the Term) for the additional Users and applications, for the remainder of the
|
||||
Term.
|
||||
|
||||
.. _charges_renewal_online:
|
||||
|
||||
5.2 Renewal charges
|
||||
-------------------
|
||||
|
||||
Upon renewal as covered in section :ref:`term_online`, if the per-User charges applied
|
||||
during the previous Term are lower than the most current applicable per-User
|
||||
list price, the per-User charges will increase by up to 7% per year.
|
||||
|
||||
|
||||
.. _charges_thirdparty_online:
|
||||
|
||||
5.3 Charges for custom features or third-party modules
|
||||
------------------------------------------------------
|
||||
|
||||
.. FIXME: should we really fix the price in the contract?
|
||||
|
||||
The additional charge for the Upgrade, Support and Bugfix Service for custom
|
||||
modules developed by Odoo SA is a recurring price depending on the number of
|
||||
hours done to develop these custom features:
|
||||
- 4 EUR / month per hour of development in European contries
|
||||
- 5 USD / month per hour of development in other countries
|
||||
|
||||
In case the modules are not developed by Odoo SA, Odoo SA reserves the right to
|
||||
reject an upgrade request for third-party modules under the above conditions if
|
||||
the quality of the source code of those modules is too low, or if these modules
|
||||
constitute an interface with third-party software or systems. The upgrade of
|
||||
such modules will subject to a separate offer, outside of this Agreement.
|
||||
|
||||
.. _taxes_online:
|
||||
|
||||
5.4 Taxes
|
||||
---------
|
||||
|
||||
.. FIXME : extra section, not sure we need it?
|
||||
|
||||
All fees and charges are exclusive of all applicable federal, provincial, state, local or other
|
||||
governmental taxes, fees or charges (collectively, "Taxes"). The Customer is responsible for paying
|
||||
all Taxes associated with purchases made by the Customer under this Agreement, except when Odoo SA
|
||||
is legally obliged to pay or collect Taxes for which the Customer is responsible.
|
||||
|
||||
|
||||
.. _conditions_online:
|
||||
|
||||
6 Conditions of Services
|
||||
========================
|
||||
|
||||
6.1 Customer Obligations
|
||||
------------------------
|
||||
|
||||
.. FIXME: removed the clause about
|
||||
|
||||
The Customer agrees to:
|
||||
|
||||
- pay Odoo SA any applicable charges for the Services of the present Agreement, in accordance with
|
||||
the payment conditions specified in the corresponding invoice ;
|
||||
- appoint 1 dedicated Customer contact person for the entire duration of the Agreement;
|
||||
|
||||
|
||||
.. _no_soliciting_online:
|
||||
|
||||
6.2 No Soliciting or Hiring
|
||||
---------------------------
|
||||
|
||||
Except where the other party gives its consent in writing, each party, its affiliates and
|
||||
representatives agree not to solicit or offer employment to any employee of the other party who is
|
||||
involved in performing or using the Services under this Agreement, for the duration of the Agreement
|
||||
and for a period of 12 months from the date of termination or expiration of this Agreement.
|
||||
In case of any breach of the conditions of this section that leads to the termination of said
|
||||
employee toward that end, the breaching party agrees to pay to the other party an amount of
|
||||
EUR (€) 30 000.00 (thirty thousand euros).
|
||||
|
||||
|
||||
.. _publicity_online:
|
||||
|
||||
6.3 Publicity
|
||||
-------------
|
||||
|
||||
Except where notified otherwise in writing, each party grants the other a non-transferable,
|
||||
non-exclusive, royalty free, worldwide license to reproduce and display the other party’s name,
|
||||
logos and trademarks, solely for the purpose of referring to the other party as a customer or
|
||||
supplier, on websites, press releases and other marketing materials.
|
||||
|
||||
|
||||
.. _confidentiality_online:
|
||||
|
||||
6.4 Confidentiality
|
||||
-------------------
|
||||
|
||||
Definition of "Confidential Information":
|
||||
All information disclosed by a party (the "Disclosing Party") to the other party
|
||||
(the "Receiving Party"), whether orally or in writing, that is designated as confidential or
|
||||
that reasonably should be understood to be confidential given the nature of the information and
|
||||
the circumstances of disclosure. In particular any information related to the business,
|
||||
affairs, products, developments, trade secrets, know-how, personnel, customers and suppliers of
|
||||
either party should be regarded as confidential.
|
||||
|
||||
For all Confidential Information received during the Term of this Agreement, the Receiving Party
|
||||
will use the same degree of care that it uses to protect the confidentiality of its own similar
|
||||
Confidential Information, but not less than reasonable care.
|
||||
|
||||
The Receiving Party may disclose Confidential Information of the Disclosing Party to the extent
|
||||
compelled by law to do so, provided the Receiving Party gives the Disclosing Party prior notice of
|
||||
the compelled disclosure, to the extent permitted by law.
|
||||
|
||||
.. _termination_online:
|
||||
|
||||
6.5 Termination
|
||||
---------------
|
||||
|
||||
In the event that either Party fails to fulfill any of its obligations arising herein, and if such
|
||||
breach has not been remedied within 30 calendar days from the written notice of such
|
||||
breach, this Agreement may be terminated immediately by the non-breaching Party.
|
||||
|
||||
Further, Odoo SA may terminate the Agreement immediately in the event the Customer fails to pay
|
||||
the applicable fees for the Services within the due date specified on the corresponding invoice.
|
||||
|
||||
Surviving Provisions:
|
||||
The sections ":ref:`confidentiality_online`”, “:ref:`disclaimers_online`”,
|
||||
“:ref:`liability_online`”, and “:ref:`general_provisions_online`” will survive any termination or expiration of
|
||||
this Agreement.
|
||||
|
||||
|
||||
.. _warranties_disclaimers_online:
|
||||
|
||||
7 Warranties, Disclaimers, Liability
|
||||
====================================
|
||||
|
||||
.. _warranties_online:
|
||||
|
||||
7.1 Warranties
|
||||
--------------
|
||||
|
||||
.. industry-standard warranties regarding our Services while Agreement in effect
|
||||
|
||||
For the duration of this Agreement, Odoo SA commits to using commercially reasonable efforts to
|
||||
execute the Services in accordance with the generally accepted industry standards provided that:
|
||||
|
||||
- the Customer’s computing systems are in good operational order and the Software is installed in a
|
||||
suitable operating environment;
|
||||
- the Customer provides adequate troubleshooting information and access so that Odoo SA can
|
||||
identify, reproduce and address problems;
|
||||
- all amounts due to Odoo SA have been paid.
|
||||
|
||||
The Customer's sole and exclusive remedy and Odoo SA's only obligation for any breach of this warranty
|
||||
is for Odoo SA to resume the execution of the Services at no additional charge.
|
||||
|
||||
.. _disclaimers_online:
|
||||
|
||||
7.2 Disclaimers
|
||||
---------------
|
||||
|
||||
.. no other warranties than explicitly provided
|
||||
|
||||
Except as expressly provided herein, neither party makes any warranty of any kind, whether express,
|
||||
implied, statutory or otherwise, and each party specifically disclaims all implied warranties,
|
||||
including any implied warranty of merchantability, fitness for a particular purpose or
|
||||
non-infringement, to the maximum extent permitted by applicable law.
|
||||
|
||||
Odoo SA does not warrant that the Software complies with any local or international law or regulations.
|
||||
|
||||
.. _liability_online:
|
||||
|
||||
7.3 Limitation of Liability
|
||||
---------------------------
|
||||
|
||||
To the maximum extent permitted by law, the aggregate liability of each party together with its
|
||||
affiliates arising out of or related to this Agreement will not exceed 50% of the total amount
|
||||
paid by the Customer under this Agreement during the 12 months immediately preceding the date of the event
|
||||
giving rise to such claim. Multiple claims shall not enlarge this limitation.
|
||||
|
||||
In no event will either party or its affiliates be liable for any indirect, special, exemplary,
|
||||
incidental or consequential damages of any kind, including but not limited to loss of revenue,
|
||||
profits, savings, loss of business or other financial loss, costs of standstill or delay, lost or
|
||||
corrupted data, arising out of or in connection with this Agreement regardless of the form of
|
||||
action, whether in contract, tort (including strict negligence) or any other legal or equitable
|
||||
theory, even if a party or its affiliates have been advised of the possibility of such damages,
|
||||
or if a party or its affiliates' remedy otherwise fails of its essential purpose.
|
||||
|
||||
.. _force_majeure_online:
|
||||
|
||||
7.4 Force Majeure
|
||||
-----------------
|
||||
|
||||
Neither party shall be liable to the other party for the delay in any performance or failure to
|
||||
render any performance under this Agreement when such failure or delay is caused by governmental
|
||||
regulations, fire, strike, war, flood, accident, epidemic, embargo, appropriation of plant or
|
||||
product in whole or in part by any government or public authority, or any other cause or causes,
|
||||
whether of like or different nature, beyond the reasonable control of such party as long as such
|
||||
cause or causes exist.
|
||||
|
||||
|
||||
.. _general_provisions_online:
|
||||
|
||||
8 General Provisions
|
||||
====================
|
||||
|
||||
.. _governing_law_online:
|
||||
|
||||
8.1 Governing Law
|
||||
-----------------
|
||||
|
||||
Both parties agree that the laws of Belgium will apply, should any dispute arise out of or
|
||||
in connection with this Agreement, without regard to choice or conflict of law principles.
|
||||
To the extent that any lawsuit or court proceeding is permitted hereinabove, both
|
||||
parties agree to submit to the sole jurisdiction of the Nivelles (Belgium) court for the purpose of
|
||||
litigating all disputes.
|
||||
|
||||
.. _severability_online:
|
||||
|
||||
8.2 Severability
|
||||
----------------
|
||||
|
||||
In case any one or more of the provisions of this Agreement or any application thereof shall be
|
||||
invalid, illegal or unenforceable in any respect, the validity, legality and enforceability of the
|
||||
remaining provisions of this Agreement and any application thereof shall be in no way thereby
|
||||
affected or impaired. Both parties undertake to replace any invalid, illegal or
|
||||
unenforceable provision of this Agreement by a valid provision having the same effects and
|
||||
objectives.
|
||||
|
||||
|
||||
.. _appendix_a_online:
|
||||
|
||||
9 Appendix A: Odoo Enterprise Edition License
|
||||
=============================================
|
||||
|
||||
.. only:: latex
|
||||
|
||||
Odoo Enterprise Edition is licensed under the Odoo Enterprise Edition License v1.0,
|
||||
defined as follows:
|
||||
|
||||
.. include:: ../licenses/enterprise_license.txt
|
||||
:literal:
|
||||
|
||||
.. only:: html
|
||||
|
||||
See :ref:`odoo_enterprise_license`.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
.. FIXME: move this is to appendix or somewhere else?
|
||||
|
||||
.. only:: disabled
|
||||
|
||||
Agreement Registration
|
||||
======================
|
||||
|
||||
Customer contact information
|
||||
----------------------------
|
||||
|
||||
Company name:
|
||||
Company address:
|
||||
VAT number (if applicable):
|
||||
Contact name:
|
||||
Email:
|
||||
Phone:
|
||||
|
||||
Technical contact information (can be an Odoo partner):
|
||||
-------------------------------------------------------
|
||||
Company name:
|
||||
Contact name:
|
||||
Email:
|
||||
Phone:
|
||||
|
||||
|
||||
By signing this Agreement I confirm I am a legal representative of Customer as stated in the
|
||||
resent section and approve all provisions and conditions of the present Agreement:
|
||||
|
||||
For and on behalf of (company name):
|
||||
Last name, first name:
|
||||
Title:
|
||||
Date:
|
||||
|
||||
Signature:
|
Loading…
Reference in New Issue
Block a user