Privacy Policy

BookedDemo checks the public routes a buyer takes to request a demo, contact sales, request a quote, or start a trial on B2B SaaS websites. It runs those checks as an outside buyer and keeps the evidence. This policy explains what information BookedDemo handles, why, and how to reach us. BookedDemo is currently in private alpha.

What BookedDemo observes

We call each of those routes a Path. A check records what an outside buyer could observe: the public pages visited, screenshots and page captures, how far the check got, timings, and the messages that reached our test inbox afterwards. We store this audit evidence as needed for the product: to produce reports, compare checks over time, and verify fixes.

Standard checks run from outside the website owner's systems and need no access to its CRM or internal systems. A check inside a customer's own systems is scoped separately, runs only with that customer's explicit approval, and is limited to what was agreed. When a customer approves a check that submits a form, books a meeting, or creates an account, BookedDemo uses a test identity agreed for that check, with a BookedDemo test email address, not the details of a real buyer.

Information we collect

Requests from this website

When you send a request from bookeddemo.com, we receive your work email, your name if you give it, the website or Path you entered, and the address of the page you sent it from. We use them to reply and to prepare the work you asked about. Requests are recorded in HubSpot, our CRM, and we attempt to send you a confirmation by email.

This website does not load analytics or advertising scripts.

BookedDemo app accounts

When you create an account at app.bookeddemo.com, we store your name, your email address, and either your password (kept only as a salted hash) or your Google sign-in, along with the workspace, Paths, and settings you set up. During the private alpha, BookedDemo approves each account before it can be used.

If you choose Continue with Google, Google shares your name, email address, profile picture, and Google account ID with us. We use them only to create your account and sign you in. Signing in with Google does not give BookedDemo access to your Gmail, contacts, or files.

Google user data

Apart from the sign-in above, BookedDemo uses Google APIs only with two mailboxes of its own. It does not ask website visitors, customers, or anyone else for access to their Gmail.

Probe mailbox: read-only access

A dedicated BookedDemo mailbox receives the messages sent to the test email addresses our checks use. With read-only Gmail access (gmail.readonly), BookedDemo looks only for messages sent to the test address of a specific check and received after that check started. From those messages it reads the sender, recipient, subject, time received, and the content needed to tell what reached the buyer, for example a confirmation, a calendar invite, or a follow-up. These details are stored as evidence for that check. BookedDemo does not send, change, or delete messages in this mailbox.

Outbound mailbox: send-only access

A separate BookedDemo mailbox sends BookedDemo's own operational emails: confirmations and internal notices for requests made on this website, account emails such as invitations and password resets, and audit emails about checks. BookedDemo uses Gmail send access (gmail.send) only to send these messages. It does not read that mailbox through Google APIs.

How Google user data is used and shared

• We use Google user data only for the functions described above, and only the minimum data those functions need.
• When the purpose of a message from the checked company is unclear, BookedDemo may send that message's subject, sender domain, timing, and an excerpt of up to 2,048 characters of its text to an AI model provider, only to classify that message for that check.
• We do not sell Google user data. We do not use it for advertising, and we do not use it to develop, improve, or train generalized AI or machine learning models.
• We share it with service providers only as needed to run these functions, or when the law requires it.

BookedDemo's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Revoking access

The owner of a Google account can revoke BookedDemo's access at any time from the third-party connections page of their Google Account. Revoking stops any further reading or sending. Evidence already stored stays under this policy until it is deleted.

Service providers

BookedDemo uses Cloudflare to host this website and its request form, Railway to run the app and the checks, S3-compatible object storage for evidence files, HubSpot as its CRM, Google for email and sign-in, and an AI model provider for narrow classification of captured page content and unclear messages. They process data on BookedDemo's behalf to provide these functions.

Access and sharing

Credentials for Google access are kept in server-side configuration and never sent to the browser. Evidence in the app is visible to members of the workspace it belongs to and to BookedDemo operators. A report shared by public link can be viewed by anyone who has the link until the share is revoked.

Retention and deletion

We keep audit evidence while the product needs it, for example to compare checks over time and verify fixes. You can ask us to delete your request, your account, or a customer workspace, and we will delete it from the systems BookedDemo controls. Copies in our providers' backups, and information already sent to a website owner's systems during an approved check, are outside that deletion.

Changes

We will update this page when our practices change and change the date at the top.

Contact

Questions and requests about your information: [email protected].

See also the Terms of Use.