Privacy policy

Data accessed and why

Access is limited by the Google permissions you grant and the task you authorize. Depending on that task, the integration can access:

• Account identity: basic profile information and email address to identify the selected account and keep account workflows separate.
• Gmail: message and thread content, headers, attachments, labels, and drafts needed to find, summarize, organize, draft, send, or reply as instructed.
• Google Drive: accessible file and folder metadata and contents needed for search and reading, plus the project files and folders the integration creates and manages.
• Google Calendar: calendar list and settings, event details, attendees, and scheduling information needed to read availability and manage requested events.

Permissions enable these capabilities; they do not authorize unrelated work. This integration uses Google data to perform the requested email, file, and scheduling workflows.

AI processing and sharing

When you use an AI agent for a task, relevant command output, including message, file, or event content, may be included in that agent’s context and sent to its model or service provider. Only retrieve and provide data appropriate to that task. The selected platform, model, account settings, and service terms govern that provider’s processing and retention; this integration cannot guarantee that data stays on the local machine.

Sending a requested email, inviting an attendee, or explicitly sharing a file also discloses its contents to the recipients you authorize. RCE Workspace Tools does not sell Google user data or use it for advertising, data brokerage, or credit decisions. It does not operate a separate model-training service.

Use and transfer of information received from Google APIs must adhere to the Google API Services User Data Policy, including its Limited Use requirements. Select agent services and settings consistent with these limits. This informational site does not certify any agent provider’s compliance.

Storage and retention

Google OAuth credentials and token caches are stored in private account profiles on the operator’s device, outside the project repository. The configured CLI encrypts its saved credentials; local keys and token caches still require filesystem protection.

Task data may remain in agent conversations, local downloads, task outputs, project records, backups, and any Google files or messages you create. There is no single automatic deletion period across these locations. Retention follows the chosen agent service and the operator’s handling of each saved artifact. Operational records should preserve only necessary task evidence, not credentials or unnecessary private content.

The public Firebase-hosted website contains informational pages only. It has no account connection form, analytics scripts, advertising, or application cookies. Hosting providers may process ordinary request metadata such as IP address, browser information, requested URLs, and timestamps to deliver and protect the site. Google account content and OAuth credentials are not uploaded to this website.

Control, revocation, and deletion

You can revoke the app’s future access through Google Account connections. Revocation does not erase existing messages, files, events, saved outputs, or agent history. Delete those separately using the relevant Google service, local storage, or agent platform controls.

For help removing operator-controlled local credentials or task records, contact jonathan@brightprice.com. Provider-managed history and backups remain subject to that provider’s controls and retention rules.

Changes and contact

This policy will be updated when the workflow’s data practices change. A new use of Google data requires updated disclosure and any required consent before that use begins. Questions can be sent to Jonathan at jonathan@brightprice.com.