mySEHA App — Privacy Policy

1. Who we are

The App is operated by VETRA LLC ("VETRA", "we", "us", "our"), 6th Floor, 1 Roxy Square, Heliopolis, Cairo, Egypt. VETRA is the data controller for the personal data processed through the App.

• Privacy and data-rights requests: privacy@myseha.ai
• Support: support@myseha.ai
• General: hello@myseha.ai

2. The data we collect

a. Account and identity. Your email address and/or phone number (used to sign in); your password, stored only as a secure hash by our authentication provider; and, if you sign in with Apple or Google, the basic identifiers those services return. We also generate a mySEHA patient identifier for your record.

Please note: your phone number is stored in ordinary (unencrypted) form in our authentication system, as it must be to send you a login code. We say this plainly because an earlier version of our in-app text said otherwise, and it was wrong.

b. Health profile. First and last name, date of birth, sex, country, language preference, and the health context you choose to enter — height, weight, activity level, blood type, allergies, declared conditions, health goals, and, where you provide them, pregnancy, lactation, menopausal status, hormonal contraception and cycle length.

c. Health and medical data — special-category data. The core of the App:

• Lab reports and medical documents you upload, as files and as the values extracted from them
• Biomarker values, reference ranges and the hormonal context of a blood draw
• The analysis, health scores, findings, recommendations and biomarker connections the App generates from them
• Medications, doses, adherence logs, prescriptions, and the prescribing doctor and clinic where these appear on a prescription
• Vital signs — blood pressure, pulse, blood glucose, waist measurement — and any notes you add
• Weight, body measurements, and body-composition results from DEXA or InBody scans
• Symptoms, mood, energy, sleep, and any free-text or voice-dictated notes
• Meals, nutrition, hydration and fasting logs, and the meal photos you send to be read — kept even if you do not log the meal, and deleted when you delete that profile or your account
• Vaccinations, preventive screenings and test reminders
• Insurance card details and emergency contacts
• Family health history
• Health and fitness data you choose to share from Apple Health or Health Connect — steps, distance, active energy, exercise, resting heart rate, heart-rate variability, blood-oxygen saturation, respiratory rate, body temperature and sleep

d. Family and dependant records. If you use the family feature, everything in (b) and (c) for each family member whose record you create — including a child in your care. Records for children include paediatric growth measurements.

e. Device and diagnostic data. Crash reports, error diagnostics and performance data, so we can find and fix faults. App version, build, platform, operating-system version and language. Your push-notification token, if you enable notifications.

f. Contact with us. Support messages, feature requests and votes, and any screenshot you attach.

g. Purchases. If you buy an analysis inside the App on an Apple device, the payment is taken by Apple and the purchase is handled by our payments provider, RevenueCat, which receives your mySEHA account identifier. We keep a record of each purchase: the store, the transaction identifier, the product, the price and the currency, and any cancellation or refund. We never receive your card or bank details — Apple holds those.

What we do not collect. We do not collect your location — the App requests no location permission. We do not collect national-identity documents, and we do not perform identity or liveness verification. We do not use advertising identifiers or build advertising profiles. We do not perform facial recognition on any photograph you upload.

3. How we use your data, and our legal basis

Under Egypt's Personal Data Protection Law No. 151 of 2020 and, where it applies, the GDPR, your health information is sensitive or special-category data. We process it on the basis of your explicit consent, which you can withdraw at any time (Section 8). Withdrawing consent does not affect processing already lawfully carried out.

How that consent is given. After you set up your basic profile — such as your name, date of birth and sex — and before you can use the App, you are asked to tick three statements, none of them ticked in advance: that you consent to mySEHA processing your health information; that your data is stored outside Egypt and that your results and the documents you upload are sent to AI providers in the United States, who can technically read them; and that the App gives educational information and does not replace a doctor. The App cannot be used until all three are ticked. We record your acceptance against your account, with the version of the wording you accepted and the time. Each acceptance is added as a new record and never overwrites an earlier one, and if the wording changes you are asked again.

