Eliza Terms & Privacy

Effective date: 2026-05-03.

Last updated: 2026-05-17.

Developer: Umut Karlikli.

Contact: umut@lechatbot.com.

Privacy contact: umut@lechatbot.com.

Terms of Use

1. About Eliza

Eliza is an AI-assisted clinical case workspace designed to help mental health professionals organize case information, draft clinical summaries, explore structured reflections, prepare session-support materials, and review training-style simulations.

Eliza is not a crisis service, emergency service, medical device, electronic health record, or substitute for professional clinical judgment. Eliza does not provide therapy, diagnosis, treatment, or medical advice to clients or patients.

2. Who May Use Eliza

You may use Eliza only if you are legally able to enter into these Terms and are using the app for lawful professional, educational, or supervised training purposes.

If you use Eliza in a clinical or training context, you are responsible for ensuring that your use complies with applicable professional rules, confidentiality obligations, data protection laws, institutional policies, and client consent requirements.

Eliza is not intended for use by children.

3. Professional Responsibility

You remain solely responsible for all clinical decisions, records, assessments, interventions, communications, and actions. You must independently review and verify any AI-generated output before relying on it.

AI-generated content may be incomplete, inaccurate, inappropriate for a specific case, or inconsistent with current clinical standards. Do not use Eliza as the only basis for diagnosis, treatment planning, risk assessment, safety planning, or any urgent decision.

If a case involves risk of self-harm, harm to others, abuse, neglect, medical emergency, or another urgent safety concern, follow your professional, institutional, and local emergency procedures immediately.

4. Client and Case Information

You should avoid entering directly identifying client information unless you have a lawful basis, proper authorization, and a professional need to do so. Where possible, use pseudonyms or de-identified case details.

You are responsible for determining whether the information you enter is protected health information, sensitive personal data, or otherwise regulated data under laws that apply to you.

Eliza stores the information you enter so the app can provide saved workspaces, continuity between sessions, AI-assisted outputs, account deletion, security controls, and product improvement. Case-specific private information is not sold, publicly disclosed, or used for targeted advertising. It is processed only as described in these Terms and the Privacy Policy, including by service providers needed to operate Eliza.

5. Accounts and Sign-In

Eliza may require an account to save your workspace, case state, preferences, usage limits, subscription state, and related app data. You are responsible for maintaining access to your sign-in method and keeping your device secure.

If you delete your account in the app, Eliza will delete your account record and associated app data from active systems unless retention is legally required or technically necessary for security, fraud prevention, dispute handling, or compliance.

If paid subscriptions are added through Apple in-app purchase, deleting your Eliza account will not automatically cancel Apple billing. You must manage cancellation through your Apple account subscription settings.

6. Acceptable Use

You may not use Eliza to:

• Provide emergency, crisis, or real-time safety response services.
• Generate or rely on clinical output without professional review.
• Violate confidentiality, privacy, data protection, or professional obligations.
• Upload data you are not authorized to process.
• Attempt to reverse engineer, disrupt, overload, or misuse the app or backend.
• Use Eliza to create harmful, abusive, discriminatory, deceptive, or unlawful content.
• Use outputs as a substitute for required supervision, licensure, documentation, or independent clinical judgment.

7. AI Features

Eliza sends selected case, journal, chat, training, and context information to backend services to generate app outputs. OpenAI or other AI service providers may process these requests on Eliza's behalf.

Model selection and prompts are controlled by backend configuration. Eliza may update prompts, models, safety checks, and output formatting over time to improve quality, reliability, cost control, and safety.

8. Subscriptions, Ads, and Availability

Eliza may offer free and paid plans. Paid digital features, if enabled on iOS, will be offered through Apple in-app purchase unless a legally permitted exception applies.

Eliza is distributed through the Apple App Store. Unless a separate custom license agreement is provided, use of the iOS app is also governed by Apple's Standard End User License Agreement (EULA):

https://www.apple.com/legal/internet-services/itunes/dev/stdeula/

The free version may show ads. Ads must not be interpreted as clinical recommendations, endorsements, or professional guidance. Eliza may provide ways to report inappropriate ads or ad issues.

Eliza may change, suspend, or discontinue features when needed for security, compliance, maintenance, or product development.

9. Intellectual Property

Eliza, including its design, code, prompts, product text, and non-user content, is owned by Umut Karlikli or its licensors. You retain responsibility for and any rights you hold in the information you enter into Eliza.

Subject to these Terms, you may use Eliza outputs for your own lawful professional or educational purposes. You are responsible for verifying outputs and deciding whether they are appropriate to use.

10. Disclaimers

