Updated 19 September 2026

Privacy

Workhouse keeps your work in your own installation. Using an online AI service still sends selected content to that service.

Who provides Workhouse

Workhouse is created and maintained by Gary Atkin. It is an independent project; BRM is its first audience. For privacy questions, email gary@bikerentalmanager.com.

This website

This website explains Workhouse. It has no account registration, advertising, analytics scripts or tracking cookies added by Workhouse. Cloudflare hosts these pages and processes connection information, such as IP addresses and requests, to deliver and protect the website. See Cloudflare’s privacy policy.

What the installed app accesses

You choose which accounts to connect and grant their permissions. Google sign-in identifies your account. Gmail reading access supports finding relevant requests and retaining their source information. Calendar reading access supports displaying events and planning work. Optional Google Meet access reads available meeting information and saved transcripts to prepare follow-ups. Slack access supports reading messages you mark for attention and their source context.

The current Google connection requests Gmail and Calendar reading access together. Meet access is requested separately. Connecting does not start message monitoring or import the old inbox. You choose when to start checks. Separate permissions may be requested for features that prepare changes to connected services.

Where your work is stored

The local app stores tasks, selected source content, meeting reviews, drafts, settings and connection information on your computer. Google sign-in tokens and saved connection settings are encrypted using a key held by that installation. The local task database is not fully encrypted by Workhouse; protect your Mac account and backups.

This public website does not receive your Workhouse database or connected messages. Connecting a shared Google application does not share your mailbox with other Workhouse users.

AI processing

When you ask your selected agent to prepare work, Workhouse supplies the relevant task and source context. Meeting analysis supplies the available transcript. If you enable automatic drafts, qualifying newly captured tasks can be supplied automatically within the app’s limits.

Codex, Claude Code or another configured online model provider may process this content on its servers under your account and that provider’s terms and privacy settings. A locally installed agent does not mean the model runs offline. Workhouse does not use connected account data to sell advertising or train its own general-purpose AI models.

Google data use

Workhouse uses Google account data to provide the features you choose: organising relevant work, calendar planning and meeting follow-ups. Its use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Your controls and retention

You can pause account checks and automatic preparation in Settings. Disconnecting removes the app’s saved access to that account; disconnecting Google applies to Gmail, Calendar and Meet together. You can also revoke access through your Google or Slack account settings.

Disconnecting does not automatically erase tasks, sources or drafts already saved. They remain in your local installation until removed. Deleted tasks may remain recoverable in the Bin, and backups can retain earlier copies. Contact Gary if you need help removing an installation and its retained data. Your AI provider may retain content already sent under its own policy.

Changes

This page describes the current local version. Any future online connection service or change in data handling will need an updated explanation before it is offered.