Skip to docs content
Browse documentation
On this page

Privacy

A plain-language summary of what Minion keeps and how it's protected. The full legal policy is the Privacy Policy ; if the two ever disagree, the Privacy Policy wins.

Who is responsible for your data

Minion is operated by 1059105 B.C. Ltd., doing business as Data McFly, in British Columbia, Canada. Questions or requests go to hello@minion.codes .

What Minion stores

Most things in Minion belong to your team, and every member of the team can use them according to their role.

  • Your account: email, name if you give one, a bcrypt hash of your password, and your sign-in sessions (with IP address and browser).
  • Your team: name, members and roles, invitations, API keys, and the AI clients you've connected.
  • Packages: code, files and every saved version, plus any data a package stores for itself. Package SQL storage gets its own database for each package.
  • Secrets: encrypted with AES-256-GCM. No API, agent or package code ever gets a secret's value back. Code uses a secret by name, and Minion fills in the value only on requests to hosts you approved. Known secret values are scrubbed from run results and logs.
  • Memories and notes: whatever you or your assistant saves. Scratchpad notes with an expiry are deleted once they expire.
  • Team inbox: mail sent to your team's address, with attachments, kept until someone on the team deletes it. Remote images and tracking pixels are blocked when you view a message.
  • Connected accounts: OAuth tokens are encrypted with AES-256-GCM and only sent to the API hosts approved for that connection.
  • Run history: status, timing, results and logs for each run, with secrets removed. Webhook request bodies are cleared after 24 hours and webhook delivery records after 30 days.
  • Usage counters: daily counts used to apply plan limits.
  • Billing: handled by Stripe Checkout. Minion stores your Stripe customer and subscription IDs and plan, never card numbers.

Who else sees it

  • Stripe for payments.
  • Cloudflare routes and delivers team inbox mail.
  • OpenAI computes search embeddings when they're enabled. It gets search queries and the text of memories, notes (title and the start of the body), package descriptions and readmes, and secret names. It never gets secret values or OAuth tokens.
  • The AI client you connect (Claude, ChatGPT, Cursor and so on) gets the results of what it asks Minion to do.
  • Services your packages call get the requests your code sends them, with the credentials you approved for them.
  • Anyone, but only for things you deliberately make public, such as a public package app.

Minion doesn't sell your data or use it for advertising, and there are no analytics or tracking cookies. The app uses sign-in cookies; the website sets a theme cookie only if you use the theme switcher.

Your choices

  • Export: team owners can download everything the team owns as JSON from Team settings, or run account.export. Credentials are left out.
  • Delete a team: team owners can delete the team from Team settings. That cancels billing, stops jobs, revokes connections, and deletes the team's content and stored files.
  • Delete your account: from account settings, with your password. You're removed from every team and your sessions, connections and API keys end. Content you created stays with your teams. To have your account record erased too, email hello@minion.codes .
  • Disconnect: remove a connected account or AI client at any time, and revoke access at the provider too.

For anything else (access, correction, deletion) email hello@minion.codes .