服務提供者

Bisonflow uses a limited set of third-party processors to provide core product capabilities. This list is intended to be concise and practical rather than a marketing directory.

If you need additional diligence information about a listed processor, contact contact@bisonflow.com.

• Purpose: authentication, account management, sessions, and organization membership workflows.
• Typical data scope: name, email address, user profile metadata, organization membership data, and session/authentication identifiers.

• Purpose: subscription billing, invoices, payment operations, customer portal workflows, and related billing support.
• Typical data scope: billing contact details, subscription records, invoice records, payment metadata, and Stripe customer identifiers. Full payment card data is handled by Stripe.

• Purpose: application backend, database, hosted functions, and operational data processing.
• Typical data scope: workspace content, tasks, comments, documents, usage events, assistant run metadata, and related application records.

• Purpose: object storage for files and rich-media assets used by the product.
• Typical data scope: task attachments, documentation images, and generated or exported assets stored through the application.

• Purpose: assistant processing, prompt interpretation, and voice transcription.
• Typical data scope: submitted prompts, preview transcripts, limited workspace context needed for the request, and uploaded voice input or transcript data used by assistant features.

• Purpose: background job and workflow orchestration for assistant and automation flows.
• Typical data scope: workflow payloads, assistant run metadata, and event data needed to execute queued background processing.