1. INTRODUCTION & SCOPE
Who This Policy Applies To
This Privacy Policy applies to MedLlama mobile applications, related MedLlama services, and the MedLlama website at www.medllama.app (collectively, the "Services"). It explains how MEDLLAMA LLC ("MedLlama", "we", "us", or "our") handles information when you create an account, sign in, build a health profile, submit clinical questions, upload medical files or images, use AI-assisted analysis, manage medication reminders, purchase or restore a subscription, contact support, use the website, export your information, or request deletion.
Privacy Is Separate From Medical Safety
This Privacy Policy concerns the collection, processing, storage, disclosure, security, retention, and deletion of information. Clinical limitations, professional responsibilities, AI safety limitations, emergency-use restrictions, and limitations of liability are addressed separately in the MedLlama Medical Disclaimer and Limitation of Liability and the Terms of Service. Those documents should be read together with this Privacy Policy.
Current Product Scope
The current version of MedLlama maintains a single account-associated personal profile and is not represented as a hospital electronic medical record system or a multi-patient medical-record management platform. Professional users may nevertheless submit clinical information or files that concern another person when they are legally and professionally authorized to do so. If MedLlama later introduces dedicated multi-patient record functionality or materially changes the categories of information processed, this Privacy Policy will be updated before or when those changes become applicable.
2. DATA CONTROLLER & CONTACT INFORMATION
Data Controller
The controller responsible for the personal information covered by this Privacy Policy is: MEDLLAMA LLC Montana, United States Business Address: 244 5th Ave, Suite 1623, New York, New York 10001, United States Website: www.medllama.app Privacy Contact: privacy@medllama.com
Privacy Questions
Questions about this Privacy Policy, privacy rights, data handling, or legally required privacy requests may be directed to privacy@medllama.com. For security, we may need to verify that a person making a privacy request is the account holder or is otherwise legally authorized to make the request before disclosing or acting on account-associated information.
No Disclosure of Internal Architecture
This Privacy Policy describes the categories of information we process and the purposes for which we process them. It does not publish internal database collection names, storage paths, security-rule logic, infrastructure credentials, or other implementation details that could reduce the security of the Services.
3. INFORMATION WE COLLECT WHEN YOU CREATE OR USE AN ACCOUNT
Account and Identity Information
Depending on the sign-in method and information you provide, we may collect or store account and identity information such as your email address, display name, username, account identifier, and profile image. Some information, such as display name, username, or profile image, may be collected as part of account creation or sign-in even if it is not currently displayed publicly within the application.
Authentication Information
MedLlama uses Firebase Authentication and supports Sign in with Apple and Sign in with Google. Authentication providers may process information necessary to verify your identity and complete sign-in. MedLlama does not receive your payment-card information through these authentication services.
Profile Information
Your MedLlama profile may include information such as gender or sex information you provide, age or date-of-birth information, height, weight, country, allergies, chronic conditions, subscription status, and other profile fields that you choose to provide through the Services.
Language Preference
Your selected application language is currently stored locally on your device for localization purposes rather than being stored as part of your server-side MedLlama account profile.
4. HEALTH, MEDICAL & OTHER SENSITIVE INFORMATION
Health Information
MedLlama processes health and medical information that you voluntarily provide in order to deliver the clinical and AI-assisted functionality you request. Depending on the feature used, this information may include symptoms, complaints, medical history, chronic conditions, allergies, medications, age, gender or sex information, height, weight, pregnancy or lactation information where provided, lifestyle information, laboratory values, clinical observations, medical reports, diagnostic information, and other health-related context.
Sensitive Personal Information
Health information, genetic information, certain sexual-health information, and some clinical records may be treated as sensitive or special-category personal information under applicable privacy laws. We process such information only for the purposes described in this Policy, including providing requested clinical features, storing your history, generating AI-assisted analysis, maintaining account functionality, and meeting applicable legal, security, and compliance obligations.
Information You Choose to Submit
You control the health and clinical information you choose to enter or upload. You should not submit information that is not reasonably necessary for the feature you are using. If you submit information concerning another person, including a patient, family member, or other individual, you are responsible for ensuring that you have the legal authority, professional authorization, consent, or other lawful basis required to submit and process that information.
5. CLINICAL QUESTIONS, CHAT, REPORTS & AI-GENERATED HISTORY
Clinical Inputs
We may store clinical questions, symptom descriptions, complaint information, health-profile context, follow-up messages, medication questions, clinical observations, and other text that you submit to MedLlama.
Generated Outputs
We may store AI-generated responses associated with your account, including structured clinical reports, differential considerations, clinical reasoning, laboratory explanations, medication reviews, interaction analyses, visual or diagnostic observations, and follow-up responses.
Persistent History
Clinical inputs and AI-generated outputs are generally retained in your MedLlama history until you delete the applicable record or delete your account, subject to the deletion and retention provisions described below. This persistence allows you to revisit previous analyses and related uploaded materials.
6. FILES, IMAGES & MEDICAL DOCUMENTS
Uploaded Content
When you choose to upload content other than plain text, the content is stored using Firebase/Google Cloud storage services so that MedLlama can process the requested feature and maintain the associated history. Uploaded content may include X-rays, CT or MRI-related images, ECG materials, skin or wound photographs, medication packaging photographs, laboratory documents, PDFs, pathology materials, genetic reports, medical reports, and other supported documents or files.
Account Association
Stored files are associated with the signed-in MedLlama account through internal account identifiers and protected storage controls. We do not publish internal storage paths or access-control architecture in this Privacy Policy.
Stored File References
MedLlama may generate and store tokenized file-access references or download URLs that allow the application and authorized backend services to retrieve files associated with your account. A tokenized URL should not be treated as a public posting. Nevertheless, users should not intentionally distribute private file-access URLs to unauthorized persons.
Image Metadata
According to the current MedLlama implementation, separate image metadata such as EXIF location metadata is not intentionally retained as an independent MedLlama profile field. MedLlama does not use uploaded image metadata to track your physical location.
Document and Embedded Metadata
PDFs, DICOM materials, reports, and other documents may themselves contain embedded metadata or identifying information. When the original document is stored, information embedded within that document may remain part of the stored file. For example, a medical document may contain names, dates, patient identifiers, facility information, study information, or other metadata. You are responsible for reviewing and minimizing such information when de-identification is legally or professionally required.
7. CAMERA, PHOTO LIBRARY & FILE ACCESS
Camera
MedLlama may request camera access when you choose to capture a supported clinical image, medication image, report, or other content for an AI-assisted feature. Camera access is used only after you choose to use a feature that requires it and is subject to the permission controls of your device operating system.
Photo Library
MedLlama may request access to photos that you select for upload and analysis. Selecting an image allows the selected content to be uploaded and processed as described in this Privacy Policy.
Files and Documents
MedLlama may use the operating system's document or file picker so that you can choose PDFs, medical reports, images, or other supported files. We process the files you select rather than requesting unrestricted access to all files on your device.
No Additional Local Archive
The current MedLlama implementation does not intentionally create a separate permanent local copy, thumbnail archive, or local clinical-file cache after content has been uploaded for the Services, apart from temporary handling that may be necessary for normal operating-system or application processing.
8. HOW AI PROCESSING WORKS
Google AI Services
MedLlama currently uses Google-provided AI infrastructure, including Firebase AI Logic and the Gemini Developer API, together with Google AI models configured by MedLlama. The exact supported model may change as MedLlama updates its AI pipeline, but the data-processing principles described in this Privacy Policy continue to apply unless we update this Policy.
Information Sent for AI Processing
When you request AI-assisted analysis, MedLlama may send to Google the information reasonably necessary to generate the requested response. Depending on the feature, this may include your prompt, relevant health-profile information, age, gender or sex information, allergies, chronic conditions, medication information, symptoms, clinical context, images, PDFs, medical documents, and related follow-up context.
Identifiers Not Intentionally Included in AI Content
MedLlama does not intentionally send your Firebase UID, email address, or username to Google as part of the clinical prompt content used to generate an AI response. Clinical files or documents you upload may nevertheless contain identifying information within their contents or embedded metadata unless you remove that information before submission.
Purpose of AI Processing
Information is sent to Google AI services only as necessary to provide the AI-assisted feature you request, operate safety and abuse-prevention controls, and support the technical delivery of the AI service under the applicable provider terms.
No MedLlama Model Training With Your Conversations
MEDLLAMA LLC does not use your clinical conversations, uploaded health data, medical files, or AI-generated reports to train its own future artificial-intelligence models, create research datasets, build advertising profiles, or produce de-identified research datasets under the current version of the Services.
9. GOOGLE AI DATA PRACTICES
Paid Gemini Developer API Configuration
MedLlama currently operates its Gemini Developer API usage through a Google Cloud project with active billing. According to Google's terms applicable to Paid Services as of the effective date of this Privacy Policy, Google states that prompts, associated system instructions, cached content, uploaded files such as images or documents, and generated responses from Paid Services are not used to improve Google's products.
Abuse Monitoring
Google may retain prompts, contextual information, and generated outputs for a limited period for abuse monitoring, safety, prohibited-use enforcement, security, and required legal or regulatory disclosures. As of the effective date of this Privacy Policy, Google's published Gemini API abuse-monitoring documentation describes a 55-day retention period for this category of logging. Google's practices may change under updated provider terms, and MedLlama will update this Policy when a material change affects our disclosures.
Possible Authorized Google Review
Google states that its abuse-monitoring systems may use automated review and, for content flagged or otherwise requiring investigation under its policies, authorized Google personnel may review relevant content through controlled internal processes. This third-party processing is separate from routine human access by MEDLLAMA LLC.
Google Technical Service Data
Google may separately process operational or technical information necessary to provide and secure its services, such as authentication information, service usage details, token counts, operational status, safety-filter signals, errors, performance information, device or network identifiers, or IP addresses, in accordance with Google's applicable terms and privacy documentation.
Provider Terms May Change
Google's data-retention, abuse-monitoring, product-improvement, and technical-processing practices are governed by Google's applicable terms and documentation. If MedLlama changes AI provider, API provider, billing status, or materially changes the way third-party AI processing occurs, we will update this Privacy Policy and applicable consent disclosures as required.
10. AI PROCESSING CONSENT
Consent Before AI Processing
Before using AI-assisted functionality, MedLlama presents a disclosure explaining that the health information, text, and files you choose to submit may be sent to Google AI services for processing. You must complete the applicable in-app consent or acknowledgment step before MedLlama makes the AI-assisted functionality available.
AI Processing Is Core to AI Features
The third-party AI processing described above is necessary for the current AI-assisted features. If you do not agree to that processing, MedLlama cannot provide those AI-assisted features. There is currently no mode that provides the same AI analysis while preventing the selected clinical content from being transmitted to the applicable Google AI service.
Stopping Future AI Processing
You can stop future AI processing by not submitting new information for AI analysis. If you wish to stop continued account-level processing and remove your stored account data, you may use the in-app account-deletion functionality. Deletion is described in detail below.
Withdrawal and Service Availability
Where applicable law treats consent as the legal basis for a particular processing activity, withdrawing that consent may make the affected MedLlama feature unavailable because the processing is technically necessary to provide the requested AI functionality. Account deletion provides a method to terminate continued use and initiate deletion of stored account-associated information.
11. FIREBASE & GOOGLE CLOUD SERVICES
Firebase Services Used
MedLlama currently uses Google Firebase and Google Cloud services for core application functionality. These services include Firebase Authentication, Cloud Firestore, Cloud Storage for Firebase, Cloud Functions for Firebase, Firebase Remote Config, Firebase App Check, and Firebase AI Logic.
Authentication
Firebase Authentication is used to create and authenticate accounts, including accounts using Sign in with Apple or Sign in with Google.
Database
Cloud Firestore is used to store account-associated application information such as profile data, health-related information, clinical history, AI-generated results, file references, account status, and subscription-related status where applicable.
Storage
Cloud Storage for Firebase is used to store user-selected images, PDFs, clinical reports, and other uploaded files associated with MedLlama functionality.
Cloud Functions
Cloud Functions for Firebase are used for server-side operations, including protected application logic and account or data-deletion workflows.
Remote Config
Firebase Remote Config is used to deliver application configuration and feature settings. MedLlama does not use Firebase Analytics to build behavioral analytics profiles.
App Integrity and Abuse Protection
Firebase App Check is used with Apple App Attest and DeviceCheck where applicable to help verify that requests originate from legitimate instances of the MedLlama application and to reduce unauthorized backend access and abuse.
Processing Locations
Firebase Authentication is operated by Google from United States data centers. Other Firebase and Google Cloud services may process information on regional, multi-regional, or global Google infrastructure depending on the service and configured resource location. Accordingly, information may be processed in the United States and other countries in which Google or its service providers operate facilities.
12. TECHNICAL TOKENS & APP INTEGRITY INFORMATION
App Check Information
MedLlama may process Firebase App Check tokens, App Attest information, DeviceCheck information, and related integrity signals for application security, backend access control, fraud prevention, and abuse prevention.
Messaging Token
A technical messaging token associated with the application installation may be stored as part of MedLlama's technical account or device information. Medication reminder notifications in the current version of MedLlama are not delivered through Firebase Cloud Messaging; they are scheduled locally on the user's device.
No Advertising Identifier Use
MedLlama does not currently use IDFA or other advertising identifiers for cross-app advertising or behavioral tracking.
No Location Collection
MedLlama does not currently request or store precise or approximate device location for the clinical functionality described in this Policy.
13. MEDICATION REMINDERS & LOCAL NOTIFICATIONS
Local Scheduling
Medication reminder schedules are currently created and maintained locally on the user's device rather than being stored in Firestore as cloud-based reminder records.
Notification Content
A locally scheduled medication reminder may display medication-related information on the device lock screen or notification center depending on the user's notification settings. Users should consider the privacy of their device and lock-screen notification settings because other people with physical access to the device may be able to see notification content.
Notification Permission
MedLlama requests operating-system notification permission so that user-created medication reminders can be displayed. You may change notification permissions through your device settings.
14. SUBSCRIPTIONS, PURCHASES & REVENUECAT
Subscription Processing
MedLlama uses RevenueCat to support subscription entitlement management, purchase validation, subscription status, and restore-purchase functionality. Payments for iOS purchases are processed through Apple's App Store infrastructure. MEDLLAMA LLC does not directly receive your full payment-card number from Apple or RevenueCat.
Anonymous RevenueCat Identifier
MedLlama does not intentionally send your Firebase UID, email address, or name to RevenueCat as your RevenueCat user identity. RevenueCat may generate or use an anonymous App User ID for purchase and entitlement management.
Purchase Information
RevenueCat necessarily processes information about purchases and subscription activity required to validate transactions and determine subscription entitlements. Depending on the platform and transaction, RevenueCat and the relevant app-store provider may process purchase history, transaction information, receipts, purchase tokens, subscription status, renewal status, product identifiers, and related technical information under their own applicable terms.
MedLlama Subscription Record
MedLlama may store a subscription or entitlement status in its own backend so that the application can determine whether subscription features should be available to the signed-in account.
No RevenueCat Advertising Integration
MedLlama does not currently use RevenueCat advertising integrations or intentionally provide RevenueCat with your name or email for marketing or advertising purposes.
15. SIGN IN WITH APPLE & SIGN IN WITH GOOGLE
Identity Providers
If you choose Sign in with Apple or Sign in with Google, the applicable provider processes information necessary to authenticate you under its own privacy terms. MedLlama receives the authentication information made available to the application that is necessary to create or access your MedLlama account.
Sign in with Apple Deletion
When an account that used Sign in with Apple is deleted, MedLlama's account-deletion process includes revocation of the associated Sign in with Apple authorization token where required and technically applicable.
Provider Retention
Deletion of your MedLlama account does not automatically erase information that Apple or Google must independently retain under their own legal, security, transaction, fraud-prevention, or account obligations. Those providers act under their respective terms and privacy policies for information they independently control.
16. SUPPORT, CONTACT & FEEDBACK
Information You Send Us
If you contact MedLlama by email, website contact form, support request, or feedback message, we may receive your email address, name if provided, message content, attachments you choose to send, and other information included in the communication.
Purpose
We use support and feedback information to respond to your request, investigate the matter you raise, maintain correspondence, protect legal rights where necessary, and improve or administer the Services where appropriate.
Do Not Send Unnecessary Medical Records to Support
Support channels are not intended to function as clinical-care channels. Please do not send unnecessary medical records, diagnostic images, or sensitive health information through ordinary support communications unless the information is genuinely necessary to address the issue and you are authorized to provide it.
Support Retention
For account holders, support correspondence may be retained while needed to address the communication and may remain for up to 60 days after the associated MedLlama account is deleted, unless a longer period is required by applicable law or necessary for a legal claim, dispute, or valid legal process.
17. MEDLLAMA WEBSITE
Website Scope
This Privacy Policy also applies to www.medllama.app when information is submitted through the MedLlama website.
Support Form
The website may provide a support or contact form. Information you voluntarily enter into that form is processed for the purpose of receiving and responding to your communication.
No Advertising or Behavioral Analytics
The current MedLlama service does not use Google Analytics, Meta Pixel, advertising SDKs, or behavioral advertising systems to profile users for advertising.
No Website Account Login in Current Version
The current website is not used as a separate account-login portal for the mobile MedLlama account. If that changes, we will update this Privacy Policy to describe the new web-account processing.
18. INFORMATION WE CURRENTLY DO NOT COLLECT FOR THE STATED FEATURES
No Advertising Data
MedLlama does not collect health data for targeted advertising and does not use personal health information to create advertising audiences.
No Cross-App Tracking
MedLlama does not currently track users across apps and websites owned by other companies for advertising purposes.
No Firebase Analytics
MedLlama does not currently use Firebase Analytics.
No Firebase Crashlytics
MedLlama does not currently use Firebase Crashlytics to collect application crash reports.
No Firebase Performance Monitoring
MedLlama does not currently use Firebase Performance Monitoring.
No HealthKit
MedLlama does not currently connect to Apple HealthKit or collect Apple Health data.
No Microphone or Voice Recording
MedLlama does not currently use microphone access, voice recording, or speech-to-text functionality for its AI features.
No MedLlama Location Feature
MedLlama does not currently provide a location-based health feature and does not request device location permission for the Services described in this Policy.
19. WHY WE USE PERSONAL INFORMATION
Provide the Services
We process account, profile, health, clinical, file, and subscription information to create and maintain your account, deliver requested clinical functionality, store your history, provide AI-assisted analysis, allow you to revisit reports, and provide subscription features.
Personalize Relevant Clinical Context
We may use the profile and health information you provide to supply relevant context to the AI feature you choose to use, such as age, allergies, chronic conditions, medications, or other clinical information that can materially affect the requested analysis.
Maintain Security
We process authentication information, application-integrity signals, access-control information, and technical tokens to protect accounts, verify legitimate application requests, enforce backend permissions, and reduce fraud or unauthorized use.
Administer Subscriptions
We process subscription status and related purchase information to activate paid features, restore purchases, determine entitlement status, and support subscription administration.
Provide Support
We process information you submit to support or the website contact form to respond to your request and maintain necessary correspondence.
Comply With Law
We may process or preserve information where reasonably necessary to comply with applicable law, respond to valid legal process, establish or defend legal claims, or satisfy binding regulatory or law-enforcement obligations.
20. LEGAL BASES FOR PROCESSING
Performance of a Contract
Where applicable, we process information that is necessary to create your account, provide the MedLlama features you request, store the history you choose to maintain, manage subscriptions, and otherwise perform the Services you request.
Consent
Where required by applicable law, we rely on consent for specified processing activities, including the in-app consent presented before selected health information, text, or files are sent to Google AI services for AI-assisted processing.
Explicit Consent for Health Information
In jurisdictions where health or other special-category information requires an additional legal condition, MedLlama may rely on explicit consent for the specific health-data processing necessary to provide the requested feature, where that basis is legally available and appropriate.
Legitimate Interests
Where legally permitted, we may rely on legitimate interests for limited purposes such as securing the Services, preventing unauthorized access or abuse, protecting legal rights, maintaining service integrity, and administering necessary technical infrastructure. We do not rely on legitimate interests to justify targeted advertising using health information.
Legal Obligations and Legal Claims
We may process information when necessary to comply with a legal obligation or to establish, exercise, or defend legal claims, where permitted by applicable law.
Local Law May Require a Different Basis
Privacy and health-data laws vary by jurisdiction. Where a specific law requires a different legal basis or additional safeguard, we apply the basis and safeguards required by that law to the extent the law applies to MEDLLAMA LLC and the relevant processing.
21. WHO WE SHARE INFORMATION WITH
Google and Firebase
We share information with Google and Firebase services as necessary for authentication, database storage, file storage, server-side functions, remote configuration, application-integrity protection, and AI functionality. The particular information shared depends on the feature you use.
Google AI
Health information, clinical text, selected profile context, images, PDFs, and other clinical files may be sent to Google AI services when you request AI-assisted analysis, as described above.
RevenueCat
Subscription and purchase-related information is processed by RevenueCat as necessary to validate purchases, maintain entitlements, and support subscription functionality.
Apple and Google Identity Services
Apple or Google may process authentication information when you use their sign-in services.
App Store Providers
Apple and other platform providers may process purchases, subscription information, account information, fraud-prevention signals, and other information required to operate their stores and payment systems.
Service Providers
We may use hosting, email, website, or infrastructure service providers where reasonably necessary to provide the Services or receive support communications. Such providers receive only the information necessary for the function they perform and are subject to applicable contractual or legal data-protection requirements.
No Unrestricted Third-Party Disclosure
We do not make your medical history, clinical reports, uploaded images, or other health information publicly available and do not sell access to those materials.
22. NO SALE, TARGETED ADVERTISING OR DATA BROKERING
We Do Not Sell Personal Information
MEDLLAMA LLC does not sell personal information or health information for monetary consideration.
We Do Not Sell Health Data
We do not sell health information, medical images, laboratory information, clinical reports, medication information, or genetic information.
No Targeted Advertising
We do not share personal or health information for cross-context behavioral advertising or targeted advertising.
No Data Brokers
We do not provide your account information or health information to data brokers.
No Advertising Profiles
We do not use clinical conversations, uploaded medical materials, or health profiles to create advertising profiles or marketing audiences.
23. HUMAN ACCESS TO STORED INFORMATION
Restricted Administrative Access
Routine MedLlama users can access only the information permitted to their own authenticated account by the application's security controls. Administrative access to production data is restricted. At the time of this Policy, direct MEDLLAMA LLC administrative access is limited to the founder/developer.
No Routine Human Clinical Review by MedLlama
MEDLLAMA LLC personnel do not routinely read user clinical conversations, medical reports, uploaded files, or AI-generated analyses as part of normal application use.
Exceptional Access
MEDLLAMA LLC may access account-associated information when necessary to comply with valid legal process, respond to lawful law-enforcement requirements, or address a legal dispute involving the information.
Third-Party Provider Access
Separate from MEDLLAMA LLC access, Google or another disclosed service provider may access information under its own controlled processes where necessary to provide, secure, investigate abuse of, or comply with legal obligations relating to its service. For Gemini API abuse monitoring, Google's current documentation states that authorized Google personnel may review content that is flagged for investigation under Google's safety and prohibited-use processes.
24. SECURITY SAFEGUARDS
Technical Safeguards
MedLlama uses a combination of technical and organizational safeguards designed to reduce unauthorized access, disclosure, alteration, or loss of information. Current controls include HTTPS/TLS transport protection, Firebase Authentication, Cloud Firestore Security Rules, Cloud Storage Security Rules, Firebase App Check, Apple App Attest, DeviceCheck, server-side Cloud Functions, and Google Cloud Identity and Access Management controls where applicable.
Account-Based Access Controls
MedLlama associates cloud-stored account information with authenticated user accounts and uses backend access rules intended to prevent ordinary users from reading another user's protected records.
Tokenized File Access
Stored file references use controlled, tokenized access mechanisms rather than intentionally publishing uploaded medical files as ordinary public website content.
No Absolute Security Guarantee
No internet service, cloud platform, device, authentication system, or security control can guarantee absolute security. Users are responsible for protecting their device, email account, Apple or Google sign-in credentials, and MedLlama account access from unauthorized use.
Security Claims
This Privacy Policy does not make unsupported claims that MedLlama is immune from breach, uses a specific encryption algorithm in every layer, or meets a certification or regulatory security standard that MEDLLAMA LLC has not formally obtained.
25. DATA RETENTION
Account Information
Account-associated information is generally retained while your MedLlama account remains active and as needed to provide the Services.
Clinical History
Clinical questions, AI-generated reports, medication analyses, visual analyses, laboratory-related history, uploaded-file references, and related records are generally retained until you delete the applicable record or delete your account.
Uploaded Files
Uploaded images, PDFs, reports, and other stored files are generally retained while the associated MedLlama record remains active. When the associated record is deleted, MedLlama's backend deletion process is designed to remove the corresponding stored file as well.
Deletion Processing Window
A deletion request may require backend processing rather than immediate physical erasure from every active system and backup copy. MedLlama's current deletion process is designed to complete deletion of account-associated data within 60 days after a valid deletion request, subject to the limited exceptions described below.
Technical Logs
MedLlama does not use Firebase Analytics, Crashlytics, or Performance Monitoring. Where limited operational, security, infrastructure, or deletion-process records exist under our control, our current retention target is no longer than 60 days unless longer retention is required by law or necessary for a legal claim.
Backups
Backup or recovery copies under MEDLLAMA LLC's control may persist for up to 60 days after deletion before being overwritten or removed through normal backup lifecycle processes. Firebase, Google, Apple, RevenueCat, or other independent service providers may maintain their own legally or technically required records under their applicable retention rules.
Support Communications
Support communications associated with an account may remain for up to 60 days following account deletion unless a longer period is required for a legal claim, dispute, security matter, or legal obligation.
Subscription Records
Subscription status maintained in MedLlama's own backend is subject to the account-retention and deletion process described here. Apple, RevenueCat, or another transaction provider may independently retain purchase and transaction records for periods required by tax, accounting, fraud-prevention, platform, or legal obligations.
Legal Exceptions
We may retain narrowly limited information beyond the ordinary deletion period when retention is legally required or reasonably necessary to establish, exercise, or defend legal claims, respond to binding legal process, prevent fraud, or satisfy another legal obligation. Where an exception applies, we limit retention to the information and duration reasonably necessary for that purpose.
26. DELETING INDIVIDUAL RECORDS
Record-Level Deletion
MedLlama allows users to delete supported individual records, which may include clinical analyses, diagnostic or visual analyses, medication analyses, complaint history, and associated uploaded files.
Backend Deletion
When a supported record is deleted, the deletion workflow is designed to remove the corresponding backend record and related Firebase Storage object rather than merely hiding the item in the user interface.
Deletion Completion
Record-level deletion may be processed asynchronously and may require up to 60 days for removal from all applicable active systems and backups under MEDLLAMA LLC's control, subject to the legal-retention exceptions described in this Policy.
27. DELETING YOUR ACCOUNT
In-App Account Deletion
If you created a MedLlama account, you can initiate account deletion from within the application.
Loss of Access
When account deletion is initiated, authentication access to the deleted account is terminated as part of the deletion workflow and the account can no longer be used as an active MedLlama account.
Backend Cleanup
The deletion request triggers MedLlama's backend deletion workflow for account-associated profile data, health information, clinical history, AI-generated reports, uploaded-file references, and Firebase Storage content associated with the account.
Deletion Period
The current deletion workflow is designed to complete deletion of account-associated data within 60 days, including deletion from ordinary active storage and applicable backups under MEDLLAMA LLC's control, except where retention is legally required.
Sign in with Apple
If the deleted account used Sign in with Apple, the associated Apple authorization is revoked as required and technically applicable as part of the account-deletion process.
Third-Party Provider Records
Deleting your MedLlama account does not necessarily cause Apple, Google, RevenueCat, or other third-party service providers to erase information that they independently retain under their own legal, security, platform, transaction, fraud-prevention, or service obligations.
28. EXPORT, CORRECTION & USER CONTROL
Data Export
MedLlama provides functionality that allows users to export or download supported information associated with their account.
Correction
You may correct supported profile or account information through the application's available editing controls.
Deletion
You may delete supported individual records and may initiate deletion of the entire account through the application.
Support Does Not Edit Ordinary Records for You
Ordinary support email or website support communications are not used as a substitute for the application's normal record-editing tools. Where applicable law creates a privacy right that cannot reasonably be exercised through the application's self-service tools, you may contact privacy@medllama.com and we will handle the request as required by applicable law after appropriate identity verification.
29. INTERNATIONAL DATA TRANSFERS
United States Controller
MEDLLAMA LLC is a United States company. Information processed through MedLlama may therefore be processed in the United States.
Global Cloud Infrastructure
Google, Firebase, RevenueCat, Apple, and other service providers may process information in countries where they or their subprocessors maintain infrastructure or personnel. Firebase Authentication is operated from United States data centers, while other Firebase and Google Cloud services may use regional, multi-regional, or global infrastructure.
Transfer Safeguards
Where applicable privacy law requires a lawful international-transfer mechanism, MEDLLAMA LLC and its service providers may rely on applicable contractual safeguards, adequacy decisions, recognized certification frameworks, or other transfer mechanisms available under the relevant law. The availability and precise legal mechanism may depend on the user location, provider, and service involved.
30. EEA, EU & UK PRIVACY RIGHTS
Special-Category Health Data
Under European and UK data-protection frameworks, health information and genetic information may constitute special-category personal data and receive additional protection. Where explicit consent is the applicable condition for processing such data, MedLlama seeks a clear affirmative consent for the relevant processing and limits the use of that information to the purposes described in this Policy.
Your Rights
Depending on applicable law and the circumstances, you may have rights to request access to personal information, correction of inaccurate information, deletion, restriction of processing, portability, objection to certain processing, and withdrawal of consent where processing is based on consent. You may also have the right to lodge a complaint with the data-protection authority in your country.
Withdrawal of Consent
Where processing is based on consent, you may stop future submissions and may delete your MedLlama account to terminate continued account-level processing. Because third-party AI processing is necessary to provide the current AI features, withdrawing the required AI-processing consent means those AI features cannot continue to be provided.
Automated Decisions
MedLlama's AI produces information and analysis for the user. The current version does not independently execute a prescription, automatically change medication, trigger an emergency intervention, automatically establish a legal or similarly significant eligibility decision, or independently make a healthcare decision that is implemented without human action.
Contact
For privacy-right requests not available through self-service tools, contact privacy@medllama.com. We may request information reasonably necessary to verify the request.
31. CALIFORNIA PRIVACY INFORMATION
Categories of Personal Information
Depending on how you use MedLlama, categories of personal information may include identifiers and contact information, account information, health information, medical or clinical content, genetic information when submitted, user content, uploaded files, purchase or subscription information, and technical or security information.
Sensitive Personal Information
California law may treat personal information collected and analyzed concerning a consumer's health, genetic data, account credentials, and certain other information as sensitive personal information. MedLlama uses sensitive information only for providing the requested Services, AI-assisted functionality, account security, service administration, legal compliance, and other purposes described in this Policy.
No Sale or Sharing for Cross-Context Behavioral Advertising
MEDLLAMA LLC does not sell personal information and does not share personal information for cross-context behavioral advertising.
California Rights
Where the California Consumer Privacy Act applies, California residents may have rights to know or access personal information, request correction, request deletion, obtain information about categories of collection and disclosure, opt out of sale or sharing, limit certain uses of sensitive personal information, and receive non-discriminatory treatment for exercising applicable privacy rights. Because MedLlama does not sell or share information for cross-context behavioral advertising, we do not use a sale or targeted-advertising business model for health information.
Exercising Rights
Many account rights can be exercised through MedLlama's self-service export, correction, record-deletion, and account-deletion tools. Where an additional legally required request is necessary, contact privacy@medllama.com.
32. USERS AGED 13 TO 17
Minimum Age
The current MedLlama onboarding flow is designed not to permit use by children under 13.
Users Under 18
For users aged 13 through 17, MedLlama currently requires an additional acknowledgment concerning use under the supervision of a doctor or qualified healthcare professional before the onboarding flow can continue.
Local Legal Requirements Still Apply
The in-app supervision acknowledgment does not override local privacy, contract, medical, or child-protection law. In jurisdictions where parent or legal-guardian authorization is legally required for a minor's account, health-data processing, consent, or use of an online service, the required authorization must be obtained before the minor uses the affected feature.
Health Data of Minors
Health information concerning minors can be particularly sensitive. Users responsible for a minor should provide only information necessary for the requested feature and should exercise appropriate professional or parental supervision as required by law.
Deletion
If we learn that information has been collected from a person in circumstances that are not legally permitted, we may restrict the account and take appropriate steps to delete the affected information.
33. PROFESSIONAL USERS & THIRD-PARTY PATIENT INFORMATION
Authorization Is Your Responsibility
If you are a healthcare professional and submit information concerning a patient or another person, you are responsible for determining that you are authorized to upload, transmit, store, and process that information through MedLlama.
Data Minimization
Professional users should avoid including direct identifiers that are unnecessary for the requested AI-assisted function and should de-identify or minimize information when required by applicable law, institutional policy, professional duties, or the circumstances of the case.
No Automatic Transfer of Professional Duties
Using MedLlama does not transfer your confidentiality, privacy, medical-record, informed-consent, or professional obligations to MEDLLAMA LLC.
Current Single-Profile Design
The current product design is based on one personal profile associated with each account and is not currently presented as a hospital-grade multi-patient record repository. If dedicated patient-record management is introduced, MedLlama will update its privacy disclosures and controls as appropriate.
34. HIPAA & U.S. HEALTHCARE ORGANIZATIONS
Current SaaS Structure
MedLlama is currently offered as a software-as-a-service application and is not currently provided under a Business Associate Agreement with healthcare organizations.
No Current BAA
MEDLLAMA LLC has not represented the current version of MedLlama as a HIPAA Business Associate service and does not currently offer a MedLlama Business Associate Agreement for the consumer/professional SaaS service described in this Policy.
No HIPAA Compliance Claim
MEDLLAMA LLC does not claim in this Privacy Policy that the current service is HIPAA-compliant merely because it processes health-related information.
Covered Entities and Business Associates
If you are subject to HIPAA or another healthcare privacy law that requires a Business Associate Agreement, specialized contractual safeguards, or a specifically approved technical environment before protected health information may be disclosed to a service provider, you must not submit such information to MedLlama unless the required arrangement is in place. Professional users remain responsible for determining whether their intended use is legally permitted.
35. AUTOMATED PROCESSING & HUMAN DECISION-MAKING
AI Generates Outputs
MedLlama's artificial intelligence generates informational and analytical outputs based on the information submitted to the selected feature.
No Automatic Clinical Action
The current version of MedLlama does not automatically prescribe medication, automatically create or change a medication schedule, automatically contact emergency services, automatically send a clinical alert to a healthcare provider, or automatically implement a diagnosis or treatment decision.
User Remains in Control
The user decides whether and how to act on an AI-generated response, subject to the Medical Disclaimer and professional responsibilities applicable to the user.
36. LAW ENFORCEMENT, LEGAL PROCESS & PROTECTION OF RIGHTS
Valid Legal Requests
We may disclose information when we reasonably believe disclosure is required by applicable law, a valid court order, subpoena, warrant, or other binding legal process.
Law Enforcement
We may cooperate with lawful law-enforcement requests when legally required to do so. We do not provide law-enforcement agencies with unrestricted direct access to MedLlama user databases.
Legal Claims
We may preserve or use limited information when reasonably necessary to establish, exercise, or defend MEDLLAMA LLC's legal rights or respond to a dispute.
Narrow Disclosure
Where legally permitted, we seek to limit disclosure to information reasonably responsive to the applicable legal requirement or request.
37. THIRD-PARTY PRIVACY POLICIES
Independent Providers
Google, Firebase, RevenueCat, Apple, and other third-party service providers maintain their own privacy policies and service terms for information they process in their own capacity. This MedLlama Privacy Policy does not replace those third-party policies.
Google provides Firebase, Google Cloud, and Google AI infrastructure used by MedLlama. Google's applicable Firebase, Google Cloud, Gemini API, and privacy documentation governs Google's processing in addition to the contractual terms applicable to MEDLLAMA LLC.
RevenueCat
RevenueCat provides subscription-management infrastructure and maintains its own privacy documentation concerning end-user purchase and technical information.
Apple
Apple processes App Store transactions and Sign in with Apple information under Apple's applicable terms and privacy documentation.
Review Provider Policies
Users may review the current privacy terms of relevant service providers for additional details about their independent processing, international transfers, and retention obligations.
38. CHANGES TO THIS PRIVACY POLICY
Policy Updates
We may update this Privacy Policy when MedLlama adds or removes features, changes its data practices, changes service providers, modifies retention periods, introduces new platforms, changes AI infrastructure, or needs to address legal or regulatory requirements.
Material Changes
Where required or appropriate, material changes may be communicated through the application, website, account interface, or another reasonable method.
Effective Version
The effective version is identified by the policy timestamp or last-update information displayed by MedLlama. Continued use after an update does not eliminate any consent requirement that applicable law requires us to obtain separately.
39. CONTACT US
Privacy Contact
For questions about this Privacy Policy or legally applicable privacy rights, contact: MEDLLAMA LLC 244 5th Ave, Suite 1623 New York, New York 10001 United States Email: privacy@medllama.com Website: www.medllama.app
Security of Requests
Do not send passwords, authentication secrets, unnecessary medical images, or unnecessary health records by ordinary email. We may ask for reasonable verification before acting on a request involving account-associated personal information.