Medentic Consent 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 the Medentic Consent App (the "App").

IMPORTANT: BY DOWNLOADING, INSTALLING, ACCESSING, OR USING THE APP, 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 THE APP.

1. Acceptance and Scope

1.1. Who is bound.

This EULA applies to the clinic, practice, healthcare provider, or other professional organization that uses the App, and to its authorized personnel who access or operate the App on its behalf.

1.2. Patients are not licensees.

Patients, parents, guardians, and other representatives who interact with the App as part of a clinic-managed signing workflow do not become separate licensees under this EULA solely by using the App during that workflow.

1.3. Professional context.

The App is intended for professional healthcare and business use in a clinic-controlled environment, and not for personal, consumer, or unsupervised patient self-service use.

1.4. Related terms.

Your use of the App may also be subject to other Medentic terms, including applicable subscription terms, privacy documentation, data processing terms, and platform policies.

2. Definitions

2.1.
"App" means the Medentic Consent App made available by Medentic for mobile devices and tablets, including updates, patches, enhancements, interfaces, and related materials made available with it.
2.2.
"Platform" means the broader Medentic environment through which accounts, subscriptions, clinic configurations, documents, records, and signing-event evidence may be managed, stored, or made available.
2.3.
"Clinic" means the healthcare provider, dental clinic, practice, or other authorized business customer using the App within its professional operations.
2.4.
"Authorized User" means a staff member, contractor, or other person whom the Clinic authorizes to access and use the App on the Clinic's behalf.
2.5.
"SES" means a simple electronic signature workflow and related evidentiary package used in connection with the App and the Platform.
2.6.
"Representative Signer" means a parent, guardian, caregiver, or other person who signs on behalf of a patient where the Clinic determines such person is legally or operationally authorized to do so.

3. License Grant and App Store 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 the App on compatible devices solely for your internal professional use in connection with the Clinic's authorized use of the Platform.

3.2. No sale.

The App is licensed, not sold. No ownership rights in the App are transferred to you.

3.3. Free download; paid service dependency.

The App may be downloaded free of charge from the Apple App Store, Google Play, or another authorized distribution channel, but access to the App and to particular functionality may depend on an active Medentic account, Clinic authorization, Platform configuration, and the applicable Medentic subscription plan or enabled features.

3.4. Reservation of rights.

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

4. Medentic Account, Clinic Authorization, and Subscription Dependency

4.1. Existing Medentic relationship required.

The App is intended for users who are already registered and authorized within Medentic. You may use the App only if you are acting under a valid Clinic relationship and authorized access to the Platform.

4.2. Clinic-controlled access.

The Clinic is responsible for determining who is an Authorized User, what workflows may be used, what documents may be presented, and what patient or representative signing scenarios are permitted within the Clinic's operations.

4.3. Suspension or termination of access.

Medentic may suspend, restrict, or terminate access to the App or certain features where the underlying account, Clinic authorization, subscription, service relationship, or configuration no longer supports such access.

5. Intended Professional Use Only

5.1. Clinical workflow tool.

The App is intended to support document presentation, data entry, signing-event capture, and associated audit and storage workflows within a Clinic-controlled process.

5.2. No consumer self-service license.

The App is not licensed as a general-purpose public signing tool, a consumer e-signature application, or an unsupervised patient kiosk service independent of the Clinic's oversight.

5.3. Authorized personnel only.

Only Authorized Users may configure, initiate, supervise, administer, or otherwise operate the App on behalf of the Clinic.

6. SES Support and Nature of the Service

6.1. Purpose of the App.

The App is designed to support SES workflows and to help collect, preserve, and store evidence relevant to the attribution, integrity, traceability, and auditability of a signing event.

6.2. No automatic legal guarantee.

Although the App is designed to support robust SES evidence collection, Medentic does not guarantee that any particular signing event, document, or evidence package will be accepted, given dispositive evidentiary weight, or regarded as sufficient by every court, authority, insurer, payer, counterparty, or other third party.

6.3. eIDAS context.

The parties acknowledge that under applicable EU electronic-signature rules, an electronic signature should not be denied legal effect solely because it is electronic or because it does not meet the requirements for a qualified electronic signature, but only a qualified electronic signature automatically benefits from the legal effect specifically attributed to that category under applicable law.

6.4. No legal advice.

Medentic does not provide legal advice through the App and does not warrant that any Clinic workflow, consent form, or operational setup independently satisfies all legal or professional obligations applicable to the Clinic.

7. NFC/eID and Identity Assistance

7.1. Assistive function only.

Where enabled, the App may use NFC, eID, or similar technical functions to read or prefill identity-related data or to support evidence collection.

