← MyTheraverseOSv1.0.0 · Updated 6 October 2026

Privacy Policy

MyTheraverseOS is a care-coordination product for a child’s therapy. Parents, therapists, schools, and therapy centres use it to keep a child’s record, appointments, and messages in one place. MyTheraverseOS operates it.

This privacy policy is the public statement of how personal data is handled on the website and in the product. Anyone can read it before creating an account. The Privacy Notice is a different document. That notice is what we show when we ask for consent. Signup, the waitlist, and the screening forms record consent against the notice.

This policy is version 1.0.0. It is effective from 1 October 2026. This page was updated on 6 October 2026. Health information remains sensitive personal data under the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, until those rules cease to apply. This page is also the policy published for that purpose.

1. Who is responsible

MyTheraverseOS is the data fiduciary for personal data it collects through the website and the product. A therapist, school, or therapy centre sees a child’s health record only when the parent has granted that share. The product does not appoint MyTheraverseOS as a processor under a separate clinic contract.

Privacy questions and grievances go to hello@mytheraverseos.com. The grievance contact is the Data Protection Grievance Officer, at the same address. A separate Data Protection Officer is not designated. A street address is not published on this page.

2. Who this covers

  • People who visit the website, join the waitlist, or complete a questionnaire
  • Parents and guardians who create an account
  • Children whose details a parent or a care provider enters. A child does not get a login
  • Therapists, schools, therapy centres, and platform administrators who have accounts

3. Information we collect

  • Parent account: full name and email. Parent signup does not ask for a phone number
  • Login: email and password. The password is stored as a hash by the authentication service
  • Waitlist: name, email, phone number, and whether the person is a parent, therapist, therapy centre, or school
  • Questionnaires on the How it works page: the adult’s name and email, the answers, and a guardian declaration when the form is about a child
  • Child profile: name or initials, date of birth, gender, diagnosis, diagnosis status, comorbidities, and milestone notes
  • Health record: diagnoses, assessments, therapy goals, session notes, medications, genetic test details, and comments on a record
  • Files a parent uploads, such as a report or a letter. The file is stored separately from its catalogue row
  • Therapist profile: name, email, phone, specialty, organisation, employment, RCI licence number, bio, experience, appointment types, availability, résumé, and profile photo
  • Messages between a parent and a therapist about a child
  • Care-assistant chats, including the reply that was shown
  • WhatsApp messages forwarded into the product when WhatsApp consent is on. The sender’s number is matched from a server-side list, or from a phone number already saved on the profile. Parent signup does not collect a phone number. Twilio carries the message
  • A voice recording made for a pre-session note, sent to turn speech into text. The recording is not kept as a file. The text can be saved if the parent saves the note
  • Appointment details, the reason, and a pre-session note
  • IP address and browser, recorded when a consent row is saved
  • A session cookie that keeps a signed-in person logged in

We do not collect advertising or analytics cookies. We do not store video recordings of sessions. A video appointment stores a link, not a recording.

4. Health and therapy information

The health record holds therapy and health information about a child: diagnoses, assessments, goals, session notes, medications, genetic-test details, uploaded clinical documents, and comments. A parent enters it, approves an extraction from a file, or a therapist writes it after the parent has shared that child.

It is used to show the child’s care in the product, to support appointments and messages, and, when the matching consent is on, to draft an extraction or an assistant reply. It is not used for advertising. It is not sold.

The parent can read it. A therapist, school, or therapy centre can read the parts their share allows, and only while that share is active. Platform administrators can read child records in the admin tools. An AI provider receives health information only in the cases in section 7.

5. How we collect it

  • Account registration for a parent or a therapist
  • Therapist onboarding, including the résumé and profile photo
  • The child profile form, the health record, and appointment forms
  • Use of messages, the care assistant, and Privacy & Data
  • A WhatsApp message from a registered number, when that consent is on
  • Files the parent uploads
  • The waitlist form and the public questionnaires
  • The sign-in cookie
  • Notes a therapist writes on a child the parent has shared

6. Why we use it

  • Create and manage accounts
  • Store and show a child’s therapy record to the people allowed to see it
  • Book and show appointments
  • Carry messages between a parent and a therapist
  • Contact someone who asked to join the founding cohort
  • Run a public questionnaire the person chose to submit
  • Extract structured fields from an uploaded file, only when AI-extraction consent is on
  • Draft a care-assistant reply, only when care-assistant consent is on
  • Turn a dictated note into text, only when speech-to-text consent is on
  • Forward a WhatsApp message into the assistant, only when WhatsApp consent is also on
  • Translate on-screen text into a language the person chooses
  • Draft a short health-record overview for the parent when care-assistant consent is on, and draft milestone steps for a therapist goal
  • Keep the service secure, limit abuse, and meet legal duties

