Data Processing Summary

1. Purpose of this page

This page summarizes how FlowSaver handles merchant and customer data in the ordinary course of product operation. It is informational only and does not replace a signed data processing agreement, enterprise order form, or separate legal advice.

2. Roles

Merchants remain responsible for the customer data they collect through their own application and the Stripe accounts they control. FlowSaver acts as a software provider processing a limited set of records needed to configure workflows, track billing state, and operate recovery logic. Stripe remains the primary payment service provider for payment method handling, settlement, and its own account records.

3. Categories of data

• Merchant workspace data such as user email, workspace settings, domain allowlists, and Stripe account IDs.
• Customer-related orchestration data such as email address, Stripe customer IDs, payment object IDs, and workflow state.
• Operational records such as audit events, automation timestamps, support history, and troubleshooting logs.

4. Processing purposes

• Connect a merchant workspace to Stripe and keep configuration in sync.
• Operate configured billing, trial, retry, and recovery workflows.
• Maintain local visibility into workflow status, audit history, and support investigations.
• Respond to deletion, security, contractual, and compliance-related requests.

5. What remains on Stripe

FlowSaver is not the primary payment system of record. Raw card data, payment method collection, tokenization, settlement, dispute rails, and broader payment account controls remain on Stripe. Merchants should not treat FlowSaver as a substitute for reviewing the records and controls available in Stripe.

6. Service providers and subprocessors

FlowSaver uses third-party infrastructure and operational service providers to host the application, run background jobs, deliver communications, and support internal operations. Those providers receive only the data reasonably needed for the service they perform. If you need a current subprocessor list or contract terms for procurement review, contact us before production use.

7. Retention and deletion

FlowSaver retains local records for as long as they are needed to run the workspace, maintain a reasonable audit trail, resolve disputes, or satisfy legal obligations. Workspace deletion removes or schedules removal of FlowSaver-local records, but does not remove data already stored in Stripe or in merchant systems outside FlowSaver.

8. Merchant controls

Merchants can update workspace configuration, change authorized domains where applicable, disconnect Stripe access, and request deletion of FlowSaver-local data. Merchants remain responsible for customer notices, lawful collection, and handling data rights requests that relate to systems they control.

9. Contracts and requests

For DPA requests, retention questions, deletion coordination, or procurement review, contact hi@flowsaver.app. Additional contractual terms may be required before using FlowSaver in enterprise, regulated, or high-risk environments.