El Doc legal

Clear rules for sensitive information.

A pre-launch framework for the policies, terms and clinical boundaries that must accompany the final El Doc products.

Draft frameworkThis is not final legal advice or a production privacy notice. It identifies product truths and the decisions that legal, privacy, security, clinical and engineering teams must verify before publication.
Privacy framework

How El Doc should describe data use.

The final notice must reflect verified production data flows, jurisdictions and operating roles.

DraftLegal review required

1. Information covered

Account details, uploaded sources, extracted health information, user replacements, longitudinal record data, family profiles, access activity, communications, support requests, device information and other data actually collected by production services.

2. Why information is used

To provide requested functions such as record ingestion, extraction, verification, longitudinal organization, explanations, graphs, patient-granted access, professional review, security and support.

3. Source and correction integrity

The original source remains unchanged. When a user flags an extraction and enters a replacement, El Doc uses the replacement. The superseded extraction remains retained as “Overwritten by user” but is excluded from views, summaries, graphs, AI processing and other outputs.

4. User control

  • Choose who receives access to the El Doc record.
  • Set how long access remains active.
  • Review important access activity and revoke access.
  • Use final export, deletion and closure controls as described by the production policy.

5. Retention and legal scope

Retention schedules and applicable legal duties depend on the verified architecture, operating role and launch jurisdiction.

Legal input required: Define retention and deletion timelines, processing roles, service providers, cross-border transfers, contact details and regional rights.

Terms & Conditions

Terms for using El Doc.

A substantive pre-launch draft for patients, caregivers and healthcare professionals. It is not yet a binding agreement.

Draft—not effectiveCounsel review required

1. Who these terms are between

These draft terms describe the intended agreement between a user and ElDocAI, Inc. for the El Doc website and products for Patients and Doctors. The final agreement must identify the contracting entity, registered address, effective date, applicable product versions and any regional addenda.

Confirm before publication: Legal entity details, effective date, supported countries and whether professional organizations need separate commercial terms.

2. Eligibility, acceptance and accounts

Before El Doc creates an account, sign-up must present the complete Terms & Conditions that apply to that user and require an unchecked, affirmative acceptance control. The user must be able to open and read the terms before agreeing; account creation cannot proceed without acceptance. The service should record the version accepted, acceptance time, account and applicable product or role. A patient, caregiver and doctor may need different supplemental terms, each presented and accepted where applicable.

Acceptance of the Terms must be distinct from optional choices such as marketing messages or non-essential tracking. The Privacy Policy and Medical Disclaimer should be clearly available during sign-up, with any separate acknowledgments required by the final legal and regulatory design.

You must meet the minimum age and other eligibility requirements in the final terms, provide accurate account details, protect your sign-in credentials and notify El Doc if you believe someone has accessed your account without permission. You are responsible for actions taken through your account unless applicable law provides otherwise.

Managing another person’s profile or uploading their records requires the appropriate authority, consent or legal guardianship. Access granted by an adult record owner does not transfer ownership of that person’s record.

Confirm before publication: Minimum age, guardian rules, professional verification, acceptance evidence, account recovery and which role-specific documents require separate acceptance.

3. What the service does

El Doc is designed to receive supported medical documents, images, voice and text; extract information; connect it into a longitudinal FHIR-based record; provide case-specific explanations, source links, composed views and AI-assisted questions; and allow the record owner to grant another person access for a selected period.

Available features and supported formats may differ by product, device, region or release. Demonstrations on this website are illustrative, not production records or a promise that every shown feature is currently available.

4. Your records and corrections

You retain your rights in records and information you submit, subject to the rights of other people and organizations involved. You grant El Doc only the permissions needed to operate the service as described in the final Privacy Policy and these terms.

Review extracted information against the original source. If an extracted value is wrong, mark it incorrect and enter the replacement. El Doc uses the replacement in views, summaries, graphs, AI processing and outputs. The superseded value stays in the database as “Overwritten by user” but is excluded from those uses; the original document remains unchanged.

Confirm before publication: Content-license scope, export rights, storage and deletion rules, and intellectual-property treatment of AI outputs.

5. Sharing and professional access

The record owner chooses who can access the El Doc record, how long access lasts and whether to revoke it. Current sharing does not provide a choice of individual record sections. Before granting access, consider that the recipient may see the record during the active access period and may retain information obtained while access was authorized.

A healthcare professional must use patient-granted access only for authorized care-related purposes and comply with the rules, professional duties and organizational policies that apply to them. Revoking access ends future access through El Doc; it cannot undo information a recipient has already viewed or independently retained.

6. AI and medical limits

El Doc may explain information, connect findings to the available case, identify missing context, and present possibilities for discussion. AI outputs can be incomplete or wrong. El Doc does not diagnose the patient, prescribe treatment or replace a qualified clinician. Do not change medication or delay care solely because of an El Doc output.

El Doc is not an emergency service. If you have severe, rapidly worsening or potentially life-threatening symptoms, seek urgent medical care or contact local emergency services.

