Last updated: September 14, 2026
Information we collect
We collect account details, authentication records, workspace activity, project metadata, uploaded assets, generated outputs, billing records, and support messages when you use SWRFlow.
We also collect technical information such as browser type, device information, page interactions, and diagnostic logs needed to keep the service secure and reliable.
How we use information
We use information to provide the canvas workspace, run generation tasks, save assets, process payments, prevent abuse, improve product quality, and respond to support requests.
Provider API keys, provider raw responses, and temporary provider URLs stay on the server side. Generated media is ingested into configured storage before it is treated as durable workspace content.
Model providers and processors
Generation tasks may be processed by third-party model providers selected by the product runtime. We send only the prompts, parameters, and input assets needed to perform the requested generation.
SWRFlow is an independent product. Third-party model names, when shown in the product, identify supported integrations and do not imply affiliation with or endorsement by those model providers.
Payments may be processed by Dodo Payments or another configured payment provider. With your permission, Google Analytics and Microsoft Clarity help us understand page use. Clarity records interactions with page content masked. You can decline or withdraw optional analytics using Cookie settings.
Plausible provides separate, cookieless traffic statistics, including page views, referral domains and aggregate device and location information. It runs independently of the analytics cookie choice and respects Global Privacy Control and Do Not Track. We remove URL query strings, fragments, project identifiers and invitation tokens before reporting page views. We do not send account identities, prompts, media files, form contents or custom event properties to Plausible.
Sentry processes technical error reports to help us find and fix software failures. Our integration removes request bodies, headers, cookies, user profiles, breadcrumbs, and free-form error messages before sending reports. Stack locations and URLs without query strings or fragments are retained for diagnosis. Sentry session replay and application log collection are disabled.
Trial and payment protection
To prevent repeated promotional claims and payment abuse, we retain keyed hashes of account email, a first-party browser identifier and trusted network address, together with claim decisions, payment disputes and review records. These security records may remain after account deletion to prevent repeated claims. Security identifiers are not sent to analytics services. Automated restrictions can be reviewed by contacting support.
Your content
You remain responsible for the prompts, reference assets, uploaded files, and outputs stored in your workspace. We do not sell your workspace content.
We may retain task and asset metadata for billing, abuse prevention, debugging, audit, and compliance needs.
Contact
For privacy questions, contact support@swrflow.com.