emTRUTH TERMS OF SERVICE
Effective Date: June 18, 2026 | Version: 3.1 (Master Enterprise & Patient Framework)
Operational Scope: This Master Agreement governs the technical use, operational parameters, and contractual constraints of the emTRUTH software framework for all individual users, patients, clinical research organizations, healthcare networks, and medical institutions.
PART A: PLAIN-LANGUAGE TERMS OF SERVICE (SUMMARY)
By using emTRUTH, you agree to the rules that keep your data safe and completely under your control. Here is a clear summary of how our operations work across all systems:
Active Opt-In Choice: You choose to join us. You are only bound by these terms if you actively check the box and accept them when creating your account.
You Are in Control: This platform is a secure utility tool. We provide the encrypted pipeline, but you command who can see your medical records and for how long.
No Rules Can Change Your Privacy: Our Terms of Service can never be used to lessen or weaken our Privacy Policy. Your privacy protections always come first.
No Property Transfer: You never give up your rights. Whether you link records from a hospital or a federal database, everything remains 100% your property forever.
Corporate Safeguards: Even if emTRUTH gets acquired or changes management, these terms legally bind the new owners. They cannot change your data ownership or sell your information.
Infrastructure Isolation: Today emTRUTH only serves users in the United States, the platform operates inside AWS GovCloud (US) to block unauthorized data viewing and protect system operations.
PART B: COMPREHENSIVE OPERATIONAL TERMS OF SERVICE FRAMEWORK
1. Contractual Relationship, Active Consent, and Service Scope
To access the platform utilities, users must complete a formal account generation sequence. Establishing a user profile, deploying API nodes, or linking medical datasets requires explicit Clickwrap active opt-in confirmation. By intentionally clicking the required checkbox to affirm acceptance, you establish a legally binding contractual relationship with emTRUTH, Inc. emTRUTH provides an advanced, secure, non-custodial, multi-layered data security architecture engineered for individual users and partner institutions to have absolute control over their health records. Passive browsing (User visiting or clicking emTRUTH links) or automated background interaction without active user consent does not constitute acceptance or bind the user to these terms.
2. Account Credentials and Password Responsibility.
You are solely responsible for maintaining the confidentiality and security of your account credentials, including your password, and for any and all activities that occur under your account. Passwords must be a minimum of fifteen (15) characters in length. You are responsible for securely storing your password; emTRUTH is not liable for any unauthorized access resulting from your failure to do so.
If you suspect or become aware that your password has been compromised, or has become known to any unauthorized individual, you must change your password immediately. You may update your password within your emTRUTH user profile, which requires verification of your current password. In the event that you lose or forget your credentials, you may initiate a password reset using the “Forgot your password?” link provided on the emTRUTH login page.
3. Federal Endorsement Attribution Disclaimer
"This product uses the Blue Button APIs but is not endorsed or certified by the Centers for Medicare & Medicaid Services or the U.S. Department of Health and Human Services."
In full alignment with federal software provisioning parameters, emTRUTH displays the mandatory attribution disclaimer text above prominently across our core application interface. The platform does not leverage federal agency naming conventions or institutional seals to imply or promote commercial endorsement of our enterprise infrastructure products.
4. Absolute Priority and Non-Contradiction Covenant
Sovereignty Non-Contradiction Mandate: No section, statement, provision, liability limitation, or operating condition contained within these Terms of Service shall be interpreted, construed, or leveraged to contradict, negate, diminish, or detract from the user privacy protections, zero-selling mandates, account deletion rights, or absolute data ownership guarantees set forth in the accompanying emTRUTH Privacy Policy. The privacy and security of health data are non-negotiable; in the event of any technical, legal, or operational conflict between these Terms of Service and the Privacy Policy, the strict protections of the Privacy Policy shall universally govern, override, and prevail.
5. Intellectual Property Rights and Non-Custodial Bounds
The operational mechanics of the platform enforce a strict separation between software utility code and user/institutional data:
No Transfer of Legal Title: When you transfer, process, log, or coordinate health records or patient telemetry across the emTRUTH framework, you do not grant emTRUTH any ownership, copyright, title, or intellectual property rights over that information. All health records, clinical assets, and identity criteria remain your exclusive property in perpetuity.
Scope of Technical License: To facilitate digital data movement, you grant emTRUTH a limited, non-assignable, zero-knowledge technical license solely to compress, translate, encrypt, and write cryptographic verification hashes of your records as commanded by your real-time platform button selections or automated API script definitions. This technical routing license is strictly temporary and terminates automatically upon account closure or user revocation of access keys.
Cryptographic encryption key ownership is strictly defined by deployment tier. Within the individual Patient application ecosystem, the user operates as the sole Administrator and owns the keys exclusively. For enterprise installations utilizing the BlockTwin for Enterprise data management protocol, the respective organization manages and owns its encryption keys via its designated corporate Administrators. emTRUTH maintains no secondary method or administrative backdoor to duplicate, override, reconstitute, or view patient data.
6. Binding Successor Liability and Corporate Structural Continuity
These Terms of Service remain fully binding upon all future corporate configurations, management boards, and commercial assigns of emTRUTH, Inc. In strict compliance with the Corporate Continuity Pledge, if the company undergoes an enterprise acquisition, asset assignment, corporate restructure, management change, or merger, the incoming management team or corporate owner is legally prohibited from amending your data sovereignty, acquiring rights to your health files, or diluting our zero-data-selling mandate. Data sovereignty remains unalterably with the individual user and partner institution in perpetuity, surviving all corporate modifications without exception.
To ensure financial protection and corporate accountability across all emTRUTH managed platform and infrastructure, emTRUTH maintains an active cyber liability insurance policy providing up to two million dollars ($2,000,000) in coverage per individual security incident.
7. Federal and Institutional Integration Caveats
emTRUTH interoperates with various third-party, state, and federal healthcare technologies. Specific integration workflows are subject to additional platform constraints:
Medicare Access Integration: For users leveraging active system connections to retrieve personal insurance and beneficiary details, the system layout displays the explicit source selector label "Medicare" within the primary user interface data-picker. The mechanical data pipelines guarantee that operational terms will never negate or detract from the federal protections detailed in the emTRUTH Privacy Policy. All Medicare-related account interactions are monitored strictly under the federal checklist framework rules.
EHR/FHIR Interoperability Networks: For clinical networks pulling data from private electronic health records using Fast Healthcare Interoperability Resources (FHIR), users maintain the absolute right to set time-delimited access bounds and pull back sharing parameters at will, in full compliance with the 21st Century Cures Act.
8. Account Termination, Closed Status, Dormant status and Right to Be Forgotten Lifecycle
Users and institutions may terminate their account relationship at any strictly chosen interval. Upon receiving an account closure or Right to Be Forgotten instruction, emTRUTH purges your data from temporary caches and deletes your name and contact details from standard systems. Data secured in blockchains, including Protected Health Information (PHI) and historical data-routing logs, are made permanently inaccessible by randomizing blockchain keys. This means no historical file can ever be re-linked or viewed by anyone.
As a courtesy, emTRUTH retains user data for seven (7) years following the user's most recent login, with the retention period resetting each time the user logs in. To keep an account secure, we encourage users to log in at least once a month. If two (2) years pass without a login, the account will be set to dormant, and the user must contact emTRUTH to reactivate it to complete a verified login sequence. If a further 5 years pass, totaling seven (7) years without a login, the account will be closed following the same procedure as a user-requested account closure.
Account status variations do not impair or diminish data ownership. Except for the seven (7) year retention limit described above, emTRUTH does not terminate user accounts or destroy access mappings solely on the basis of passive account dormancy. As a security measure, if an account experiences an extended period of inactivity exceeding twenty-four (24) consecutive months, emTRUTH may pause active API processing nodes and transaction routing lines associated with that specific account to preserve cloud processing efficiency within our secure AWS GovCloud instances. Users retain an absolute, perpetual right to reactivate their dormant profiles at any time so long as no greater than 7 years has passed from their last log in. Account reactivation requires no penalty fees or data restoration protocols; the user simply needs to complete a standard verified login sequence to unpause active database pipelines and restore immediate data-sync capabilities.
However, once 7 years have passed without a log n, the account will not be recoverable.
The user can create a new account and repopulate their account with their medical data stored on other platforms.
9. System Warranties, Disclaimers, and Clinical Limitations
Infrastructure Isolation Guarantee: For users served in the United States, emTRUTH guarantees that all software execution pipelines, transaction mapping, and identity routing occur exclusively within an environment isolated inside AWS GovCloud secure infrastructure. For users in other countries, this processing occurs within a comparably secure environment located in a region that meets that country’s applicable legal and regulatory requirements, as described in the Geographic Scope and Data Residency provision below.
Geographic Scope and Data Residency: emTRUTH currently provides the Service to users located in the United States, and user data is stored within AWS GovCloud (US). As emTRUTH expands to additional countries, each user’s country of origin is collected at registration (patient.emtruth.com) and used to store and process that user’s data within a region that meets the legal and regulatory requirements applicable to that country. Country-specific, localized, and translated versions of these Terms will be issued at the time of each international launch.
Clinical and Medical Disclaimer: emTRUTH functions solely as an administrative, cryptographic software utility layer. emTRUTH is not a licensed healthcare provider, does not deliver clinical diagnostics, does not formulate medical treatment plans, and does not offer medical advice. emTRUTH assumes no liability or operational responsibility for the foundational accuracy, integrity, or clinical validity of information generated or provided by external third-party systems, electronic health records, medical practitioners, or the historical data repositories of federal healthcare databases.



