Medentic QES Connect EULA

Last updated on March 16, 2026

This End User License Agreement ("Agreement" or "EULA") is a legally binding agreement between you and Medentic LLC, a Bulgarian single-member limited liability company, UIC 207854560, with registered office at Bulgaria, 7000 Ruse, Tsar Ferdinand St. 4, Floor 4, Office 20 ("Medentic", "we", "us", or "our"), governing your download, installation, access to, and use of Medentic QES Connect ("QES Connect").

IMPORTANT: BY DOWNLOADING, INSTALLING, ACCESSING, OR USING QES CONNECT, YOU CONFIRM THAT YOU HAVE READ, UNDERSTOOD, AND AGREE TO BE BOUND BY THIS EULA. IF YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, ACCESS, OR USE QES CONNECT.

1. Acceptance and Scope

1.1. Who is bound.

This EULA applies to the organization, clinic, practice, company, or other professional user that uses QES Connect, and to its authorized personnel who access or operate QES Connect on its behalf.

1.2. Professional context.

QES Connect is intended for authorized professional and business use as a Medentic Platform companion client and not for general personal-use signing scenarios unrelated to Medentic workflows.

1.3. Related terms.

Your use of QES Connect may also be subject to applicable Medentic subscription terms, privacy documentation, data processing terms, and other Platform policies.

2. Definitions

2.1.
"QES Connect" means the Medentic QES Connect software client or application, including updates, patches, enhancements, interfaces, and related materials made available with it.
2.2.
"Platform" means the broader Medentic environment through which accounts, subscriptions, integrations, workflow configurations, audit data, and connected signing or submission processes may be managed or made available.
2.3.
"Organization" means the clinic, company, practice, legal entity, or other authorized business customer using QES Connect.
2.4.
"Authorized User" means a user, employee, contractor, or other person whom the Organization authorizes to use QES Connect on its behalf.
2.5.
"QES Device" means the hardware token, smart card, secure signing device, or comparable secure signing environment that stores or uses the certificate and private key required for qualified or regulated signing operations.
2.6.
"Certificate" means the digital certificate used with the QES Device or secure signing environment.
2.7.
"QTSP" means a qualified trust service provider or equivalent issuer or provider of qualified certificates or related trust services under applicable law.
2.8.
"PIN" means the credential used to unlock, activate, or authorize use of a QES Device or secure signing environment.
2.9.
"PUK" means the credential or recovery code used to reset or unblock a PIN where applicable.

3. License Grant and Availability

3.1. License grant.

Subject to this EULA, Medentic grants you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to download, install, and use QES Connect on compatible systems solely for your internal authorized professional use in connection with the Platform and supported signing or authentication workflows.

3.2. Licensed, not sold.

QES Connect is licensed, not sold. No ownership rights in QES Connect are transferred to you.

3.3. Download availability.

QES Connect may be made available for download without separate charge, but intended use cases, connected workflows, and Platform-linked functionality may depend on an active Medentic account and the applicable subscription tier, enabled feature set, or access level, including free access levels where offered.

3.4. Reservation of rights.

All rights not expressly granted under this EULA are reserved by Medentic and its licensors.

4. Medentic Account, Authorization, and Subscription Dependency

4.1. Authorized Medentic relationship required for connected use.

QES Connect is intended to operate as part of the Platform for users who are already registered and authorized within Medentic.

4.2. Connected functionality depends on account status.

Access to connecting QES Connect to Medentic workflows depends on an active Medentic account and the applicable subscription or enabled access level for the relevant user or Organization.

4.3. Technical possession is not full entitlement.

Although downloaded versions of QES Connect may be technically capable of running, the intended business cases and Platform-connected functionality depend on active Medentic authorization and configuration.

4.4. Suspension or termination of access.

Medentic may suspend, restrict, or terminate connected access or certain features if the underlying account, Organization authorization, subscription, or service relationship no longer supports that access.

5. Intended Professional Use Only

5.1. Platform companion role.

QES Connect is intended to support professional signing, authentication, verification, submission, and regulated-access workflows connected to the Platform.

5.2. No general consumer license.

QES Connect is not licensed as a general-purpose consumer signing utility or as a public signing service independent of Medentic workflows.

5.3. Authorized personnel only.

Only Authorized Users may configure, connect, supervise, administer, or otherwise operate QES Connect on behalf of the Organization.

6. QES Connect Purpose and Nature of the Service

6.1. Purpose of QES Connect.

QES Connect is designed to facilitate the use of third-party certificates, QES Devices, and secure signing environments for:

(a)
local signing of supported document types such as PDF and XML;
(b)
verification and certificate-related workflow support;
(c)
connected signing or regulated authentication workflows through the Platform; and
(d)
supported submission or access actions carried out on behalf of the user within authorized Platform workflows.
6.2. Nature of the service.

QES Connect is a technical facilitation tool and workflow bridge. It does not itself issue certificates or act as the legal source of trust service status.

6.3. No legal advice.