7. Acceptable use

You must follow applicable law and use El Doc only for authorized purposes. You must not:

  • Upload or disclose another person’s health information without the necessary authority.
  • Impersonate a patient, caregiver or clinician, or misuse a sharing invitation.
  • Attempt unauthorized access, interfere with security, probe systems or introduce harmful code.
  • Use automated scraping or bulk access without written authorization.
  • Present AI output as a verified diagnosis or clinician-approved decision when it is not.

Final usage rules should be published separately when needed and incorporated by reference only after legal review.

8. Fees, app stores and subscriptions

Pricing, free features, trials, subscriptions, renewals, cancellation and refunds have not been finalized. If paid features are introduced, the final terms must state the price, billing cycle, taxes, renewal mechanism, how to cancel, refund rights and whether payment is handled by El Doc, Apple or Google.

Confirm before publication: Commercial model and app-store-specific conditions. No automatic-renewal clause should be published until the actual checkout flow is verified.

9. Suspension, closure and data

The final terms may allow El Doc to suspend or end access for security threats, unauthorized use, legal requirements or material violations, with notice where appropriate. Users should be able to close an account using the published process. Account closure, export and deletion must align with the final Privacy Policy, retention schedule and legal obligations.

Confirm before publication: Notice, appeal, cure periods, data export window and post-closure retention.

10. Ownership of the service and third parties

ElDocAI, Inc. and its licensors retain rights in El Doc software, branding and service design. Your right to use the service is limited to what the final terms permit. Third-party platforms, app stores, medical terminology licenses and external links may have their own terms; El Doc must not imply that those organizations endorse the product.

11. Changes, availability and service quality

El Doc may improve, modify or discontinue features as the product evolves. Material changes to binding terms should be communicated through a defined notice process, with an effective date and any required opportunity to decline. The final agreement must describe support, availability and any service commitments accurately.

Confirm before publication: Change-notice period, service levels and regional consumer protections.

12. Disclaimers and liability

Any warranty disclaimer, liability cap, exclusion of damages or indemnity must be drafted for the actual business model and reviewed under the laws of each launch market. Mandatory consumer and patient rights cannot be waived by a generic clause.

Legal drafting required: Do not publish a limitation-of-liability amount or indemnity provision until counsel selects and validates it.

13. Complaints and disputes

The final terms must explain how to contact El Doc about a complaint, which law applies, where disputes are resolved and whether any alternative dispute process applies. These choices may differ by country and by patient versus professional account.

Legal drafting required: Governing law, venue, mediation or arbitration, class-action treatment, complaint contact and regional addenda.

14. Contact and final agreement

The published version should provide a real legal contact, notice address, effective date and revision history. It should identify the Privacy Policy and any professional, app-store or regional terms that also apply.

Confirm before publication: Legal contact, address and policy links.

Medical Disclaimer

El Doc does not diagnose the patient.

The product supports understanding, preparation and professional review; it does not replace medical care.

DraftClinical and legal review required

1. Educational and organizational support

El Doc can extract facts, explain terminology, distinguish reported normal and abnormal findings, relate information to the available longitudinal record, identify uncertainty and missing context, and suggest questions for a healthcare professional.

2. No independent diagnosis or treatment

El Doc does not independently diagnose, prescribe treatment or make final clinical decisions. AI content may be incomplete or incorrect and must be considered with symptoms, examination, history, medicines, original sources and professional judgment.

3. Emergency situations

El Doc is not an emergency service. Severe, rapidly worsening or potentially life-threatening symptoms require local emergency services or urgent medical care—not app interpretation.

4. Professional use

Professional features are decision-support tools. Qualified professionals remain responsible for reviewing the patient’s information and exercising independent clinical judgment.

Review required: Align the final language with intended use, product classification, markets and regulatory strategy.

Cookies & Tracking

Explain every technology used.

The final notice must match the verified website, application and SDK configuration.

DraftTechnical audit required

1. Essential technologies

Technologies needed for security, navigation, preferences and requested functionality should be separated from analytics and optional technologies.

2. Optional analytics

No analytics or advertising claim should be published until website, app, SDK and data flows are audited. Where consent is required, optional technologies should remain inactive until a valid choice is made.

3. Health-data boundaries

Authenticated health-record areas require especially careful review before any analytics, replay, advertising pixel or third-party tracker is added.

4. Final inventory

Technical input required: Document provider, purpose, collected data, duration, retention, consent basis and jurisdiction for every cookie and SDK.

Shared principles

What every final policy must preserve.

Plain languageMake choices and consequences understandable.
Product accuracyPolicies must match real data flows and controls.
Source integritySources and superseded extractions remain distinguishable.
Access controlUsers choose the recipient, duration and revocation.
AI boundariesDo not turn possibilities into diagnoses.
Regional reviewReview every launch market and operating role.
Before publication

Convert this framework into verified legal documents.

Legal, privacy, security, clinical, product and engineering teams should review the same production data map before approval.

Open Help Center