7.2. Not the signature act.

Reading a card, chip, identifier, or identity record through NFC, eID, or another technical method does not by itself constitute the patient's legal signature, consent, or approval of a document.

7.3. Clinic verification still required.

The Clinic remains responsible for confirming that the correct person is present, that the correct document is being used, and that the person completing or signing the workflow is the person entitled to do so.

8. Clinic Responsibilities

8.1. Identity and workflow control.

The Clinic is responsible for conducting the real-world identity check and for verifying that the person using the App is the correct patient or a valid Representative Signer for the workflow in question.

8.2. Document and signer matching.

The Clinic is responsible for making sure that the selected document, patient record, signer context, and any representative-signing scenario are appropriate and sensibly matched before signature capture begins.

8.3. Patient explanation.

The Clinic, and not Medentic, is responsible for explaining the consent process, document contents, treatment context, risks, alternatives, and consequences of signing, and for answering patient questions.

8.4. Lawful use.

The Clinic is responsible for determining whether its use of the App, its documents, its consent process, and its operational configuration comply with applicable law, professional obligations, and internal procedures.

8.5. Data review.

The Clinic must exercise reasonable care to review whether information entered through the App appears coherent and sensible in the circumstances, but the Clinic is not responsible for false statements made by a patient or Representative Signer if the Clinic did not know, and could not reasonably have known, that such statements were false or misleading.

9. Representative Signing

9.1. Supported workflow.

The App may be used for workflows in which a parent, guardian, or other Representative Signer signs on behalf of a patient, including minors or other patients who require representation.

9.2. Clinic responsibility for authority.

The Clinic is responsible for deciding whether representative signing is appropriate in the circumstances and for verifying that the Representative Signer is legally or operationally authorized to act on the patient's behalf.

9.3. Representative responsibility.

A Representative Signer is responsible for the truth, completeness, and legitimacy of the information they provide and for any representation that they are authorized to sign for the patient.

10. Signer Responsibility for Entered Information

10.1. Responsibility of the signer.

The patient or Representative Signer is responsible for the truthfulness, completeness, and accuracy of the information they enter, confirm, or submit through the App.

10.2. No clinic guarantee of truth.

Except to the extent the Clinic knew or should reasonably have known otherwise, the Clinic is not deemed to guarantee the substantive truth of information supplied by the patient or Representative Signer through the App.

11. Evidence Capture, Storage, and Auditability

11.1. Evidence package.

To support SES defensibility and auditability, Medentic may collect, generate, process, retain, and store the signed document and a broad evidence package associated with the signing event.

11.2. Types of evidence.

Such evidence may include, where enabled, configured, or technically available:

(a)
entered or confirmed form data;
(b)
timestamps and sequence information;
(c)
document identifiers, version data, and integrity data such as hashes or equivalent controls;
(d)
signer-flow events and audit logs;
(e)
signature image data;
(f)
signature-related biometric or behavioral data, including coordinates, timing, stroke sequence, pressure, and similar technical signals;
(g)
device, application, clinic, account, and session metadata; and
(h)
other technical techniques reasonably used to support attribution, integrity, traceability, auditability, dispute resolution, and SES evidence quality.
11.3. Storage in the Platform.

Signed documents and related SES evidence may be stored by Medentic within the Platform as part of the service.

11.4. Purpose limitation.

Medentic collects and processes such data primarily to present documents, operate signing workflows, create and preserve a defensible SES evidence package, support integrity and traceability, and maintain records and auditability within the Platform.

12. Devices, Warnings, and Continue-at-Own-Risk Use

12.1. Recommended device profile.

Medentic may recommend device configurations, including Android devices and stylus-capable hardware with technical characteristics suitable for stronger signature evidence capture.

12.2. Diagnostics and validation.

The App may perform technical checks, diagnostics, or signature-capability validation designed to assess whether a device appears suitable for the intended signing workflow or evidence model.

12.3. No blanket prohibition on other devices.

The Clinic may choose to use other devices, but Medentic may warn that a device does not satisfy recommended technical conditions for the intended SES evidence quality.

12.4. Effect of warnings.

If a device does not meet recommended technical conditions, signatures collected on that device may have reduced evidentiary quality and may not meet applicable legal or regulatory expectations or standards in the relevant context.

12.5. Proceeding after warning.

Where the App allows the Clinic to continue despite such warning, the Clinic accepts responsibility for deciding to proceed on that device and for the consequences of using a non-recommended or non-validated device configuration.

13. Security and Shared Device Operation

13.1. App-level safeguards.

The App may include authentication logic, patient-mode restrictions, locking behavior, session controls, and other workflow safeguards designed to reduce misuse and protect signing sessions.

