The questions people actually ask

SHELY is a health platform being built in India for women and families, and for the clinicians, labs, pharmacies and hospitals who look after them. The idea is one account across a family of connected apps: cycle and pregnancy tracking, health records, plain-language education, and the tools a clinic actually runs on. It has not launched. Today you can read the health library, use the calculators and join the waitlist.

Thirteen are planned: Care, One, Doctor, Assist, Lab, Rx, Hospital, Manage, Varsity, Vault, Schedule, Billing and Store. Planned is the operative word. They sit at different stages of development, several are still untested internally, and none of them has launched publicly. Each app page on this site says where that one stands.

Nothing is charged today. We are pre-launch, so no billing is running and there is no paid plan you could buy even if you wanted to. The numbers on our pricing page are indicative and will be confirmed before anyone is ever charged. The intention is for personal tracking and the health library to stay free, and we will say so in advance, in writing, if anything becomes paid.

Ten: English, Hindi, Bengali, Marathi, Gujarati, Punjabi, Malayalam, Telugu, Tamil and Kannada. Coverage is uneven and we would rather admit that than claim parity — the interface is translated across all ten, but not every article and page is finished in every language. If a language you need reads badly, tell us and we will prioritise it.

Open care.shely.health in a browser and sign up with your phone number or email, then pick your language. There is nothing to install and no card is needed, because nothing is charged yet. We are not on the Apple App Store or Google Play — join the waitlist and we will email you when native apps exist.

Primarily women and families in India, across every stage from a first period to menopause — and the doctors, nurses, ASHA workers, labs, pharmacies and hospitals who serve them. The consumer apps and the professional apps are designed to share one record, so a lab result or a prescription does not have to be typed in twice.

Join the waitlist and we invite people in batches as capacity allows. We onboard slowly on purpose: a small team shipping health software would rather get it right for a few hundred people than open the doors and break things for thousands. If you have a specific need or timeline, say so when you sign up and we will be straight with you about it.

Not yet. Community spaces are designed and partly built, but SHELY has no public user base to host them. We are pre-launch, which means no members, no forums running, and no adoption numbers we could honestly quote you. Until that changes, the real answer is: email us and a person on the team reads it.

This website, in full: the health library, the condition guides, the calculators and self-checks, and the waitlist. Behind it, the apps are in active development — most features are built but unfinished or untested, and none is production-ready. We would rather write that down than show you a demo and call it a product.

It is written in-house from established medical guidance: clinical guidelines, national health-service material and standard references. It is not clinically reviewed. Independent clinical review is in progress, and until a named clinician has signed off on an article we will not describe it as expert-reviewed, medically reviewed or doctor-approved. If you find those words anywhere on this site, they are wrong and we want to know.

No. Nothing on SHELY diagnoses you and nothing here replaces a consultation. Tracking shows you patterns, calculators do arithmetic, and articles explain what a condition usually looks like — none of that knows your history or has examined you. If something worries you, or a self-check flags a warning sign, see a clinician.

Care is for one person: cycle tracking, pregnancy, symptom logging and the health library. One is for a household — a profile for each family member, shared records and reminders, so one person can keep track for a parent or a child. Both are in development and neither has launched.

It is the clinic-side app: patient history, appointments, digital prescriptions, consultation notes and billing in one place, connected to Lab, Rx and Vault. Those core practice tools are what we are building first. Video consultations are not production-ready, so do not plan live consults around them yet.

Vault is a personal record locker — lab reports, prescriptions, scans, discharge summaries and vaccination records in one place, shared only with people you choose and revocable at any time. It is still in development, so do not move your only copy of anything into it. We will publish the security detail in full before anyone is asked to store real records.

It is planned as a marketplace for health, maternity and baby products listed by third-party sellers, with payments through Razorpay and 7-day returns on eligible items. It is not open to the public. We do not run a clinical vetting programme for sellers, so we will not tell you products are verified — the returns policy is the protection you actually get.

Health education in plain language: periods and PCOS, fertility, pregnancy, nutrition and mental health, written for people rather than for clinicians. There are no certificates, no accreditation and no CME credit attached to any of it. Like the rest of our library it is written from established medical guidance, with independent clinical review in progress.

That is the design: a test ordered in Doctor appears in Lab, the result flows back to the patient record and the doctor's dashboard, and a prescription reaches a pharmacy running Rx. The pieces exist in development. The end-to-end flow is not something you could rely on in a working clinic today.

Assist is aimed at ASHA and community health workers: household visits, maternal tracking, immunisation records and reporting, in local languages. Offline-first field use is the whole reason the app exists, but robust offline support is not in place yet, so it is not ready for a real village round.

We build to it: consent before collection, only the data a feature needs, and your right to see, correct and erase what we hold. The Act's rules are still being phased in and nobody has certified us against it, so designed to comply is an honest description and certified compliant would not be.

In transit with TLS 1.3, at rest with AES-256, and behind role-based access so nobody browses records without a reason. What we do not claim is zero-knowledge encryption: our systems can read your data, because reminders, search and sharing require it. If you see the phrase zero-knowledge attached to SHELY anywhere, it is wrong.

The calculators and self-checks on this site work without an account, and what you type into them is not stored. Inside the apps, anonymous community spaces are designed but not running, because there is no community yet. And an account always carries an identifier — anonymity there would mean other members cannot see who you are, not that we hold nothing.

