vivaXite

Tenant Cockpit

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 purposeReading, storing, analysing and displaying administrative data of the tenant; sending reports, alerts and questions to owners by email
Data categories
  • Identity data: sign-in name (UPN), display name, email address, and object and tenant ID of users, guests and owners
  • Object data: name, type, owners, member and guest counts, creation, expiry and activity dates of teams, groups, SharePoint sites, Power Platform and Power BI objects, app registrations and enterprise applications
  • Security data: role assignments, sign-in security (MFA status), Secure Score and Defender findings, domains and their configuration
  • Device data: device name, operating system, compliance status and assigned user
  • Storage data: usage and size trend of SharePoint sites
  • Licence data: licence assignment and usage
  • Usage data in the Tenant Cockpit: settings, deferrals, answers to owner questions and a change log with user and time
Keine Inhalte von Dateien, E-Mails oder Chats. Keine besonderen Data categories (Art. 9 DSGVO).
Data subjectsEmployees, guests and other users as well as owners of objects in the controller's tenant

3. Obligations of the processor

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

Annex 2: Sub-processors

CompanyServiceLocation
Microsoft Ireland Operations Ltd. (Azure)Hosting of the website and API, regular scansEU
Microsoft Ireland Operations Ltd. (Exchange Online)Sending emails (unless the customer's own sender is used)EU
Supabase Inc., data centre on AWSDatabaseZurich, 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 purposeReading 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
  • Change log: the affected setting, the executing person, the time, the result (successful/denied/failed), the smallest possible excerpt of the value before and after the change, and – if rejected by Microsoft Graph – the requested Microsoft Entra role.
  • Consent status: the version of this annex and of the terms addendum, with the name and time of the consenting person.
Access token in the browserThe 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 storedAccess 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.