7. AI processing

These features send information to an outside model. A reply or a draft is not a diagnosis and is not a substitute for a therapist’s judgment. We do not state here whether a provider trains its models on that information. No such restriction is recorded in our product contracts.

  • Document extraction. When a parent clicks Extract and AI-extraction consent is on, the file is sent to Anthropic to propose structured clinical fields. The result stays pending until the parent approves it. Approved fields are saved on the health record. Staff do not review the file before the parent sees the draft.
  • Care assistant. When care-assistant consent is on, a message can include the child’s name, date of birth, diagnosis, and approved goals. That context is sent to Anthropic to draft a reply. The reply is stored in the account. Staff do not approve the reply before it is shown.
  • WhatsApp. A WhatsApp message can be forwarded to that same assistant only when WhatsApp consent and care-assistant consent are both on. Twilio carries the message.
  • Speech-to-text. When that consent is on, a recording from a pre-session note is sent to Sarvam AI in India. The recording is not kept as a file.
  • Interface translation. Text on the screen can be sent to Sarvam AI, or to Bhashini if Sarvam is unavailable, to translate the interface or an assistant reply. That text can include a child’s name. There is no separate consent switch for translation.
  • Health-record overview. When care-assistant consent is on, a short summary for the parent is drafted by Anthropic from the approved record, including the child’s details. When that consent is off, the summary is written in the product from the same record and is not sent to Anthropic. It is not saved as a clinical record.
  • Milestone steps. On a therapist’s goal form, Suggest milestones sends the therapy, domain, objective, baseline, target, and frequency to Anthropic. The child’s name is not attached. The therapist can edit the steps before saving them. There is no separate consent switch. If no model key is configured, a fixed template is used and nothing is sent.
  • Demo sandbox assistant. The sandbox assistant calls Anthropic on fictional scenario data. It does not check care-assistant consent.

8. WhatsApp

If someone messages MyTheraverseOS on WhatsApp, Twilio receives the message in order to deliver it. We forward it to the care assistant only when WhatsApp consent is on and care-assistant consent is on. The stored reply does not repeat the inbound message. Turning WhatsApp consent off stops further WhatsApp messages from being processed in the product.

WhatsApp and Twilio operate their own services. MyTheraverseOS does not control their networks, their retention, or their own terms. A message can sit with that provider even after the switch in MyTheraverseOS is turned off.

9. Who else receives it

  • A therapist, school, or therapy centre, only for a child the parent has shared, and only while the share is active
  • The service providers below, for the purpose named
  • Razorpay, when a therapist pays for a subscription. Card or UPI details are entered on Razorpay’s page. We do not store the full card number
  • A public authority, when the law requires a disclosure

Service providers:

  • Supabase — Authentication and database (India (Mumbai, ap-south-1))
  • Amazon S3 — Private storage of uploaded health documents, therapist résumés, and profile photos. Files open through short-lived links (India (Mumbai, ap-south-1))
  • Anthropic — AI document extraction when you trigger Extract, and the care assistant when care-assistant consent is on (United States)
  • Vercel — Application hosting (United States / global edge)
  • Sarvam AI — Translation of the interface and assistant replies into Indian languages you choose; speech-to-text only when that consent is on (India)
  • Twilio — Deliver WhatsApp messages when WhatsApp consent is on (United States)
  • Bhashini (MeitY, Government of India) — Fallback translation of the app interface and assistant replies into Indian languages you choose (India)

We do not use an analytics provider. We do not sell personal data.

10. Storage and security

  • The site is served over HTTPS
  • A signed-in person can read the rows their role is allowed to read
  • Child-record files, therapist résumés, and profile photos are stored in a private Amazon S3 bucket in Mumbai. A parent opens a file through a short-lived link. A therapist can view a child’s document in the record; the original file is not offered as a download.
  • Passwords are stored as a hash

The database host describes its stored data as encrypted. We do not hold a separate security certification, and we do not run a separate backup archive in the product. The host may keep its own infrastructure copies. We do not set a distinct backup period here.

Write to hello@mytheraverseos.com if you believe data has been exposed.

11. How long we keep it

  • Account and health records: up to 7 years after last activity, unless erasure is requested sooner
  • Consent logs: 7 years
  • Grievance and request records: 3 years

An administrator runs retention from Privacy requests. Consent logs older than 7 years are deleted then. Closed grievances and other closed requests older than 3 years are deleted then. Open requests stay. Child profiles, health records, and uploaded files are deleted when that account has had no activity for 7 years. The login stays until an administrator approves an erasure request. Accounts with no activity for 24 months are listed for review and are not deleted by that list.

