mirror of
https://github.com/andwati/zitadel.git
synced 2026-11-21 20:38:47 +00:00
docs: introduce versioned docs and migrate to fuma (#11166)
## Todos for release - [x] Configure Env in docs project on vercel - [x] Configure Root Path in the docs project on vercel - [ ] Remove old CSP https://github.com/zitadel/website/pull/1592 ## What we did This pull request migrates the project documentation from the old `docs/` directory to the new `apps/docs/` directory, introduces a new documentation system built with Next.js and Fumadocs, and updates all relevant references, configuration files, and documentation to reflect this change. It also adds new configuration and ignore files for the new documentation app, updates CI and linting to exclude the new docs from certain checks, and revises the contributing guidelines accordingly. **Documentation System Migration and New Docs App** * Migrated all documentation from `docs/` to `apps/docs/`, and updated all references in `README.md`, `CONTRIBUTING.md`, and other files to point to the new location. [[1]](diffhunk://#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055L585-L640) [[2]](diffhunk://#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055L660-R607) [[3]](diffhunk://#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055L740-R687) [[4]](diffhunk://#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L2-R3) [[5]](diffhunk://#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L30-R30) * Added a new Next.js/Fumadocs-based documentation app under `apps/docs/`, including core app files, layouts, routing, search API, and a comprehensive `README.md` with development and contribution instructions. [[1]](diffhunk://#diff-5a1b07344a2c1b4d3f37b23ff1388b62cd9f57dea3c1cd23d8a0412b7602b132R1-R74) [[2]](diffhunk://#diff-462b9ad1eabbb7d1c29bb9c36e4931eb180fd7190900e6d2babf8f4d66ad1c28R1-R39) [[3]](diffhunk://#diff-e16ae25660ded787b10ac35dea96d5ecaacf895dae0afc8a9bd4382dc79a8c87R1-R7) [apps/docs/app/[[...slug]]/layout.tsxR1-R81](diffhunk://#diff-59e08acde4e805b7aeccef1dcf98f1d71dfc550777e6b9402085cee0e9fa4e0aR1-R81), [apps/docs/app/[[...slug]]/page.tsxR1-R79](diffhunk://#diff-e5df3f80d0fa01e12d63d81f29c57a9d14e846c78fd3beabb2ef768e38fd9580R1-R79), [[4]](diffhunk://#diff-389b34918e040cacaa87cd7201ffa462cc2b0b716736f537e3d3c660ac69353bR1-R7) [[5]](diffhunk://#diff-d3b03416d1c457b19f1c27b26f2db741412df841b875c26ccadc36e4522247f4R1-R29) [[6]](diffhunk://#diff-c8fb8339570a5305809be7c618e14705fd86390dc278e6ce8ba224a7bc8b0c3cR1-R25) **Configuration and Tooling Updates** * Updated `.github/workflows/codeql.yml`, `.golangci.yaml`, and `.github/dependabot.yml` to properly handle the new docs app: excluded `apps/docs` from certain checks, added npm dependency updates for the docs app, and excluded generated content. [[1]](diffhunk://#diff-12783128521e452af0cfac94b99b8d250413c516ec71fe6d97dbea666ff7ba27L8-R14) [[2]](diffhunk://#diff-9917ddc9f1c3304218f7269265b746d997c5c0615478177b5fceecd33ef47cb5R5-R6) [[3]](diffhunk://#diff-9917ddc9f1c3304218f7269265b746d997c5c0615478177b5fceecd33ef47cb5R126-R129) [[4]](diffhunk://#diff-dd4fbda47e51f1e35defb9275a9cd9c212ecde0b870cba89ddaaae65c5f3cd28R89-R106) * Updated `.devcontainer/devcontainer.json` to use the latest Go 1.25.3 version for consistency. **Licensing and Miscellaneous** * Added `apps/docs/` to the list of licensed directories in `LICENSING.md`. These changes ensure the documentation is now maintained in a modern, scalable system and all project tooling is updated to support the new structure. --------- Co-authored-by: Federico Coppede <[email protected]>
This commit is contained in:
co-authored by
Federico Coppede
parent
7b6395c348
commit
d8ea041c56
@@ -0,0 +1,93 @@
|
||||
<table>
|
||||
<tr>
|
||||
<th>Type of personal data</th>
|
||||
<th>Examples</th>
|
||||
<th>Affected data subjects</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Basic data</strong></td>
|
||||
<td>
|
||||
<ul>
|
||||
<li>First and last names</li>
|
||||
<li>Email addresses</li>
|
||||
<li>User name</li>
|
||||
</ul>
|
||||
</td>
|
||||
<td>All users</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Login data</strong></td>
|
||||
<td>
|
||||
<ul>
|
||||
<li>Randomly generated ID</li>
|
||||
<li>Password</li>
|
||||
<li>Public keys / certificates ("FIDO2", "U2F", "x509", ...)</li>
|
||||
<li>User names or identifiers of external login providers</li>
|
||||
<li>Phone number(s)</li>
|
||||
</ul>
|
||||
</td>
|
||||
<td>
|
||||
<p>All users</p>
|
||||
<p>Password: Users who use authentication methods with password.</p>
|
||||
<p>Public Keys: Users who use an authentication procedure with cryptographic keys.</p>
|
||||
<p>External login provider identifiers: Users who use an external login provider.</p>
|
||||
<p>Phone number: Users who use authentication methods with SMS</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Profile data</strong></td>
|
||||
<td>
|
||||
<ul>
|
||||
<li>Profile pictures</li>
|
||||
<li>Gender</li>
|
||||
<li>Language</li>
|
||||
<li>Nickname</li>
|
||||
<li>Display name</li>
|
||||
<li>Phone number(s)</li>
|
||||
</ul>
|
||||
</td>
|
||||
<td>Users who voluntarily add profile data</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Communication data</strong></td>
|
||||
<td>
|
||||
<ul>
|
||||
<li>Emails</li>
|
||||
<li>Chats</li>
|
||||
<li>Call metadata</li>
|
||||
</ul>
|
||||
</td>
|
||||
<td>Customers and users who communicate with us directly (e.g. support)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Payment data</strong></td>
|
||||
<td>
|
||||
<ul>
|
||||
<li>Billing address</li>
|
||||
<li>Payment information</li>
|
||||
<li>Customer number</li>
|
||||
<li>Customer history</li>
|
||||
<li>Credit rating information</li>
|
||||
</ul>
|
||||
</td>
|
||||
<td>
|
||||
<p>Customers who use services that require payment</p>
|
||||
<p>Credit rating information: Only customers who pay by invoice</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>Usage metadata</strong></td>
|
||||
<td>
|
||||
<ul>
|
||||
<li>User agent</li>
|
||||
<li>IP addresses</li>
|
||||
<li>Operating system</li>
|
||||
<li>Time and date</li>
|
||||
<li>URL</li>
|
||||
<li>Referrer URL</li>
|
||||
<li>Accept Language</li>
|
||||
</ul>
|
||||
</td>
|
||||
<td>All users</td>
|
||||
</tr>
|
||||
</table>
|
||||
@@ -0,0 +1,68 @@
|
||||
---
|
||||
title: Annex for ZITADEL Enterprise and Support Services
|
||||
sidebar_label: Enterprise Agreement
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on November 15, 2023
|
||||
|
||||
This annex of the [Framework Agreement](./terms-of-service) describes the commercial support services (**Support Services**, **Enterprise License**, or **Enterprise Agreement**) for units of ZITADEL software products (**Unit**), if not otherwise defined a Unit refers to a is a single, dedicated setup of an application or service covered under an Enterprise agreement.
|
||||
|
||||
The customer relationship (**Framework Agreement** or **The Agreement**) is created by the **Customer** (**"you"**) by accepting a **Purchase Order** (**"PO"**) for the specified Support Services (**Booking**). Jointly you and ZITADEL will be referred to as **the Parties**. The terms of service (**"TOS"**) outlined in this document establish the most important points of this Framework Agreement – independently of the use of any other services.
|
||||
|
||||
### Term
|
||||
|
||||
Coverage under this Agreement will start with Booking of Support Services, for a minimum period of 12 months.
|
||||
Support Services agreements will automatically renew for additional one-year term upon submission of a purchase order for renewal, unless either you or ZITADEL provides written notice (E-Mail sufficient) of termination of any such term.
|
||||
Each renewal will be at ZITADEL's then-current rate.
|
||||
In the event that you accesses ZITADEL Support services in any way after the Agreement has expired or been terminated, you will continue to be bound by this Agreement, which will continue to apply to the services after such expiration or termination.
|
||||
|
||||
### Service review
|
||||
|
||||
If not otherwise agreed, ZITADEL offers a yearly review meeting with you to discuss the service quality and any feedback you might have. We are not required to participate in the meeting after the term has expired.
|
||||
|
||||
## Your obligations
|
||||
|
||||
### Maintenance of units
|
||||
|
||||
You will ensure that units eligible for Support Service are maintained and upgraded frequently.
|
||||
If you operate units with a release date older than 180 days since our latest stable release, the term is continued but ZITADEL is not required to handle any support request for that unit until the units are upgraded and re-certified.
|
||||
|
||||
### Support Process
|
||||
|
||||
You will ensure to follow the support process, especially provide all required initial information to the issue, as outlined in the [Annex](./service-description/support-services) to this document.
|
||||
|
||||
### Training of support staff
|
||||
|
||||
You will ensure regular training of your support staff. Your support staff must be able to provide the required information for support issues to us, and thus requires access and up-to-date knowledge of the services.
|
||||
|
||||
Initial know-how transfer for the services will be organized in training sessions conducted by us. We can provide knowledge sessions throughout the term to train newly onboarded staff, update your support staff about important updates, or refresh knowledge in specified areas. In case we notice insufficient quality of support requests from Customers, we will propose appropriate training sessions.
|
||||
|
||||
## Financial
|
||||
|
||||
### Lapsed Service Fee
|
||||
|
||||
In case the term of the Support Service contract has expired within 1 to 180 days, you will be required to pay a Lapsed Service fee in addition to purchasing and activating a one-year renewal contract term at the then-current fee and conditions. The renewal term's start date will also be backdated to begin coverage from the service's original expiration date.
|
||||
|
||||
Please contact us for current fees.
|
||||
|
||||
### Recertification Fee
|
||||
|
||||
Recertification of a unit, to be covered under Support Services, is required for:
|
||||
|
||||
* units for which Support Services have been expired for more than 180 days
|
||||
* units that run a release that is older than 180 days from the products most recent stable release
|
||||
* requests for support on products and services purchased or supported from non-authorized resellers
|
||||
|
||||
Recertification of a unit requires payment of a Recertification Fee which results in a checkup of the unit by ZITADEL. The unit will be inspected to asses its condition and eligibility for service coverage.
|
||||
|
||||
Please contact us for current fees.
|
||||
|
||||
### Disaster recovery
|
||||
|
||||
You are solely responsible to ensure appropriate backup and disaster recovery of Units managed by you.
|
||||
Any liability for damages, indirect or direct, in case of data loss is explicitly rejected.
|
||||
|
||||
### Amendments
|
||||
|
||||
We are entitled to unilaterally amend these TOS at any time. The current version is accessible via our website. We will inform you of any amendments via email. These amendments shall be considered as accepted upon booking additional services or at the latest after 30 days. In the case of a rejection on your part we reserve the right to terminate the Framework Agreement.
|
||||
@@ -0,0 +1,329 @@
|
||||
---
|
||||
title: Data Processing Agreement
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
import { PiiTable } from "@/components/pii_table";
|
||||
|
||||
Last updated on May 8, 2025
|
||||
|
||||
This Data Protection Agreement and its annexes (“**DPA**”) are part of the [Framework Agreement](./terms-of-service) between Zitadel, Inc. and it's affiliates ("**Zitadel**") and the Customer in respect of the provision of certain services, including any applicable statement of work, booking, purchase order (PO) or any agreed upon instructions (the "**Agreement**") and applies where, and to the extent that, Zitadel processes Personal Data as a Processor on behalf of the Customer under the Framework Agreement (each a “**Party**” and together the “**Parties**”).
|
||||
|
||||
All capitalized terms not defined in this DPA will have the meanings set forth in the Agreement.
|
||||
Any privacy or data protection related clauses or agreement previously entered into by Zitadel and the Customer, with regards to the subject matter of this DPA, will be superseded and replaced by this DPA.
|
||||
No one other than a Party to this DPA, their successors and permitted assignees will have any right to enforce any of its terms.
|
||||
|
||||
This DPA shall become legally binding upon Customer entering into the Agreement.
|
||||
|
||||
## Definitions
|
||||
|
||||
"**Applicable Data Protection Law**" means all worldwide data protection and privacy laws and regulations applicable to the Personal Data, including, where applicable, EU/UK Data Protection Law and US Data Protection Laws (in each case, as amended, adopted, or superseded from time to time).
|
||||
|
||||
“**Controller**,” “**collecting**,” “**processor**,” and “**processing**,” shall have the meanings given to them under Applicable Data Protection Law.
|
||||
|
||||
“**Business**,” “**service provider**,” “**contractor**,” “**selling**,” “**sharing**” and “**third party**” shall have the meanings given to them under applicable US Data Protection Laws.
|
||||
|
||||
"**Customer Data**" means information, data and other content, in any form or medium, that is submitted, posted or otherwise transmitted by or on behalf of the Customer through the Zitadel Cloud or Services. For the avoidance of doubt, Customer Data includes Customer Personal Data.
|
||||
|
||||
“**Customer Personal Data**” means, in any form or medium, all Personal Data that is processed by Zitadel or its sub-processors on behalf of Customer in connection with the Agreement.
|
||||
|
||||
“**EU/UK Data Protection Law**” means: (i) Regulation 2016/679 of the European Parliament and of the Council on the protection of natural persons with regard to the processing of Personal Data and on the free movement of such data, also known as the General Data Protection Regulation (“**GDPR**”); (ii) the GDPR as saved into United Kingdom law by virtue of section 3 of the United Kingdom’s European Union (Withdrawal) Act 2018 (“**UK GDPR**”); (iii) the EU e-Privacy Directive (Directive 2002/58/EC); (iv) the Swiss Federal Act on Data Protection of 2020 and its Ordinance (“**Swiss FADP**”) and (v) any and all applicable national data protection laws and regulatory requirements made under, pursuant to or that apply in conjunction with any of (i), (ii) or (iii); in each case as may be amended or superseded from time to time.
|
||||
|
||||
“**Personal Data**” shall have the meaning given to it, or to the terms “personally identifiable information” and “personal information” under applicable Data Protection Law, but shall include, at a minimum, any information related to an identified or identifiable natural person.
|
||||
|
||||
“**Restricted Transfer**” means: (i) where the GDPR applies, a transfer of Personal Data from the EEA to a country outside of the EEA which is not subject to an adequacy determination by the European Commission; and (ii) where UK-GDPR applies, a transfer of Personal Data from the United Kingdom to any other country which is not subject to adequacy regulations pursuant to Section 17A of the United Kingdom Data Protection Act 2018, in each case whether such transfer is direct or via onward transfer.
|
||||
|
||||
“**Security Incident**” means any unauthorized or unlawful breach of security leading to, or reasonably believed to have led to, the accidental or unlawful destruction, loss, or alteration of, or unauthorized disclosure or access to, Personal Data transmitted, stored or otherwise processed by Zitadel under or in connection with the Agreement.
|
||||
|
||||
“**Standard Contractual Clauses**” or “**SCCs**” means the contractual clauses annexed to the European Commission’s Implementing Decision 2021/914 of 4 June 2021 on standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council.
|
||||
|
||||
“**sub-processor**” means any third-party processor engaged by Zitadel to process Customer Data (but shall not include Zitadel employees, contractors or consultants).
|
||||
|
||||
“**UK Addendum**” means the International Data Transfer Addendum (version B1.0) issued by the Information Commissioner’s Office under S119(A) of the UK Data Protection Act 2018, as updated or amended from time to time.
|
||||
|
||||
“**US Data Protection Laws**” means any relevant U.S. federal and state privacy laws (and any implementing regulations and amendment thereto) effective as of the date of this DPA and that applies to the processing of Customer Personal Data under the Agreement, which may include, depending on the circumstances and without limitation, (i) the California Consumer Privacy Act (Cal. Civ. Code §§ 1798.100 et seq.), as amended by the California Privacy Rights Act of 2020 along with its implementing regulations (“**CCPA**”), (ii) the Colorado Privacy Act (Colo. Rev. Stat. §§ 6-1-1301 et seq.) (CPA), (iii) Connecticut’s Data Privacy Act (CTDPA), (iv) the Utah Consumer Privacy Act (Utah Code Ann. §§ 13-61-101 et seq.) (UCPA) and (v) the Virginia Consumer Data Protection Act VA Code Ann. §§ 59.1-575 et seq. (VCDPA).
|
||||
|
||||
## Processing of Personal Data
|
||||
|
||||
This DPA applies where and only to the extent that Zitadel processes Customer Personal Data in connection with the provision of the Services under the Agreement involving the processing of Personal Data protected by Applicable Data Protection Law.
|
||||
This DPA reflects the commitment of both Parties to abide by Applicable Data Protection Law for the processing of Personal Data by Zitadel as a processor for the purpose of the Zitadel's provision of the Services and its execution of the Agreement.
|
||||
|
||||
This DPA will become effective on the date the Agreement enters into effect and will remain in force for the term of the Agreement, unless otherwise provided for in this DPA or unless individual provisions obviously result in obligations going beyond this.
|
||||
For the avoidance of doubt, the terms of the Framework Agreement will continue in full force and effect; however, to the extent any term in any Agreement regarding either Party’s obligations with respect to Customer Data is less restrictive than or is inconsistent with this DPA, the terms of this DPA shall supersede and control.
|
||||
|
||||
The Parties acknowledge that the following Customer Data will be processed as part of the Services:
|
||||
|
||||
<PiiTable />
|
||||
|
||||
## Scope
|
||||
|
||||
Under this Agreement, Zitadel shall process Customer Personal Data to perform its obligations under the Agreement and and strictly in accordance with the documented instructions of Customer (the “**Permitted Purpose**”), except where otherwise required by law(s) that are not incompatible with Applicable Data Protection Law.
|
||||
|
||||
The Parties acknowledge and agree that for the purposes of this DPA, the Customer is the controller and appoints Zitadel as a processor to process the Customer Personal Data.
|
||||
To the extent that the Parties are subject to the California Consumer Privacy Act (CCPA), the Customer is the business whereas Zitadel is a service provider to the Customer.
|
||||
Each Party shall comply with the obligations that apply to it under Applicable Data Protection Law.
|
||||
|
||||
Each Party shall comply with its own obligations under Applicable Data Protection Law in respect of any Customer Personal Data processed under the Agreement.
|
||||
|
||||
## Customer's Responsibilities
|
||||
|
||||
The Customer’s instructions to Zitadel shall comply with Applicable Data Protection Law.
|
||||
The Customer will have sole responsibility for the accuracy, quality and legality of the Customer Data, the means by which the Customer acquired the Customer Data, and the Customer's permissions to process the Customer Data pursuant to this DPA.
|
||||
|
||||
As required under Applicable Data Protection Law, the Customer will provide all necessary notices to data subjects and secure the applicable lawful grounds for processing Data under the DPA, including where applicable, all necessary permissions and consents from them. To the extent required under Applicable Data Protection Law, the Customer will receive and document the appropriate consent from the data subject(s).
|
||||
|
||||
The Customer represents and warrants that (i) it complies with Applicable Data Protection Law as relevant to the lawful processing by Zitadel of Customer Personal Data for the purposes contemplated by this DPA and the Agreement; and (ii) to the knowledge of the Customer, the processing of Customer Personal Data by Zitadel in accordance with the Customer’s instructions will not cause Zitadel to be in breach of any Applicable Data Protection Law.
|
||||
|
||||
The Customer shall not disclose any special categories of Personal Data or sensitive personal information (as these terms are defined under Applicable Data Protection Law) to Zitadel for processing.
|
||||
|
||||
## Obligations of the processor
|
||||
|
||||
### Bound by the Customer's directions and instructions
|
||||
|
||||
Customer hereby instructs Zitadel to process Customer Data for the Permitted Purpose.
|
||||
|
||||
Zitadel processes Personal Data in accordance with its privacy policy (cf. [Privacy Policy](./policies/privacy-policy)) and upon the documented directions of the Customer (which includes the Agreement).
|
||||
Subsequent instructions shall be given either in writing, whereby e-mail shall suffice, or orally with immediate written confirmation.
|
||||
|
||||
Zitadel shall promptly inform Customer if it becomes aware that such processing instructions infringe Applicable Data Protection Law (but without obligation to actively monitor compliance with Applicable Data Protection Law).
|
||||
In such case, Zitadel shall be entitled to suspend the processing until the infringing instruction is withdrawn or confirmed.
|
||||
|
||||
### Confidentiality obligations
|
||||
|
||||
Zitadel shall ensure that any person that it authorizes to process Customer Data (including Zitadel’s staff, agents and sub-processors) (an “Authorized Person”) shall be subject to a strict duty of confidentiality (whether a contractual duty or a statutory duty) and shall not permit any person to process the Customer Data that is not under such a duty of confidentiality.
|
||||
Zitadel shall ensure that all Authorized Persons process the Customer Data only as necessary for the Permitted Purpose.
|
||||
|
||||
### Technical and organizational measures
|
||||
|
||||
Zitadel shall implement appropriate technical and organizational measures to protect the Customer Data from a Security Incident, as described in Annex II to this DPA.
|
||||
Such measures shall comply with all Applicable Data Protection Law and shall further have regard to the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons.
|
||||
The Customer acknowledges that such measures are subject to technical progress and development and that Zitadel may update or modify such measures from time to time, provided that such updates and modifications do not degrade or diminish overall security of the Customer Data, or of the Services under the Agreement.
|
||||
|
||||
### Involvement of subcontracted processors
|
||||
|
||||
Customer agrees that Zitadel may engage sub-processors to process Customer Data on Customer’s behalf. A current and complete [list of involved and approved sub-processors](https://zitadel.com/trust) can be found on our [Trust Center](https://zitadel.com/trust) (as may be updated from time to time in accordance with this DPA).
|
||||
|
||||
Zitadel will notify Customer by updating the list of sub-processors and, if Customer has subscribed to notices, via email.
|
||||
If, within five (5) calendar days after such notice, Customer notifies Zitadel in writing that Customer objects to Zitadel's appointment of a new sub-processor based on reasonable data protection concerns, the parties will discuss such concerns in good faith with a view to achieving a commercially reasonable resolution.
|
||||
If the parties are not able to mutually agree to a resolution of such concerns, Customer, as its sole and exclusive remedy, may terminate the Agreement for convenience with no refunds and Customer will remain liable to pay any committed fees in an order form, order, statement of work or other similar ordering document.
|
||||
|
||||
Zitadel shall inform the Customer if it adds or replaces any sub-processor at least fifteen (15) days prior to any such change (including details of the processing it performs or will perform).
|
||||
The Customer may object in writing to Zitadel’s engagement of a new sub-processor on reasonable grounds relating to the protection of Customer Personal Data by notifying Zitadel promptly in writing within fifteen (15) calendar days of receipt of Zitadel’s notice.
|
||||
In such case, the parties shall discuss Customer’s concerns in good faith with a view to achieving a commercially reasonable resolution.
|
||||
If such objection right is not exercised by Customer, silence shall be deemed to constitute an approval of the relevant sub-processor engagement.
|
||||
|
||||
Where Zitadel appoints a sub-processor, Zitadel shall: (i) enter into an agreement with each sub-processor containing data protection terms that provide at least the same level of protection for Customer Data as those contained in this DPA, to the extent applicable to the nature of the services provided by such sub-processor; and (ii) remain responsible to the Customer for Zitadel’s sub-processors’ failure to perform their obligations with respect to the processing of Customer Data.
|
||||
|
||||
Taking into account the safeguards set forth in this DPA, Customer Data may be processed outside of Switzerland or the EU/EAA, such as in the United States or any country in which Zitadel or is sub-processors operate. Our [list of involved and approved sub-processors](https://zitadel.com/trust) provides additional details.
|
||||
|
||||
### Assistance in responding to requests
|
||||
|
||||
Zitadel shall provide all reasonable and timely assistance (which may include by appropriate technical and organizational measures) to the Customer to enable the Customer to respond to: (i) any request from a data subject to exercise any of their rights under Applicable Data Protection Law ("**Data Subject Request**"); and (ii) any other correspondence, enquiry or complaint received from a data subject, regulator or other third party in connection with the processing of Customer Personal Data.
|
||||
|
||||
In the event that any such request, correspondence, enquiry or complaint is made directly to Zitadel, Zitadel shall promptly inform the Customer providing full details of the same.
|
||||
Zitadel will not respond to a Data Subject Request, however the Customer acknowledges and agrees that Zitadel may at its discretion respond to confirm that such request relates to the Customer.
|
||||
|
||||
The Customer hereby acknowledges and agrees that the Services include features which will allow the Customer to manage Data Subject Requests directly through the Services without additional assistance from the Processor.
|
||||
If the Customer does not have the ability to address a Data Subject Request, Zitadel will, upon the Customer’s written request, provide reasonable assistance to facilitate the Customer’s response to such Data Subject Request to the extent such assistance is consistent with Applicable Data Protection Law; provided that the Customer will be responsible for paying for any reasonable costs incurred or fees charged by Zitadel for providing such assistance.
|
||||
|
||||
Zitadel, unless prohibited from doing so by applicable law, will promptly notify the Customer of any requests from a regulator, law enforcement authority or any other relevant and competent authority in relation to the Customer Personal Data that is being processed on behalf of the Customer, to the extent that the request may result in the disclosure of Customer Personal Data to such regulator, law enforcement authority or any other relevant and competent authority.
|
||||
|
||||
### Cooperation and support for the Customer
|
||||
|
||||
Zitadel shall provide the Customer with all such reasonable and timely assistance as Customer may require in order to enable it to conduct a data protection impact assessment (or equivalent document) where required by Applicable Data Protection Law, including, if necessary, to assist Customer to consult with its relevant data protection or other regulatory authority.
|
||||
|
||||
### Security incidents
|
||||
|
||||
Upon becoming aware of a Security Incident, Zitadel shall inform Customer without undue delay and provide all such timely information and cooperation as Customer may require for the Customer to fulfil its data breach or cybersecurity incident reporting obligations under (and in accordance with the timescales required by) Applicable Data Protection Law.
|
||||
Customer shall further take all such measures and actions as are reasonable and necessary to investigate, contain, and remediate or mitigate the effects of the Security Incident, to the extent that the remediation is within Zitadel's control, and shall keep Customer informed of all material developments in connection with the Security Incident.
|
||||
|
||||
Notwithstanding anything to the contrary, Zitadel's notification of or response to a Security Incident under this section will not be construed as an acknowledgment by Zitadel of any fault or liability with respect to such Security Incident.
|
||||
|
||||
### Deletion or destruction after termination
|
||||
|
||||
Upon termination or expiry of the Agreement, Zitadel shall (at the Customer’s election) destroy or return to the Customer all Customer Data (including all copies of the Customer Data) in its possession or control (including any Customer Data subcontracted to a third party for processing).
|
||||
This requirement shall not apply to the extent that Zitadel is required by any applicable law to retain some or all Customer Data, in which case Zitadel shall isolate and protect the Customer Data from any further processing except to the extent required by such law until deletion is possible.
|
||||
|
||||
### Customer's information and audit rights
|
||||
|
||||
To the extent required under Applicable Data Protection Law and on written request from the Customer, Zitadel shall provide written responses (which may include audit report summaries/extracts) to all reasonable requests for information made by the Customer related to its processing of Customer Personal Data as necessary to confirm Zitadel's compliance with this DPA.
|
||||
The Customer shall not exercise this right more than once in any twelve (12)-month rolling period, except (i) if and when required by instruction of a competent data protection or other regulatory authority; or (ii) if Zitadel has experienced a Security Incident where Customer was directly impacted.
|
||||
|
||||
Nothing in this section shall be construed to require Zitadel to document or provide: (i) trade secrets or any proprietary information; (ii) any information that would violate Zitadel’s confidentiality obligations, contractual obligations, or applicable law; or (iii) any information, the disclosure of which could threaten, compromise, or otherwise put at risk the security, confidentiality, or integrity of Zitadel’s infrastructure, networks, systems, algorithms or data.
|
||||
|
||||
### Service Optimization
|
||||
|
||||
Where permitted by Applicable Data Protection Law, Zitadel may process Customer Data: (i) for its internal uses to build or improve the quality of its services; (ii) to detect Security Incidents; and (iii) to protect against fraudulent or illegal activity.
|
||||
|
||||
Zitadel may: (i) compile aggregated and/or de-identified information in connection with the provision of the Services, provided that such information cannot reasonably be used to identify Customer or any data subject to whom Customer Personal Data relates (“Aggregated and/or De-Identified Data”); and (ii) use such Aggregated and/or De-Identified Data for its lawful business purposes in accordance with Applicable Data Protection Law.
|
||||
|
||||
### Data Transfers
|
||||
|
||||
Where either Party intends to transfer Personal Data cross-border and Applicable Data Protection Law requires certain measures to be implemented prior to such transfer, each Party agrees to implement such measures to ensure compliance with Applicable Data Protection Law.
|
||||
|
||||
To the extent that the transfer of Personal Data from Customer to Zitadel involves a transfer of Personal Data outside the European Economic Area (EEA), Switzerland, or the United Kingdom to a jurisdiction which is not subject to an adequacy determination by the European Commission, United Kingdom or Swiss authorities (as applicable) that covers such transfer, then the SCCs are hereby incorporated by reference and form an integral part of the DPA.
|
||||
|
||||
#### EEA Transfers
|
||||
|
||||
To the extent that Customer Personal Data is subject to the GDPR, and the transfer would be a Restricted Transfer, the SCCs apply as follows:
|
||||
|
||||
1) the Customer is the ‘data exporter’ and Zitadel is the ‘data importer’;
|
||||
2) the Module Two terms (Transfer controller to processor) apply;
|
||||
3) in Clause 7, the optional docking clause does not apply;
|
||||
4) in Clause 9, Option 2 (General Authorization) applies and the time period for prior notice of sub-processor changes is set out in this DPA;
|
||||
5) in Clause 11, the optional language does not apply;
|
||||
6) in Clause 17, Option 1 applies, and the SCCs are governed by German law;
|
||||
7) in Clause 18(b), disputes will be resolved before the courts of Hamburg in Germany;
|
||||
8) in Annex I, the details of the parties and the transfer are set out in the Agreement;
|
||||
9) in Clause 13(a) and Annex I, the Hamburg data protection authority will act as competent supervisory authority;
|
||||
10) in Annex II, the description of the technical and organizational security measures is set out in Annex 2 of this DPA or, if not set out therein, the applicable statement of work; and
|
||||
11) in Annex III, the list of sub-processors is set out at the address [https://zitadel.com/trust](https://zitadel.com/trust) or, if not set out therein, applicable statement of work.
|
||||
|
||||
#### Swiss Transfers
|
||||
|
||||
To the extent that Customer Personal Data is subject to Swiss law, and the transfer would be a Restricted Transfer, the SCCs apply as set out above with the following modifications:
|
||||
|
||||
1) references to ‘Regulation (EU) 2016/679’ are interpreted as references to the Swiss FADP or any successor thereof;
|
||||
2) references to specific articles of ‘Regulation (EU) 2016/679’ are replaced with the equivalent article or section of the Swiss FADP,
|
||||
3) references to ‘EU’, ‘Union’ and ‘Member State’ are replaced with ‘Switzerland’,
|
||||
4) Clause 13(a) and Part C of Annex 2 is not used and the ‘competent supervisory authority’ is the Swiss Federal Data Protection Information Commissioner (“**FDPIC**”) or, if the transfer is subject to both the Swiss FADP and the GDPR, the FDPIC (insofar as the transfer is governed by the Swiss FADP) or the DPC (insofar as the transfer is governed by the GDPR),
|
||||
5) references to the ‘competent supervisory authority’ and ‘competent courts’ are replaced with the FDPIC and ‘competent Swiss courts’,
|
||||
6) in Clause 17, the SCCs are governed by the laws of Switzerland,
|
||||
7) in Clause 18(b), disputes will be resolved before the competent Swiss courts, and
|
||||
8) the SCCs also protect the data of legal entities until entry into force of the revised Swiss FADP.
|
||||
|
||||
#### UK Transfers
|
||||
|
||||
To the extent that Customer Personal Data is subject to Applicable Data Protection Law of the United Kingdom, and the transfer would be a Restricted Transfer, the SCCs as set out above shall apply as amended by Part 2 of the UK Addendum, and Part 1 of the UK Addendum is deemed completed as follows:
|
||||
|
||||
1) in Table 1, the details of the parties are set out in the Agreement or, if not set out therein, the applicable statement of work;
|
||||
2) in Table 2, the selected modules and clauses are set out in Section 6.3 of this DPA;
|
||||
3) in Table 3, the appendix information is set out in the annexes to this DPA or, if not set out therein, the applicable statement of work; and
|
||||
4) in Table 4, the ‘Exporter’ is selected.
|
||||
|
||||
#### Alternative Transfer Mechanism
|
||||
|
||||
In the event that a court of competent jurisdiction or supervisory authority orders (for whatever reason) that the measures described in this DPA cannot be relied on to lawfully transfer Customer Personal Data, or Zitadel adopts an alternative data transfer mechanism to the mechanisms described in this DPA, including any new version of or successor to the standard contractual clauses (“Alternative Transfer Mechanism”), the Customer agrees to fully co-operate with Zitadel to agree an amendment to this DPA and/or execute such other documents and take such other actions as may be necessary to remedy such non-compliance or give legal effect to such Alternative Transfer Mechanism.
|
||||
|
||||
### Additional Provisions under US Data Protection Laws
|
||||
|
||||
The Parties agree that all Customer Personal Data that is subject to US Data Protection Laws (including the CCPA) is disclosed to Zitadel by the Customer for the Permitted Purpose and its use or sharing by the Customer with Zitadel is necessary to perform such Permitted Purpose.
|
||||
|
||||
Zitadel agrees that it will not:
|
||||
|
||||
1. sell or share any Customer Personal Data to a third party for any purpose other than than for the Permitted Purpose;
|
||||
2. retain, use, or disclose any Customer Personal Data (i) for any purpose other than for the Permitted Purpose, including for any commercial purpose, or (ii) outside of the direct business relationship between the Parties, except as necessary to perform the Permitted Purpose or as otherwise permitted by US Data Protection Laws; or
|
||||
3. combine Customer Personal Data received from or on behalf of Customer with Personal Data received from or on behalf of any third party or collected from Zitadel’s own interaction with individuals or data subjects, except to perform a Permitted Purpose in accordance with the CCPA, the Agreement and this DPA.
|
||||
|
||||
The Parties acknowledge that the Customer Personal Data that Customer discloses to Zitadel is provided only for the limited and specified purposes set forth as the Permitted Purpose in the Agreement and this DPA.
|
||||
|
||||
Zitadel shall provide the same level of protection to Customer Personal Data as required by the CCPA and will: (i) assist the Customer in responding to any request from a data subject to exercise rights under US Data Protection Laws; and (ii) immediately notify the Customer if it is not able to meet the requirements under the CCPA.
|
||||
|
||||
The Customer may take such reasonable and appropriate steps as may be necessary (a) to ensure that the Customer Personal Data collected is used in a manner consistent with the business’s obligations under the CCPA; and (b) to stop and remediate any unauthorized use of Customer Personal Data, and (b) to ensure that Customer Personal Data is used in a manner consistent with the CCPA.
|
||||
|
||||
### Miscellaneous
|
||||
|
||||
This DPA shall be governed by and construed in accordance with the governing law and jurisdiction provisions set out in the Agreement, unless required otherwise by Applicable Data Protection Law.
|
||||
|
||||
Any liability owed by one party to the other under this DPA shall be subject to the limitations of liability set forth in the Agreement.
|
||||
|
||||
This DPA shall terminate upon the earlier of (i) the termination or expiry of all Agreement under which Customer Data may be processed, or (ii) the written agreement of the Parties.
|
||||
|
||||
Any notices shall be delivered to a Party in accordance with the notice provisions of the Agreement, unless otherwise specified hereunder.
|
||||
|
||||
## Annex 1: Description of Processing Activities / Transfer
|
||||
|
||||
### List of Parties
|
||||
|
||||
| Data Exporter | Data Importer |
|
||||
| :---- | :---- |
|
||||
| Name: The Party identified as the Customer in the Agreement. | Name: The Party identified as Zitadel in the Agreement. |
|
||||
| Address: As identified in the Agreement. | Address: As identified in the Agreement. |
|
||||
| Contact Person's Name, position and contact details: As identified in the Agreement. | Contact Person's Name, position and contact details: As identified in the Agreement. |
|
||||
| Activities relevant to the transfer: See below | Activities relevant to the transfer: See below |
|
||||
| Role: Controller | Role: Processor |
|
||||
|
||||
### Description of processing / transfer
|
||||
|
||||
| | Description |
|
||||
| :---- | :---- |
|
||||
| **Categories of data subjects:** | As described in the section "Processing of Personal Data" of the DPA |
|
||||
| **Categories of personal data:** | As described in the section "Processing of Personal Data" of the DPA |
|
||||
| **Sensitive data:** | None. |
|
||||
| **If sensitive data, the applied restrictions or safeguards** | N/A |
|
||||
| **Frequency of the transfer:** | Continuous |
|
||||
| **Nature and subject matter of processing:** | The Services described in the Agreement. |
|
||||
| **Purpose(s) of the data transfer and further processing:** | As set forth in the Agreement. |
|
||||
| **Retention period (or, if not possible to determine, the criteria used to determine that period):** | The personal data may be retained until termination or expiry of the DPA. |
|
||||
|
||||
### Competent supervisory authority
|
||||
|
||||
The competent supervisory authority in connection with Customer Personal Data protected by the GDPR, is the Hamburg data protection authority.
|
||||
If this is not possible, then as otherwise agreed by the parties consistent with the conditions set forth in Clause 13.
|
||||
|
||||
In connection with Customer Personal Data that is protected by UK-GDPR, the competent supervisory authority is the Information Commissioners Office (the "ICO").
|
||||
|
||||
## Annex 2: Technical and organizational measures
|
||||
|
||||
Zitadel has implemented an information security program, that is designed to protect the confidentiality, integrity and availability of Customer Data. Zitadel's information security program includes the following organizational and technical security measures to ensure a level of protection of the Personal Data processed that is appropriate to the risk:
|
||||
|
||||
### Pseudonymization / Encryption
|
||||
|
||||
The following measures for pseudonymization and encryption exist:
|
||||
|
||||
1. All communication is encrypted with TLS >1.2 with PFS
|
||||
2. Critical data is exclusively stored in encrypted form
|
||||
3. Storage media that store customer data are always encrypted
|
||||
4. Passwords are irreversibly stored with a hash function
|
||||
5. Data for web analytics are pseudonymized and do not contain any personal data
|
||||
|
||||
### Ensuring certain properties of the systems and services
|
||||
|
||||
#### Confidentiality
|
||||
|
||||
The following confidentiality measures exist:
|
||||
|
||||
1. Information security policies
|
||||
2. Authentication policies
|
||||
3. Vendor management policies
|
||||
4. Technical measures in this annex
|
||||
|
||||
#### Integrity
|
||||
|
||||
The following integrity measures exist:
|
||||
|
||||
1. Code and container images are automatically checked for vulnerabilities
|
||||
2. An automated system is used to keep dependencies up to date
|
||||
3. Secrets are automatically rotated whenever possible and are short-lived (for example, signing keys)
|
||||
4. Changes to code or infrastructure require mandatory review by at least one other employee
|
||||
|
||||
#### Availability
|
||||
|
||||
The following measures of availability exist:
|
||||
|
||||
1. Operation of the systems in combination with a CDN/DDoS mitigation service
|
||||
2. High availability operation
|
||||
3. Geo-redundant operation over at least two data centers
|
||||
|
||||
#### Load capacity
|
||||
|
||||
The following measures of availability exist:
|
||||
|
||||
1. Automatic scaling of resources
|
||||
2. Monitoring, logging, tracing and alerting
|
||||
|
||||
#### Restoring availability and access
|
||||
|
||||
The following measures exist to restore availability and access:
|
||||
|
||||
1. Implementation of a backup concept
|
||||
2. Emergency plan
|
||||
3. Testing of the emergency plan
|
||||
|
||||
#### Regular review, assessment and evaluation of effectiveness
|
||||
|
||||
The following measures exist for regular review, assessment and evaluation of effectiveness:
|
||||
|
||||
1. At least annual audit and evaluation of processes within the framework of an information security management system
|
||||
2. Responsible Disclosure and Bug Bounty policies
|
||||
3. External audit of system security ("penetration testing")
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Legal Agreements"
|
||||
description: "This section contains important agreements, policies and appendices relevant for users of our websites and services. All documents will be provided in English language."
|
||||
---
|
||||
|
||||
{/* THIS FILE IS AUTO-GENERATED FROM SIDEBAR-DATA.
|
||||
ANY MANUAL CHANGES WILL BE OVERWRITTEN.
|
||||
*/}
|
||||
|
||||
import { Card, Cards } from 'fumadocs-ui/components/card';
|
||||
import { FileText, Folder, Link as LinkIcon } from 'lucide-react';
|
||||
|
||||
<Cards>
|
||||
<Card title="Terms Of Service" href="/legal/terms-of-service" icon={<FileText />} />
|
||||
<Card title="Data Processing Agreement" href="/legal/data-processing-agreement" icon={<FileText />} />
|
||||
<Card title="Subprocessors" href="/legal/subprocessors" icon={<FileText />} />
|
||||
<Card title="Annex Support Services" href="/legal/annex-support-services" icon={<FileText />} />
|
||||
<Card title="Service Description" href="/legal/service-description" icon={<Folder />} />
|
||||
<Card title="Policies" href="/legal/policies" icon={<Folder />} />
|
||||
</Cards>
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: Acceptable Use Policy
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on November 15, 2023
|
||||
|
||||
This policy is an annex to the [Terms of Service](../terms-of-service) and clarifies your obligations while using our Services.
|
||||
|
||||
## Use
|
||||
|
||||
You will ensure that the use of our Subscription Services and Website by yourself, your customers, or third parties comply with all applicable legislation.
|
||||
|
||||
You may not:
|
||||
|
||||
1. Use Subscription Services or Website for phishing, social engineering, or committing fraud or any other illegal, malicious or fraudulent activity
|
||||
2. Attempt to interfere with the functionality or proper working of the Subscription Services or Website
|
||||
3. Upload any materials to the Subscription Services or Website in violation of any third-party privacy or data protection rights, to store and transmit any kind of malware
|
||||
4. Attempt to probe, scan, penetrate or test the vulnerability of our Subscription Services, Website, systems, or network or try to circumvent our authentication. Any penetration testing must not be conducted without prior written consent by CAOS.
|
||||
5. Use any organization or domain name that includes or is confusingly similar with trademarks, or any third parties. CAOS may determine any violation at its sole discretion
|
||||
6. Collecting any information about our Customers, our Customers users, or our users without the consent of the person identified. This includes phishing, social engineering, scamming, spidering or harvesting information from any Subscription Service or Website
|
||||
7. Use Actions to run workloads that are unrelated to the Subscription Services and Websites, such as excessively calling unrelated third party services, crypto mining, intentionally long running code
|
||||
|
||||
## Fair use principles
|
||||
|
||||
The “fair use” principle applies to the use of our services.
|
||||
We optimize our infrastructure in such a way that sufficient capacity is available to you even during short-term increased demand (“peaks”) and implement mitigation measures such as our [Rate Limit Policy](./rate-limit-policy).
|
||||
You are nonetheless required to adhere to reasonable use of our resources in order to avoid negatively affecting the services for other customers.
|
||||
|
||||
You agree that we may delete any data on our systems or networks, if CAOS believes that this data may corrupt our systems, interfere or may compromise other customers' data.
|
||||
|
||||
You agree to adhere to the following fair use limits:
|
||||
|
||||
- Usage limits that were agreed by both parties in advance for the duration of the term
|
||||
|
||||
## Violations of this policy
|
||||
|
||||
We may suspend or terminate your usage of our Services for any violation of this Acceptable Use Policy.
|
||||
You will not be entitled to any Financial Credit or compensation for any interruptions caused by violation of this policy.
|
||||
@@ -0,0 +1,66 @@
|
||||
---
|
||||
title: ZITADEL Account Lockout Policy
|
||||
sidebar_label: Account Lockout Policy
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on June 25, 2025
|
||||
|
||||
This policy is an annex to the [Terms of Service](../terms-of-service) and outlines your responsibilities, as well as our procedures, for handling situations where you are unable to access your ZITADEL Cloud services or data.
|
||||
|
||||
It applies specifically to cases where **ZITADEL** must restore your access to services that are otherwise operational, and does **not** cover service outages or unavailability.
|
||||
|
||||
## Why do we have this policy?
|
||||
|
||||
Users may lose access to ZITADEL services due to lost credentials or misconfiguration.
|
||||
|
||||
In some cases, it may not be possible to recover access through self-service options—for example, losing access to 2FA credentials or being unable to reverse a misconfiguration. These situations may require support from our team to help you regain access to your data.
|
||||
|
||||
To assist with such requests, we will require specific information and may request additional details throughout the process.
|
||||
|
||||
**ZITADEL reserves the right to decline any access recovery request without providing a reason if the required information cannot be verified or provided.**
|
||||
|
||||
## Scope of This Policy
|
||||
|
||||
This policy applies to the following situations:
|
||||
|
||||
- Loss of access to your **ZITADEL Cloud Admin Account** (customer portal)
|
||||
- Inability to access **Instance Manager accounts** for a specific instance
|
||||
- Need to **undo configuration changes** that caused a lockout (e.g., a misconfigured Action)
|
||||
|
||||
## Out of Scope
|
||||
|
||||
The following types of access recovery requests are **not** covered by this policy:
|
||||
|
||||
- Situations where you can request access from another **Admin** or **Instance Manager**
|
||||
- Requests made by **end-users** who should instead contact their Admin or Manager
|
||||
- Issues related to **self-hosted ZITADEL instances**
|
||||
- **Free accounts/Instances**
|
||||
|
||||
## Process
|
||||
|
||||
Before submitting a request to restore access to your account, please ensure that you are unable to regain access through your existing **Manager** or **Admin**, or by contacting another **Manager/Admin** within your organization.
|
||||
|
||||
### ZITADEL Cloud account (Customer Portal)
|
||||
|
||||
Please visit the [support page in the customer portal](https://zitadel.com/admin/support):
|
||||
|
||||
- State clearly in the subject line that this is related to an account lockout for a ZITADEL Cloud account
|
||||
- The sender's email address must match the verified email address of the account owner
|
||||
- State the reason why you're not able to recover the account yourself
|
||||
|
||||
Please allow us time to validate your request.
|
||||
Our support team will follow up with additional verification steps if needed.
|
||||
|
||||
### Instance Manager access recovery
|
||||
|
||||
If you need to recover a Manager account to an instance, please make sure you can't recover the account via another user or service user with Manager permissions.
|
||||
|
||||
Please visit the [support page in the customer portal](https://zitadel.com/admin/support):
|
||||
|
||||
- State clearly in the subject line that this is related to an account lockout **for** the affected instance
|
||||
- The sender's email address must match the verified email address of the affected instance manager
|
||||
- State the reason why you're not able to recover the account yourself
|
||||
|
||||
Please allow us time to validate your request.
|
||||
Our support team will follow up with additional verification steps if needed.
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Use of brands and trademarks
|
||||
sidebar_label: Brand and Trademark Policy
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on November 15, 2023
|
||||
|
||||
This policy is an annex to the [Terms of Service](../terms-of-service) that clarifies how you may use our brands and trademarks under fair use.
|
||||
|
||||
We reserve the right to object to any use or misuse of brands and trademarks in any jurisdiction worldwide.
|
||||
If you are unsure about the use of our logos, please contact [[email protected]](mailto:[email protected]).
|
||||
|
||||
## Conditions
|
||||
|
||||
ZITADEL's brand assets and trademarks are proprietary assets owned exclusively by us.
|
||||
|
||||
No third party may claim ownership over brand assets and trademarks or brands and trademarks that are confusingly similar. This extends to all trademarks in image, textform, combined image and text, visual, and audio.
|
||||
|
||||
You must not include our brands and trademarks in the name of your product or service wether commercial or non-commercial, this includes, but is not limited to, websites, blogs, informational, advertising, and personal home pages, applications.
|
||||
|
||||
## Spelling
|
||||
|
||||
When referring to ZITADEL, please make sure it is spelled correctly and written in uppercase letters.
|
||||
|
||||
## Logo usage
|
||||
|
||||
When embedding our logo, always use the official version.
|
||||
You must not alter the logo in any way, and avoid overlapping with other images.
|
||||
|
||||
To ensure the logo is used as intended, we provide specific examples below and reserve the right to object to any use or misuse.
|
||||
|
||||
### Fair use
|
||||
|
||||
- Use in architecture diagrams without implying affiliation or partnership
|
||||
- Editorial and informational purposes such as blog posts or news articles
|
||||
- Linking back to our [website](https://zitadel.com), official [repositories](https://github.com/zitadel), or [documentation](/docs)
|
||||
- Indicating that the software is available for use or installation without implying any affiliation or endorsement
|
||||
|
||||
### Not acceptable
|
||||
|
||||
- Using our brands and trademarks, including our logo, or any variations for your own product or services
|
||||
- Modification of our brands and trademarks
|
||||
- Integration of our brands and trademarks into your own brands and trademarks
|
||||
- Suggesting affiliation, endorsement, or partnership without our consent
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: Feature Development Policy
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on September 25, 2023
|
||||
|
||||
This policy clarifies how we handle requests for feature prioritization and development. This policy is applicable to situations where a user wants to prioritize certain features or development for our products and services.
|
||||
|
||||
## Why to do we have this policy?
|
||||
|
||||
Shaping of the roadmap and prioritization of features is done by ZITADEL.
|
||||
You are welcome to give feedback on the [roadmap](https://zitadel.com/roadmap) and we are happy to [accept upstream pull requests](https://github.com/zitadel/zitadel/CONTRIBUTE.md) for ZITADEL.
|
||||
|
||||
In case you can't contribute directly to the open source version of ZITADEL, but want to accelerate development, we may develop the feature on request, under the conditions laid out in this policy.
|
||||
|
||||
Features that will be part of the publicly available ZITADEL [repositories](https://github.com/zitadel/), ZITADEL Cloud, or optional components to our products that might be available only under a commercial license.
|
||||
|
||||
### Conditions
|
||||
|
||||
All intellectual property and ownership of the changes remain with ZITADEL.
|
||||
Changes may be published under an Open Source or commercial license.
|
||||
ZITADEL will guarantee maintenance and warranties according to the license and terms of services under which the changes are being released.
|
||||
|
||||
## Process
|
||||
|
||||
1. [Contact us](https://zitadel.com/contact) about your feature request
|
||||
2. We will share the scope of the feature and acceptance criteria with you
|
||||
3. As soon as you confirm the scope we will provide you with a quote containing scope, timeline, estimated effort, and price for the feature development
|
||||
4. When you accept 50% of the cost is due
|
||||
5. We inform you when the feature is available and provide you with instructions on how to conduct the acceptance tests
|
||||
6. You will need to report any issues within 14 days, if not otherwise agreed (see below)
|
||||
7. On completion (see below) the remaining cost is due
|
||||
|
||||
### Development cost
|
||||
|
||||
We will estimate the overall effort and development cost of the changes.
|
||||
For features that are not on the roadmap or feature requests where a defined deadline for general availability of the feature must be met, we take 100% of the development cost as base.
|
||||
For prioritization of a features that are already on the roadmap, we take 50% of the development cost as base.
|
||||
|
||||
We will provide you with a quote for fixed price of the overall effort and ZITADEL will carry any overages.
|
||||
|
||||
Cost, scope and timeline will be agreed in a formal quote.
|
||||
|
||||
### Payment
|
||||
|
||||
50% of the cost will be due on accepting the quote.
|
||||
We will send you an invoice and expect payment within the given deadline.
|
||||
|
||||
50% on completion of the feature development.
|
||||
Completion means that the agreed scope is available according to the agreed acceptance criteria.
|
||||
You had 14 days to verify the acceptance criteria and report any issues.
|
||||
A feature is considered complete, if the outstanding issues are being solved, or a timeline for resolution of the issues has been mutually agreed, or if we haven't got any response within the last 14 days.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
title: "Policies"
|
||||
description: "Policies and guidelines in addition to our terms of services."
|
||||
---
|
||||
|
||||
{/* THIS FILE IS AUTO-GENERATED FROM SIDEBAR-DATA.
|
||||
ANY MANUAL CHANGES WILL BE OVERWRITTEN.
|
||||
*/}
|
||||
|
||||
import { Card, Cards } from 'fumadocs-ui/components/card';
|
||||
import { FileText, Folder, Link as LinkIcon } from 'lucide-react';
|
||||
|
||||
<Cards>
|
||||
<Card title="Policies" href="/legal/policies" icon={<Folder />} />
|
||||
</Cards>
|
||||
@@ -0,0 +1,332 @@
|
||||
---
|
||||
title: Privacy Policy
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
import { PiiTable } from "@/components/pii_table";
|
||||
|
||||
Last updated on October 23, 2025.
|
||||
|
||||
This privacy policy describes how Zitadel, Inc. and its wholly owned subsidiaries and affiliates (collectively, "**Zitadel**", "**CAOS**", "**we**" or "**us**") collect, use, disclose and otherwise process your personal data in connection with the management of our business and our relationships with customers, visitors and event attendees.
|
||||
|
||||
This privacy policy explains your rights and choices related to the personal data we collect when:
|
||||
|
||||
* You interact with our websites, including zitadel.com, zitadel.cloud and zitadel.ch as well any other websites that we operate and that link to this privacy policy (our "**Sites**")
|
||||
* You visit, interact with, or use any of our offices, events, sales, marketing or other activities; and
|
||||
* You use our platform, including Zitadel and our software, mobile application, and other products and services (the "**Services**").
|
||||
|
||||
This privacy policy does not cover:
|
||||
|
||||
* **Organizational Use**. When you use our Services on behalf of an organization (your employer), your use is administered and provisioned by your organization under its policies regarding the use and protection of personal data. If you have questions about how your data is being accessed or used by your organization, please refer to your organization's privacy policy and direct your inquiries to your organization's system administrator.
|
||||
* **Third Parties**. Our Sites include links to websites and/or applications operated and maintained by third parties (e.g. GitHub, LinkedIn, etc.). This privacy policy does not apply to any products, services, websites, or content that are offered by third parties and/or have their own privacy policy.
|
||||
|
||||
If any inconsistencies arise between this privacy policy and the otherwise applicable contractual terms, framework agreement, or general terms of service, the provisions of this privacy policy shall prevail (where applicable). This privacy policy covers both existing personal data and personal data which may be collected from you in the future.
|
||||
|
||||
Zitadel determines the purposes for and means of the processing (i.e., we are the data controller) of your personal data as described in this privacy policy, unless expressly specified otherwise. The responsible party for the data processing described in this privacy policy and contact for questions and issues regarding data protection is:
|
||||
|
||||
**Zitadel, Inc.**
|
||||
Data Protection Officer
|
||||
1 Embarcadero Center
|
||||
Suite 1200
|
||||
San Francisco, CA 94111-4164
|
||||
United States of America
|
||||
[[email protected]](mailto:[email protected])
|
||||
|
||||
**CAOS AG (Affiliate of Zitadel, Inc.)**
|
||||
Data Protection Officer
|
||||
Lerchenfeldstrasse 3
|
||||
9014 St. Gallen
|
||||
Switzerland
|
||||
[[email protected]](mailto:[email protected])
|
||||
|
||||
Our representative in the EU is
|
||||
|
||||
**VGS Datenschutzpartner GmbH**
|
||||
Am Kaiserkai 69
|
||||
20457 Hamburg
|
||||
Germany
|
||||
[[email protected]](mailto:[email protected])
|
||||
|
||||
## General notes
|
||||
|
||||
Based on Article 13 of the Swiss Federal Constitution and the data protection provisions of the Swiss Confederation (Data Protection Act, DSG), every person has the right to protection of their privacy as well as protection against misuse of their personal data. The operators of these websites and services take the protection of your personal data very seriously. We treat your personal data confidentially and in accordance with the legal data protection regulations as well as this data protection declaration.
|
||||
|
||||
In cooperation with our suppliers, we make every effort to protect the databases and any of our users data as well as possible against unauthorized access, loss, misuse or falsification. We point out that data transmission over the internet in general may result in security risks. A complete protection of the data against access by third parties is not possible.
|
||||
|
||||
This website uses TLS encryption for security reasons and to protect the transmission of confidential content, such as requests that you send to us as the website operator. You can recognize an encrypted connection by the fact that the address line of the browser changes from "http://" to "https://".
|
||||
|
||||
## Data Privacy Framework (DPF) Adherence Statement
|
||||
|
||||
Zitadel complies with the EU-U.S. Data Privacy Framework (EU-U.S. DPF), the UK Extension to the EU-U.S. DPF, and the Swiss-U.S. Data Privacy Framework (Swiss-U.S. DPF) as set forth by the U.S. Department of Commerce.
|
||||
Zitadel has certified to the U.S. Department of Commerce that it adheres to the EU-U.S. Data Privacy Framework Principles (EU-U.S. DPF Principles) with regard to the processing of personal data received from the European Union in reliance on the EU-U.S. DPF and from the United Kingdom (and Gibraltar) in reliance on the UK Extension to the EU-U.S. DPF.
|
||||
Zitadel has also certified to the U.S. Department of Commerce that it adheres to the Swiss-U.S.
|
||||
Data Privacy Framework Principles (Swiss-U.S. DPF Principles) with regard to the processing of personal data received from Switzerland in reliance on the Swiss-U.S. DPF.
|
||||
If there is any conflict between the terms in this privacy policy and the EU-U.S. DPF Principles and/or the Swiss-U.S. DPF Principles, the Principles shall govern.
|
||||
To learn more about the Data Privacy Framework (DPF) program, and to view our certification, please visit [https://www.dataprivacyframework.gov/](https://www.dataprivacyframework.gov/)
|
||||
|
||||
### Transfers of Employee Data
|
||||
|
||||
Zitadel also commits to apply the DPF Principles to personal data of its employees collected in the context of their employment relationship with zitadel, where such data is transferred from the EU, UK, or Switzerland to the United States. In this regard, Zitadel commits to cooperate with the EU data protection authorities (DPAs), the UK Information Commissioner's Office (ICO) (and the Gibraltar Regulatory Authority (GRA)), and the Swiss Federal Data Protection and Information Commissioner (FDPIC) and comply with the advice given by these authorities with regard to such data.
|
||||
|
||||
## Processing of personal data, legal basis, storage period
|
||||
|
||||
**Personal data** is any information that relates to an identified or identifiable person. A **data subject** is a person about whom personal data is processed. Processing includes any handling of personal data, regardless of the means and procedures used, in particular the storage, disclosure, acquisition, deletion, storage, modification, destruction and use of personal data.
|
||||
|
||||
We process personal data in accordance with Swiss data protection law. In addition, we process - to the extent and insofar as the EU Data Protection Regulation is applicable - personal data in accordance with the following legal bases within the meaning of Art. 6 (1) DSGVO:
|
||||
|
||||
* Insofar as we obtain the consent of the data subject for processing operations, Art. 6 (1) a) DSGVO serves as the legal basis.
|
||||
* When processing personal data for the fulfillment of a contract with the data subject as well as for the implementation of corresponding pre-contractual measures, Art. 6 para. 1 lit. b DSGVO serves as the legal basis.
|
||||
* To the extent that processing of personal data is necessary to comply with a legal obligation to which we are subject under any applicable law of the EU or under any applicable law of a country in which the GDPR applies in whole or in part, Art. 6 para. 1 lit. c GDPR serves as the legal basis.
|
||||
* For the processing of personal data in order to protect vital interests of the data subject or another natural person, Art. 6 para. 1 lit. d DSGVO serves as the legal basis.
|
||||
* If personal data is processed in order to protect the legitimate interests of us or of third parties and if the fundamental freedoms and rights and interests of the data subject do not override our interests and the interests of third parties, Article 6 (1) (f) of the GDPR serves as the legal basis. Legitimate interests are in particular our business interest in being able to provide our website and our products, information security, the enforcement of our own legal claims and compliance with Swiss law.
|
||||
|
||||
We will retain personal data for the period of time necessary for the particular purpose for which it was collected and where we have an ongoing legitimate business need to do so (for example to comply with applicable legal, tax or accounting requirements). Subsequently, they are either deleted or made anonymous, unless we need them for a longer period of time in exceptional cases, e.g. due to legal storage and documentation obligations or our legitimate interests, such as the protection of rights to which we are entitled or the defense of claims.
|
||||
|
||||
### Processing of personal data when using the website, contact forms and in connection with newsletters
|
||||
|
||||
Our websites can generally be visited without registration. Each time one of our website is requested, data such as content of the requested page, name of the requested file, IP address, date and time are automatically stored in log files on the server.
|
||||
|
||||
This data is processed to enable correct delivery and functioning of the website. In addition, we use the data to optimize the website and to ensure the security of our systems.
|
||||
|
||||
Personal data, in particular name, address or e-mail address are collected as far as possible on a voluntary basis, for example when you contact us via a contact form or by e-mail. Without your consent, the data will not be passed on to third parties, unless otherwise stated in this privacy policy.
|
||||
|
||||
If you send us inquiries via contact form, your data from the form, including any data you provided, will be stored by us for the purpose of processing the inquiry and in case of follow-up questions. We do not pass on this data without your consent, except insofar as this is shown in this privacy policy.
|
||||
|
||||
If you would like to receive newsletters offered on our Sites, we require an e-mail address from you as well as information that allows us to verify that you are the owner of the specified e-mail address and agree to receive the newsletter. Further data will not be collected. We use this data exclusively for sending the requested information and do not pass it on to third parties, except as described in this privacy policy.
|
||||
|
||||
You can revoke your consent to the storage of the data, the e-mail address and their use for sending the newsletter at any time, for example via the "unsubscribe link" in the newsletter.
|
||||
|
||||
### Processing of personal data when applying for a job with us
|
||||
|
||||
Our Sites can generally be visited without registration. If you apply for a job with us, we may collect and process according to the [Privacy policy for the Zitadel employer branding and recruitment](https://jobs.zitadel.com/privacy-policy). You may request and delete your data with the links on our [data & privacy page](https://jobs.zitadel.com/data-privacy).
|
||||
|
||||
### Processing of personal data in connection with the use of our Services
|
||||
|
||||
The use of our services is generally only possible with registration. During registration and in the course of using the services, we collect and process various personal data.
|
||||
|
||||
In particular, the following personal data are part of the processing:
|
||||
|
||||
<PiiTable />
|
||||
|
||||
Unless otherwise mentioned, the nature and purpose of the processing is as follows:
|
||||
|
||||
The data is uploaded by customers in our Services or collected by us based on requests from users. The personal data is processed by us exclusively for the provision of the requested Services or the use of the agreed Services.
|
||||
|
||||
The fulfillment of the contract includes in particular, but is not limited to, the processing of personal data for the purpose of:
|
||||
|
||||
* Authentication and authorization of users
|
||||
* Storage and processing of user actions in the audit trail
|
||||
* Processing of personal data and login information
|
||||
* Verification of communication means
|
||||
* Communication regarding service interruptions or service changes
|
||||
|
||||
## Disclosure to third parties
|
||||
|
||||
### Third party sub-processors
|
||||
|
||||
We use third-party services to provide the website and our offers. An up-to-date list of all the providers we use and their areas of activity can be found on our [Trust Center](https://zitadel.com/trust).
|
||||
|
||||
### External payment providers
|
||||
|
||||
This Site uses external payment service providers through whose platforms users and we can make payment transactions. For example, via [Stripe](https://stripe.com/ch/privacy).
|
||||
|
||||
As an alternative, we offer customers the option to pay by invoice instead of using external payment providers. However, this may require a positive credit check in advance.
|
||||
|
||||
The data processed by the payment service providers includes personal data, such as the name and address, bank data, such as account numbers or credit card numbers, passwords, TANs and checksums, as well as the contract, totals and recipient-related information. The information is necessary to carry out the transactions. However, the data entered is only processed by the payment service providers and stored with them. We as the operator do not receive any information about (bank) account or credit card, but only information to confirm (accept) or reject the payment. Under certain circumstances, the data is transmitted by the payment service providers to credit agencies. The purpose of this transmission is to check the identity and creditworthiness of the payment service provider. In this regard, we refer to the terms and conditions and data protection information of the payment service providers.
|
||||
|
||||
For payment transactions, the terms and conditions and the data protection notices of the respective payment service providers apply, which can be accessed within the respective website or transaction applications. We also refer to these for the purpose of further information and assertion of revocation, information and other rights concerned.
|
||||
|
||||
### Law enforcement
|
||||
|
||||
We disclose personal data to law enforcement agencies, investigative authorities or in legal proceedings to the extent we are required to do so by law or when necessary to protect our rights or the rights of users.
|
||||
|
||||
## Cookies
|
||||
|
||||
Our Sites use cookies. These are small text files that make it possible to store specific information related to the user on the user's terminal device while the user is using the website. Cookies enable us, in particular, to offer a single sign-on procedure, to control the performance of our Services, but also to make our offer more customer-friendly. Cookies remain stored beyond the end of a browser session and can be retrieved when the user visits the site again.
|
||||
|
||||
When you use our Services, we may collect information about your visit, including via cookies, beacons, invisible tags, and similar technologies (collectively "cookies") in your browser and on emails sent to you. This information may include personal data, such as your IP address, web browser, device type, and the web pages that you visit just before or just after you use the Services, as well as information about your interactions with the Services, such as the date and time of your visit, and where you have clicked.
|
||||
|
||||
### Necessary cookies
|
||||
|
||||
Some cookies are strictly necessary to make our Services available to you. We cannot provide you with our Services without this type of cookies.
|
||||
|
||||
Necessary cookies provide basic functionality such as:
|
||||
|
||||
* Session Management
|
||||
* Single Sign-On
|
||||
* Rate Limiting
|
||||
* DDoS Mitigation
|
||||
* Remembering Preferences
|
||||
|
||||
### Analytical cookies
|
||||
|
||||
We use cookies for website analytics purposes in order to operate, maintain, and improve the Services for you.
|
||||
We use third-party providers, mentioned in our [List of Subprocessors](https://trust.zitadel.com/subprocessors), that collect and process certain analytics data on our behalf.
|
||||
These third-party providers helps us understand how you engage with the Services and may also collect information about your use of other websites, apps, and online resources.
|
||||
|
||||
You can opt out by managing your cookie consent through our Services or a third-party tool of your choice.
|
||||
|
||||
If you do not want us to use cookies during your visit, you can disable their use in your browser settings.
|
||||
In this case, certain parts of our Sites (e.g. language selection) may not function or may not function fully.
|
||||
Where required by applicable law, we obtain your consent to use cookies.
|
||||
|
||||
## How we protect personal data
|
||||
|
||||
Personal data is maintained on our servers or those of our service providers, and is accessible by authorized employees, representatives, and agents as necessary for the purposes described in this privacy policy.
|
||||
|
||||
We maintain a range of physical, electronic, and procedural safeguards designed to help protect personal data. While we attempt to protect your personal data in our possession, we cannot guarantee at all times the security of the data as no method of transmission over the internet or security system is perfect.
|
||||
|
||||
If you choose to remain logged in, you should be aware that anyone with access to your device will be able to access your account and we therefore strongly recommend that you take appropriate steps to protect against unauthorized access to, and use, of your account. Please also notify us as soon as possible if you suspect any unauthorized use of your account or password.
|
||||
|
||||
## Rights of data subjects
|
||||
|
||||
Depending on your location and subject to applicable law, you may have the following rights regarding the personal data we process:
|
||||
|
||||
### Right to information
|
||||
|
||||
You have the right to know what personal data we hold and process about you and to access such personal data.
|
||||
|
||||
### Right to rectification
|
||||
|
||||
You have the right to request the correction of inaccurate personal data concerning you.
|
||||
|
||||
### Right to erasure (right to be forgotten)
|
||||
|
||||
You have the right to request the deletion or erasure of the personal data concerning you.
|
||||
|
||||
### Right to restrict processing
|
||||
|
||||
You have the right to request to restrict the processing of your personal data in certain cases.
|
||||
|
||||
### Right to data portability
|
||||
|
||||
You have the right to receive the personal data concerning you in a structured, common and machine-readable format, and to have this data transferred to another data processor if the legal requirements are met.
|
||||
|
||||
### Right to object
|
||||
|
||||
Depending on the circumstances, you have the right to object to the processing of personal data concerning you, insofar as we base the processing of your personal data on a balancing of interests. This is the case if the processing is not necessary, for example, to fulfill a contract or a legal obligation.
|
||||
|
||||
To exercise such an objection, please indicate your reasons why we should not process your personal data as we have done. We will then review the situation and either stop or adjust the data processing or explain our reasons for continuing the processing.
|
||||
|
||||
### Right to revoke consent under data protection law
|
||||
|
||||
Insofar as our processing is based on consent, you have the right to revoke your consent at any time with effect. Withdrawing your consent will not affect the lawfulness of any processing we conducted prior to your withdrawal, nor will it affect processing of your personal data conducted in reliance on lawful processing grounds other than consent.
|
||||
|
||||
### Assertion of rights by the data subjects
|
||||
|
||||
If you wish to exercise your rights, you may do so by contacting the above-mentioned contact person.
|
||||
|
||||
You can opt out of receiving marketing emails from us by following the unsubscribe link in the emails or by emailing us. If you choose to no longer receive marketing information, we may still communicate with you regarding such things as your security updates, product functionality, responses to service requests, or other transactional, non-marketing purposes.
|
||||
|
||||
If you have a concern about how we collect and use personal data, please contact us using the contact details provided at the beginning of this privacy policy. You also have the right to contact your local data protection authority if you prefer, such as:
|
||||
|
||||
* Data protection authorities in the European Economic Area (EEA): [https://edpb.europa.eu/about-edpb/board/members_en](https://edpb.europa.eu/about-edpb/board/members_en);
|
||||
* Swiss data protection authorities: [https://www.edoeb.admin.ch/edoeb/en/home/deredoeb/kontakt.html](https://www.edoeb.admin.ch/edoeb/en/home/deredoeb/kontakt.html);
|
||||
* UK data protection authority: [https://ico.org.uk/global/contact-us/](https://ico.org.uk/global/contact-us/).
|
||||
|
||||
## Recourse, Enforcement, and Liability
|
||||
|
||||
Zitadel, Inc. is committed to addressing any concerns regarding its compliance with the Data Privacy Framework Principles.
|
||||
|
||||
### Commitment to Resolve Complaints
|
||||
|
||||
Zitadel commits to resolving complaints about our collection or use of your DPF-covered personal information. Individuals from the EU, UK, or Switzerland with inquiries or complaints regarding our DPF policy should first contact Zitadel Inc. at the address given in this policy.
|
||||
|
||||
Zitadel will investigate and attempt to resolve DPF-related complaints and disputes within 45 days of receipt.
|
||||
|
||||
### Alternative Dispute Resolution (ADR)
|
||||
|
||||
In compliance with the EU-U.S. DPF and the UK Extension to the EU-U.S. DPF and the Swiss-U.S. DPF, Zitadel Inc. commits to refer unresolved complaints concerning our handling of personal data received in reliance on the EU-U.S. DPF and the UK Extension to the EU-U.S. DPF and the Swiss-U.S. DPF to JAMS Mediation, Arbitration and ADR Services ("JAMS"), an alternative dispute resolution provider based in the United States. If you do not receive timely acknowledgment of your DPF Principles-related complaint from us, or if we have not addressed your DPF Principles-related complaint to your satisfaction, please visit [https://www.jamsadr.com/dpf-dispute-resolution](https://www.jamsadr.com/dpf-dispute-resolution) for more information or to file a complaint. The services of JAMS are provided at no cost to you.
|
||||
|
||||
### Binding Arbitration
|
||||
|
||||
Under certain conditions, more fully described on the [Data Privacy Framework website](https://www.dataprivacyframework.gov/framework-article/ANNEX-I-introduction), you may be entitled to invoke binding arbitration for DPF complaints not resolved by any of the other DPF mechanisms. This option serves as an ultimate recourse for individuals if other avenues for resolution have been exhausted.
|
||||
|
||||
### Liability in Cases of Onward Transfers
|
||||
|
||||
Zitadel is committed to the Data Privacy Framework (DPF) Principles, which includes accountability for personal data that it subsequently transfers to a third party acting as an agent on its behalf. Zitadel remains liable under the DPF Principles if an agent processes such personal data in a manner inconsistent with the Principles, unless Zitadel proves that it is not responsible for the event giving rise to the damage.
|
||||
|
||||
### U.S. Regulatory Oversight
|
||||
|
||||
Zitadel's compliance with the Data Privacy Framework Principles is subject to the investigatory and enforcement powers of the U.S. Federal Trade Commission (FTC). The FTC has jurisdiction over Zitadel's adherence to its DPF commitments. This oversight by a U.S. regulatory authority is a key component of the DPF's enforcement structure.
|
||||
|
||||
### Cooperation with Data Protection Authorities
|
||||
|
||||
Zitadel commits to cooperate with the EU DPAs, the UK ICO (and GRA), and the Swiss FDPIC in the investigation and resolution of complaints brought under the DPF and will comply with the advice given by these authorities with regard to data transferred from the EU, UK, and Switzerland.
|
||||
|
||||
## Additional Information for U.S. Residents
|
||||
|
||||
Categories of personal data we collect and our purposes for collection and use
|
||||
You can find a list of the categories of personal data that we collect in the section above titled "Processing of personal data, legal basis, storage period". In the last 12 months, we collected the following categories of personal data depending on the Services used:
|
||||
|
||||
* Identifiers and account information, such as the username and email address;
|
||||
* Commercial information, such as information about transactions undertaken with us;
|
||||
* Internet or other electronic network activity information, such as information about activity on our Site and Services.
|
||||
* Geolocation information based on the IP address.
|
||||
* Audiovisual information in pictures, audio, or video content that you may choose to submit to us.
|
||||
* Professional or employment-related information or demographic information, but only if you explicitly provide it to us, such as by filling out a survey or by applying for a job with us.
|
||||
* Inferences we make based on other collected data, for purposes such as recommending content and analytics.
|
||||
|
||||
For details regarding the sources from which we obtain personal data, please see the "Processing of personal data, legal basis, storage period" section above.
|
||||
We collect and use personal data for the business or commercial purposes described in the "Processing of personal data, legal basis, storage period" section above.
|
||||
|
||||
### Categories of personal data disclosed and categories of recipients
|
||||
|
||||
We disclose the following categories of personal data for business or commercial purposes to the categories of recipients listed below:
|
||||
|
||||
* We disclose identifiers with businesses, service providers, and third parties, such as analytics providers and social media networks.
|
||||
* We disclose Internet or other network activity with businesses, service providers, and third parties, such as analytics providers and social media networks.
|
||||
* We disclose geolocation information with businesses, service providers, and third parties such as advertising networks, analytics, and social media.
|
||||
* We disclose payment information with businesses and service providers who process payments.
|
||||
* We disclose commercial information with businesses, service providers, and third parties, such as analytics providers and social media networks.
|
||||
* We disclose audiovisual information with businesses and service providers who help administer customer service and fraud or loss prevention services.
|
||||
* We disclose inferences with businesses and service providers who help administer marketing and personalization.
|
||||
|
||||
### Privacy rights
|
||||
|
||||
Right to Opt-Out of Cookies and Sale/Sharing: Although we do not sell personal data for monetary value, our use of cookies and automated technologies may be considered a "sale" / "sharing" in certain states, such as California. Visitors to our US website can opt out of such third parties by clicking the "Manage cookie preferences" link at the bottom of our Site. The categories of personal data disclosed that may be considered a "sale" / "sharing" include identifiers, device information, Internet or other network activity, geolocation data, and commercial data.
|
||||
|
||||
The categories of third parties to whom personal data was disclosed that may be considered "sale"/ "sharing" include data analytics providers and social media networks.
|
||||
|
||||
We do not have actual knowledge that we sell or share the personal data of individuals under 16 years of age.
|
||||
|
||||
If you are a resident of the State of Nevada, Chapter 603A of the Nevada Revised Statutes permits a Nevada resident to opt out of future sales of certain covered information that a website operator has collected or will collect about the resident. Although we do not currently sell covered information, please contact us to submit such a request.
|
||||
|
||||
Right to Limit the Use of Sensitive Personal Information: We only collect sensitive personal information, as defined by applicable privacy laws, for the purposes allowed by law or with your consent. We do not use or disclose sensitive personal information except to provide you the Services or as otherwise permitted by law. We do not collect or process sensitive personal information for the purpose of inferring characteristics.
|
||||
|
||||
Right to Access, Correct, and Delete Personal Data: Depending on your state of residence in the U.S., you may have:
|
||||
(i) the right to request access to and receive details about the personal data we maintain and how we have processed it, including the categories of personal data, the categories of sources from which personal data is collected, the business or commercial purpose for collecting, selling, or sharing personal data, the categories of third parties to whom personal data is disclosed, and the specific pieces of personal data collected;
|
||||
(ii) the right to delete personal data collected, subject to certain exceptions;
|
||||
(iii) the right to correct inaccurate personal data.
|
||||
|
||||
When you make a request, we will verify your identity by asking you to sign into your account or if necessary by requesting additional information from you. You may also make a request using an authorized agent. If you submit a rights request through an authorized agent, we may ask such agent to provide proof that you gave a signed permission to submit the request to exercise privacy rights on your behalf. We may also require you to verify your own identity directly with us or confirm to us that you otherwise provided such agent permission to submit the request. Once you have submitted your request, we will respond within the time frame permitted by the applicable law.
|
||||
|
||||
If you have any questions or concerns, you may reach us by contacting using one of the contact details listed at the beginning of this privacy policy.
|
||||
|
||||
Depending on your state of residence, you may be able to appeal our decision to your request regarding your personal data. To do so, please contact us by using one of the contact details listed at the beginning of this privacy policy. We respond to all appeal requests as soon as we reasonably can, and no later than legally required.
|
||||
|
||||
We do not discriminate against customers who exercise any of their rights described in our privacy policy.
|
||||
|
||||
California Shine the Light: Customers who are residents of California may request information concerning the categories of personal data (if any) we disclose to third parties or affiliates for their direct marketing purposes. If you would like more information, please submit a written request to us by using one of the contact details listed at the beginning of this privacy policy.
|
||||
|
||||
Do Not Track signals: Most modern web browsers give you the option to send a 'Do Not Track' signal to the sites you visit, indicating that you do not wish to be tracked. However, there is currently no accepted standard for how a site should respond to this signal, and we do not take any action in response to this signal.
|
||||
|
||||
## Note on international data transfers
|
||||
|
||||
Our Sites and Services make use of tools from companies based in countries outside of Switzerland or the EU/EEA, namely those based in the USA. When these tools are active, your personal data may be transferred to the servers of the respective companies abroad. If you are using the Site or Services from outside the United States, your personal data may be processed in a foreign country, where privacy laws may be less stringent than the laws in your country. In these cases, we only transfer personal data after we have implemented the legally required measures for this, such as concluding standard contractual clauses on data protection or obtaining the consent of the data subjects. If interested, the documentation on these measures can be obtained from the contact person mentioned above. By submitting your personal data to us you agree to the transfer, storage, and processing of your personal data in a country other than your country of residence including, but not necessarily limited to, the United States.
|
||||
|
||||
We actively try to minimize the use of tools from companies located in countries without equivalent data protection, however, due to the lack of alternatives, this is currently not always feasible without major inconvenience. If you have any concerns, please contact us directly and we will try to find a mutual solution for your needs.
|
||||
|
||||
## Children's Privacy
|
||||
|
||||
Our Site is not intended for or directed to children under the age of 14. We do not knowingly collect personal data directly from children under the age of 14 without parental consent. If we become aware that a child under the age of 14 has provided us with personal data, we will delete the information from our records.
|
||||
|
||||
## Changes to this Privacy Policy
|
||||
|
||||
We may revise this privacy policy from time to time and will post the date it was last updated at the top of this privacy policy.
|
||||
We will provide additional notice to you if we make any changes that materially affect your privacy rights.
|
||||
Please subscribe to updates in our [Trust Center](http://trust.zitadel.com/updates) to receive future notices and updates.
|
||||
|
||||
## Contact us
|
||||
|
||||
If you have any questions about our data processing, please email us or contact us by using the contact details listed at the beginning of this privacy notice.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: Rate Limit Policy
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on February 24, 2025
|
||||
|
||||
This policy is an annex to the [Terms of Service](../terms-of-service) and clarifies your obligations while using our Services, specifically how we will use rate limiting to enforce certain aspects of our [Acceptable Use Policy](./acceptable-use-policy).
|
||||
|
||||
## Why do we rate limit
|
||||
|
||||
To ensure the availability of our Services and to avoid slow or failed requests by our Customers, due to overloads, we impose rate limits on certain API. These limits helps us guarantee the performance and availability of ZITADEL Cloud.
|
||||
|
||||
## How is the rate limit implemented
|
||||
|
||||
ZITADEL Clouds rate limit is built around a `IP` oriented model.
|
||||
Please be aware that we also utilize a service for DDoS mitigation.
|
||||
So if you simply change your `IP` address and run the same request again and again you might get blocked at some point.
|
||||
|
||||
If you are blocked you will receive a `http status 429`.
|
||||
|
||||
<Callout title="Implement exponential backoff">
|
||||
You should consider to implement [exponential backoff](https://en.wikipedia.org/wiki/Exponential_backoff) into your application to prevent a blocking loop.
|
||||
</Callout>
|
||||
|
||||
<Callout title="Raising limits">
|
||||
We understand that there are certain scenarios where your users access ZITADEL from shared IP Addresses.
|
||||
For example if you use a corporate proxy or Network Address Translation NAT.
|
||||
Please [get in touch](https://zitadel.com/contact) with us to discuss your requirements, and we'll find a solution.
|
||||
</Callout>
|
||||
|
||||
## What rate limits do apply
|
||||
|
||||
For ZITADEL Cloud, we have dedicated rate limits for the user interfaces (login, register, management console,...) and the APIs.
|
||||
|
||||
Rate limits are implemented with the following rules:
|
||||
|
||||
| Path | Description | Rate Limiting | One Minute Banning |
|
||||
|----------------------|----------------------------------------|--------------------------------------|---------------------------------------|
|
||||
| /ui/\* | Global Login, Register and Reset Limit | 10 requests per second over a minute | 15 requests per second over 3 minutes |
|
||||
| All other paths | All gRPC-, REST and OAuth APIs | 50 requests per second over a minute | 50 requests per second over 3 minutes |
|
||||
|
||||
## Load Testing
|
||||
|
||||
If you would like to conduct load testing of ZITADEL Cloud or a managed instance, you MUST request to do so with a minimum of 2 weeks notice before the test by contacting us at [[email protected]](mailto:[email protected]).
|
||||
You MUST NOT conduct load testing without prior approval by us. Without prior approval and setup there is a high risk of being flagged by our DDoS solution as malicious traffic. This can have a severe impact on your service quality or result in termination of your agreement.
|
||||
@@ -0,0 +1,90 @@
|
||||
---
|
||||
title: Vulnerability Disclosure Policy
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on March 16, 2023
|
||||
|
||||
At ZITADEL we are extremely grateful for security aware people who disclose vulnerabilities to us and the open source community.
|
||||
All reports will be investigated by our team and we will work with you closely to validate and fix vulnerabilities reported to us.
|
||||
|
||||
We require that you keep vulnerabilities confidential until we are able to address them, since public disclosure of security vulnerabilities could put the ZITADEL community at risk.
|
||||
|
||||
ZITADEL (CAOS Ltd.) will not take legal action against you or terminate your access to our services, conditional that you report vulnerabilities in accordance to this policy.
|
||||
|
||||
## Scope
|
||||
|
||||
The scope of this policy applies to all Websites and Services operated by ZITADEL.
|
||||
|
||||
All security issues that concern our Product in form of Software in our [open source repositories](https://github.com/zitadel), should be reported according to [Security Policy](https://github.com/zitadel/zitadel/blob/main/SECURITY.md).
|
||||
|
||||
When in doubt about the scope of your vulnerability, please follow the process outlined in this policy.
|
||||
|
||||
## Discovering a vulnerability
|
||||
|
||||
Responsible security research on our Websites, Products, and Services is encouraged and we allow you to conduct testing on our services to which you have authorized access.
|
||||
|
||||
You must not do research or testing that involves
|
||||
|
||||
- Any activity that violates applicable law
|
||||
- Modify or destroy any data that does not belong to you
|
||||
- Accessing or attempt to access data that does not belong to you
|
||||
- Executing denial of service attacks
|
||||
- Executing load testing
|
||||
|
||||
Exceptions may be granted after your initial report by a member of our security team.
|
||||
|
||||
## Reporting a vulnerability
|
||||
|
||||
To file an incident, please disclose it by e-mail to [[email protected]](mailto:[email protected]) including the following details of the vulnerability:
|
||||
|
||||
- Target: ZITADEL, Website (zitadel.com), ZITADEL Cloud (zitadel.cloud), Other (please describe)
|
||||
- Type: For example DoS, authentication bypass, information disclosure, broken authorization, ...
|
||||
- Description: Provide a detailed explanation of the issue, steps to reproduce, and assumptions you have made
|
||||
- URL / Location (optional): The URL of the vulnerability
|
||||
- Contact details (optional): In case we should contact you on a different channel
|
||||
|
||||
At the moment GPG encryption is no yet supported, however you may sign your message at will.
|
||||
|
||||
Your email will be acknowledged within 48 hours.
|
||||
We will follow-up within the next 3 business days indicating next steps in handling your report.
|
||||
|
||||
If you haven't received a response within 48 hours, or you didn't get a reply from our security team within the last 5 days, please contact [[email protected]](mailto:[email protected]).
|
||||
|
||||
Please inform us in your report whether we should mention your contribution.
|
||||
We will not publish this information by default to protect your privacy.
|
||||
|
||||
### What not to report
|
||||
|
||||
- Disclosure of known public files or directories, e.g. robots.txt, files under .well-known, or files that are included in our public repositories (eg, go.mod)
|
||||
- DoS of users when [Lockout Policy is enabled](/guides/manage/console/default-settings#lockout)
|
||||
- Suggestions on Certificate Authority Authorization (CAA) rules
|
||||
- Suggestions on DMARC/DKIM/SPF settings
|
||||
- Suggestions on DNSSEC settings
|
||||
- Phishing or Social Engineering Attacks
|
||||
- Lack of security flags on non-sensitive cookies
|
||||
|
||||
## Disclosure Process
|
||||
|
||||
Our security team will follow the disclosure process:
|
||||
|
||||
1. We will acknowledge the receipt of your vulnerability report
|
||||
2. Our security team will try to verify, reproduce, and determine the impact of your report
|
||||
3. A member of our team will respond to either confirm or reject your report, including an explanation
|
||||
4. Code will be audited to assess if the report uncovers similar issues
|
||||
5. Fixes are prepared for the latest release
|
||||
6. On the date that the fixes are applied, we will create a CVE and publish a [security advisory](https://github.com/zitadel/zitadel/security/advisories). Affected users of our Product, Services, or Website will be informed of the fix and required actions.
|
||||
|
||||
We think it is crucial to publish advisories `ASAP` as mitigations are ready. But due to the unknown nature of the disclosures the time frame can range from 7 to 90 days.
|
||||
|
||||
## Bug Bounty / Compensation
|
||||
|
||||
At this moment, we do not pay out monetary compensation for reporting security vulnerabilities.
|
||||
|
||||
Please inform us in your report whether we should mention your contribution.
|
||||
We will not publish this information by default to protect your privacy.
|
||||
|
||||
In case we have confirmed your report, we may compensate you, given prior written approval by ZITADEL, for costs
|
||||
|
||||
- incurred during research for using our paid services
|
||||
- on time & material spend on analysis after confirming your report
|
||||
@@ -0,0 +1,85 @@
|
||||
---
|
||||
title: Service description for ZITADEL Cloud and ZITADEL Enterprise
|
||||
sidebar_label: Service description
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on April 5, 2024
|
||||
|
||||
This annex of the [Framework Agreement](../terms-of-service) describes the services offered by us.
|
||||
|
||||
## Services offered
|
||||
|
||||
### ZITADEL Cloud
|
||||
|
||||
[ZITADEL Cloud](https://zitadel.com) is a fully managed cloud service of the [ZITADEL software](https://github.com/zitadel).
|
||||
|
||||
You will benefit from the same software as the open-source project, but we take care of the hosting, maintenance, backup, scaling, and operational security. The cloud service is managed and maintained by the team that also develops the software.
|
||||
|
||||
When creating a new instance, you are able to choose a [data location](#data-location).
|
||||
We follow a single-provider strategy by minimizing the involved [sub-processors](../subprocessors) to increase security, compliance, and performance of our services. [Billing](https://help.zitadel.com/pricing-and-billing-of-zitadel-services) is based on effective usage of our services.
|
||||
|
||||
### Enterprise license / self-hosted
|
||||
|
||||
The ZITADEL Enterprise license allows you to use the [ZITADEL software](https://github.com/zitadel) on your own data center or private cloud.
|
||||
|
||||
You will benefit from the transparency of the open source and the hyper-scalability of the same software that is being used to operate [ZITADEL Cloud](#zitadel-cloud).
|
||||
|
||||
#### Benefits over using open source / community license
|
||||
|
||||
- [Enterprise supported features](https://help.zitadel.com/zitadel-support-states#enterprise) are only supported under an Enterprise license
|
||||
- Individual [onboarding support](./support-services#onboarding-support) tailored to your needs and team
|
||||
- Get access to our support with a [Service Level Agreement](./support-services#service-level-agreement) that is tailored to your needs
|
||||
- Benefit from personal [technical account management](./support-services#technical-account-manager) provided by our engineers to help you with architecture, integration, migration, and operational improvements of your setup
|
||||
|
||||
#### Benefits over ZITADEL Cloud
|
||||
|
||||
You can reduce your supply-chain risks by removing us as sub-processor of personal information about your users.
|
||||
Support staff will have no access to your infrastructure and will only provide technical support.
|
||||
Operation and direct maintenance of ZITADEL will be done by you.
|
||||
|
||||
You can freely choose the infrastructure and location to host ZITADEL.
|
||||
|
||||
### Responsibilities
|
||||
|
||||
Your obligations while operating and using ZITADEL are detailed in our [terms of service](/legal/terms-of-service#your-obligations) given the provisions in our [acceptable use policy](/legal/policies/acceptable-use-policy).
|
||||
When using ZITADEL Cloud, we may processing data on behalf according to the [data processing agreement](/legal/data-processing-agreement).
|
||||
|
||||
In a self-hosted setup, you will be responsible for the cost, operations, and availability of your infrastructure.
|
||||
For DDoS, bot, and threat detection and protection we rely on external services in ZITADEL Cloud.
|
||||
In a self-hosted setup, it is your responsibility to secure the infrastructure to protect confidentiality, integrity, and availability of your data.
|
||||
|
||||
ZITADEL Cloud comes with pre-configured SMTP service, SMS service, and a generated domain name.
|
||||
The SMTP service and SMS service are limited in use.
|
||||
You should configure your own service providers for production use cases.
|
||||
In a self-hosted setup, you will be responsible for SMTP / SMS services, domains and certificates.
|
||||
|
||||
| Responsibility | ZITADEL Cloud | Self-Hosted |
|
||||
| --- | --- | --- |
|
||||
| Data / Information | Customer | Customer |
|
||||
| User Access | Customer | Customer |
|
||||
| SMTP Service | Customer (trial: ZITADEL) | Customer |
|
||||
| SMS Service | Customer (trial: ZITADEL) | Customer |
|
||||
| Custom Domain / TLS | Customer (trial: ZITADEL) | Customer |
|
||||
| DDoS & Bot protection | ZITADEL | Customer |
|
||||
| WAF / Threat detection | ZITADEL | Customer |
|
||||
| [Backup](#backup) | ZITADEL | Customer |
|
||||
| Networking | ZITADEL | Customer |
|
||||
| Compute / Scaling | ZITADEL | Customer |
|
||||
| Database | ZITADEL | Customer |
|
||||
| Application | ZITADEL | ZITADEL |
|
||||
|
||||
## Data location
|
||||
|
||||
Data location refers to a region, consisting of one or many countries or territories, where the customer's data is being hosted.
|
||||
|
||||
We can not guarantee that during transit the data will only remain within this region. We take measures, as outlined in our [privacy policy](../policies/privacy-policy), to protect your data in transit and in rest.
|
||||
|
||||
## Backup
|
||||
|
||||
Our backup strategy executes daily full backups and differential backups on much higher frequency.
|
||||
In a disaster recovery scenario, our goal is to guarantee a recovery point objective (RPO) of 1h, and a higher but similar recovery time objective (RTO).
|
||||
Under normal operations, RPO and RTO goals are below 1 minute.
|
||||
|
||||
If you you have different requirements we provide you with a flexible approach to backup, restore, and transfer data (f.e. to a self-hosted setup) through our APIs.
|
||||
Please consult the [migration guides](/guides/migrate/introduction) for more information.
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: "Service description"
|
||||
description: "Description of services and service levels for ZITADEL Cloud and Enterprise subscriptions."
|
||||
---
|
||||
|
||||
{/* THIS FILE IS AUTO-GENERATED FROM SIDEBAR-DATA.
|
||||
ANY MANUAL CHANGES WILL BE OVERWRITTEN.
|
||||
*/}
|
||||
|
||||
import { Card, Cards } from 'fumadocs-ui/components/card';
|
||||
import { FileText, Folder, Link as LinkIcon } from 'lucide-react';
|
||||
|
||||
<Cards>
|
||||
<Card title="Service Description" href="/legal/service-description" icon={<Folder />} />
|
||||
<Card title="Billing" href="https://help.zitadel.com/pricing-and-billing-of-zitadel-services" icon={<LinkIcon />} external />
|
||||
</Cards>
|
||||
@@ -0,0 +1,85 @@
|
||||
---
|
||||
title: Service level description for ZITADEL Cloud
|
||||
sidebar_label: Service Level
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on November 15, 2023
|
||||
|
||||
This annex of the [Framework Agreement](../terms-of-service) describes the service levels offered by us for our Services (ZITADEL Cloud).
|
||||
|
||||
## Definitions
|
||||
|
||||
### Monthly Uptime Percentage
|
||||
|
||||
Monthly Uptime Percentage means total number of minutes in a month, minus the number of minutes of Downtime suffered from all Downtime Periods in a month, divided by the total number of minutes in a month.
|
||||
|
||||
### Downtime Period
|
||||
|
||||
Downtime Period means a period of one or more consecutive minutes of Downtime. Partial minutes or intermittent Downtime for a period of less than one minute will not count towards any Downtime Period.
|
||||
|
||||
### Downtime
|
||||
|
||||
Downtime means any period of time in which Core Services are not Available within the Region of the customer’s organization. Downtime excludes any time in which ZITADEL Cloud is not Available because of
|
||||
|
||||
- [Announced maintenance work](https://help.zitadel.com/zitadel-software-release-cycle#maintenance)
|
||||
- Emergency maintenance
|
||||
- Force majeure events.
|
||||
|
||||
### Available
|
||||
|
||||
Available means that Core Services of ZITADEL Cloud respond to Customer Requests in such a way that results in a Successful Minute. The Availability of Core Services will be monitored from CAOS’ facilities from black-box monitoring jobs.
|
||||
|
||||
### Customer Requests
|
||||
|
||||
Customer Requests means a HTTP request made by a Customer or a Customers’ users to Core Services within the Customer’s organization’s region.
|
||||
|
||||
### Successful Minute
|
||||
|
||||
Successful Minute means a minute in which ZITADEL Cloud is not repeatedly returning Failed Customer Requests and includes minutes in which no Customer Requests were made.
|
||||
|
||||
Failed Customer Request means Customer Requests that
|
||||
|
||||
- Returns an server error; or
|
||||
- is received by ZITADEL Cloud and results in no response where one is expected
|
||||
|
||||
This excludes specifically:
|
||||
|
||||
- Failed Customer Requests due to malformed requests, client-side application errors outside of ZITADEL Cloud’s control
|
||||
- Customer Requests that do not reach ZITADEL Cloud Core Services
|
||||
|
||||
### Core Services
|
||||
|
||||
Core Services means the following ZITADEL Cloud Services and API’s:
|
||||
|
||||
- **Authentication API** Endpoints including the session endpoints
|
||||
- **OpenID Connect 1.0 / OAuth 2.0 API** Endpoints
|
||||
- **SAML 2.0** Endpoints
|
||||
- **Login Service** means the graphical user interface of ZITADEL Cloud for users to Login, Self-Register, and conduct a Password Reset.
|
||||
- **Identity Brokering Service** means the component of ZITADEL Cloud that handles federated authentication of users with third-party identity provider, excluding any failure or misconfiguration by the third-party
|
||||
|
||||
### Financial Credit
|
||||
|
||||
**Financial Credit** means the percent of the monthly subscription fee applicable to the month in which the guaranteed service level was not met, according to the actual achieved monthly uptime percentage, as shown in the following table
|
||||
|
||||
Achieved vs. Guaranteed| 99.50% | 99.90% | 99.95%
|
||||
--- | --- | --- | ---
|
||||
99.5% - < 99.9% | n/a | n/a | 10%
|
||||
99.0% - < 99.5% | n/a | 10% | 25%
|
||||
95.0% - < 99.0% | 10% | 25% | 50%
|
||||
< 95.0% | 50% | 50% | 50%
|
||||
|
||||
## Service Levels
|
||||
|
||||
### Availability Objective
|
||||
|
||||
1. During the term of the subscription agreement under which CAOS has agreed to provide ZITADEL Cloud to Customer, the Core Services will provide a Monthly Uptime Percentage to Customer conditional on the subscription plan as follows (the “SLO”):
|
||||
|
||||
Option | Monthly Uptime Percentage
|
||||
--- | ---
|
||||
Default | 99.50%
|
||||
Extended SLA | 99.95%
|
||||
|
||||
1. If CAOS Ltd. does not meet the guaranteed service level, Customer might be eligible to receive Financial Credit as described in this document. Financial Credit shall be the sole and exclusive remedy for breach of this SLA.
|
||||
2. The Customer must request Financial Credit and must notify CAOS Support in writing within 30 days of becoming eligible for Financial Credit and must prove Failed Customer Requests during Downtime Periods. Financial Credit will be made in the form of a monetary credit applied to the next possible subscription invoice of ZITADEL Cloud, may only be used to book services in the future, and will in no case be paid as a cash equivalent. No further guarantees are provided.
|
||||
3. The Service Level commitments apply only to organizations with a subscription plan where a Service Level is applicable and does not include any other organizations of the same customer. The Customer is not entitled to any Financial Credit, if it is in breach of the Agreement at the time of the occurrence of the event giving rise to the credit.
|
||||
@@ -0,0 +1,254 @@
|
||||
---
|
||||
title: Support service description for ZITADEL
|
||||
sidebar_label: Support service
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on November 15, 2023
|
||||
|
||||
This annex of the [Framework Agreement](../terms-of-service) and the [Support Service Terms and Conditions](../annex-support-services) describes the support services offered by us for our Services.
|
||||
|
||||
Support Services for products and services provided by ZITADEL is offered to customers according to the terms and conditions outlined in this document.
|
||||
The customer may purchase support services from ZITADEL (CAOS Ltd.) directly.
|
||||
|
||||
## Service Level Agreement
|
||||
|
||||
ZITADEL provides a Service Level Agreement for support of the [services offered](./cloud-service-description#services-offered).
|
||||
Depending on your subscription plan you might be eligible to the following support service level agreement.
|
||||
|
||||
### ZITADEL Cloud
|
||||
|
||||
Based on your subscription plan you may be eligible for the support services as outlined in this document.
|
||||
You may purchase additional premium support plans which replace the default support features.
|
||||
|
||||
#### Support in subscription plans
|
||||
|
||||
Support features for ZITADEL Cloud subscriptions are as follows:
|
||||
|
||||
Subscription Plans | Free | Production | Enterprise Cloud
|
||||
--- | --- | --- | ---
|
||||
[Support hours](#support-hours) | Business hours | Business hours | bespoke (up to 24x7)
|
||||
[Response Time](#slo---initial-response-time) (Severity 1) | n/a | 48 business hours | bespoke (as low as 30min)
|
||||
[Community support](#community-support) | yes | yes | yes
|
||||
[Professional support](#professional-support) | no | yes | yes
|
||||
[Enterprise supported features](https://help.zitadel.com/zitadel-support-states#enterprise) | no | no | yes
|
||||
[Technical Account Management](#technical-account-manager) | no | no | bespoke
|
||||
|
||||
#### Extended support
|
||||
|
||||
Extended support can be added to ZITADEL Cloud subscription plans.
|
||||
The default support features will be replaced as follows:
|
||||
|
||||
Extended support | Default
|
||||
--- | ---
|
||||
[Support hours](#support-hours) | [Extended hours](#extended-hours)
|
||||
[Response Time](#slo---initial-response-time) (Severity 1) | 1 business hour
|
||||
[Community support](#community-support) | yes
|
||||
[Professional support](#professional-support) | yes
|
||||
[Enterprise supported features](https://help.zitadel.com/zitadel-support-states#enterprise) | no
|
||||
[Technical Account Management](#technical-account-manager) | no
|
||||
|
||||
### ZITADEL Enterprise / self-hostable
|
||||
|
||||
With ZITADEL Enterprise you become eligible for support plans according to your purchase order for self-hosting ZITADEL.
|
||||
Please refer to the [service description](./cloud-service-description#enterprise-license-self-hosted) for an overview of ZITADEL Enterprise.
|
||||
|
||||
ZITADEL Enterprise self-hostable| Default
|
||||
--- | ---
|
||||
[Support hours](#support-hours) | bespoke (up to 24x7)
|
||||
[Response Time](#slo---initial-response-time) (Severity 1) | bespoke (as low as 30min)
|
||||
[Community support](#community-support) | yes
|
||||
[Professional support](#professional-support) | yes
|
||||
[Enterprise supported features](https://help.zitadel.com/zitadel-support-states#enterprise) | yes
|
||||
[Technical Account Management](#technical-account-manager) | bespoke
|
||||
|
||||
## Description of support services
|
||||
|
||||
### Support hours
|
||||
|
||||
#### Business hours
|
||||
|
||||
Business hours means 08:00-17:00 Monday - Friday Switzerland time (or as per agreement with the customer). All times exclude public holidays in Switzerland / Canton St. Gallen.
|
||||
|
||||
#### Extended hours
|
||||
|
||||
Extended hours means 07:00-19:00 Monday - Friday Switzerland time (or as per agreement with the customer). All times exclude public holidays in Switzerland / Canton St. Gallen.
|
||||
|
||||
### Ticket
|
||||
|
||||
Ticket means a discrete technical or non-technical issue that was submitted by the customer and exists in the support portal. A ticket includes a record of all communication associated with the issue.
|
||||
|
||||
### SLO - Initial response time
|
||||
|
||||
ZITADEL service level objective (SLO) for Support Services is defined in terms of initial response time to a support request, as outlined in the table below per plan.
|
||||
ZITADEL will use reasonable efforts to resolve support requests, but does not guarantee a work-around, resolution or resolution time.
|
||||
|
||||
Subscription Plans | Default | Extended SLA | Custom
|
||||
--- | --- | --- | ---
|
||||
Severity 1| Best effort | 1 business hour | up to 30min
|
||||
Severity 2| Best effort | 2 business hour | 2 business hours
|
||||
Severity 3| Best effort | 12 business hour | 12 business hours
|
||||
Severity 4| Best effort | 24 business hour | 24 business hours
|
||||
|
||||
If we fail to provide the initial response time objective, you will be entitled to service credits. For every 15 minutes exceeding the state objective, 1 day will be added as extension to the current term.
|
||||
|
||||
### Communication
|
||||
|
||||
#### Community support
|
||||
|
||||
Community support for ZITADEL is available on our website, our [public chat](https://zitadel.com/chat), and [GitHub](https://github.com/zitadel/).
|
||||
|
||||
We do only guarantee response times to Tickets reported via [professional support](#professional-support) channels only.
|
||||
If you are an eligible customer, please use Tickets for critical or urgent issues.
|
||||
|
||||
#### Professional support
|
||||
|
||||
- Support is available in English
|
||||
- Default contact: Whenever customers require support, Customers should consult the documentation of the service or product or post a question to our community
|
||||
- When Customer is eligible for support services through a Subscription Plan, Customer may contact ZITADEL support via the following channels
|
||||
|
||||
Support Feature | Contact information
|
||||
--- | ---
|
||||
Ticket | Submit an issue via the [customer portal](https://zitadel.com/admin/support)
|
||||
eMail Support | [email protected]
|
||||
Chat Support | Private chat channel between ZITADEL and Customer that is opened when Subscription becomes active
|
||||
Phone Support | +41 43 215 27 34
|
||||
|
||||
- ZITADEL Cloud system status, incidents and maintenance windows will be communicated via [our status page](https://zitadelstatus.com).
|
||||
- Questions regarding pricing, billing, and invoicing of our services should be addressed to [email protected]
|
||||
- Security related questions and incidents can also be directly addressed to [email protected]
|
||||
|
||||
### Technical account manager
|
||||
|
||||
ZITADEL will enhance its support offering by providing eligible clients with a Technical Account Manager (TAM), who will perform the following tasks for up to the agreed amount of time during the term of service:
|
||||
|
||||
- Provide support and advice regarding best practices on platform, product and configuration covered by the applicable Support Services;
|
||||
- Participate in review calls every other week at mutually agreed times addressing customer’s operational challenges or complex support requests;
|
||||
- Walk-through of new features and customer feedback.
|
||||
|
||||
We offer TAM services only bundled with specific subscription plans, and the option to add more TAM hours per period to these plans.
|
||||
If you require consulting for your projects, please request a quote via our [website](https://zitadel.com/contact).
|
||||
|
||||
### Onboarding support
|
||||
|
||||
Our onboarding support should help you, as a new customer, to get a better understanding on how to integrate ZITADEL into your solution, how to tackle the migration, and ensure a highly-available day-to-day operation.
|
||||
|
||||
Onboarding support services can be offered to customers that enter a ZITADEL Cloud or a ZITADEL Enterprise subscription.
|
||||
|
||||
If you intend to use the open-source version exclusively then please join our community chat or GitHub.
|
||||
Your questions might help other people in the community and will make our project better over time.
|
||||
|
||||
Please [contact us](https://zitadel.com/contact) for a quote and to get started with onboarding support.
|
||||
Below you will find topics covered and scope of the offered services.
|
||||
|
||||
#### Proof of value
|
||||
|
||||
Within a short time-frame, f.e. 3 weeks, we can show the value of using our services and have the ability to establish the proof a of working setup for your most critical use cases.
|
||||
We may offer to support you during an initial period to evaluate next steps.
|
||||
Before the start of the period we may ask you to provide a description of your critical use cases and a high-level overview of your planned integration architecture.
|
||||
During this period you should make sure that you have the necessary resources on your side to complete the proof of value.
|
||||
|
||||
#### Onboarding term
|
||||
|
||||
With the onboarding support we provide the initial knowledge transfer to configure and operate ZITADEL.
|
||||
During the term you will get direct access to our engineering team via [Technical Account Management](#technical-account-manager).
|
||||
Duration is typically 3 months but this could vary depending on your requirements.
|
||||
|
||||
We offer an onboarding term in combination with ZITADEL Enterprise subscriptions.
|
||||
|
||||
#### Topics covered
|
||||
|
||||
The scope will be tailored to your requirements.
|
||||
Topics of the onboarding term may include
|
||||
|
||||
- Administration
|
||||
- DevOps (Operation)
|
||||
- Architecture
|
||||
- Integration
|
||||
- Migration
|
||||
- Security Best Practices & Go-Live Checkup
|
||||
|
||||
<Tabs>
|
||||
<Tab value="in" label="Topics in scope">
|
||||
<ul>
|
||||
<li>IAM Configuration</li>
|
||||
<li>Walk-though all features</li>
|
||||
<li>Users / Manuals</li>
|
||||
<li>Authentication & Management APIs</li>
|
||||
<li>Validation of tokens</li>
|
||||
<li>Client integration best-practices</li>
|
||||
<li>Event types</li>
|
||||
<li>Database schemas and compute models</li>
|
||||
<li>Accessing database</li>
|
||||
<li>Observability (Logs, Errors, Metrics, Tracing)</li>
|
||||
<li>Operations best practices (Deployment, Backup, Networking etc.)</li>
|
||||
<li>Check prerequisites and architecture</li>
|
||||
<li>Troubleshoot installation and configuration of ZITADEL</li>
|
||||
<li>Troubleshoot and configuration connectivity to the database</li>
|
||||
<li>Functional testing of the ZITADEL instance</li>
|
||||
</ul>
|
||||
</Tab>
|
||||
<Tab value="out" label="Topics out of scope" default>
|
||||
<ul>
|
||||
<li>Performance testing</li>
|
||||
<li>Setting up or maintaining backup storage</li>
|
||||
<li>Running multiple ZITADEL instances on the same cluster</li>
|
||||
<li>Integration into internal monitoring and alerting</li>
|
||||
<li>Multi-cluster architecture deployments</li>
|
||||
<li>DNS, Network and Firewall configuration</li>
|
||||
<li>Customer-specific Kubernetes configuration needs</li>
|
||||
<li>Non-production environments</li>
|
||||
<li>Production deployment</li>
|
||||
<li>Application-side coding, configuration, or tuning</li>
|
||||
</ul>
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
## Support
|
||||
|
||||
### Support request
|
||||
|
||||
ZITADEL agrees to handle support incidents in the following scenarios:
|
||||
|
||||
1. Service, product or configuration as provided by ZITADEL contains errors or critical security-related issues
|
||||
2. Service or product requires upgrades or changes through the customer
|
||||
3. Service or product has incorrect or missing documentation
|
||||
|
||||
Support features include:
|
||||
|
||||
- Answer questions regarding usage of specific features or configurations
|
||||
- Provide high-level suggestions regarding appropriate usage, features or configurations
|
||||
- Assist in troubleshooting of issues to isolate potential root cause
|
||||
- Document and advise alternative solutions for reported defects
|
||||
|
||||
Excluded are broader consulting & customer-specific engineering requests regarding use of our products and services. Moreover support requests from Customer’s end users must be handled by the Customer directly.
|
||||
|
||||
### Support service process
|
||||
|
||||
The customer may submit support requests (“ticket”) through any means of eligible communication channels, consisting of
|
||||
|
||||
- Single discrete problem, issue, or request
|
||||
- Initial severity level and impact statement for assessment
|
||||
- Description of the issue and if possible a description of the observed and expected behavior, steps to reproduce the issue, evidence that issue is not caused by connectivity / compute, relevant anonymized log-files etc.
|
||||
- All information requested by ZITADEL as we resolve the ticket (e.g. system logs)
|
||||
|
||||
ZITADEL will review the case information and determine the severity level (see below), working with the customer to assess the urgency of the request and use reasonable efforts to respond to support requests within the initial response time.
|
||||
|
||||
ZITADEL will use reasonable efforts to resolve support request as defined below, but does not guarantee a workaround, resolution or resolution time.
|
||||
|
||||
Severity Level | Description
|
||||
--- | ---
|
||||
**Severity 1**<br/> Critical / Service down| <p>Widespread failure or complete unavailability of ZITADEL Core Services. </p><p> ZITADEL will use continuous effort to provide a workaround or permanent solution. When Core Services are available, the severity will be lowered to the new appropriate level.</p>
|
||||
**Severity 2**<br/> Core functionality unavailable or severely degraded| <p>Core Services of ZITADEL software continue to operate in severely restricted fashion, yet long-term productivity may be impacted.</p><p> When Core Services are no longer severely degraded (eg, through a viable workaround or release), the severity level will be lowered to Severity 3.</p>
|
||||
**Severity 3**<br/>Standard support request| <p>Partial and non-critical loss of ZITADEL software functionality or major software defect, yet a workaround exists for viable long-term operation.</p><p>ZITADEL will continue to work on developing permanent resolution.</p>
|
||||
**Severity 4**<br/>Non-urgent request| Defined as follows: <ul><li>Request for information or general query</li><li>Feature request</li><li>Performance issues and little to none functional impact</li><li>Defects with workarounds and little to low functional impact</li></ul>
|
||||
<p>ZITADEL will continue to work on developing permanent resolution and response to general requests. ZITADEL does not provide a timeline or guarantee to include any feature requests.</p>
|
||||
|
||||
### Escalation
|
||||
|
||||
The customer may escalate support requests following the escalation process:
|
||||
|
||||
1. For non-urgent needs, the client may request management escalation within the ticket. A manager will review the request and provide a response within one business day.
|
||||
2. For urgent needs, the client may escalate directly by calling +41 71 560 28 06 and emailing to [[email protected]](mailto:[email protected]). A manager will review the request and provide response within two business hours.
|
||||
|
||||
If we fail to provide a response to the escalation, you will be entitled to service credits. For every 15 minutes exceeding the state objective, 1 day will be added as extension to the current term.
|
||||
@@ -0,0 +1,17 @@
|
||||
---
|
||||
title: Third party sub-processors for ZITADEL
|
||||
sidebar_label: Third Party Sub-Processors
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on December 5, 2025.
|
||||
|
||||
In order to achieve the best possible transparency we publish which sub-processors and services we use to provide ZITADEL and related services.
|
||||
The table shows what activity each entity performs.
|
||||
More information about each activity is provided directly below.
|
||||
This explains the limited processing of customer data the entity is authorized to perform.
|
||||
|
||||
We regularly audit all data processing agreements that we have with our sub-processors to guarantee that they adhere to the same level of privacy as ours to protect your personal data.
|
||||
|
||||
You can find [the full list of sub-processors in our trust center](https://trust.zitadel.com/subprocessors). We try to minimize the number of sub-processors that handle end-user data on our behalf to reduce any vendor related risks.
|
||||
Some providers are used by default, but you can opt-out of the default provide and replace the sub-processor by a provider of your choice.
|
||||
@@ -0,0 +1,230 @@
|
||||
---
|
||||
title: Terms of Service Agreement
|
||||
custom_edit_url: null
|
||||
---
|
||||
|
||||
Last updated on November 15, 2023
|
||||
|
||||
## General
|
||||
|
||||
### Introduction
|
||||
|
||||
CAOS Ltd. (**"We"**, **ZITADEL**, **CAOS AG**, or simply **CAOS**), with head office in Lerchenfeldstrasse 3, 9014 St. Gallen, Switzerland, offers "Identity and Access Management as service" with the brand name "ZITADEL Cloud Services" and all of our Websites (**Services** or **ZITADEL Cloud**).
|
||||
|
||||
The customer relationship (**Framework Agreement** or **The Agreement**) is created by the **Customer** (**"you"**) by creating a user or organization within the ZITADEL Cloud Service or with signature of a purchase order between you and ZITADEL (jointly referred to as **Parties**).
|
||||
On the basis of this Framework Agreement you may then choose to make use of payable services (**Subscription**) as you wish, i.e. you may book services, options and packages yourself at any time (**Booking**, **Purchase Order**, **PO**) and subsequently terminate them.
|
||||
|
||||
The terms of service (**"TOS"**) outlined in this document establish the most important points of this Framework Agreement – independently of the use of any services.
|
||||
|
||||
This Agreement has the following appendices. When you enter the Agreement with us, you accept these agreements.
|
||||
|
||||
* [**Data Processing Agreement**](./data-processing-agreement) - How we process personal data on behalf of you
|
||||
* [**Service Descriptions**](./service-description) - How we provide services to you
|
||||
* [**Policies**](./policies) - Policies that apply for use of our services
|
||||
* [**Enterprise Agreement**](./annex-support-services) - Annex for Enterprise Agreement and Support Services
|
||||
|
||||
The outlined policies complement these terms of service.
|
||||
When accepting the TOS, you accept these policies.
|
||||
|
||||
### Alterations
|
||||
|
||||
Any provisions which deviate from these TOS must be agreed in writing between the Customer and us. Such agreements shall take precedence over the TOS outlined in this document.
|
||||
|
||||
### Transfer
|
||||
|
||||
You may only transfer the Framework Agreement or Services used in the context of the Framework Agreement to third parties with our prior written consent.
|
||||
|
||||
## Our Services
|
||||
|
||||
### Type and scope of the services
|
||||
|
||||
We provide the Services under the conditions stated on our websites, or the latest customer specific purchase order, at the time of booking.
|
||||
|
||||
### Modifications of services offered
|
||||
|
||||
We are entitled to offer new services, to withdraw existing services (**Termination**) or to modify the specifications and prices of existing services (**Modification**) at any time.
|
||||
If the modification or termination affects a service that you are using at that time, we will inform you via email that said service will be automatically modified and/or is no longer available after a period of 30 days.
|
||||
|
||||
If such modification would have a disadvantageous impact on the Customer use of service, ZITADEL and Customer must discuss the change with the Customer first and, to the best of its ability, find a solution that is acceptable to both Parties.
|
||||
If such a solution cannot be found, ZITADEL may implement the modification and Customer may submit notice of termination of the relevant Service (email is sufficient) before the modification becomes effective without being obliged to pay contractual penalties or termination fees.
|
||||
ZITADEL may modify the prices for a service after the minimum term of the agreement.
|
||||
|
||||
### Modification of services booked by you
|
||||
|
||||
You may change or terminate Services or Subscriptions booked by you at any time.
|
||||
You may, where applicable, add more Services (e.g. add-ons) to your existing Services at any time.
|
||||
Modifications will take effect in the next billing period, or as agreed otherwise between the Parties.
|
||||
Changing services booked by you requires a new purchase order, stating the new conditions of the services after Modification, to be accepted by the Parties.
|
||||
|
||||
### Due care
|
||||
|
||||
We take all appropriate physical and electronic precautions to ensure the security and availability of our infrastructure and the service offered thereupon, in particular to protect against unauthorized access to data, data loss, failures and misuse.
|
||||
|
||||
The [Annex of the data processing agreement](./data-processing-agreement#annex-2-technical-and-organizational-measures) outlines the measures we take in more detail.
|
||||
|
||||
### Support
|
||||
|
||||
We offer Support Services directly related to the use of our Services.
|
||||
The Description of Support Services is available as [Annex](./service-description/support-services) to this document.
|
||||
|
||||
Customers without a subscription can contact us via the official [communication channels](https://zitadel.com/contact).
|
||||
The parties may enter a service level agreement, as specified in our [Support Service Description](./service-description/support-services), for booked Support Services.
|
||||
Only named persons in the Purchase Order, or as agreed in writing (email is sufficient) may use the Support Services to interact with ZITADEL.
|
||||
|
||||
### Service level
|
||||
|
||||
Customers with a Subscription may be eligible for a SLA as outlined in our [Service Level Description](./service-description/service-level-description).
|
||||
|
||||
### Service credit
|
||||
|
||||
Failure to provide the agreed service level objectives during the term of the Agreement results in compensation via service credits, as outlined in the [Annex](./service-description/support-services) per service level objective.
|
||||
|
||||
Customer must request service credit and must notify ZITADEL in writing (email sufficient) within 30 days of becoming eligible for service credit and must prove failure of ZITADEL to meet the stated objective.
|
||||
ZITADEL will confirm or reject the claim with reasons for a refusal within 10 days.
|
||||
Service credit will in no case be paid as a cash equivalent.
|
||||
No further guarantees are provided.
|
||||
|
||||
### Limited influence
|
||||
|
||||
Be advised that the scope of our influence is limited. For example, the actual accessibility of a service is also dependent on the connection to and between various Internet Service Providers ("ISPs").
|
||||
Portions of our services, i.e. software components, may also be beyond our influence and be subject to their own contractual conditions. You accept that in such cases we reject any responsibility.
|
||||
|
||||
### Inclusion of third parties
|
||||
|
||||
We may include third parties in the provision of our services. See our [Privacy Policy](./policies/privacy-policy), [Third Party Sub-Processor List](./subprocessors), and our [Data Processing Agreement](./data-processing-agreement) for more information.
|
||||
|
||||
## Your obligations
|
||||
|
||||
### Contact information
|
||||
|
||||
At our request you will provide your truthful contact information and keep it updated at all times. You must also ensure that you actually receive messages, in particular emails, intended for you.
|
||||
|
||||
### Use
|
||||
|
||||
You will ensure that the use of our Websites and Services by you or third parties complies with all applicable legislation, this Agreement, any Annexes and policies, specifically the [Acceptable Use Policy](./policies/acceptable-use-policy), at all times.
|
||||
|
||||
### Security
|
||||
|
||||
You will take appropriate measures to prevent any misuse of the services you booked.
|
||||
These include, for example, securing the software used and the prompt installation of security updates as well as using suitably secure passwords.
|
||||
|
||||
### Disaster recovery
|
||||
|
||||
We take care of the necessary disaster recovery measures. The goal is to maintain a maximum 24h old restore point off all the vital data.
|
||||
|
||||
Any liability for damages, indirect or direct, in case of data loss is explicitly rejected.
|
||||
|
||||
### Reporting obligations
|
||||
|
||||
You will immediately report any knowledge of a misuse of your booked services.
|
||||
|
||||
### Cooperation
|
||||
|
||||
If the maintenance of service quality requires your cooperation, for example to remedy errors in the services you use, you will provide said cooperation promptly and free of charge.
|
||||
|
||||
### Third party obligations
|
||||
|
||||
You will ensure that your vicarious agents, customers and third parties fulfill these obligations as well.
|
||||
|
||||
## Financial
|
||||
|
||||
### Credit and payment
|
||||
|
||||
Signup to our Services does not require you to open a payment account.
|
||||
However, a payment account is required for the purchase of our Subscriptions.
|
||||
The costs for the services you have purchased will be debited periodically from your payment account or must be paid according to the purchase order.
|
||||
|
||||
### Payment procedure
|
||||
|
||||
If payment upon invoice is agreed, the payment deadline shall be 30 days after receipt of the invoice, or as stated in the purchase order.
|
||||
|
||||
### Offsetting
|
||||
|
||||
Offsetting against a counterclaim is prohibited.
|
||||
|
||||
### Collection
|
||||
|
||||
In the event of default we reserve the right to transfer our claim to a collections agency. You will bear any resulting costs insofar as legally permissible.
|
||||
|
||||
## Termination
|
||||
|
||||
### Termination by you
|
||||
|
||||
You may terminate the Framework Agreement at any time by ceasing your use of the services and deleting your customer account on our website.
|
||||
|
||||
For purchase orders, the term must be terminated by providing written notice (email is sufficient) of termination at least 30 days prior to the end of the term.
|
||||
|
||||
### Termination by us
|
||||
|
||||
We may terminate the Framework Agreement at any time via email message with a notice period of 90 days. Any use of the services will cease at the end of this period and the Framework Agreement will be terminated.
|
||||
|
||||
### Automatic termination
|
||||
|
||||
If you have neither used services nor made payment for a period of 180 days, the Framework Agreement will be considered automatically terminated at the end of this period.
|
||||
|
||||
If you have a Subscription to any free plans, that don't require payment, we automatically the Framework Agreement will be considered automatically terminated after 30 days without any Daily Active User on the Unit.
|
||||
|
||||
### No reimbursement
|
||||
|
||||
Any remaining credit shall automatically expire upon termination of the Framework Agreement.
|
||||
|
||||
### Termination of services
|
||||
|
||||
We are entitled to suspend and terminate services used by you if
|
||||
|
||||
* Your credit has been used up by services and/or any applicable credit limit has been reached;
|
||||
* You are in default in the payment of open invoices and/or prompt payment seems unlikely (i.e. in the event of insolvency proceedings);
|
||||
* Your services were used illegally or in breach of contract, or if there is reasonable suspicion of such use (i.e. in the event of complaints or abuse reports);
|
||||
* Other customers' services are being negatively affected in breach of the fair use provision, including in the event of your services being subject to attacks by third parties (i.e. DoS/DDoS attacks);
|
||||
* We consider the suspension or termination of the services to be necessary for the protection of ourselves, our infrastructure or other customers.
|
||||
|
||||
We reserve the right to immediately terminate the Framework Agreement in such cases.
|
||||
|
||||
### Deletion of data
|
||||
|
||||
In the event of the termination of the contract, we reserve the right to irrevocably delete all of your data.
|
||||
|
||||
## Data protection
|
||||
|
||||
Please consult the annex to this Framework Agreement, specifically our [Privacy Policy](./policies/privacy-policy), [Data Processing Agreement](./data-processing-agreement), [Third Party Sub-Processors](./subprocessors), and or our [Trust Site](https://zitadel.com/trust/) for more information about how we process and protect your data.
|
||||
|
||||
## Liability
|
||||
|
||||
### Our liability
|
||||
|
||||
We and/or third parties which we involve are only liable for demonstrably willful or grossly negligent damages.
|
||||
Our liability per damage event is limited to the value of the services used during the previous contractual year.
|
||||
Any liability in other cases, for consequential damages or lost profits is hereby excluded.
|
||||
|
||||
### Your liability
|
||||
|
||||
You are liable for all damages and costs arising from the illegal or non-contractual use of the services which you have booked.
|
||||
We in particular reserve the right to invoice you for any additional costs incurred by us in this context.
|
||||
|
||||
### Force majeure
|
||||
|
||||
You acknowledge that we may be partially or entirely unable to provide our services during and/or as a result of events beyond our influence.
|
||||
These include events such as natural disasters, war, terrorism, sabotage, attacks on our infrastructure (i.e. DoS/DDoS attacks), failure of electrical or data connections and unexpected official requirements.
|
||||
We are not liable for any damages in such cases.
|
||||
|
||||
## Final provision
|
||||
|
||||
### Applicable law
|
||||
|
||||
The Framework Agreement is subject to Swiss law.
|
||||
|
||||
### Place of jurisdiction
|
||||
|
||||
The exclusive place of jurisdiction is St. Gallen, Switzerland.
|
||||
|
||||
### Severability clause
|
||||
|
||||
Should any provision of these TOS be or become invalid, this shall not affect the validity of the remaining TOS. The invalid provision will be replaced by a valid one which approximates the invalid one as much as possible.
|
||||
|
||||
### Amendments
|
||||
|
||||
We are entitled to unilaterally amend this Agreement at any time.
|
||||
The current version is accessible via our website.
|
||||
We will inform you of any amendments via email.
|
||||
These amendments shall be considered as accepted upon booking additional services or at the latest after 30 days.
|
||||
In the case of a rejection on your part we reserve the right to terminate the Framework Agreement.
|
||||
Reference in New Issue
Block a user