Last updated 22 October 2026
Captain is a private editorial workspace. This policy explains the information Captain needs to run the service and connect the accounts each journalist chooses.
Diana McDermott, an individual based in the United Kingdom, operates the beta under the trading name Captain. Captain is not currently an incorporated company. Diana McDermott is the data controller for personal information used to administer accounts, secure the service and communicate with users.
You control the editorial information you add to your private workspace. For privacy questions, correction or deletion requests, contact Diana McDermott at diana@captainwrites.com.
Captain processes your sign-in identity, editorial profile, briefs, source material, drafts, edits, approvals and delivery history. If you connect an outside service, Captain stores the account and channel identifiers you select plus the access grant needed to carry out your requests.
LinkedIn and X are connected through your own Buffer account. Captain does not receive your LinkedIn, X or Buffer password. Google uses its own consent screen, and WordPress uses the application password you create for that purpose.
The information is used to provide your private editorial workspace, generate and revise work at your direction, preserve versions, export approved documents and publish only the exact destination package you approve. Captain does not publish merely because an account was connected.
Captain sends information to hosting, database, job-processing and AI providers only as needed to operate the requested feature. When you approve a delivery, the approved text and any approved image are sent to the connected destination, including Buffer, Google or WordPress as applicable. Those services process information under their own terms and privacy policies.
Connected-account tokens and WordPress application passwords are encrypted at rest and are available only to Captain's server-side delivery process. Each connection is tied to the signed-in journalist. Disconnecting an account removes its stored access grant and disables that publishing destination.
Editorial records are retained while the private workspace remains active or as required by its operator. Ask the workspace administrator to correct or delete records that should no longer be retained. Revoking Captain in Buffer or another provider also stops future access through that grant.
This page will be updated when Captain materially changes how it handles personal information. The latest revision date appears at the top. If a company is formed to operate Captain and takes over responsibility for personal information, we will explain that change and update the operator and contact details before it takes effect.