Coaching Hub Privacy Policy

This page explains what Coaching Hub collects when you use it, where that data lives, how long we keep it, and how to ask us to delete it. Future Workshops Limited (FWL, UK) is the data controller for Coaching Hub. Sister entities Future Workshops Europe SL (FWE) and Future Workshops Saudi Arabia Limited (FWSA) operate under the same privacy practices.

What we collect

Coaching Hub collects the data you give us directly and the data your Claude usage produces while Coaching Hub is wired into your tools. Specifically:

• Account profile. Your name and email, supplied directly or via Google OAuth (we read your basic Google profile and email when you sign in with Google; we do not read your Google contacts, drive, or mailbox).
• Usage metadata. When your organisation has connected Claude to Coaching Hub and enabled usage metadata, we receive events describing the shape of each session: the model used, tools and skills invoked, token counts, MCP server calls, errors, cost figures, and timestamps. Usage metadata is an organisation-wide setting, controlled by a workspace admin in Insights setup.
• Prompt content. The text of your prompts is stored only when you have individually opted in, per surface (Claude Cowork, Claude Code), on the in-app Privacy & data page. If you have not opted in, your prompt text is not stored. Claude's replies are never sent to Coaching Hub.
• Coaching content. Notes, board cards, comments, files, and other content you create in Coaching Hub.
• Billing data. Your subscription state, seat count, invoice history, and payment status are stored. Card details are handled by Stripe and are never stored on Coaching Hub servers.
• Email delivery metadata. Outbound transactional email (booking nudges, weekly reports, password resets) is sent via Mailtrap. Mailtrap retains delivery logs in line with their own retention policy.

Where the data lives

Coaching Hub runs on Heroku. Our primary database is Heroku Postgres. Outbound email goes through Mailtrap. Authentication uses Google OAuth where you choose to sign in with Google. Stripe processes payments and stores card details for the purpose of taking payment.

How we use it

We use the data above to run the coaching service: to render your weekly insights reports, to surface session-level detail to you and (where you've opted in) to your assigned coach, to schedule and deliver coaching sessions, and to take payment. We do not sell Coaching Hub data, and we do not share it with third parties beyond the operational subprocessors listed above (Heroku, Stripe, Mailtrap, Google).

What you can control

Inside the app, the Privacy & data page (reachable from the account menu when you're signed in) lets you choose whether your prompt text is stored, per surface (Claude Cowork, Claude Code), and request a data export or account deletion. Whether usage metadata is collected at all is an organisation-wide setting controlled by a workspace admin in Insights setup. Deletion removes your user record, your sessions, and your coaching content; account-level data shared with teammates may be retained where they continue to use the service.

Retention

Session telemetry is kept for as long as your account is active so weekly and historical reports remain useful. When you delete your account, telemetry tied to your user is deleted within 30 days. Invoices and billing records are retained for the period required by applicable tax law (typically 7 years) and are not removed by an account deletion.

Data requests and contact

To request a data export, deletion outside the in-app flow, or to ask any other privacy question, email privacy@futureworkshops.com. We respond to data requests within 30 days.

Insights are in beta

The Insights features described above are in beta. Their behaviour and the metrics they surface may change. See our Terms of Service for the corresponding responsibility wording.