Privacy notice
Last updated October 28, 2026
Workflow brings your communications and next steps into a private workspace. This notice explains how the service at workflow.bburr.com, operated by Brandon Burr, handles your information.
Information we access and store
When you connect a Gmail, Slack, or IMAP account, Workflow stores the account identity, connection settings, and the credentials or access tokens needed to keep it connected. With your permission, it retrieves and stores messages and related details, such as senders, recipients, subjects, timestamps, conversation identifiers, and read status.
Workflow also stores the projects, tasks, drafts, preferences, and review decisions you create. Basic session cookies keep you signed in; technical logs help operate and secure the service.
How your information is used
Your information is used to display your communications timeline, suggest messages that may need a reply or task, identify subscription messages, and save the follow-up work you choose. Suggestions use message wording and metadata and may need your correction.
The communication connections are read-only. Workflow does not automatically send replies, change your source messages, or unsubscribe you. Reply drafts and review decisions stay in Workflow.
Access, hosting, and sharing
Your workspace requires a login. Data is processed on the server hosting Workflow and exchanged with the providers you connect to retrieve messages and maintain authorized access. Authorized operators and infrastructure providers may access information as necessary to operate, support, or secure the service, or as required by law.
Workflow does not sell your personal information, use it for advertising, or use Google user data to train generalized artificial intelligence or machine learning models. If you choose to share information through another tool, that tool's policies also apply.
Protection and retention
Connections to Workflow use HTTPS. Stored provider credentials, message bodies, previews, and reply drafts are encrypted at rest. Account identifiers and message headers, including subjects, senders, recipients, and timestamps, are stored without this field-level encryption to support your workspace. No security measure can eliminate every risk.
Saved communications and workspace records remain available until removed by the operator. Disconnecting an account stops future syncing and removes its stored connection credentials; it does not automatically delete previously imported messages, projects, or tasks. To request access, correction, or deletion of stored information, contact Brandon Burr at brandon@bburr.com.
Your connection choices
You can disconnect an account in Communications → Manage channels. You can also revoke Google's access in your Google Account connections, or revoke Slack access through Slack's app settings. Revoking access prevents future retrieval through that connection.
Google API data
Workflow's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.