HIVE SECURE ID d.o.o.

Terms of Use and End-User Licence Agreement (EULA)

Hive MFA

Final version for publication on the company website, Google Play Store and Apple App Store.

Document owner	Hive Secure ID d.o.o.
Product	Hive MFA / Hive mobile authenticator
Version	1.0
Effective date	27 July 2026
Language	English
Status	Final legal version

---

Contents

1. Subject matter, scope and acceptance
2. Definitions
3. Hive platform and scope of the mobile application
4. Relationship with the customer organisation
5. Eligibility and authority
6. Account and device enrolment
7. TOTP accounts, secrets, synchronisation and recovery
8. Push authentication and request context
9. Biometric and local device authentication
10. FIDO2, WebAuthn, passkeys and passwordless access
11. Adaptive authentication, device posture and session governance
12. External accounts and third-party services
13. User security obligations
14. Acceptable and prohibited use
15. Limited licence
16. Licence restrictions and vulnerability reporting
17. Devices, permissions and network connectivity
18. Availability, maintenance and service changes
19. Updates and supported versions
20. Support
21. Account lifecycle, deregistration and deletion
22. Privacy and data protection
23. Intellectual property and open-source components
24. Feedback
25. Third-party services and components
26. Suspension and termination
27. Security limitations of MFA and organisational responsibility
28. Warranties
29. Limitation of liability
30. Mandatory consumer rights
31. Export controls and sanctions
32. Changes to these Terms
33. Governing law and dispute resolution
34. Other contractual provisions
35. Apple App Store-specific provisions
36. Google Play-specific provisions
37. Contact and notices

---

1. Subject matter, scope and acceptance

These Terms of Use and End-User Licence Agreement, together referred to as the “Terms”, govern the download, installation, activation, access to and use of the Hive MFA mobile application, its updates, related software components, user documentation, support channels and those Hive Secure ID platform functions that are directly connected with user authentication.

Hive MFA may also be described on the website as the “Hive mobile authenticator”. In these Terms, both names refer to the same mobile application unless the context clearly indicates otherwise.

The Service is provided by Hive Secure ID d.o.o., Karađorđev trg 11, 11080 Belgrade – Zemun, Republic of Serbia, website hivesecureid.com, email [email protected], privacy contact [email protected].

By downloading, installing, activating or using the Application, the user confirms that the user has read, understood and accepted these Terms. A person who does not accept the Terms must not use the Application.

Use of broader Hive IGA, Access Management, SSO, JML, recertification, segregation-of-duties, role-mining or other enterprise modules may additionally be governed by an agreement between Hive and the customer organisation. These Terms do not replace such agreement.

2. Definitions

Term	Meaning
Application / Hive MFA	The Hive Secure ID mobile authentication application, including updates and related components.
Hive / we / us	Hive Secure ID d.o.o., Belgrade – Zemun, Republic of Serbia.
Customer organisation	A legal entity, sole trader, public authority or other organisation that provides or manages the user’s access to the Hive platform.
User	A natural person who uses Hive MFA in the user’s own name or under the authority of a customer organisation.
Device	A supported mobile or other compatible device on which the Application is installed or on which a supported authenticator resides.
Authentication secret	A TOTP seed/shared secret, private key, recovery code, activation code or other information whose disclosure may enable unauthorised authentication.
External account	An account with a third-party service for which Hive MFA is used as a TOTP, FIDO2/WebAuthn or other authentication factor.
Service	Hive MFA and the related Hive platform functions that enable enrolment, authentication, device management and security controls.

3. Hive platform and scope of the mobile application

Hive is a modular identity and access management platform. The Hive MFA mobile Application is the authentication component of the platform and may be used as a standalone authenticator for supported TOTP accounts or as an authentication factor for systems connected to the Hive Access Management module.

Depending on the version, configuration, organisational licence and supported device, the Application may enable:

• TOTP time-based one-time passwords;
• push approval or rejection of authentication requests;
• biometric unlocking or local confirmation using device functions;
• FIDO2, WebAuthn, passkey and passwordless authentication;
• enrolment and deregistration of devices and authenticators;
• risk-based step-up authentication and additional verification where risk is elevated;
• device integrity and security-posture checks;
• security notifications and limited information about authentication activity;
• synchronisation of selected data where that function is enabled;
• reauthentication, session restriction or session termination under the customer organisation’s policy.

