Legal
Sub-processors
The providers that handle personal data for Plotwork, what each does, and where it handles it. It is the list a security review or a data processing agreement asks for, taken from the privacy policy, which says what each one sees. Plotwork is run by Buun Group Pty Ltd (ABN 75 687 193 675), Australia.
Last updated: 2026-10-25
TL;DR
| Question | Answer |
|---|---|
| Who are they? | Cloudflare, Resend, Stripe, Google, PostHog, Sentry and GitHub. The service sends data to no other provider. |
| Where is the data held? | On Cloudflare's global network. Cloudflare chooses where the database runs, and the choice is not limited to Australia. |
| Is diagram source sent to any of them? | A diagram sent to be drawn is worked on in memory on Cloudflare and not stored, unless you publish it or put it on a whiteboard. No other provider receives it. |
| Who chose the tools my organisation sends its audit events to? | Your organisation did. Those tools, and the email service an organisation connects, are its own providers, not ours. |
| Can I keep everything inside my network? | Yes, with the self-hosted engine, which makes no outbound request. It has no accounts, hosting or organisations. |
| How do I hear about a change? | This page and the privacy policy change together, and the date at the top of each moves. |
| Where do I ask? | legal@buungroup.com (opens in a new tab). |
The list
| Provider | What it does for us | Where |
|---|---|---|
| Cloudflare (opens in a new tab) | Hosts the sites, the API, the MCP server, the account database, the caches and rate limits, hosted and organisation diagrams, organisations' live whiteboards and call history. Checks with Turnstile that an Enterprise enquiry and a sign-in come from a person. | A global network. Cloudflare chooses where the database runs, and the choice is not limited to Australia. |
| Resend (opens in a new tab) | Delivers the sign-in, invitation, support request and board access request emails. | United States |
| Stripe (opens in a new tab) | Takes payments for the Pro plan, and hosts the pages where you pay and manage billing. | Where Stripe chooses, as its privacy policy describes. |
| Google (opens in a new tab) | Runs Google Analytics on plotwork.dev and the docs, only for visitors who accept. Never on the portal. | United States |
| PostHog (opens in a new tab) | Runs product analytics and session recordings on plotwork.dev and the docs, only for visitors who accept. Never on the portal. | United States |
| Sentry (opens in a new tab) | Collects error reports and timings from the hosted service and its pages, with no diagram source, request body, cookie, key or account in them. | United States |
| GitHub | Hosts the public repositories, where people can open issues. For an organisation that links the Plotwork GitHub App, it is the organisation's own repository host. | Public repositories are public, under GitHub's terms. An organisation's repositories are under its own agreement with GitHub. |
These providers handle data outside Australia, and for a visitor in the European Union or the United Kingdom, outside their own region. Each describes its own safeguards for such transfers in the privacy policy linked beside its name.
What stays with you
| You run | What it means |
|---|---|
| The local MCP server from npm | It draws on your device and, by default, sends nothing to Plotwork. Usage sharing is off unless you turn it on. |
| The self-hosted engine | It draws inside your network, sends no telemetry and makes no outbound request. |
| Your own SIEM or webhook, for an Enterprise organisation's audit events and drift | Plotwork sends copies there because your organisation asked, and your organisation chose it. |
| Your own Google Drive or bucket, for a Pro or Enterprise organisation's library | Plotwork sends the library's diagrams there because your organisation asked, and your organisation chose it. |
| Your own email service, for an Enterprise organisation's invitations and reminders | Its token is sealed, and the service is your organisation's provider. |
See also
| Page | Why |
|---|---|
| Privacy policy | What each provider sees, and your rights |
| Data retention policy | How long each kind of data is kept |
| Self-hosting the engine | Drawing inside your own network |
| Send audit events and drift to your tools | The destinations an organisation chooses |
| Send your library to your own storage | The storage an organisation chooses |
| Vulnerability disclosure | How to report a security problem |