How Brandpatch handles your data
Brandpatch LLC operates Brandpatch AI from Florida, United States. This notice explains the information used for your account and work, Google connections, sharing and removal. Contact info@mybrandpatch.com about privacy.
Updated October 21, 2026
Account and workspace information
Brandpatch stores your account identity, profile, role and preferences to manage access. Passwords are stored as hashes. Sign-in records include sessions, timestamps, IP addresses and browser information.
Early-access requests include the details you submit for review. Prompts, replies, job records and workspace files are saved so you can return to your work. Usage and operational records support limits, execution and recovery.
If you email support, Brandpatch receives your contact details and the content you choose to provide.
The Google access you choose
Connecting Google is optional. Each connection belongs to your signed-in Brandpatch account. Choose only the capabilities you need:
- Read Gmail: Search messages and read their text. Remote images are not opened. When you request an attachment transfer to Drive or a forward with selected original files, the server reads those exact named attachment bytes; the files are not sent to the AI model.
- Send email: Send the email or threaded reply you request from your connected account. Ask for a draft to review it first.
- Read Drive: Search files and extract bounded text from supported text, Google Docs, Sheets, Slides, PDF and Office documents. Scanned, encrypted, oversized and unsupported documents may not provide readable text.
- Write Drive: Create plain-text files or update an existing plain-text file’s name and content. You can also create native Google Docs or Sheets, append text at the end of a selected Doc tab, or append rows of text, numbers or booleans after a selected Sheet tab’s last row with data, starting in column A. You can also review replacing an exact range of existing Sheet cells or uploading an original chat attachment as a new Drive file. In Desk, your request authorizes the specified change. Ask for a draft when you want to review before saving. Native appends do not replace existing text or cells. Reviewed replacements change only the displayed range, can clear cells, and may remove rich-text links or smart chips from those cells. Spreadsheet cells support explicitly selected text, numbers and booleans. A blank value clears a cell in an exact-range replacement. Text beginning with = stays literal text and does not run a formula.
- Read Calendar: Read events on your primary calendar in a requested date range of up to 366 days, or the next 30 days by default.
- Write Calendar: Create or update primary-calendar events you request. Events with attendees can send them invitations.
- Manage Tasks: Read task lists and tasks, then create, edit or complete a task you request. Task due dates are dates, not timed reminders.
The connection also requests identity access to verify your Google account and email address. Adding a capability requests it alongside permissions you previously approved. Write permissions can include read access. Google access is published for external accounts. Sensitive and restricted permissions are not yet verified by Google, so Google may show an unverified-app warning or limit new authorizations. Branding verification does not approve access to Google data.
Connection data and action receipts
Brandpatch stores your verified Google identity, connection metadata and encrypted access and refresh credentials on its server. Credential encryption does not encrypt every identity or metadata field.
Opening Connections or the Google panel checks status. Manual browsing loads content only when you choose a read action and does not save those previews as chat messages. When you submit a chat request with a connected Google account, the assistant can fetch relevant content to complete that request. Read the separate AI-sharing notice below.
Prepared email, Calendar, Drive and Tasks actions are stored as encrypted drafts so you can reopen and review them. Pending reviews expire after one day. Confirming a reviewed action submits it to Google. Delivery or change receipts retain the sending account, request identifier, a hash of the submitted details, status, timestamps and resource identifier when available. Receipt records do not contain message bodies or recipients; the encrypted prepared draft and saved conversation may contain them.
Google-enabled turns can include attachments saved in the chat workspace. The assistant receives file metadata and bounded extracted text from supported documents. When requested or needed for your task, image inspection sends the selected AI provider an orientation-corrected JPEG preview of the first frame. Brandpatch removes preview metadata and may resize it. The provider may retain the preview in its conversation history. Upload reviews retain the original file reference, type, size and fingerprint and optionally the destination folder; confirming uploads the original bytes to Google Drive.
Your browser keeps temporary recovery information. Checking an existing action receipt does not repeat its write. An uncertain result must be checked in Google before creating a new action.
Content you submit to AI or share
Manual Google previews do not automatically send content to AI. Connecting Google makes its approved services available automatically to the selected assistant for your chat requests. There is no separate per-chat activation switch. The Google panel identifies the selected engine and explains saved content and sharing.
The browser verifies the current account, sign-in and Google connection before each eligible chat request, including after reloads, engine changes and follow-ups. It does not store a separate activation choice for each chat or tab. Access remains limited to the requesting user’s current connection and approved capabilities. Disconnect Google in Connections to stop future access. Coding and Together use their separate runtimes without connected Google tools. Supported connected workflows can pass only the necessary task data and owned artifacts between bounded services; each action remains tied to your account and saved receipt.
Google results used by the assistant are sent to the selected provider and can appear in saved replies, job events and provider conversation history. Sources and prepared actions are saved with your work. Text you manually copy and submit is also saved and sent to your chosen engine. Future conversation requests can include saved history; changing the provider or sharing the chat can expose that history to the provider or authorized collaborators.
The connected providers are OpenAI for Codex, Anthropic for Claude and xAI for Grok. Processing, retention and training settings depend on the selected service and host account configuration. Consider that service’s handling before submitting private material. This notice does not certify Google verification or provider-policy compliance.
Sharing a thread or project gives selected collaborators access according to its permissions. Authorized host operators have technical access to the server and database for administration and investigation. Google credentials are held by the platform and are not included in assistant tool results.
Cookies and browser requests
Brandpatch uses a sign-in cookie to maintain your session. Your browser also stores interface preferences and temporary recovery information.
Session storage keeps temporary work drafts, selected threads and recovery references for submissions and connected actions. It does not keep a separate Google activation choice for each chat. The service checks the current account and approved Google capabilities for each eligible request. Recovery checks read existing status or receipts; they do not repeat uncertain writes.
Copying text places it on your device’s clipboard.
Pages that load fonts from Google Fonts make requests to Google, which receives network information such as your IP address. Reading these policy pages does not load your Google connection or workspace content.
Disconnecting, retention and backups
Disconnect removes live local Google credentials and identity and invalidates pending approval requests. Brandpatch also attempts to revoke Google access. If revocation cannot be confirmed, remove Brandpatch access in your Google account’s third-party permissions.
Account deactivation removes local Google credentials, identity, pending approval requests and sign-in sessions. It does not revoke Google permissions remotely. Original Google mail, files and events remain in Google.
Stored connections have no configured maximum retention period. Unused approval links stop working after ten minutes. Expired approval records are removed in periodic batches while the service runs and during later connection attempts. Outages or a backlog can delay cleanup. Saved work and send receipts do not currently have a fixed automatic deletion schedule. Archiving a thread preserves its content.
Database backups may contain earlier credentials, identity and saved work. Local daily database backups retain the newest seven copies. Off-host application backups include the database and workspace files and are configured to expire after 7 days for daily copies, 28 days for weekly copies and 90 days for monthly copies. Older object versions are configured to expire after one day. Lifecycle cleanup does not guarantee deletion at an exact time. Manual and release snapshots have no unified expiry schedule. These backup periods do not set a deletion schedule for live saved work. Disconnecting or deactivating an account does not erase those backups, sent email, recipient copies, clipboard contents or content already submitted to Desk or a provider.
Privacy and account requests
You can download a private copy from Account data in your account menu. It includes your own saved conversations, notes, whiteboards, App inputs and results, schedules and connected-action records in JSON files, with a contents manifest. It includes archived conversations you own and excludes inaccessible projects and other people’s shared work. The ZIP is unencrypted and limited to 32 MiB and 20,000 records. Original file bytes, credentials, unsent browser drafts and unsaved connected-service content are excluded; download individual attachments and generated files using their existing controls.
Email info@mybrandpatch.com for questions or requests concerning your account, access, corrections or removal. Include enough information to identify your account, but do not send passwords, connection secrets or unrelated private content. Removal depends on the data involved, including saved work, backups and copies held by recipients or providers.