Legal
Subprocessors
The providers that handle personal data for Flung, what each does, what it sees, and where. It is the list a security review or a data processing agreement asks for. Flung is run by Buun Group Pty Ltd (ABN 75 687 193 675), Australia.
Last updated: 2026-10-31
TL;DR
| Question | Answer |
|---|---|
| Who are they? | Cloudflare, Stripe, Resend, Sentry, Neynar and PostHog, and on these docs and flung.dev only, Google Analytics. |
| Where is the data held? | On Cloudflare's global network. The database, files and app grants live there, and Cloudflare chooses where they run. |
| Do AI model providers see my data? | No. Flung sends no customer data to an AI model provider today. If a feature that does is added, the provider is listed here first. |
| Are the social platforms subprocessors? | No. X, Instagram, LinkedIn and the rest are destinations you choose. Flung sends them what you ask it to post, under their own terms. |
| What about Plotwork? | Plotwork is another Buun Group product. It is involved only if a workspace connects it, and then Flung reads the diagrams the workspace picks. |
| How will I hear about a change? | We add a new subprocessor to this page 30 days before it starts, with an entry in the changelog below, and email you if you asked us to. |
| Where do I ask? | legal@buungroup.com (opens in a new tab). |
The list
| Provider | What it does for Flung | Data involved | Where |
|---|---|---|---|
| Cloudflare | Runs all of Flung: the sites, the API, the database, the files and the background work. What Cloudflare runs lists each service. | Everything the privacy policy lists, with platform tokens encrypted. Turnstile reads browser signals and the IP address. | Cloudflare's global network. No fixed location. |
| Stripe | Takes payments for paid plans and hosts the pages to pay, change a plan and see invoices. | The buyer's email address, the workspace id, and what the buyer enters on Stripe's pages, such as the card and billing address. Flung keeps only Stripe's ids, the plan and its status. | Where Stripe chooses, as its privacy policy describes. |
| Resend | Sends every email: sign-in codes, the welcome, notices that an account needs reconnecting or a post failed, and the confirmation that an account or a workspace was deleted. Tells Flung whether each was delivered. | The recipient's email address and the email itself. | United States |
| Sentry | Receives error reports from Flung's services and pages, only where error reporting is set up for that service. | What failed, where in the code, the browser or service, and the time. Email addresses, tokens, keys, codes, cookies, request bodies and queries are removed before a report leaves, and no user is attached. | United States |
| Neynar | Carries Farcaster sign-in, casts and replies, for workspaces that connect a Farcaster account. | The Farcaster account's id, username and picture, and what is posted to it. | United States |
| Google Analytics | Counts visits to these docs and flung.dev (Google Analytics), only for visitors who accept analytics. Never on the portal or the staff console. | The page's address without its query, the page before it, the browser and device, and an approximate location from the IP address, which Google does not store. | United States |
| PostHog | Counts which links and buttons are used on these docs and flung.dev, only for visitors who accept analytics. Also receives the app's usage events, such as a channel connected or a post scheduled, sent from Flung's servers for people who have not turned them off. No script and no cookie in the portal or the staff console. | On the sites: the page's address without its query, the links and buttons clicked, the browser and device, and an approximate location, never what is typed, and no screen recording. From the app: which events happened, under random ids for the person and the workspace, with the workspace's plan; no content, no handle, no email and no IP address. | United States |
The service sends personal data to no other provider. These providers handle data outside Australia, and for a person in the European Union or the United Kingdom, outside their own region. The data processing addendum says how those transfers are covered.
Each provider's terms
| Provider | Privacy policy | Data processing terms |
|---|---|---|
| Cloudflare | Cloudflare privacy policy (opens in a new tab) | Customer DPA (opens in a new tab) |
| Stripe | Stripe privacy policy (opens in a new tab) | DPA (opens in a new tab) |
| Resend | Resend privacy policy (opens in a new tab) | DPA (opens in a new tab) |
| Sentry | Sentry privacy policy (opens in a new tab) | DPA (opens in a new tab) |
| Neynar | Neynar privacy policy (opens in a new tab) | On request from Neynar |
| Google Analytics | Google privacy policy (opens in a new tab) | Data processing terms (opens in a new tab) |
| PostHog | PostHog privacy policy (opens in a new tab) | DPA (opens in a new tab) |
What Cloudflare runs
| Service | What it does for Flung |
|---|---|
| Workers | Runs the API, the portal, the staff console, the MCP server, the status page and these docs |
| D1 | The database: accounts, workspaces, connected accounts, posts, webhooks, keys and billing ids |
| R2 | Stores uploaded images and videos, their thumbnails, invoice and receipt PDFs, and the screenshots attached to bug reports |
| KV | Holds the grants of the apps and agents people approve |
| Durable Objects, Workflows and Queues | Run each connected account's work, publish scheduled posts, renew tokens, and deliver webhook events |
| Media Transformations | Makes a thumbnail of each uploaded video |
| Browser Rendering | Prints invoices and receipts to PDF. It keeps nothing. |
| Rate limiting and request logs | Limits requests per key and per app, and keeps a log of each request to find faults and abuse |
| Turnstile | Checks that a person is signing in, approving an app, or deleting an account or a workspace |
AI model providers
Flung's staff console can hold keys for AI model providers, such as OpenAI, Anthropic, Google Gemini, Mistral and others, and test that a key works. No feature sends customer data to any of them today: no post, account, file or comment goes to a model, and nothing is used to train one.
When a feature that sends customer data to a model is added, the provider it uses is added to the list above first, with the same notice as any other new subprocessor, and the privacy policy says what the feature sends.
What is not a subprocessor
| Who | Why it is not on the list |
|---|---|
| X, Instagram, Facebook, Threads, LinkedIn, TikTok, YouTube, Pinterest, Mastodon, Bluesky, Discord and Farcaster | The social platforms are where you tell Flung to post. A person connects each account on the platform's own page and approves the access, and Flung sends the platform only what the workspace asks it to post or read. The platform then handles that data as its own, under its own terms and privacy policy. |
| Plotwork | A Buun Group product. It is involved only when a workspace connects it on the portal's Integrations page. Flung then reads, with that person's permission, the diagrams the workspace picks to attach to a post, and the account's name and address to show who connected it. Plotwork's tokens are stored encrypted, and disconnecting deletes them. Plotwork is under its own privacy policy (opens in a new tab). |
| Google and GitHub | Used only for sign-in. A person who chooses Continue with Google or Continue with GitHub signs in on that provider's own page, under their own account there. Flung receives the account's id, its verified address and name, and keeps no token. |
| Your own servers | Webhook events go to the addresses a workspace sets. What happens there is the workspace's own business. |
Changes to this list
| Change | What we do |
|---|---|
| A new subprocessor | We add it to this page and the changelog below at least 30 days before it receives personal data, and email everyone who asked to be told. |
| A provider we stop using | We take it off the list and add a changelog entry once it holds no Flung data. |
| An objection | If you object to a new subprocessor on reasonable data protection grounds, write to legal@buungroup.com (opens in a new tab) before it starts. We will try to find a way that works for you. If we cannot, you may end the affected service and we refund any month paid for and not used. |
| Being told | Write to legal@buungroup.com (opens in a new tab) with "Subprocessors" in the subject, from the address you want the notices sent to. |
Changelog
| Date | Change |
|---|---|
| 2026-10-31 | First published: Cloudflare, Stripe, Resend, Sentry, Neynar, Google and PostHog. |
| 2026-10-31 | PostHog also receives the app's usage events, from Flung's servers under random ids, with an opt-out on the Account page. |
See also
| Page | Why |
|---|---|
| Privacy policy | The personal data Flung collects, why, and your rights |
| Data processing addendum | The terms Flung processes a workspace's personal data under |
| Security | How the data these providers hold is protected |
| Cookie policy | The cookies and browser storage on each Flung site |
| Terms of service | The agreement to use Flung |
| Acceptable use policy | What Flung may not be used for |
| Data deletion | Every way to delete your data |