A separate permission for each AI provider. Before a document or photo is first sent for analysis, you are asked separately for permission to send it to Anthropic. Before a voice note or a food search is first sent, you are asked separately for permission to send it to Google Gemini. Each screen names the company and says what is and is not sent, neither permission counts as the other, and you can withdraw either one at any time in Me → Privacy & Data. Withdrawing stops new documents, photos, recordings and food searches from being sent, but it does not stop work already under way on something you had sent before.

One thing these permissions do not cover: the short written explanation of your health scores is generated by Anthropic automatically when your scores are calculated, and it is not behind the separate Anthropic permission. It relies on the consent you gave to the three statements above.

We do not sell your personal data. We do not use it for advertising. We do not use your health data to make automated decisions producing legal or similarly significant effects about you — the App's analysis is educational information for you to read and discuss with a doctor, not a decision taken about you.

4. Artificial intelligence, and what it means for your data

The App's analysis is generated by artificial intelligence. This matters for your privacy in a way you should understand clearly.

To analyse your data, our AI providers must be able to read it. There is no way to have a service that explains your lab results while keeping those results secret from the system doing the explaining. We will never claim otherwise.

• Anthropic (United States) receives your biomarker values and health context to generate your analysis, and receives the images of the documents you upload — lab reports, prescriptions and scans — in order to read them, and the photos of meals and nutrition labels you take to log food, in order to identify the food. Where a document prints your name, your doctor's name or your clinic, that text is in the image. Under our agreement, Anthropic retains API data for up to 7 days for operational and safety purposes and does not use it to train its models.
• Google (United States), through its Gemini service, receives the audio of a voice note if you record one, in order to transcribe it, and the name of a food you type into search when we cannot match it from our own food data. Neither is sent with your name, your contact details or your health records — but a recording carries your voice. The audio is not stored by us. Under Google’s terms for paid use of its API, which is how we use Gemini, Google does not use this data to improve its products, and logs it for a limited period to detect misuse.

Before your structured data is sent for analysis, we remove direct identifiers, replace your identifiers with a pseudonymous token and reduce dates to the month. Your age is handled differently depending on the step. For the main analysis of your lab results we send your exact age, because some reference ranges depend on exact age and cannot be applied correctly to an age band. For the explanations of individual biomarkers and of your health scores, your age is grouped into a band. None of this applies to document and photo images, which are sent as they are.

The output is educational information, not a medical diagnosis or treatment. It is generated by an automated system and can be incomplete or wrong. Always consult a qualified physician before acting on anything the App shows you.

5. Who we share your data with

We share data only with providers that help us operate the App, and only so they can perform that function for us. We never sell your data and never share your health information with advertisers or data brokers.

Our current sub-processors, what each receives, and where they process it, are listed on our Sub-processors page. In summary:

Apple Health and Health Connect are read on your device. We read what you permit and store it in your mySEHA record; we never write back to them.

We may also disclose data where required by law, or to protect our rights or the safety of people. Our approach to such requests is published in our Law Enforcement Request Policy.

6. Where your data is stored

Your data is stored and processed outside Egypt, on servers in the European Union (Ireland). Crash diagnostics are processed in the European Union (Germany). AI analysis, voice transcription and food-search matching are carried out by providers based in the United States — Anthropic and Google — and some other providers listed above also operate from the United States. Google’s terms allow it to process data in any country where it or its agents have facilities.

We rely on your explicit consent and on our providers' contractual and technical safeguards, including Standard Contractual Clauses where applicable.

An honest note on access. Because our service must read your data to analyse it, our hosting and AI providers can technically access it in order to provide their services, and may be compelled to disclose data under the laws that apply to them. We do not use end-to-end encryption, and we will never claim that we or our providers are unable to see your data. We protect it with the measures in Section 7 instead.

7. How we protect your data

