Privacy Policy

Who we are

Cowboy Hub is run by [Company legal name], [Registered address] (“we”, “us”). For the data in this policy about the people who use the Hub, we are the controller.

For the personal data on your WordPress sites that passes through the Hub while it works for you, your workspace is the controller and we are its processor. See Data on your sites below.

What we collect

• Your account: your email address and the sign-in records Supabase Auth keeps. If you sign in with Google, the basic profile Google shares (your name and email address).
• Your workspace: its name, its members and their roles, and the email addresses of people invited to it.
• Connected sites: each site’s address, its plugin and WordPress versions, its Cowboy MCP settings, its policy and tags, and when it last checked in.
• Site access: the scoped OAuth token each site issues to the Hub, and the SSH or SFTP credential for a site if you add one. Both are sealed with envelope encryption.
• Your OpenRouter key, if you add one, sealed the same way. It is shown back only as a prefix.
• AI client sign-ins: records of the AI apps members connect to the Hub, and API keys for terminals. The Hub stores only a hash of each token and key.
• The activity timeline: who did what on which site, the tool or command, its arguments with secrets redacted, and the result.
• Agent conversations: the messages members send to the agent by email, Telegram or Slack, and its replies. Site content appears in them only where the agent quoted it.
• Skill runs and job results: what a skill run or a background job did, and its result.
• Restore copies: a copy of every file the Hub changes or deletes over server access, made before the change.
• Chat identity links: which Telegram user, Slack user or email address belongs to which member.
• The waitlist: the first name and email address you gave on the marketing site’s early-access list.
• Billing state: your Stripe customer and subscription ids, the plan, its status and period end, and which version of the terms the workspace accepted. We never receive or store card numbers: Stripe keeps your card, invoices, billing address and tax id.
• Technical logs: request logs and error logs from our hosting, which can include IP addresses.

Why we use it, and the legal basis

• To provide the Hub to your workspace: sign-in, connecting sites, running calls, approvals, the activity timeline, the agent, billing, and emails about your workspace such as approval requests. Legal basis: the contract with you (our Terms of Service).
• To keep the Hub secure and working: preventing abuse, investigating incidents and fixing errors. Legal basis: our legitimate interest in a secure, working service.
• To run the waitlist and email launch offers. Legal basis: your consent, given when you joined the waitlist. You can withdraw it at any time by email.
• To keep billing and tax records. Legal basis: the contract, and our legal obligations under tax law.

Data on your sites

When the Hub works on your sites, it reads and changes what is on them, which can include personal data: users, customers, comments, form entries and the content itself. Some of it can end up in the activity timeline, in agent conversations and in restore copies.

For that data your workspace is the controller and we act only on its instructions. The Data Processing Terms cover it.

Where it is kept

The Hub’s data is stored in the US, in Northern California: the database with Supabase, and the services and restore copies with DigitalOcean. If you are in the EU or the EEA, your data is transferred to the US; the transfer is covered by the EU Standard Contractual Clauses or another transfer mechanism the law allows.

How long we keep it

• Activity timeline, agent conversations and job results: 90 days.
• Restore copies: 30 days.
• Workspace data (sites, members, settings, sealed tokens and credentials): while the workspace exists. A token or credential is deleted when you remove it. After the workspace ends, we delete its data within [30] days.
• The waitlist: until you ask us to remove you.
• Billing records: as long as tax law requires. Stripe keeps invoices and payment records under its own policy.
• Technical logs: [log retention period: confirm].

Sub-processors

We use these companies to run the Hub. This is the same list as in the Data Processing Terms.

Cookies

The Hub sets only the cookies it needs to work:

• Sign-in cookies that keep you signed in.
• A workspace cookie that remembers which workspace you chose.

There are no tracking, analytics or advertising cookies. Stripe’s checkout and customer portal pages, and Google’s sign-in page, set their own cookies under their own policies.

Your rights

You can ask us for a copy of your personal data, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a portable format. Where we rely on consent, you can withdraw it at any time. Email us at hub@cowboymcp.com. We answer within one month.

If your request is about data on a site managed by a Hub workspace, we pass it to that workspace, which decides on it as the controller.

You can also complain to the data protection supervisory authority where you live or work.

Security

How we protect your data, including the encryption of tokens and credentials, is described on the Security page.

Changes to this policy

If we change this policy, the date at the top of this page changes, and we tell workspace owners by email before a change that matters.

Contact

Questions about privacy: hub@cowboymcp.com, or by post to [Company legal name], [Registered address].