A particular function may be unavailable, restricted or configured differently for different organisations, countries, devices or Application versions. Product descriptions on the website provide a general overview and are not an unconditional warranty that every function is included in every implementation.

4. Relationship with the customer organisation

Hive MFA is primarily intended for users whose digital identity is associated with an organisation using the Hive platform. The customer organisation may determine eligibility to use the Service, systems accessible to the user, authentication methods, security requirements, step-up rules, permitted devices, session duration, log-retention periods, suspension and account termination.

If documents conflict, the following order of precedence applies:

1. mandatory law;
2. the data processing agreement for processing on the organisation’s instructions;
3. the master or SaaS agreement between Hive and the organisation;
4. these Terms governing the end user’s use of the Application.

As a rule, the customer organisation, not Hive, decides whether access to a particular enterprise application, resource or transaction is granted. Hive technically enforces configured policies within the scope of the contracted Service.

5. Eligibility and authority

A user may use Hive MFA only if the user has the necessary legal capacity, valid organisational authority where required, uses the user’s own assigned account, provides accurate information and complies with applicable law and the organisation’s security requirements.

A person using the Application on behalf of a legal entity confirms that the person is authorised to act within the assigned identity and access rights. The right to use the Service ends when the employment, contractual, customer or other relationship on which the account was based ends, unless the organisation determines otherwise.

The Application is not directed or marketed to children. A minor may use the Application only where lawful and authorised by the relevant organisation and, where required, by a parent or legal guardian.

6. Account and device enrolment

Enrolment may include receiving an invitation or activation link, scanning a QR code, entering an activation code, confirming an email address, binding a device, generating a cryptographic credential, enabling notifications and configuring local device protection.

The user must not enrol a public, shared, rooted, jailbroken, compromised or unauthorised device, an emulator or an environment that does not meet the organisation’s requirements. Activation codes, QR codes, enrolment links and recovery information must be treated as confidential.

Hive or the customer organisation may reject enrolment or require additional verification where the device, account, network or enrolment flow does not meet applicable security conditions.

7. TOTP accounts, secrets, synchronisation and recovery

Hive MFA may generate time-based one-time passwords for Hive and external accounts supporting the TOTP standard. A TOTP account may include an issuer name, account label, username or email address, algorithm, number of digits, validity period and enrolment secret.

A TOTP seed/shared secret and a current one-time code are authentication secrets. The user must not share them, copy them into unprotected notes, send them by email, place them in a support ticket or otherwise make them available to an unauthorised person.

Depending on the configuration, a TOTP secret may remain only in secure device storage or may be stored and synchronised in encrypted form for authorised recovery, transfer or token-management purposes. A “last synced” or similar status does not guarantee that every token can be recovered or that every item of data has been transferred to another device.

The user must retain recovery codes issued by an external service and check available recovery methods before replacing, resetting or losing a device. Hive does not guarantee recovery of a locally stored TOTP token, private key or information that was not included in an approved synchronisation or backup process.

Deleting a token from the Application may prevent access to an external account. Before deletion, the user is responsible for establishing another factor or recovery method with the relevant service.

8. Push authentication and request context

A push request may display the requesting system or application, request time, device or browser information, an approximate network location, a number-matching code and other information intended to help the user assess the request.

The user must approve only a request personally initiated by the user and consistent with the expected action. Unexpected, repeated, unusually timed or unclear requests must be rejected and reported to the customer organisation or Hive.

Approval may enable access to a business system, information or transaction. Hive is not responsible for consequences where the user intentionally or through gross negligence approves a request that the user did not initiate, except to the extent liability cannot lawfully be excluded.

Delivery of push notifications depends on Apple Push Notification service, Firebase Cloud Messaging, network connectivity, device settings and other factors. A delayed or undelivered push message does not necessarily mean that the authentication system has failed; an alternative method may be available depending on the configuration.

9. Biometric and local device authentication

Where enabled, the Application may use biometric or device-credential functions provided by the operating system to unlock the Application locally or confirm an authentication action.

Hive does not receive or store raw facial images, fingerprints or biometric templates. Matching is normally performed by the operating system or a secure hardware environment, and the Application receives only a technical success or failure result.

The user is responsible for controlling whose biometrics are enrolled on the Device. A biometric belonging to another person and enrolled on the same Device may, depending on the Device and policy, permit confirmation. Where this risk is unacceptable, the user should use a PIN, password or another approved method.