Not by yourself, not yet. Self-service export is on the roadmap and is not built. Today you email support@shely.health and we do it by hand. Standard clinical formats such as FHIR are an intention rather than a feature — we do not have them, and we are not going to list them as if we did.

Our privacy policy sets the retention periods and they are not all short: account data is kept while your account is active and for a period after deletion, and some records must be held longer where law requires it. Health calculator results on this site are not stored at all unless you choose to save them. Read the retention section before you assume deletion is instant.

No. Linking an Ayushman Bharat Health Account is on the roadmap and there is no working ABHA integration today. This page used to say otherwise; that was wrong and we have corrected it.

Yes, and you do not owe us a reason. Right now it is a manual request: email support@shely.health and we delete the account and the data held against it. A self-service delete control inside the app is being built. The retention exceptions in our privacy policy still apply — records we are legally required to keep.

On infrastructure we run ourselves rather than a managed health cloud, currently hosted with a European provider. We are not claiming Indian data residency, because it would not be true today. If where your data physically sits matters to you or your organisation, ask us before you commit to anything.

No. We do not sell personal or health data and there is no data-broker tracking on this site. The site uses essential cookies for sessions plus product analytics, and the cookie banner lets you turn analytics and marketing cookies off. We have no revenue from data today and no plan to build any.

The plan is that personal tracking, your own records and the health library stay free, with the basics not gated behind a paywall. Nothing is live and nothing is charged, so free tier describes an intention rather than a product you can sign up to today.

We have not fixed it. The figures on the pricing page are indicative and will be confirmed before anyone is charged a rupee. We would rather set the price with the people who use it than quote a number now and quietly move it later.

There will be, and it will depend on size, modules and deployment. We do not publish an enterprise price list or a service-level agreement yet and we are not going to invent one. Start a conversation and we will be straight about fit and timing.

Payments run through Razorpay, so UPI, cards and net banking. Nothing is charged today: Razorpay is wired up for the Store, and subscription billing is not running. We have no invoice terms or credit arrangements to offer, because we have no billing customers.

Set out in full in our Cancellation and Refund Policy: pro-rata refunds of unused subscription time by default, 7-day returns on eligible Store products, refunds to the original payment method, and a refund where something was charged in error or never delivered. We deliberately do not promise a fixed number of days for money to land — that depends on your bank, and we will not invent a timeline before launch.

The pricing page shows an annual option at a discount, but every number on it is indicative while we are pre-launch. Treat it as direction, not a quote.

That is what SHELY Billing is being built for: GST-ready invoices, plans and subscriptions for an organisation. Today the only thing that works end to end is paying an invoice online through Razorpay. Central institutional billing, department cost allocation and dedicated account management do not exist yet.

Barely, and not reliably. SHELY is an online experience today — the web app needs a connection and this website has no offline mode. Offline-first logging matters enormously on real Indian networks and it is on the roadmap, but do not plan around it yet. We will say so clearly when that changes.

No. Apple Health and Android Health Connect need a native app, and we do not have one on either store. There is groundwork in the backend for ingesting wearable data later, but there is nothing you can connect a watch or a ring to today.

Not a public one. There is no published documentation, no sandbox and no keys to issue. An integration API for partners is planned. If you need one, start a conversation rather than waiting for a developer portal to appear.

Eventually, and no lock-in is a principle we intend to keep — your records are yours. Practically: export is manual today and we have not built FHIR or HL7 export. Ask support and we will send you what we hold in a readable format.

Current versions of Chrome, Edge, Safari and Firefox, on desktop and on phones. The site is built mobile-first because most people in India will read it on a phone. You can add it to your home screen for a full-screen view, though that does not give you offline access.

No. Nothing is published on the Apple App Store or Google Play — if you find a store link for SHELY, it does not work. SHELY runs in a mobile browser at care.shely.health and can be added to your home screen for a full-screen view. Native builds are in development and we have not announced a date.

When they ship: a stable connection of roughly 1 Mbps, a device with a camera and microphone, and a current browser. They are not production-ready, so we do not recommend relying on them for a real consultation today.

Cloud-hosted is what we run. On-premises and hybrid are things we would scope with an early partner, not options you pick from a menu. We are not offering data-residency guarantees either, because our current infrastructure is not in India.

None, and we will not print one we cannot meet. We are pre-launch: monitoring and failover are being built rather than measured, so we have no uptime history to stand behind. Availability commitments and support terms will be published before we sign an enterprise contract, not after.

It is designed for it — your branding, your domain, on infrastructure we maintain. Nobody is running a white-labelled deployment today, so treat it as a capability we are building with early partners rather than a shipped feature.

The intent is to connect with the HIS, EMR, LIS and billing systems you already run, and with India's ABDM rails. We have no pre-built connectors and no professional-services team. Bring us the systems you actually use and we will tell you honestly where they sit on the plan.

For early partners, from the people who build the product — not from a training department, because we do not have one. No on-site programmes, no certification tracks and no dedicated onboarding managers. What is on offer is a small team that answers its own email.

None. There is no tiered support desk, no ticket SLA and no phone line. Publishing response times we cannot hold to would be worse than admitting we have none. Email support@shely.health and someone on the team reads it.

No. We hold none — not SOC 2, not ISO 27001. Independent audits and formal certification are on our roadmap and are not completed, so there is no certificate we could send you. What exists is a system designed around DPDP Act principles and recognised security practice, described on our security page.