Content Comparison

1. We do not store any personal data.

2. Technical data (such as identifiers, cloud ID, license information and others) that are needed to validate a licensed installation and to perform a secure communication with Confluence are transmitted and stored encrypted at rest.

3. We do not store diagrams themselves. They Your BPMN and/or DMN diagrams are not stored by us. Instead, the corresponding files are attached as Confluence page Attachements to your Confluence site and thus lie with sites and therefore stored as part of your Confluence instance by Atlassian.

4. For certain services provided by our app apps (e.g., PDF Rendering), diagrams are sent to our servers securely for processing and are deleted afterwards completely.

5. We do store data , that is strictly necessary to deliver certain features. This includes technical Ids for diagrams and IDs of Confluence content such as page IDs or space keys. Additionally, we store technical IDs of diagrams. Some features, e.g. page Ids or space keys, certain diagram names and element names (for example for the process net). We have no control, whether this information contains PII or sensitiv data, as we only receive the user input as-is. This data is stored securelyand encrypted at rest., require the storage of additional data such as the names of specific diagrams or of elements therein. This data is stored and encrypted at rest. Since these are user generated they might potentially contain sensitive or personal identifiable information. This data is stored encrypted at rest.

6. Usually, neither diagrams nor their names contain personal information, as BPMN and DMN models represent business objects. However, these models and their names contain text which is entered freely by end users, in which case this personal will also be processed by our apps and - in the case of names - potentially also be stored.

7. Technical data (such as identifiers, cloud ID, license information and others) that are needed to validate a licensed installation and to perform a secure communication with Confluence are transmitted and stored encrypted at rest.

8. As usual, our apps for Confluence Cloud necessitate communication between end users' browsers and the apps' backend servers to function. To serve these requests, the end users' IP addresses are processed.

All models are saved solely as Confluence page attachments. They are not saved on any servers hosted by viadee.

The data we store is saved in a Google Firestore database that is hosted in GCP multi-region eur3 (Europe: europe-west1 (Belgium), europe-west4 (Netherlands) europe-north1 (Finland)).

Data is encrypted at rest with security standard aes-256-gcm and we have enabled full-disk encryption.

Please care for a regular Confluence Backups, as you models are included there as page attachments.

For the data that is stored by viadee, we perform security backups every 7 days. These backups are held for another 30 14 days and are stored securely with GCP. After this time, the data will deleted and cannot be recovered.

We are operating application servers in Germany, USA, and China (Hong Kong). Requests are always routed to the nearest cluster via DNS routing, meaning that e.g. customers from the EU Europe will always communicate with our servers in Germany (Frankfurt).

The BPMN Modeler and DMN Modeler for Confluence Cloud do not collect any personal information.

We store user input data, which is not under our control and might contain personal data. (see Which data is stored by the app?)

All models are saved solely as Confluence page attachments. They are not saved on any servers hosted by viadee.

How to configure Data Residency for Confluence Cloud and decide where your in-scope product data is hosted, is described by Atlassian at https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/.

You find the privacy policy for our products and services at https://www.viadee.de/en/privacypolicy/.