Submitted care requests
Only this browser has the local keys needed to decrypt request contents. If the keys are missing, Sucha can still see status metadata but not the private details.
Account login
Use this only when you need to verify this browser, switch email, or reload your private dashboard on a new device.
Use the same email you used for care requests. We will send a 6-digit code and a sign-in link.
Email verification is your account login for now. Password/passkey login and reset can be added in the next account phase.
Wallet and payments
Add funds to your Sucha wallet through Razorpay. UPI, Indian cards, and international cards can appear in checkout when enabled by Razorpay and the issuing bank. Care details are not sent to Razorpay payment notes.
Wallet funds can later be used to pay matched providers while keeping care details out of card/UPI payment metadata.
Submitted intake details
The bio/intake details from the first care or provider form are kept inside each request card under “Show submitted intake details.” They stay hidden by default so the dashboard does not expose sensitive details at a glance.
Those details decrypt only on browsers that still have the local request key.
Encryption and recovery
Current care requests use browser-held encryption keys. Password reset can restore account access in a future account system, but it should not unlock old encrypted care details unless a recovery key or trusted-device recovery is configured.
Do not store PHI in email, URLs, payment metadata, analytics, or support tickets.
A local lock helps when someone else uses this device. It does not replace encryption or device-level security.