13.2. Recommended best practices.

Medentic recommends the use of PINs, device biometrics where appropriate, staff access controls, device locking, and secure handling practices consistent with the Clinic's environment and workflow.

13.3. Clinic responsibility for operation.

The Clinic remains responsible for the secure day-to-day operation of devices used with the App, including physical control, user access, credential management, device readiness, and review of warnings or notices presented by the App.

13.4. Shared devices.

If the App is used on a shared clinic device, the Clinic is responsible for ensuring that only authorized staff use the device and that the device is secured when not in active supervised use.

14. Privacy Notice and Data Processing Terms

14.1. Additional privacy terms.

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

14.2. Clinic responsibility for lawful basis.

The Clinic is responsible for ensuring that it has an appropriate legal basis, required notices, and any necessary internal authorizations for using the App in connection with patient data, representative data, identity-related data, and signature-event evidence within its professional operations.

14.3. Platform storage.

Data collected on devices through the App may be stored in the Platform for practical operation, signing-event support, auditability, and recordkeeping, subject to the applicable privacy and data-processing documentation.

15. Availability and Updates

15.1. Service evolution.

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

15.2. Feature variability.

Features may vary by subscription plan, country, device, operating system, Clinic configuration, or integration status.

15.3. Technical changes.

Medentic may change technical requirements, evidence-capture methods, supported devices, validation thresholds, workflow logic, or diagnostics over time.

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 the App except to the extent such restriction is prohibited by applicable law;
(b)
copy, modify, adapt, translate, create derivative works from, or redistribute the App 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 the App or Platform;
(e)
use unauthorized, misleading, false, or shared credentials in a manner not approved by the Clinic;
(f)
access or use the App outside authorized Clinic workflows;
(g)
use the App in violation of applicable law, professional obligations, or third-party rights; or
(h)
use the App in a way that could damage, impair, overload, or compromise the App, the Platform, or related systems.

17. No Medical Advice and No Emergency Use

17.1. No medical advice.

The App does not provide medical advice, diagnosis, treatment recommendations, or clinical judgment, and it does not replace the Clinic's professional obligation to communicate with patients and obtain legally and clinically appropriate consent.

17.2. No emergency reliance.

The App is not intended as an emergency service, an emergency communication system, or the sole means of accessing urgent clinical information where delay, downtime, connectivity issues, or device failure could create immediate risk.

18. Disclaimers

18.1. As-is basis.

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

18.2. No outcome warranty.

Medentic does not warrant that the App will be uninterrupted, error-free, accepted by every third party, or sufficient for every legal, evidentiary, clinical, or operational purpose.

18.3. No legal-compliance warranty.

Medentic does not warrant that the Clinic's chosen forms, workflows, explanations, signers, device choices, or local procedures satisfy all legal or professional obligations applicable to the Clinic.

19. Limitation of Liability

19.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 the App or this EULA.
19.2.
To the maximum extent permitted by applicable law, Medentic's aggregate liability arising out of or relating to the App and this EULA will not exceed the total amount paid by the Clinic for the relevant Medentic subscription or services during the twelve (12) months preceding the event giving rise to the claim.
19.3.
Nothing in this EULA excludes or limits liability to the extent such exclusion or limitation is prohibited by applicable law.

20. Suspension and Termination

20.1.
Medentic may suspend or terminate access to the App or any related functionality if you breach this EULA, misuse the App, lose authorized access to the Platform, or create legal, operational, or security risk for Medentic, the Platform, or other users.
20.2.
Upon termination or suspension, your license to use the App will end to the extent of the affected access.
20.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.

21. Governing Law and Contracting Entity

21.1.
This EULA is concluded with Medentic LLC, a Bulgarian single-member limited liability company, UIC 207854560.
21.2.
This EULA is governed by the laws of Bulgaria, without regard to conflict-of-law rules, unless mandatory law requires otherwise.
21.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.

22. Apple App Store and Google Play Terms

22.1. Store distribution.

If the App is downloaded through the Apple App Store, Google Play, or another authorized app marketplace, you must also comply with the applicable terms of that marketplace and of your device operating system.

22.2. License source.

The license granted under this EULA is granted by Medentic, and not by Apple, Google, or another marketplace operator.

22.3. Platform responsibility limits.

Apple, Google, and other marketplace operators are not responsible for the App, its content, maintenance, support, or claims relating to the App, except to the extent required under their mandatory marketplace terms.

22.4. Third-party beneficiary.

To the extent required by Apple marketplace terms, Apple and its subsidiaries are third-party beneficiaries of this EULA and may enforce this EULA against you in that capacity.

23. General

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