Data Processing Agreement (DPA)
Agreement under Art. 28 GDPR between you as the controller and vivaXite as the processor.
This is a translation for your convenience. In case of doubt, the German version prevails.
Parties
Controller (client): the company using the Tenant Cockpit, as stated in the order or licence process.
Processor (contractor): vivaXite e.U. (owner Ing. Thomas Bernhard, MBA), Winkelberggasse 240, 2392 Grub im Wienerwald, Austria, VAT ID ATU79768912, company register no. FN 611470x, Regional Court Wiener Neustadt. Data protection contact: gdpr@tenant-cockpit.com.
This agreement under Art. 28 GDPR supplements the Terms of Use and takes effect upon acceptance by both parties. On request it can be requested here as a signed PDF.
1. Subject matter and duration
On behalf of the controller, the processor processes personal data as part of the “Tenant Cockpit” service (analysis of metadata of the controller's Microsoft 365 tenant, reports, alerts, questions to owners). The agreement applies as long as the controller uses the Tenant Cockpit and ends at the latest when the connection is disconnected or the licence ends.
2. Nature, purpose, data and data subjects
| Nature and purpose | Reading, storing, analysing and displaying administrative data of the tenant; sending reports, alerts and questions to owners by email |
|---|---|
| Data categories |
|
| Data subjects | Employees, guests and other users as well as owners of objects in the controller's tenant |
3. Obligations of the processor
- Instructions: processing takes place only on documented instructions of the controller (this agreement, the settings in the Tenant Cockpit). If the processor considers an instruction unlawful, it informs the controller without undue delay.
- Confidentiality: only persons committed to confidentiality have access.
- Security: the processor takes the measures under Art. 32 GDPR as set out in Annex 1.
- Sub-processors: only those listed in Annex 2 may be used. The processor announces changes at least 30 days in advance by email; the controller may object for an important data protection reason. Equivalent obligations are imposed on sub-processors.
- Data subject rights: the processor supports the controller with requests from data subjects and forwards requests it receives without undue delay.
- Assistance: it assists with data protection impact assessments and consultations of the supervisory authority (Art. 32 to 36 GDPR) where necessary and reasonable.
- Breaches: it reports personal data breaches without undue delay, usually within 48 hours of becoming aware, together with the available information. Reporting channel: by email to the contact address named by the controller, otherwise to the address the controller provided when concluding the contract; incident reports from the controller to the processor go to support@tenant-cockpit.com.
- Deletion: “Disconnect” in the Tenant Cockpit immediately deletes all stored tenant data. Only the tenant ID and tenant name with the status “disconnected”, the contract data (licence or Marketplace subscription with the licensee's user name) and the note that the trial was used remain. Backups of the database provider are overwritten according to its regular retention.
- Evidence and audits: it provides the information needed to demonstrate compliance and allows audits, including by auditors mandated by the controller, after timely notice (at least 14 days) and during normal business hours.
- Third countries: processing takes place in the EU or in Switzerland (adequacy decision). There is no transfer to other third countries.
4. Obligations of the controller
The controller is responsible for the lawfulness of the processing and for informing data subjects. It grants consent in Microsoft Entra ID only through authorised persons and names contacts for data protection questions.
5. Liability, law, final provisions
Liability is governed by Art. 82 GDPR; between the parties, the liability rules of the Terms of Use apply. Austrian law applies, the place of jurisdiction is Wiener Neustadt. In case of conflict, this agreement takes precedence over the Terms of Use in data protection matters.
Annex 1: Technical and organisational measures
- Access control: sign-in only via Microsoft Entra ID (including your multi-factor and conditional access policies); guest accounts are excluded; page access via Entra groups; administrator roles separated.
- Tenant isolation: every query is bound to the tenant ID of the verified Microsoft token; database access takes place only on the server side (row-level security enabled).
- Transfer control: encrypted transmission only (HTTPS/TLS); no disclosure to third parties other than the sub-processors.
- Input and access logs: changes to settings, deferrals and owner questions are stored with user and time.
- Availability: operation on Azure and Supabase; backups and restore by the database provider; dependency updates through automated tests and deployments.
- Organisation: commitment to confidentiality, access to production data only when needed and only by the operator.
Annex 2: Sub-processors
| Company | Service | Location |
|---|---|---|
| Microsoft Ireland Operations Ltd. (Azure) | Hosting of the website and API, regular scans | EU |
| Microsoft Ireland Operations Ltd. (Exchange Online) | Sending emails (unless the customer's own sender is used) | EU |
| Supabase Inc., data centre on AWS | Database | Zurich, Switzerland (adequacy decision) |
Annex 3: Remediation add-on
This annex applies additionally to tenants using the optional "Remediation" add-on (automated correction of individual findings from "Configuration & Policies" with the delegated rights of the signed-in person).
| Nature and purpose | Reading and – after confirmation by the signed-in person – writing individual tenant settings via Microsoft Graph, solely with that person's own delegated rights (on-behalf-of); no application permissions, no storage of access tokens on vivaXite servers. |
|---|---|
| Additional data categories |
|
| Access token in the browser | The delegated access token of the Remediation app ("Tenant Cockpit Remediation") is held exclusively in the local browser storage of the signed-in person on the tenant-cockpit.com domain. It is valid only for the Remediation area (permission "Remediation.Execute"), short-lived (access token about one hour; Microsoft limits the refresh token for browser applications to 24 hours), is sent only as a bearer token to our own API and never to third parties, and is removed from the browser on sign-out. It is protected by a strict Content Security Policy (scripts from our own domain only) and by Microsoft Entra (bound to the signed-in person, Conditional Access, revocable at any time). The server additionally checks every change against the person's Microsoft Entra role. |
| Not stored | Access tokens are never written to a database or file on vivaXite servers. The token generated for Microsoft Graph is held for at most 50 minutes in the working memory of the respective function instance and discarded when it ends. |
For sub-processors, technical and organisational measures and all other points, this DPA including Annex 1 and 2 applies unchanged; the certificate for signing this add-on's Microsoft Entra sign-in is kept in Azure Key Vault, the private key never leaves the Key Vault.
