Frequently Asked Questions

Pro Therapy is iMegha's first vertical product — an AI scribe for cash-pay solo private-practice therapists. You record the session, AI drafts a SOAP note, you review and sign. The difference: all patient data stays in your own AWS account, not on a vendor's server. See /pro-therapy/ for details.

Yes. Patient data — audio, transcripts, notes — stays in your own AWS account; iMegha never sees PHI. BAA included with your subscription; pair with the AWS BAA (free, covers infrastructure). End-to-end encryption in transit and at rest. Audio auto-deleted after processing. CloudTrail audit logging.

Whisper handles transcription (high accuracy for clinical dictation in a quiet room; slight error rate on numbers, medication names, specialty terms). Claude Sonnet 4.6 generates the SOAP note. You review and edit before signing — no note is auto-saved or auto-signed. The AI is a draft generator, not a replacement for clinical judgment.

You correct it before signing. Every section of the SOAP note is fully editable. After signing, the note is locked — same as any clinical record. If you need to correct a signed note, you create an addendum that preserves the original for audit.

Currently in early access. Pilot users get founder pricing — reach out and we'll discuss. You'll also have a direct AWS bill for the resources running in your account; typical usage (100-150 sessions/month) runs under $2/month on AWS.

Import support is on our roadmap. Today, Pro Therapy is for new sessions — start using it for your next session and your patient history builds up over time inside iMegha. If migrating matters for your decision, tell us and we'll prioritize.

We provide an iMegha BAA covering the application layer (authentication, app behavior, AI model). It pairs with the AWS BAA (free, provided by AWS) covering the infrastructure layer where your data lives. Both take a few minutes to sign during onboarding.

No. Bedrock invocations run in your AWS account, not a shared service. Your audio and SOAP notes are never sent to a third-party model training pipeline.

Roughly in priority order: patient roster (link notes to specific patients), note signing + lock, PDF export, receipt/superbill generation, treatment plans, mobile app. We're early — your feedback shapes priorities.

Email us with "iMegha pilot" in the subject. We'll schedule 30 minutes to walk through your workflow and show the system. If you decide to try it, one-time AWS account setup takes ~15 minutes (we walk you through). First SOAP note can be generated within an hour of signing up.

iMegha is a personal cloud platform where YOUR data stays in YOUR cloud account. We provide the app — you provide the cloud. Your files and messages are locked before they leave your browser, and we can never see them.

With traditional cloud storage, your files live on their servers and they hold the keys. With iMegha, your files are encrypted before they leave your browser and stored in your own cloud account. iMegha does not have access to your data — we only ever see encrypted gibberish.

Not at all. The app looks and feels like any modern cloud storage. The only extra step is creating a cloud account (free) and following our guided setup to link it. The encryption happens automatically in your browser.

A Guest account is free and doesn't require a cloud account. Guests can receive shared files, view content, and connect with others. They can't send messages, upload files, or share — for that, they'd upgrade to a Personal Cloud.

Your data is locked in your browser using bank-grade encryption (the same standard used by governments and banks) before it ever leaves your device. We use multiple layers of locks — each file and conversation gets its own unique key. We never see the unlocked version.

No. Your files are encrypted in your browser before they ever leave your device. iMegha does not have access to your data — all we ever see is encrypted gibberish that is completely useless without your password. We cannot read your files, even if we wanted to.

iMegha does not have access to your data, so there is nothing useful to steal. An attacker would only find encrypted gibberish (useless without your password), public keys (public by design), and email addresses. They would NOT get: your files, messages, passwords, or private keys. Your data stays encrypted and safe in your own cloud account.

Use your 24-word recovery phrase to reset your password. If you lose both your password AND recovery phrase, your data is permanently inaccessible. This is by design — it means no one can access your data without your credentials.

All the technical specifics — encryption algorithms, key hierarchy, infrastructure architecture, threat model — are in our Technical Whitepaper at /whitepaper/.

For typical personal use (a few GB of files, moderate messaging): $5-20/month paid to your cloud provider. During your first year with free tier, it can be as low as $0-5/month. iMegha does not charge a platform fee during beta.

No. You can create a free cloud account during setup. The free tier includes generous storage and API allowances — more than enough to get started.

Your data stays in your cloud account. You own it. You can continue accessing it directly, migrate it to another service, or delete it. There's no vendor lock-in.

When you share a file, it stays in your cloud. Your browser creates a special key for the recipient. They view the file directly from your cloud in their browser and unlock it with their key. No copies on our servers. Recipients can view shared files in-browser but cannot download them — the file never leaves your cloud.

Yes. Revoking deletes the recipient's key. Without it, they can no longer view the file — even if they have a cached copy of the scrambled version.

Not yet, but public share links are coming soon. Currently, recipients need at least a free Guest account to receive shares.

Yes. Every share, view, and download is logged in your cloud's audit trail. You can see who accessed what and when — all stored in your own cloud, not on our platform.