Medentic does not provide legal advice through QES Connect and does not warrant that any given document, submission, organizational process, or use case is legally appropriate for signing.

7. No QTSP Role

7.1. Medentic is not a QTSP.

Medentic is not a qualified trust service provider and does not issue qualified certificates, manage certificate revocation as a trust service provider, or provide qualified trust services in its own name through QES Connect.

7.2. Third-party trust services remain separate.

Certificates, trust status, revocation status, qualified-device status, and related trust-service obligations remain governed by the relevant third-party QTSP or provider and the applicable law.

7.3. QES Connect still facilitates QES workflows.

Nothing in this Section means QES Connect is not intended to facilitate lawful use of third-party issued certificates and QES Devices within supported workflows.

8. Local Signing Mode

8.1. Local signing use.

QES Connect may be used to perform local signing operations for supported document types, including PDF and XML, using the user's available certificate and QES environment.

8.2. No automatic document transmission for local signing.

In local signing mode, the document being signed is not transmitted to the Platform merely because the signing operation is carried out through QES Connect.

8.3. Scope of the local-mode statement.

This local-mode statement does not prevent the Platform from processing account data, workflow status data, diagnostics, or other non-document operational data where relevant to the user's connected use of Medentic services.

9. Connected Signing, Authentication, and Third-Party System Access

9.1. Connected mode.

When an Authorized User or Organization connects QES Connect to the Platform and enables connected workflows, they authorize Medentic and QES Connect to use the connected QES environment within the scope of supported workflows where signing, authentication, regulated access, or submission is required.

9.2. Background or unattended availability.

Where enabled by the user or Organization, QES Connect may remain available for background, queued, or unattended workflow operations through the Platform.

9.3. Examples of supported connected use.

Supported workflows may include, where configured and supported, signing documents or structured payloads, authenticating into third-party regulated systems, performing submissions, or accessing external systems on the user's behalf, including systems such as his.bg and nhif.bg, as non-exhaustive examples.

9.4. User control over availability.

The user or Organization may stop connected availability at any time by disconnecting QES Connect from the Platform, unplugging or disabling the QES Device, changing local configuration, or otherwise preventing QES Connect from servicing connected requests.

10. Private Key, PIN, PUK, and Local Credential Handling

10.1. Private key non-custody.

Medentic does not take custody of the private key. The private key remains on the QES Device or secure signing environment used by the user.

10.2. PIN and PUK transmission.

PINs, PUKs, and private keys are not transmitted to Medentic.

10.3. Local PIN convenience features.

QES Connect may offer local PIN storage or convenience features on the user's system. Where offered, such storage is intended to rely on secure local credential-storage mechanisms made available by the operating system or comparable secure local facilities.

10.4. No PUK storage obligation.

Medentic does not undertake to store PUKs through QES Connect.

10.5. Credential responsibility.

The user and Organization remain responsible for PIN custody, credential hygiene, device access, token access, recovery procedures, and the consequences of loss, compromise, blocking, misuse, or unauthorized use of credentials or devices.

11. User and Organization Responsibilities

11.1. Authority over the certificate and signing environment.

The user and Organization are responsible for ensuring that the relevant user lawfully controls, possesses, or is authorized to use the relevant certificate, QES Device, and signing environment.

11.2. Authority to sign or authenticate.

Medentic does not verify whether a user has corporate authority, representative authority, mandate, or legal power to sign a particular document, submission, or access request. That responsibility remains with the user and Organization.

11.3. Appropriate use of connected workflows.

The user and Organization are responsible for deciding whether enabling connected or background use of QES Connect is appropriate in their environment and for securing the workstation, token access, local session, and organizational authority model accordingly.

11.4. Document and submission responsibility.

The user and Organization remain responsible for the appropriateness, accuracy, legality, and consequences of documents, payloads, submissions, or regulated-access actions carried out through QES Connect.

11.5. QTSP and third-party obligations.

The user and Organization remain responsible for their relationship with the relevant QTSP, certificate provider, reader/token vendor, middleware provider, and any third-party system accessed through supported workflows.

12. Compatibility and Supported Environments

12.1. Supported operating environments.

QES Connect is intended to operate on Windows 10, Windows 11, recent macOS environments including the current Tahoe generation, and recent Linux environments where compatible dependencies are available.

12.2. Compatibility is environment-specific.

Actual compatibility may depend on token type, smart-card reader, driver, middleware, certificate-provider tooling, operating-system version, permissions, local security settings, and system configuration.

12.3. No universal Linux compatibility promise.

Medentic does not guarantee compatibility with every Linux distribution, package set, token, smart-card reader, middleware stack, certificate provider, or system environment.

12.4. Compatibility may change.

Supported environments, dependencies, integrations, and compatibility expectations may change over time as operating systems, providers, drivers, and external systems evolve.

13. Telemetry, Diagnostics, and Support Data

13.1. Operational telemetry and diagnostics.

Medentic may collect technical telemetry, diagnostics, crash data, compatibility information, support-related operational data, and similar technical information necessary to operate, secure, maintain, troubleshoot, and improve QES Connect and its interaction with the Platform.

