Privacy policy

Effective November 6, 2026. This policy covers Client Onboarding POC, the invitation-only onboarding service at app.bennybot.ai. Contact its operator at [email protected] for support, privacy questions, or a request to delete your stored data.

Information we use

• Account and checklist information: your name, email, Google account identifier, invitation, approved tasks, consent records, task outcomes, and timestamps.
• Google authorization: encrypted access credentials needed to carry out the tasks you approve. Google handles your password and Google verification; the app does not collect your Google password.
• Gmail: with your permission, the app searches recent messages for selected publishers and processes matching message headers and contents to verify deliveries or recognize newsletter confirmation links. Google grants mailbox-wide read access. The app does not send, delete, or mark email as read.
• YouTube: the app uses YouTube API Services to check your account/channel and selected subscriptions, create approved subscriptions, and store channel identifiers, titles, and task results. The granted scope includes broader content-management rights; the implemented tasks only check and create the subscriptions you approve.
• Sign-in and operation: essential session cookies, temporary invitation state in browser session storage, encrypted authenticator setup data or passkey public keys for workspace operators, and operational/security records.

How information is used and shared

We use this information to authenticate you, run your approved checklist, prevent duplicate actions, show results, and operate and secure the service. Your workspace owner and assigned assistant see client identity, consent/status information, and checklist results. The workspace interface does not expose your Gmail message contents, Google credentials, or private browser controls to assistants.

Your email is sent to the publishers you approve and their signup providers. Google receives API requests for your connected services. DigitalOcean hosts the application and its database. Browserbase runs private browser sessions used for publisher signup forms, which may process your email and pages visited for those tasks. The app disables browser session recordings and does not export browser cookies; providers may retain their own operational records. Publishers and these providers also operate under their own privacy policies.

The app does not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Google API data is used and transferred only for the disclosed user-facing functionality and permitted operational purposes, consistent with the Google API Services User Data Policy, including its Limited Use requirements. Google services are also covered by the Google Privacy Policy.

Optional video viewing

Opening Watch playlist loads a visible YouTube player in privacy-enhanced mode. You choose when to start playback. YouTube receives your browser/network information and the app's origin, but the app does not send your invitation, account identifier, or Google authorization credentials to the player. YouTube handles playback data under its own privacy policy. This app does not record viewing history or watch time, report viewing to your assistant, or use it to mark checklist tasks complete. Closing the section removes the player and stops playback.

Storage and retention

Stored Google refresh credentials and authenticator secrets are encrypted. Raw Gmail message bodies, subjects, message IDs, and confirmation URLs are processed temporarily and are not saved to the app database or shown in the workspace. The app stores hashed message references and limited confirmation outcomes instead.

Checklist authorization lasts up to seven days in this pilot. Expiration stops further authorized work and triggers credential cleanup. Disconnect stops new tasks and schedules revocation and removal of saved Google credentials; cleanup may be delayed if a provider is unavailable. Client identity, consent, task history, and operational records are retained for the pilot's status and support functions until removed through a deletion request. Disconnecting alone does not delete those records. Infrastructure backups may retain prior copies until the provider's normal backup expiry.

Your choices

You can decline Google permissions, use Disconnect Google on your client page, or revoke access in your Google account connections. To request deletion of stored client data, email [email protected] from the connected address. We may need to verify the request. Disconnecting does not undo newsletter signups or YouTube subscriptions; manage those with the publisher or YouTube.

If the service changes how it uses Google data, its disclosures will be updated and new consent requested before the changed use.