Last updated: April 14, 2026
This Privacy Policy describes how FlowSaver processes personal data in connection with the FlowSaver application, website, merchant workspaces, and support requests. It is intended to explain the product's current data handling posture and does not replace a separate contract, data processing agreement, or Stripe's own privacy materials.
Merchants remain responsible for the customer data they collect through their own product, checkout flows, and Stripe account. FlowSaver processes a limited set of merchant and customer data to operate billing orchestration, recovery, workspace administration, and support. Where Stripe holds the primary payment record, the merchant and Stripe remain responsible for that record under their own terms.
Workspace owner and team email addresses, authentication-related account data, connected Stripe account identifiers, configured flows, authorized domains, and product settings.
Customer email, Stripe customer and payment object identifiers, billing state, recovery state, timestamps, and limited metadata used to track workflow execution.
Local audit events, logs related to workflow execution, and information you send in support, security, or contractual communications.
FlowSaver does not collect or store raw card numbers. Payment method collection and storage remain on Stripe infrastructure.
FlowSaver shares data with service providers only where needed to run the product, host the application, send product-triggered communications, monitor operations, or respond to support and security matters. Stripe remains a separate provider responsible for its own services and records. We may also disclose data where required by law, to enforce our terms, or to respond to a credible security or abuse issue.
We retain FlowSaver-local data for as long as needed to operate the workspace, maintain a reasonable audit trail, resolve disputes, or meet legal obligations. When a workspace is deleted, FlowSaver-local records may be removed or scheduled for removal through product controls or manual processing. Deleting a FlowSaver workspace does not delete records stored in Stripe or in merchant systems outside FlowSaver.
FlowSaver and its service providers may process data in jurisdictions where their infrastructure or personnel operate. If you require region-specific contractual terms or transfer language, contact us before using the service for regulated or high-risk workloads.
Depending on your jurisdiction, you may have rights to request access, correction, deletion, or restriction of personal data. FlowSaver can address requests about FlowSaver-local records. Merchants remain responsible for requests concerning records they control in their own systems or through Stripe.
Privacy requests can be sent to hi@flowsaver.app.
FlowSaver uses Stripe Connect OAuth for Stripe account linking and relies on Stripe for payment method handling. FlowSaver is not represented as a replacement for Stripe's compliance, account controls, or payment security obligations. Additional detail about the product's current architecture boundaries is available on the security page.
We may update this policy as the product and its operating model change. Material updates will be reflected on this page. Questions can be sent to hi@flowsaver.app.