Eliza is provided "as is" and "as available." To the fullest extent permitted by law, Umut Karlikli disclaims warranties of accuracy, reliability, fitness for a particular purpose, non-infringement, uninterrupted availability, and error-free operation.

11. Limitation of Liability

To the fullest extent permitted by law, Umut Karlikli will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for loss of data, profits, goodwill, or professional opportunity arising from your use of Eliza.

Nothing in these Terms limits liability where the law does not allow limitation.

12. Termination

You may stop using Eliza at any time. We may suspend or terminate access if we reasonably believe there has been misuse, security risk, legal risk, or a violation of these Terms.

13. Changes

We may update these Terms as Eliza evolves. If changes are material, we will provide notice in the app or by another reasonable method. Continued use after changes means you accept the updated Terms.

14. Governing Law and Contact

These Terms are governed by the laws of Turkiye, unless local consumer or data protection law requires otherwise.

Contact: umut@lechatbot.com

Developer: Umut Karlikli

Address: Istanbul, Turkiye

Privacy Policy

1. Summary

Eliza is designed for sensitive clinical-adjacent workflows. We collect and process data to provide the app, authenticate users, save workspace state, generate AI-assisted outputs, maintain security, enforce quotas, manage subscription state, and improve reliability.

Eliza stores user-provided data to make the product work over time and to improve the app. We do not sell personal data. We do not use sensitive case, journal, chat, or training content for targeted advertising. We do not share case-specific private information publicly or with independent third parties for their own purposes.

When product improvement requires analysis, we aim to use non-sensitive operational data, preference data, aggregate patterns, de-identified data, or minimized excerpts where possible. Access to sensitive clinical workspace content should be limited to what is necessary to provide the requested functionality, troubleshoot issues, maintain safety/security, comply with law, or improve product quality under appropriate safeguards.

2. Data We Collect

Account and authentication data:

• User ID.
• Email address or provider identity information from Apple or Google sign-in.
• Authentication tokens stored securely on supported devices.

Profile and preferences:

• Profession or role.
• Therapy experience level.
• Therapy methods.
• AI response style.
• Language preference.

Clinical workspace content:

• Case summaries, case variables, pseudonyms, notes, presenting problems, and related case details.
• Journal entries and journal previews.
• Chat memory and AI conversation context.
• Feature outputs such as anamnesis, session plan, case formulation, diagnosis-support drafts, and todo-style outputs.
• Training session messages and evaluations.

Operational data:

• Case IDs, chat IDs, timestamps, workflow IDs, model/config traceability, request status, error codes, latency, token usage, estimated cost, quota counters, plan state, and subscription state.

Ads and product interaction data:

• Ad display events and ad request information handled through advertising SDKs.
• Product interaction data such as app launches, taps, feature use, and usage state where needed for app functionality, analytics, reliability, or quota enforcement.

Device, diagnostic, and technical data:

• Device and app technical information needed for security, debugging, performance, crash investigation, backend operation, or third-party SDK functionality.

Sensitive personal attributes:

Eliza does not ask users to provide their own sensitive personal attributes such as sexual orientation, religious beliefs, political opinions, disability status, or similar characteristics as structured profile fields. However, users may choose to enter sensitive information about clients, patients, supervisees, or case subjects in free-form clinical workspace fields. Eliza processes that information as user-provided clinical workspace content.

3. Sensitive Health and Clinical Information

Some information you enter into Eliza may include health, medical, mental health, or other sensitive personal information. Eliza treats case, journal, chat memory, feature output, and training message content as sensitive clinical content.

You should enter only information you are authorized to process. Where possible, avoid direct identifiers and use pseudonyms.

4. How We Use Data

We use data to:

• Authenticate users and maintain account access.
• Save and restore app state.
• Generate AI-assisted responses and structured outputs.
• Personalize outputs based on selected preferences.
• Enforce plan limits, quotas, and usage policies.
• Maintain security and prevent misuse.
• Debug errors and improve app reliability.
• Operate ads in free plan surfaces, where enabled.
• Comply with legal obligations and App Store requirements.

Sensitive clinical workspace content is used to provide app functionality and generate requested outputs. It should not be treated as generic advertising or marketing data.

5. Product Improvement and Confidentiality

We may use stored information to understand whether Eliza is working reliably, which features are useful, where errors occur, and how to improve prompts, workflows, safety checks, onboarding, language quality, and user experience.

For product improvement, Eliza should prefer:

• Aggregated usage metrics.
• De-identified or minimized data.
• Non-sensitive profile and preference fields.
• Operational metadata such as workflow status, latency, token usage, error codes, and feature usage.

Sensitive case-specific private information should not be sold, used for targeted advertising, published, or shared with unrelated third parties. It should not be used as a general analytics dataset where non-sensitive alternatives are sufficient.

