privacy
This website is the front door. It does not run the assistant, and it does not show a dashboard.
Sign-in keeps an access token and a refresh token in local storage on this browser so you can finish onboarding. Sign out clears them. The Google return puts those tokens in the address fragment, which is not sent to the website host. The page removes the fragment after saving the tokens.
Payments go through Razorpay. The browser receives a publishable checkout key and an order id from the Admeasy API. Card and UPI details stay with Razorpay. Admeasy confirms the payment with a signature check on the server.
Phone verification asks you to send a one-time code on WhatsApp, from the number you typed, to the Admeasy business number. That ties the number to your account. The code is also kept in this tab's session storage until it expires or you finish, so a refresh can still show the QR code.
When you later ask Admeasy to use a cloud computer or a linked laptop, it can see that screen for the task. Screenshots from that work are kept for a short time, about 15 minutes, then dropped. Don't send a password in the WhatsApp chat.
Optional analytics on public pages use Google Analytics 4 only after you opt in on the banner. We send page views and a coarse referrer class (for example ai search) without phone numbers, email, or chat content. See your browser local storage key admeasy.analytics.consent to clear the choice.