16.2 Data Protection & Privacy
Last updated: 18 September 2026
Scope and responsibility
This notice covers the OLIVE handbooks and the hosted OLIVE platform, connectivity editor and Keycloak sign-in service operated by BOC Products & Services AG, Operngasse 20b, 1040 Wien, Austria. Contact: olive-support@boc-group.com. See the Impressum.
BOC is the controller for processing whose purposes and means it determines, such as its own service administration and security. For personal data processed in connectivity content on a tenant's instructions, the tenant's controller information and the applicable data processing agreement also apply. Customer-operated installations require the customer's own notice.
The software settings described below are defaults, not evidence of the settings or retention in a particular running installation. Before using this notice for a production deployment, the operator must verify hosting recipients, international transfers and effective retention. These facts cannot be established from editor source code alone.
Data and purposes
| Processing | Data involved | Purpose and legal basis where BOC is controller |
|---|---|---|
| Accounts and access control | Account identifier, username, email, tenant membership, roles, authentication and session information | Authorised access and tenant administration; Article 6(1)(f) GDPR, legitimate interests in providing a secure business service to the tenant and its authorised staff. Article 6(1)(b) applies where processing is necessary for a contract with the individual concerned. |
| Service delivery and support | Requests, connectivity definitions and content submitted by users, support correspondence | Deliver requested functionality and resolve support requests; Article 6(1)(f) for operating and supporting the tenant's service, or Article 6(1)(b) where the individual is a contracting party. Tenant-controlled content is processed under the applicable data processing agreement. |
| Security and diagnostics | IP address, request metadata, timestamps, error information, security/admin events, configured backend logs and telemetry | Detect abuse, investigate incidents and maintain service reliability; Article 6(1)(f), legitimate interests in protecting accounts, tenant data and service availability. |
| Statutory obligations | Records required by the applicable obligation | Article 6(1)(c), where a specific legal obligation requires processing. This does not authorise unrelated logging or indefinite retention. |
Authentication information is necessary to access the restricted production service. Without it, access cannot be provided. Account data may be supplied by your tenant administrator or configured identity provider. Access decisions use assigned tenant membership and roles.
Cookies and browser storage
Storing or accessing information on a device is governed by § 165(3) TKG 2021. Strictly necessary sign-in and security storage does not require cookie consent. This exemption does not automatically cover every preference or optional technology.
| Storage / provider | Purpose and location | Lifetime / removal |
|---|---|---|
| Keycloak sign-in cookies / platform operator | Maintain the authentication flow and authenticated session on the sign-in host. Typical names include AUTH_SESSION_ID, KC_RESTART, KEYCLOAK_IDENTITY and KEYCLOAK_SESSION; the exact inventory depends on the deployed Keycloak version and enabled features. | Depends on the flow, realm session settings and Remember Me choice. Inspect the deployed cookies for their actual Domain, Expires and Max-Age values. |
| Gateway and CSRF security cookies / platform operator | Maintain access through the authentication gateway and protect requests on the platform host. | Determined by the deployed gateway and backend configuration; separate from Keycloak session timeouts. |
sensitiveDataAuthHash in sessionStorage / editor | Additional authorisation for access to sensitive data, on the editor origin. | Browser page session; cleared by the editor's logout action. |
ui_settings_view_mode in localStorage / editor | Remember the selected editor view on the editor origin. | No built-in expiry; cleared by the editor's logout action or clearing site data. |
olive.monacoEditor.settings in localStorage / editor | Remember console layout and editor preferences on the editor origin. | No built-in expiry; cleared by the editor's logout action, overwritten when settings are reset, or removed by clearing site data. |
olive.bulk.selectedIds in localStorage / editor | Restore selected connectivity-element identifiers on the editor origin. | No built-in expiry; removed when selection is empty, by the editor's logout action, or by clearing site data. |
The realm import defaults are an 8-hour SSO idle timeout, 24-hour SSO maximum lifetime, and 5-minute access-token lifetime. Remember Me is enabled in the import template. These are session/token settings, not a promise that every cookie expires at these times; existing realms and deployment overrides may differ.
The current editor persists the preferences and selection listed above. The operator must assess their necessity and provide an opt-in or change the persistence behaviour where required before production use. Clearing browser data can reset preferences and require sign-in again. A privacy-notice link or continued use is not consent.
No advertising or analytics consent mechanism is introduced by the legal-link feature. Additional analytics, tracking or other non-essential storage must be assessed separately and must not start before any required consent.
External resources and recipients
The handbooks are hosted on GitLab Pages. The editor currently permits and uses externally loaded Monaco resources through cdn.jsdelivr.net. Loading such resources sends network data, including the visitor's IP address and request metadata, to the CDN infrastructure; this is different from merely displaying a link. Self-hosting those resources avoids that third-party request.
Authorised operating and support staff and the hosting, identity, logging and monitoring providers configured for the installation may receive data necessary for their roles. Tenant administrators manage their users and access rights. The operator must identify the actual providers, processing locations, and any transfers outside the EEA and their applicable safeguards in the deployment-specific information. A link to a provider's website alone does not establish GDPR transfer compliance.
Retention
Account data is retained while needed for authorised access and tenant administration, then deleted or restricted when no longer necessary, subject to applicable contractual and statutory retention requirements. Tenant content follows the tenant's instructions and the applicable agreement, including deletion and backup arrangements.
Browser-storage lifetimes are described above. The setup chart requests 180 days of Keycloak admin-event retention by default. If the running Keycloak version does not support that setting, the setup script warns and external deletion/retention management is required. Logs, traces, gateway sessions and backups have separate retention settings. The earlier blanket statement of 90 days for technical data is not a verified platform-wide limit.
Your rights and contact
Subject to the GDPR's conditions, you may request access, rectification, erasure, restriction and data portability. You may object to processing based on legitimate interests on grounds relating to your particular situation. Where processing relies on consent, you may withdraw it at any time without affecting the lawfulness of processing before withdrawal.
Contact olive-support@boc-group.com. For tenant-controlled data, contact your tenant's controller; we can help route the request. You may lodge a complaint with the Austrian Data Protection Authority or another competent supervisory authority.
The applicable framework includes the GDPR, the Austrian DSG and TKG 2021. We update this notice when processing changes; updates do not themselves constitute user consent.