Limited access to sensitive content may occur only when necessary to provide the service, generate AI output requested by the user, investigate a user-reported issue, debug safety or reliability problems, comply with legal obligations, protect users or the service, or perform carefully controlled product-quality review.

6. Storage and Security

Eliza uses Firebase / Firestore as the source of truth for app data.

Sensitive clinical content is stored encrypted at rest where the app's current encryption layer applies, including case summaries, journal entries, chat memory, feature outputs, and training messages. Some non-clinical metadata, such as IDs, timestamps, profile preferences, quota counters, plan state, and workflow traceability, may be stored in plaintext for app functionality, operations, debugging, and compliance.

No method of transmission or storage is completely secure. We use technical and organizational safeguards appropriate to the sensitivity of the data, but we cannot guarantee absolute security.

7. AI Processing

Eliza's AI features run through backend services. OpenAI calls are backend-only. When you request an AI output, the backend may send the relevant compact context packet, prompt, and selected user input to OpenAI or another configured AI service provider to generate the response.

Do not enter information into Eliza unless you are comfortable with it being processed by backend and AI service providers for the requested app functionality.

AI service providers and infrastructure providers are not permitted to use case-specific private information for their own independent purposes except as allowed by their service terms, data processing terms, applicable law, and the configuration selected for Eliza. Before production launch, provider terms should be reviewed for health/sensitive-data suitability.

8. Third-Party Services

Eliza may use third-party service providers, including:

• Firebase / Google Cloud for authentication, backend, database, hosting, and infrastructure.
• OpenAI or other configured AI providers for AI output generation.
• Google AdMob and related Google advertising/consent SDKs for ads, where enabled.
• Apple and Google sign-in providers for authentication.
• Apple App Store services for in-app purchases and subscription management, if paid plans are enabled.

These providers may process data according to their own terms, privacy policies, SDK behavior, and platform requirements.

9. Advertising

The free version of Eliza may display ads. Ads must not use sensitive health, medical, or clinical case content for targeted or behavioral advertising.

Advertising SDKs may collect or process data such as advertising data, device identifiers, coarse location, product interaction, diagnostics, or ad performance data as described in App Store privacy disclosures and SDK manifests.

Users may be able to control tracking permissions through iOS privacy settings. If tracking permission is required, Eliza should request it through Apple's App Tracking Transparency framework before tracking occurs.

10. Account Deletion and Retention

You may initiate account deletion from within the app. Account deletion is intended to remove your account record and associated app data from active systems, including saved case workspace content, journal entries, training sessions, subscription state, quota state, profile data, and Firebase Auth user record, unless retention is legally required or technically necessary.

Some records may remain temporarily in backups, logs, security records, or systems where immediate deletion is not technically feasible. These records are retained only as long as reasonably necessary for security, compliance, dispute handling, fraud prevention, or legal obligations.

If Apple in-app subscriptions are enabled, deleting your Eliza account does not cancel Apple billing. You must manage subscriptions through your Apple account.

11. Your Choices and Rights

Depending on your location, you may have rights to access, correct, delete, export, restrict, or object to certain processing of your personal data.

You can:

• Delete your account in the app.
• Change profile and preference information in the app.
• Manage Apple subscriptions through your Apple account settings, if applicable.
• Contact us at umut@lechatbot.com for privacy requests.

We may need to verify your identity before acting on certain requests.

12. Professional and Health Data Responsibilities

If you use Eliza with health, mental health, therapy, supervision, or clinical case information, you are responsible for ensuring that you have the required legal basis, consent, authorization, institutional approval, or professional authority to enter and process that information.

Depending on your location and role, laws such as HIPAA, GDPR, KVKK, professional confidentiality rules, health-record rules, or other sector-specific obligations may apply. Eliza is not a substitute for your required clinical record system, consent process, supervision process, mandatory reporting process, or emergency procedure.

Before using Eliza with identifiable client or patient information, confirm whether you need a data processing agreement, business associate agreement, explicit consent, institutional approval, or additional safeguards.

13. International Transfers

Your data may be processed in countries other than where you live, including countries where our service providers operate. Where required, we rely on appropriate legal mechanisms for such transfers.

14. Children

Eliza is not intended for children and should not be used by children. If we learn that we collected personal data from a child without appropriate authorization, we will take steps to delete it.

15. Changes to This Policy

We may update this Privacy Policy as Eliza changes. If changes are material, we will provide notice in the app or by another reasonable method.

16. Contact

Privacy contact: umut@lechatbot.com

Support contact: umut@lechatbot.com

Developer: Umut Karlikli

Address: Istanbul, Turkiye

Source: docs/legal/eliza-terms-privacy.md