10. FIDO2, WebAuthn, passkeys and passwordless access

Where enabled, Hive MFA and the Hive platform may register and use FIDO2/WebAuthn credentials, passkeys or other cryptographic authenticators. The server may store a credential identifier, public key, user handle, relying-party data, status and authentication metadata.

The private key normally remains in the Device, a secure hardware element, an external authenticator or a credential manager. Hive cannot extract a private key that has been properly generated as a non-exportable credential.

A passkey may be device-bound or synchronised through Apple, Google or another credential provider. Such synchronisation is controlled by the relevant provider under its own terms. Deleting a public credential on the Hive side may not automatically remove the passkey from the Device or the provider account; the user must also remove it from that environment where necessary.

Hive does not warrant compatibility with every authenticator, browser, operating system or credential provider. The customer organisation may restrict approved authenticator types, attestation characteristics and recovery methods.

11. Adaptive authentication, device posture and session governance

The Hive platform may apply adaptive policies and risk-based step-up authentication using combinations of signals such as device-registration status, Application integrity, root/jailbreak or emulator indicators, operating-system version, security-patch level, IP and network characteristics, frequency and timing of sign-in, failed attempts, device changes, resource sensitivity, prior security events and session status.

Under the customer organisation’s policy, the system may require an additional factor, biometric confirmation, credential re-entry or re-enrolment; delay or reject authentication; alert an administrator; restrict a session; or terminate a session.

Risk assessment is not infallible and may produce false positive or false negative results. The user may request a review from the organisation managing the account. Hive and the organisation may withhold details of detection logic where disclosure would enable circumvention of security controls.

A device-posture check does not give Hive a right to access private photographs, messages, contacts or the content of other applications, unless a particular processing activity is expressly necessary, lawful, technically enabled and clearly explained to the user in advance.

12. External accounts and third-party services

Hive MFA may be used for TOTP, FIDO2/WebAuthn or other factors with third-party services, including enterprise, cloud, development or other digital services. Hive does not own or operate those accounts unless expressly stated otherwise.

Third-party names and marks displayed in the Application, on the website or in promotional materials belong to their respective owners. Their display does not imply partnership, endorsement or affiliation unless such relationship is expressly disclosed.

Hive cannot reset an external-service password, recover an external recovery code, restore a deleted external account or guarantee acceptance of a TOTP code or passkey by a third-party service. The user is responsible for complying with that service’s terms and maintaining an alternative recovery method.

13. User security obligations

The user must:

• keep the Device under appropriate physical control and use a screen lock;
• protect PINs, passwords, passkeys, recovery codes, TOTP seeds and other authentication secrets;
• before approval, verify the service name, time and available context of the request;
• reject and report unexpected or suspicious requests;
• keep the operating system, Application and security patches up to date;
• not use the Application on a rooted, jailbroken or compromised Device;
• promptly deregister a lost, stolen, sold or compromised Device;
• not share the Device or registered factor with another person without express authorisation;
• comply with the organisation’s security policies and reasonably cooperate with incident investigations.

Repeated push requests must not be approved merely to stop the notifications. Such a pattern may indicate MFA fatigue or a social-engineering attack.

14. Acceptable and prohibited use

The user may use the Service only lawfully, within the user’s authority and for its intended authentication purpose. In particular, the user must not:

• impersonate another person or use another person’s identity, account or registered Device;
• approve or facilitate a fraudulent or unauthorised transaction;
• circumvent access policies, device-posture checks or step-up controls;
• automate approval of push requests or intercept authentication messages;
• introduce malware, disrupt availability or attempt unauthorised access to the platform;
• scan, penetration test or conduct security research without written authorisation;
• use the Service in breach of sanctions, export-control law or third-party rights;
• use the Application for surveillance or processing without an appropriate legal basis.

15. Limited licence

Subject to compliance with these Terms, Hive grants the user a limited, personal, revocable, non-exclusive, non-transferable and non-sublicensable licence to install and use the Application on a supported Device owned or controlled by the user, solely for authorised authentication and security purposes.

The Application is licensed, not sold. All rights not expressly granted remain with Hive and its licensors. The right to use may depend on the customer organisation’s active agreement, an allocated licence and the status of the user account.

16. Licence restrictions and vulnerability reporting

