ProtectDome · SAMsoric GmbH

ProtectDome privacy policy

Effective date: 8 September 2026. This notice is available at https://protectdome.eu/privacy.

Who operates ProtectDome

ProtectDome is operated by SAMsoric GmbH, Sonnenstraße 12, 8700 Leoben, Austria. Contact samsoric@samsoric.com about personal data or this notice. The Android app is published on Google Play by CodeRabbit GmbH.

Your organization provides your access, assigns permissions, and determines which sites, equipment and incident records you can use. For questions about your organization's monitoring activities and workplace records, contact your organization as well as SAMsoric. This notice describes the ProtectDome service; it does not replace your organization's own information about its monitoring activities.

Data and purposes

Account and access. We process your name, email address, user identifier, organization memberships and permissions to authenticate you, manage access and protect organizational data. Accounts are provisioned by administrators. Authentication is handled by the service's Keycloak identity system.

Incidents and organizational records. We process the comments and notes you choose to add, incident actions and their timestamps, and your association with these records. Authorized members of your organization can see records according to their assigned permissions. ProtectDome displays temperatures, device status, incident history and RGB/thermal evidence supplied by your organization's monitoring equipment. The Android app does not capture photographs, audio or phone location.

Notifications. Android notifications use Google's Firebase Cloud Messaging (FCM). Push registration tokens, Firebase installation identifiers, application version and technical SDK information support delivery and operation of this service. The server associates a registered push token with your account and records whether notifications are authorized. Test notifications can record receipt and opening events. Your organization can configure additional server-side notification channels, including email and safeREACH, to deliver incident information to its chosen recipients.

Technical operation and security. The service processes request and audit logs and diagnostic traces to provide the app, investigate errors, monitor reliability and prevent unauthorized access. These may contain request paths, timestamps, network addresses and browser/device information. Application logging redacts authorization headers, cookies and named secret fields. No advertising SDK or advertising identifier is used in this Android release, and no use of phone location or IP-derived location was identified in the service implementation.

Legal grounds

Where processing is necessary to perform a contract with you, the basis is performance of that contract. Maintaining a secure and reliable organizational service, controlling access and investigating misuse serve legitimate interests. Information may also be processed to meet applicable legal obligations. Your organization is responsible for the legal grounds of the monitoring and employment-related activities it determines. Where consent is the applicable basis, it can be withdrawn for future processing.

Device choices and protected sign-in

Notification permission is optional and can be changed in Android settings. The Firebase SDK may create an installation identifier even if notification permission is declined.

If you enable protected sign-in, the app stores an encrypted session on your device and uses Android's biometric or device-passcode authentication to unlock it. ProtectDome does not receive fingerprint images or face templates. You can disable protected sign-in in the app. The saved session has a seven-day inactivity limit; signing out clears local credentials and attempts to deregister the device's push token.

Service providers and international processing

Core application, identity, database, evidence storage and diagnostic services run on infrastructure operated for SAMsoric: Hetzner in Germany. Authorized service providers process data to supply these services. Your organization controls its members' access and its configured notification recipients.

Google processes information needed for Firebase Cloud Messaging. Firebase processing can involve countries outside the European Economic Area. Google's applicable Firebase data-processing terms describe the transfer mechanisms, including standard contractual clauses where required. See Firebase privacy information and Firebase data-processing terms.

Retention

Account records, organization memberships, incident comments/actions/evidence, and notification registrations have no automatic expiry configured in the application database. Disabling access does not itself erase those records. Their removal must be handled through an account/data request or the organization's service arrangements, taking into account shared incident records and any applicable legal need to retain information.

Application logs and diagnostic traces are configured for seven-day retention. The sensor-event database has a scheduled 90-day retention policy; deletion is performed by the scheduled maintenance job. These periods describe the active services and do not establish the retention of every backup copy.

Backups are retained for up to six months. Personal data removed from active systems can remain in existing backup copies until those copies expire.

Google's Firebase notice states that FCM installation identifiers are retained until the customer requests deletion through the relevant Firebase API, and are then removed from live and backup systems within 180 days. This is Google's stated retention behavior, not a promise that uninstalling ProtectDome automatically removes every server-side record.

Request account and data deletion

Use Request account deletion, available without signing in, or email samsoric@samsoric.com. The app also provides this link on Sign in and Profile. Include your ProtectDome account email and organization name. Write from your account email if you still have access to it; otherwise explain this so your identity can be verified. Do not send your password.

SAMsoric handles verified requests to delete account/profile data, organization memberships, notification registrations and associated personal information. For shared organizational incident records, the request is coordinated with your organization. Where information must be retained for a legal obligation or the establishment, exercise or defence of legal claims, the response identifies the retained categories, reason and applicable period or criteria. Removing the app or signing out is not an account-deletion request.

Your rights

Subject to the conditions in applicable law, you can request access, correction, erasure, restriction of processing and data portability, and object to processing based on legitimate interests. You can withdraw consent where processing relies on it. Send requests to samsoric@samsoric.com; proportionate identity verification may be necessary to protect your data.

You may complain to your competent data-protection authority, including the Austrian Data Protection Authority. We will make updates to this notice available at the policy URL shown above.