Privacy policy

Who I am

Ployz is run by me, Nick Potts, an individual based in Australia. I'm responsible for the personal information this page describes. For any privacy question or request, email support@ployz.dev.

What this covers

This page covers the ployz.dev website, Ployz Cloud (the dashboard at ployz.dev), the ployz CLI when you sign in with it, and the remote MCP server at ployz.dev/mcp.

It doesn't cover a self-hosted Ployz Cloud. Whoever runs that one is responsible for it, and it sends no analytics to me.

Your apps and their data

Your apps, their databases, volumes and secrets run on servers you rent. Their logs and metrics are kept on those servers, and the dashboard reads them from your servers when you open them. Ployz Cloud doesn't keep a copy.

Ployz Cloud does store what it needs to run your organizations: your projects, services, settings, variables (sealed values are encrypted), domains, servers and deployments.

Your apps' data leaves your servers in two cases, both started by you:

• The Ployz agent. When you ask the agent in the dashboard, or your own coding agent through the MCP server, it can read your logs, metrics and settings to answer. What it reads goes to Anthropic with your prompt (see below).
• Support access. It's off until an owner or admin turns it on under Organization → General. While it's on, I can open your organization to help you. Variable values, config file contents and container logs stay hidden unless you turn on their own switches.

What I collect

• Your account. You sign in with GitHub, which gives me your name, email address, avatar and GitHub account ID. For each place you're signed in, a browser or the CLI, I keep its IP address, its browser or client name and when it was last active. You can see these under Account → Sessions.
• GitHub repositories. When you install the Ployz GitHub App, Ployz Cloud can read the repositories you grant it, to build, deploy and run preview environments for pull requests. You choose the repositories in GitHub and can remove the app there.
• Agent chats. Your conversations with the Ployz agent are stored in Ployz Cloud so you can come back to them.
• Billing. Payments go through Polar. Polar collects your payment details; I never see your card number.
• Usage and analytics. On the website and in the dashboard, PostHog records the pages you view, what you click, errors, and session replays: a recording of the page as you use it. Replays include what you type into forms, except passwords and fields that hold secrets. Once you're signed in, this is linked to your account ID, name, email and organization. The CLI tells me which coding agent ran ployz login, if it can tell. I also record which agent tools ran, how long they took and whether they failed, without what they were given or returned. Invite pages record nothing.
• Email. Ployz Cloud emails you about uptime incidents, failed deploys, failed server upgrades and crashed services. Turn any of them off under Account → Notifications or from the email.

I don't sell your information, and I don't use it for advertising.

Cookies

Ployz Cloud uses a cookie to keep you signed in. PostHog stores an anonymous ID in a cookie on ployz.dev. The website and the dashboard share that address, so if you sign up after visiting the website, your earlier visits are linked to your new account.

Who it goes to

These services handle personal information for Ployz:

• Railway hosts Ployz Cloud and its database, in the EU.
• GitHub handles sign-in and the repository access you grant. Based in the US.
• PostHog stores the analytics and session replays described above, in the US.
• Anthropic runs the model behind the Ployz agent and the MCP server's agent tools. Your prompts and what the agent reads to answer them go to Anthropic's API, in the US.
• Polar handles payments.
• Postshiba sends Ployz Cloud's emails.

So your information is stored and processed outside Australia, mainly in the EU and the US. I share it with anyone else only when the law requires it.

Connecting an agent

When you connect a coding agent to the MCP server, you sign in and pick the one organization it works in. Log out of Ployz Cloud in the browser you connected from, and every agent you connected there loses access. Leaving the organization does the same for that organization.

How long I keep it

I keep your account, your organizations and your agent chats until you ask me to delete your account. Email support@ployz.dev from the address on your account and I'll delete it.

Your rights

You can ask what personal information I hold about you, ask me to correct it, or ask me to delete it. Email support@ployz.dev. I may need to confirm it's you before I act.

Australia's Privacy Act 1988 applies to how I handle your information. If you're not happy with my answer to a complaint, you can take it to the Office of the Australian Information Commissioner.

Changes

When this page changes, the date at the top changes with it.