Except where mandatory law expressly permits otherwise or Hive gives prior written authorisation, the user must not:

• copy, distribute, resell, rent or sublicense the Application;
• modify, translate or create derivative works;
• reverse engineer, decompile or attempt to extract source code;
• extract or attempt to obtain cryptographic keys or security mechanisms;
• circumvent licence, authentication, integrity or anti-tampering controls;
• remove copyright, trade mark or other proprietary notices;
• use technical-analysis results for attack, abuse or unauthorised exploitation.

A suspected vulnerability or security issue should be responsibly reported to [email protected] with the subject “Security Vulnerability”. The user must not access another person’s data, alter or delete data, cause service disruption, use social engineering or publicly disclose details before a reasonable verification and remediation period has elapsed.

17. Devices, permissions and network connectivity

The user is responsible for a compatible Device, a supported operating system, internet or mobile connectivity and any data-transfer charges. Refusal of a permission may prevent the relevant function from operating.

Permission / capability	Purpose and limitation
Notifications	Delivery of push authentication requests and security notifications.
Camera	Scanning a QR code to enrol a TOTP account, Device or credential; the image is not used for another purpose unless clearly stated.
Biometric / device credential	Local unlocking of the Application or confirmation of an action through the Device operating system.
Network access	Communication with the Hive platform, customer-organisation systems and supported services.
Device-integrity information	Assessment of Device and Application status to the extent required by the security policy.

18. Availability, maintenance and service changes

Hive aims to provide appropriate availability, security and performance but does not guarantee uninterrupted or error-free operation. The Service may be affected by maintenance, network outages, push-service delays, operating-system changes, customer-system outages, cyberattacks, force-majeure events and other circumstances outside Hive’s reasonable control.

Hive may change the interface, technical requirements, security controls, supported methods or availability of particular functions. A material change affecting user rights will be communicated where legally or operationally required.

A service level agreement applies only where included in a separate agreement with the customer organisation and does not create a direct right for an end user unless expressly agreed or required by law.

19. Updates and supported versions

Hive may issue patches, corrections, security updates and new versions. Updates may be installed automatically depending on Device and app-store settings.

The user must install security-critical updates within a reasonable period or within a period set by the customer organisation. Hive may block an outdated or insecure version where necessary to protect users, customer organisations or the platform.

Support for a particular operating system, Device, authenticator or SDK may end when it is no longer secure, maintained or technically compatible.

20. Support

A support request may be submitted through the customer organisation, an approved support channel or [email protected]. The user must not provide passwords, current TOTP codes, seed values, private keys or recovery codes in a support request.

Hive may request technical information reasonably necessary for diagnosis, including the Application version, Device, operating system, time of the event and transaction identifier. Support does not entitle Hive to request a complete authentication secret.

Apple and Google have no obligation to provide support for Hive MFA.

21. Account lifecycle, deregistration and deletion

Where an account is managed by a customer organisation, the organisation normally determines creation, suspension, reactivation and deletion of the business identity. The user may deregister a Device, remove a token or request deletion of data to the extent permitted by the configuration and applicable law.

Uninstalling the Application does not automatically delete a server-side account, audit logs, credentials on other Devices or records held by the customer organisation. Deleting a passkey or TOTP token in one environment may not remove a copy from another authorised Device, backup or credential provider.

If the Application enables direct creation of a Hive account, the user will be provided with a method to initiate deletion in the Application and through a publicly accessible web resource. Data that must be retained for security, fraud prevention, legal obligations or legal claims may be retained on a restricted basis for the periods described in the Privacy Policy.

Before deregistration or deletion, the user should establish another approved access factor to avoid losing access to an external or business account.

22. Privacy and data protection

Hive processes personal data in accordance with the applicable Hive MFA Privacy Policy and data-protection law. The Privacy Policy explains Hive’s roles as controller or processor, data categories, TOTP and FIDO/WebAuthn data, device-posture and risk signals, legal bases, recipients, international transfers, retention, deletion and individual rights.

Where a customer organisation manages the account, it may separately process employment, customer-relationship, authority, access-right and authentication-history information. The user should also review that organisation’s privacy notice.

Acceptance of these Terms does not constitute consent for processing that requires another legal basis and does not waive any statutory data-protection right.

23. Intellectual property and open-source components

Hive MFA, the Hive platform, source and object code, documentation, design, databases, trade marks, logos and other materials are owned by Hive or its licensors and protected by intellectual-property law.