13.2. Collection may be required for intended operation.

Certain technical telemetry or diagnostic processing may be required for QES Connect to function as intended within Medentic services.

13.3. Scope and detail.

The types of data collected and the purposes for which they are processed are described more fully in the applicable Privacy Notice and related service documentation.

14. Privacy Notice and Data Processing Terms

14.1. Additional privacy terms.

The processing of personal data in connection with QES Connect and the Platform may be governed by Medentic's Privacy Notice, any applicable Data Processing Agreement, and other service documentation.

14.2. High-level role statement.

Depending on the relevant workflow and service configuration, Medentic may act as a service provider of software functionality, as a processor, or in another role described in the applicable service and privacy documentation.

14.3. Connected workflow data.

Platform-connected workflows may involve processing of account data, operational metadata, audit information, workflow status data, integration data, and other information needed to provide the relevant Medentic services.

15. Availability and Updates

15.1. Service evolution.

Medentic may update, modify, improve, suspend, discontinue, or impose new conditions on any part of QES Connect or related functionality at any time for product, technical, legal, security, compatibility, or operational reasons.

15.2. Changes in supported environments.

Medentic may change supported operating systems, middleware assumptions, token support, integration support, or technical requirements over time.

15.3. Dependency on third parties.

Availability of certain workflows may depend on third-party providers, QTSPs, middleware, external systems, or regulated portals and may change when those external dependencies change.

16. Prohibited Conduct

16.1.
You may not, and may not permit any third party to:
(a)
reverse engineer, decompile, disassemble, or otherwise attempt to derive the source code of QES Connect except to the extent such restriction is prohibited by applicable law;
(b)
copy, modify, adapt, translate, create derivative works from, or redistribute QES Connect except as expressly permitted by this EULA;
(c)
remove, obscure, or alter proprietary notices;
(d)
bypass, disable, interfere with, or circumvent technical controls, workflow restrictions, security features, diagnostics, or access limitations of QES Connect or the Platform;
(e)
use QES Connect with false, misleading, unauthorized, or improperly shared credentials;
(f)
use QES Connect outside authorized professional workflows or in violation of applicable law, professional obligations, or third-party rights; or
(g)
use QES Connect in a way that could damage, impair, overload, or compromise QES Connect, the Platform, or related systems.

17. Disclaimers

17.1. As-is basis.

To the maximum extent permitted by applicable law, QES Connect is provided on an "as is" and "as available" basis.

17.2. No outcome warranty.

Medentic does not warrant that QES Connect will be uninterrupted, error-free, accepted by every external system, or sufficient for every legal, regulatory, operational, or evidentiary purpose.

17.3. No warranty of legal authority or appropriateness.

Medentic does not warrant that any user has authority to sign, authenticate, submit, or access a particular system or document, or that any given workflow is appropriate under the user's legal or organizational obligations.

18. Limitation of Liability

18.1.
To the maximum extent permitted by applicable law, Medentic will not be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, goodwill, use, data, business opportunity, or anticipated savings arising out of or relating to QES Connect or this EULA.
18.2.
To the maximum extent permitted by applicable law, Medentic's aggregate liability arising out of or relating to QES Connect and this EULA will not exceed the total amount paid by the Organization for the relevant Medentic subscription or services during the twelve (12) months preceding the event giving rise to the claim.
18.3.
Nothing in this EULA excludes or limits liability to the extent such exclusion or limitation is prohibited by applicable law.

19. Suspension and Termination

19.1.
Medentic may suspend or terminate access to QES Connect or related connected functionality if you breach this EULA, misuse QES Connect, lose authorized access to the Platform, or create legal, operational, or security risk for Medentic, the Platform, or other users.
19.2.
Upon termination or suspension, your license to use QES Connect will end to the extent of the affected access.
19.3.
Provisions of this EULA that by their nature should survive termination will survive, including provisions relating to ownership, restrictions, disclaimers, limitation of liability, governing law, and dispute-related matters.

20. Governing Law and Contracting Entity

20.1.
This EULA is concluded with Medentic LLC, a Bulgarian single-member limited liability company, UIC 207854560.
20.2.
This EULA is governed by the laws of Bulgaria, without regard to conflict-of-law rules, unless mandatory law requires otherwise.
20.3.
The competent courts of Bulgaria will have jurisdiction over disputes arising out of or in connection with this EULA, unless mandatory law requires otherwise.

21. General

21.1.
If any provision of this EULA is held unenforceable, the remaining provisions will remain in full force to the extent permitted by law.
21.2.
Medentic may update this EULA from time to time by publishing an updated version through the Platform, QES Connect, or Medentic's legal pages. Your continued use of QES Connect after the effective date of an updated version constitutes acceptance of the updated EULA to the extent permitted by applicable law.
21.3.
This EULA, together with the applicable Platform terms it references, constitutes the entire agreement between you and Medentic regarding QES Connect and supersedes prior understandings relating specifically to QES Connect.