inDemo
inDemo is a business application for software companies. It runs live, voice-guided demos of your product for your sales leads — driving your real product in a real browser, narrating out loud, answering questions — and then emails each lead a recap of the demo they were given.
What inDemo does
A visitor on your website clicks a link and gets a real demo immediately, at any hour, without booking a call. inDemo opens your actual product in a browser, walks through the flow you taught it, and speaks to the visitor while it does. The visitor can interrupt, ask questions out loud, and take the controls themselves. Every demo captures the lead's name and email, and ends with a follow-up email containing the recording and answers to what they asked.
The follow-up email is the only part of inDemo that touches Google. Everything else — running the demo, the voice, the recording, the dashboard — works with no Google Account connected at all.
How inDemo uses Google user data
Connecting a Google Account is optional. Its only purpose is to let the demo recap go out from your own address instead of ours, so the prospect receives it from a person at your company rather than from a third-party tool. If you never connect one, inDemo sends from its own domain and requests nothing from Google.
When you do connect one, inDemo requests exactly two scopes:
https://www.googleapis.com/auth/gmail.send
Why it is needed: to send the demo recap and follow-up emails from your address. This is the entire feature — there is no way to send mail as you without it.
What it is used for: sending only. inDemo sends a message when a demo ends, or when you or your demo agent explicitly compose a follow-up from the dashboard. It sends nothing else.
What it cannot do: this scope grants no read access whatsoever. inDemo cannot read, search, list, download, forward, or delete anything in your mailbox, and does not attempt to. Replies from your prospects do not arrive through Gmail either — they are routed through a separate reply address on our own mail infrastructure.
https://www.googleapis.com/auth/userinfo.email
Why it is needed: so the dashboard can display which Google Account is currently connected, and so you can confirm mail will go out from the right address before a demo ever sends one.
What it is used for: displaying the connected address, and nothing else. It is not used to build a profile, and it is not matched against any other data set.
What we store, and for how long
- The refresh token Google issues, encrypted at rest, so recaps can send after a demo without you re-authorising each time.
- The connected email address, shown in your settings and used as the From address.
- The message and thread IDs Gmail returns when a message is sent, so a follow-up threads under the original instead of starting a new conversation.
We store no message content, no contacts, and nothing else from your Google Account. Disconnecting in inDemo's settings, or revoking access from your Google Account permissions, ends the access and deletes the stored token.
Limited Use. inDemo's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically: we do not use Google user data for advertising or to serve ads; we do not sell it; we do not transfer it to third parties except as necessary to provide or improve this feature, to comply with applicable law, or as part of a merger or acquisition; we do not use it to train machine-learning or AI models; and we do not allow humans to read it except with your explicit consent, for security purposes, to comply with applicable law, or where the data is aggregated and anonymised for internal operations.
More
Our full Privacy Policy covers everything else inDemo collects, and the Security page describes how credentials and tokens are protected. Questions about any of this: support@indemo.ai.
Never miss another lead.
30 free demo minutes · no card