Open-source and third-party components remain governed by their own licences. Where such a licence grants broader rights in relation to a particular component, that licence applies only to that component.

24. Feedback

The user may voluntarily provide suggestions, comments or ideas. Unless otherwise agreed in writing, Hive may use them to develop and improve products without payment, provided that Hive does not disclose confidential information or publicly identify the user without an appropriate legal basis.

25. Third-party services and components

The Service may depend on Apple App Store, Google Play, Apple Push Notification service, Firebase Cloud Messaging, operating systems, mobile networks, cloud infrastructure, crash or analytics services, credential managers, external authenticators and customer-organisation systems.

Third parties operate under their own terms and privacy practices. The user must comply with applicable Device, network, app-store, credential-provider and external-service terms. Hive is not responsible for an independent third-party service or its interruption, except to the extent liability cannot lawfully be excluded or Hive has expressly accepted responsibility in a separate agreement.

26. Suspension and termination

Hive or the customer organisation may suspend, restrict or terminate access where the user is no longer authorised, a Device or account is compromised, misuse or fraud is suspected, the user breaches these Terms, continued access creates a security risk, suspension is required by law or the customer organisation’s agreement ends.

The user may stop using the Application by deregistering the Device and uninstalling it. Termination does not affect accrued rights or obligations, required retention of security and audit data, intellectual-property rights, confidentiality or provisions intended by their nature to survive termination.

27. Security limitations of MFA and organisational responsibility

MFA materially reduces certain account-compromise risks but does not eliminate phishing, social engineering, malware, Device takeover, compromise of email or recovery processes, user approval of a fraudulent request, vulnerabilities in connected systems or misconfiguration.

The customer organisation remains responsible for identity lifecycle management, entitlement allocation, resource classification, selection of policies and risk thresholds, user education, incident response, recovery procedures and controls outside Hive’s contracted responsibility.

The Application is not a substitute for a complete IAM, PAM, endpoint-security, monitoring, security-awareness or other proportionate control framework.

28. Warranties

To the maximum extent permitted by law, the Service is provided on an “as available” basis. Hive does not warrant uninterrupted operation, prevention of every attack, immediate delivery of every push request, recoverability of every token, operation of every function on every Device or compatibility with every external service.

Nothing in these Terms excludes warranties or rights that cannot lawfully be excluded, or obligations expressly accepted by Hive in a separate agreement.

29. Limitation of liability

Nothing excludes or limits liability for death or personal injury where exclusion is prohibited, fraud, intentional unlawful conduct, gross negligence where it cannot lawfully be limited, breach of mandatory data-protection or consumer law, or any other liability that cannot legally be excluded.

For a user acting for business or professional purposes, Hive is not liable under these Terms for indirect or consequential loss, loss of profit, revenue, business opportunity, anticipated savings, reputation, or loss arising predominantly from a Device, external service, organisational configuration or conduct outside Hive’s reasonable control.

Contractual limits between Hive and the customer organisation are governed by their separate agreement. The user is responsible for loss caused by the user’s intentional, fraudulent or unlawful misuse, to the extent permitted by law.

30. Mandatory consumer rights

Where the user is a consumer, these Terms do not reduce rights granted by mandatory law in the country of the user’s habitual residence. Warranty, liability, governing-law and jurisdiction clauses apply only to the extent permitted by such law.

Where the Application is provided by an employer or another organisation exclusively for business access, the relationship may primarily be business or employment-related rather than consumer-related.

31. Export controls and sanctions

The user confirms that the user is not prohibited by applicable law from using the Service and will not export, re-export or use the Application in breach of applicable sanctions or export-control rules. Hive may restrict access where reasonably necessary for compliance.

32. Changes to these Terms

Hive may update these Terms due to changes in functionality, security, law, Apple or Google requirements, the business model or operational processes. The current version will be published on the website and made available in the Application where appropriate.

Appropriate notice will be given of material changes that significantly affect user rights, and renewed acceptance will be requested where legally required. Continued use constitutes acceptance only to the extent permitted by law.

33. Governing law and dispute resolution

These Terms are governed by the laws of the Republic of Serbia, without prejudice to mandatory consumer, data-protection and jurisdiction rules that cannot be excluded by contract.