12. Deletion

A signed-in person can ask for account deletion from Privacy & Data by choosing Erasure / deletion. That sends a request and signs them out. An administrator deletes the account from Privacy requests. Until then the account still exists. Deletion removes the account, child profiles, health records, and files. The consent and request log is kept. The name, email, IP address, and the text they typed are removed from that log, and the row says “Removed on erasure”.

Choosing Withdraw consent under Submit a request deletes uploaded documents from Amazon S3 and health-record entries extracted from those files. The account stays, and notes entered by hand stay. The consent switches are separate: turning one off stops that purpose and does not by itself delete files.

A correction or grievance submitted on that form is queued for a person to answer. The reply shows in Request history. A nomination stores the nominee’s name, email, and relationship, and gives you a link to send them. The link does not include health information. Accepting does not let them sign in, and the product does not detect a death. After they accept, an administrator records that the account holder has died or cannot act. The same link can then download the data or ask for the account to be deleted.

Someone without an account can ask to delete a waitlist or questionnaire row by emailing hello@mytheraverseos.com from the same address they entered. An administrator account cannot erase itself from this form.

13. Your rights

  • Access. Data access on Privacy & Data downloads a zip file: a readable report, plus the uploaded files that are in Amazon S3. Export my data does the same download.
  • Correction. Edit your own profile and health record in the product, or submit a correction request. A reviewer applies it or replies in Request history. The form does not edit the record by itself.
  • Erasure. Privacy & Data sends the request and signs the person out. An administrator deletes the account from Privacy requests. The account remains until then.
  • Withdraw consent. Submit a request of that type to delete uploaded documents and extracted entries. Use the switches to turn a purpose off without deleting files.
  • Grievance. Submit it on Privacy & Data. The officer replies in Request history within 30 days. You can also email hello@mytheraverseos.com.
  • Nomination. Enter the nominee’s name, email, and relationship. Send them the link. They accept or decline on a page that shows no health information. After an administrator confirms death or incapacity, that link can download the data. It does not create a login.

A complaint may also be made to the Data Protection Board of India, in the manner the Board publishes.

14. Consent and withdrawal

At parent or therapist signup, the account form asks for consent to the Terms of Service and the Privacy Notice. A parent also consents to child-data processing, declares they are the parent or lawful guardian, and consents to storage of the child’s health records. Those ticks are what is stored.

Later, Privacy & Data has separate switches for AI document extraction, the care assistant, speech-to-text, and WhatsApp. Each stays off until it is turned on. The sign-in cookie notice records essential-cookie consent when a signed-in person dismisses it.

Turning off child-data processing, the guardian declaration, or health-record storage records the withdrawal and withdraws therapist, school, and therapy-centre shares. Records already stored stay until erasure. Turning the switch back on records consent again. A single share can be withdrawn on the same page without turning the others off. Turning off the care assistant, speech-to-text, WhatsApp, or AI extraction stops further use of that feature.

The consent log, and processing needed to keep the service secure or to meet a legal duty, can continue after a purpose is withdrawn.

15. Children

A child does not create an account. A parent enters the child’s details. The parent declares that they are the parent or lawful guardian and consents on the child’s behalf. That declaration is stored. The form does not verify identity or age. Initials may be used instead of a full name. A child’s data is not used for advertising.

16. Cookies

We use a strictly necessary cookie so a signed-in session stays logged in. We do not use advertising or analytics cookies. Details are in the Cookie Policy. Clearing the cookie signs the person out.

17. Data outside India

Uploaded documents, résumés, and profile photos are in a private Amazon S3 bucket in Mumbai, India (ap-south-1). The Supabase project that holds accounts and records is also in Mumbai. Anthropic, Vercel, and Twilio process data in the United States. Sarvam AI and Bhashini process data in India. Razorpay processes a therapist subscription payment. We do not publish a separate transfer agreement on this page.

Each provider publishes how it stores and processes personal data, and how it protects that data. Those pages are the provider’s own, and they can change them.

18. A personal data breach

If we become aware of a personal data breach, each account holder sees a notice in the product. The notice describes what happened, the likely impact, and what the person can do. People who only joined the waitlist or completed a questionnaire, and who have no account, are not emailed. An administrator prepares a notice for the Data Protection Board of India and records the time they submit it. The detailed notice is due within 72 hours of becoming aware. Questions go to hello@mytheraverseos.com.

19. Changes

If this policy changes, the date at the top of this page changes with it. An existing account is not asked to consent again automatically when the version number changes. The Privacy Notice has its own date.

20. Contact

MyTheraverseOS
hello@mytheraverseos.com
Data Protection Grievance Officer: hello@mytheraverseos.com