• Encryption in transit — all traffic uses HTTPS/TLS.
• Encryption at rest — AES-256 at the storage layer, applied to the database and to uploaded files.
• Additional field-level encryption — AES-256-GCM with a separately held key is applied to insurance card details and emergency contact details. To be precise, and because the distinction matters: this additional layer does not currently cover lab results, biomarker values, medications, vital signs or the analysis — those are protected by storage-layer encryption and access control.
• Row-level security — every table holding personal or health data enforces, in the database itself, that a record can only be read by the account that owns it. Row-level security is enabled on every one of our tables; the only ones readable across accounts are shared reference information that is the same for everybody — such as our biomarker and food catalogues — and the public feature-request board, where you choose what to post.
• Private file storage — uploaded documents are held in private storage and served only through short-lived signed links.
• On-device protection — data cached on your phone is encrypted with a key held in the device keychain, and you can require Face ID, Touch ID or your device passcode to open the App.
• Separation — the mySEHA website and our content system run on entirely separate infrastructure with no route to the health database.

No method of storage or transmission is completely secure, and we cannot guarantee absolute security.

8. Your rights

Under the PDPL and, where it applies, the GDPR, you have the right to access your data, correct it, delete it, withdraw consent, object to or restrict our use of it, receive a copy in a portable form, and complain to the competent authority — in Egypt, the Personal Data Protection Centre.

Deleting your account. You can delete individual records at any time, and you can delete your entire account from Me → Privacy & Data → Delete your account. You will be shown what will be erased and asked to type DELETE to confirm. Doing so removes your health records, your uploaded documents and your account from our live systems, and removes your contact from our email provider. Full detail, including how to request deletion without installing the App, is on our Delete your account page.

Deletion cannot reach copies held briefly by providers outside our systems — such as our AI providers’ short-term operational retention, or our diagnostics provider’s error records — which expire on their own schedules.

Getting a copy of your data. We do not yet offer automated export from inside the App. Email privacy@myseha.ai and we will prepare and send your copy within the time the law requires. We would rather tell you this than offer a button that does nothing.

Withdrawing consent. Email privacy@myseha.ai. Because the App's core purpose is to process your health data, withdrawing that consent means we can no longer provide the service, and we will help you delete your account.

9. How long we keep your data

We keep your data for as long as your account exists, so that your health record accumulates and your trends remain meaningful over time. We do not currently apply an automatic expiry to health records.

When you delete your account, we remove your data from our live systems immediately. Backups are overwritten on a rolling schedule, and we may retain the minimum required to meet a legal obligation.

10. Children and family records

The App is intended for adults, and you must be 18 or older to create an account.

The family feature lets you create and manage a record for someone in your care, including a child, only where you are that child’s parent or legal guardian. By adding another person’s data you confirm you have the authority to do so and that you are responsible for that record. Records for children may include growth measurements and other paediatric health data, and we treat children’s health data as the most sensitive data we hold.

We do not currently verify age at sign-up. We are telling you this rather than implying a control we do not have. If you believe a child has created their own account, contact privacy@myseha.ai and we will address it.

11. Diagnostics, and what we do not do with them

We do not use any third-party analytics or advertising SDK. No analytics vendor receives anything.

The App does record a small amount of usage information into our own database, and you should know what that includes. Most of it is shape-only — that an action happened, not what it contained. One exception is worth stating plainly: when you open the page for a particular biomarker, we record which biomarker it was, against your profile and the time. We use this to understand which parts of the library people find useful. It is health-adjacent information about you, it stays in our own systems, it is never sold or shared, and it is deleted with your account.

Medication reminders are scheduled and delivered by your own device and do not pass through us or any third party.

Our crash diagnostics are configured to strip request bodies, cookies and headers, to drop console logs, and to redact values matching a list of health and identity terms. Session replay is switched off. Two things you should know precisely: crash reports carry your account identifier, and performance events carry the names of the screens you visited together with a profile identifier — in a health app, a screen name can itself be revealing. We are working to remove that association.

12. Changes to this Policy

We may update this Policy. We will change the "Last updated" date and the version above, and for material changes affecting how we use your health data we will notify you in the App and, where required, ask for fresh consent.

13. Contact

VETRA LLC
6th Floor, 1 Roxy Square, Heliopolis, Cairo, Egypt
privacy@myseha.ai