For business and professional users, the competent courts in Belgrade have jurisdiction unless a separate agreement or mandatory law provides otherwise. A consumer may bring proceedings before a court having jurisdiction under mandatory consumer law.

Before commencing proceedings, the parties should attempt to resolve the matter through good-faith communication, except where delay could prejudice a right, a limitation period or security.

34. Other contractual provisions

If a provision is invalid or unenforceable, the remaining provisions remain effective, and the invalid provision will be interpreted or replaced so as to achieve its lawful purpose as closely as possible.

Hive’s failure to enforce a provision is not a waiver. The user may not assign rights or obligations without Hive’s prior consent. Hive may transfer the agreement as part of a corporate change, reorganisation, sale of business or transfer to an affiliate, while preserving the user’s statutory rights.

These Terms, the Privacy Policy and the applicable customer-organisation agreement constitute the relevant contractual framework. An oral statement does not amend these Terms unless confirmed in writing by an authorised representative.

35. Apple App Store-specific provisions

35.1. Relationship with Apple

These Terms are concluded between the user and Hive, not between the user and Apple. Hive, not Apple, is responsible for the Application and its content. These Terms must not conflict with applicable Apple Media Services Terms and Conditions or Usage Rules.

35.2. Scope of licence

The licence for the Apple version is limited to a non-transferable right to use the Application on Apple-branded products owned or controlled by the user and as permitted by Apple Usage Rules. The Application may be accessible through related accounts via Family Sharing, volume purchasing or other Apple functionality where permitted.

35.3. Maintenance and support

Hive is solely responsible for maintenance and support to the extent required by these Terms or applicable law. Apple has no obligation to provide maintenance or support.

35.4. Warranty

Hive is responsible for applicable warranties to the extent they cannot validly be excluded. If the Application fails to conform to an applicable warranty, the user may notify Apple, and Apple may refund the purchase price paid for the Application. To the maximum extent permitted by law, Apple has no other warranty obligation, and remaining claims concerning non-conformity are Hive’s responsibility.

35.5. Product claims

Hive, not Apple, is responsible for addressing claims by the user or a third party relating to the Application, including product-liability, regulatory-compliance and consumer, privacy or similar claims, within the limits of applicable law.

35.6. Intellectual property

If a third party claims that the Application or its use infringes intellectual-property rights, Hive, not Apple, is responsible for investigation, defence, settlement and discharge of that claim.

35.7. Legal compliance

The user represents that the user is not located in a region subject to a United States Government embargo or designated by the United States Government as supporting terrorism and is not listed on any United States Government prohibited or restricted-party list.

35.8. Developer information

Questions, complaints or claims concerning the Application should be directed to: Hive Secure ID d.o.o., Karađorđev trg 11, 11080 Belgrade – Zemun, Republic of Serbia; email: [email protected]; telephone: [INSERT OFFICIAL TELEPHONE NUMBER BEFORE APP STORE PUBLICATION].

35.9. Third-party terms

The user must comply with applicable third-party terms, including mobile-network, internet-service-provider, operating-system, credential-provider and Apple-service terms.

35.10. Third-party beneficiary

Apple and its subsidiaries are third-party beneficiaries of these Apple-specific provisions. Upon the user’s acceptance of these Terms, Apple has the right to enforce those provisions against the user as a third-party beneficiary.

36. Google Play-specific provisions

These Terms are concluded between the user and Hive, not between the user and Google. Hive is responsible for the Application, its content, maintenance, support and user claims. Google has no obligation to provide support for Hive MFA.

The user must comply with applicable Google Play terms. Refunds, where applicable, may be subject to Google Play procedures and mandatory law.

Where the Application permits creation of an account, the user will be provided with a clear method to initiate deletion of the account and associated data within the Application and through an appropriate public web resource, together with an explanation of data that must be retained for legitimate reasons.

Nothing in this section imposes an obligation or liability on Google beyond that expressly established by applicable Google terms or mandatory law.

37. Contact and notices

Provider	Hive Secure ID d.o.o.
Address	Karađorđev trg 11, 11080 Belgrade – Zemun, Republic of Serbia
Website	https://hivesecureid.com
General enquiries and support	[email protected]
Privacy and DPO	[email protected]
Security vulnerability	[email protected], subject: Security Vulnerability

A notice sent to a contact address provided by the user or customer organisation is deemed delivered when sent unless the sender receives an automated delivery-failure notice. The user and customer organisation must keep contact information current.