Tenant access controls
BidFlow uses organisation-scoped server-side authorisation checks and row-level security policies on relevant tenant-data tables. These controls are designed to prevent an authenticated user from accessing another organisation’s Customer Data.
No security architecture makes unauthorised access impossible. BidFlow combines these controls with authenticated sessions, role-based permissions, service-role restrictions, logging and ongoing remediation. Customer administrators remain responsible for user access, roles, credentials and devices.
Hosting and processing locations
BidFlow uses Supabase for its primary database, authentication and object storage, and Vercel for application hosting, serverless processing and delivery. AI, email and customer-requested website-import features use the providers described in the Privacy Policy and DPA.
We do not describe all BidFlow processing as UK-only. Provider support, AI inference and other subprocessors may involve international processing. Restricted transfers are handled under the safeguards described in the DPA. Customers with a residency requirement should ask us to confirm the deployed project region and applicable feature routes before relying on a particular location.
AI data controls
BidFlow routes AI requests through Vercel AI Gateway. Current approved inference providers include OpenAI and Anthropic, and the provider or model can differ by feature and configuration.
Gateway requests are configured to disallow routes that use prompts for provider model training. OpenAI requests also disable provider response storage where supported. BidFlow does not use Customer Data to train or fine-tune general or shared AI models without the Customer’s express written agreement.
BidFlow does not claim universal Zero Data Retention. Unless a verified ZDR route is enabled and eligible, providers may retain limited inputs and outputs under their applicable commercial/API abuse-monitoring and legal-retention rules. When BidFlow enables its optional ZDR control, the Gateway is instructed not to fall back to a route that does not satisfy it.
Encryption and service security
Supported connections between browsers and BidFlow, and between BidFlow and its configured service providers, use HTTPS/TLS in transit. BidFlow also relies on the encryption and infrastructure controls supplied by its selected hosting, database and storage providers.
Security controls reduce risk; they do not guarantee that an incident cannot occur. BidFlow assesses suspected incidents and will notify affected Customers of a personal data breach without undue delay where required by the DPA and applicable law.
Payments
Payment-card details entered at checkout are collected and processed by Stripe. BidFlow does not store full card numbers or CVC data. BidFlow does receive and store information needed to administer subscriptions, such as Stripe customer and subscription identifiers, billing status, invoice information and limited payment-method metadata.
Stripe is not sent tender documents or Generated Content for payment processing.
Human review and procurement decisions
BidFlow is designed as a human-in-the-loop drafting and decision-support platform. AI output may be incomplete or inaccurate. The Terms require Customers to review and approve Generated Content, factual claims, pricing and commitments before relying on or submitting them.
BidFlow does not make procurement decisions and does not guarantee an award, qualification, score, ranking or win rate. Internal scores and evaluator simulations are decision-support indicators, not forecasts of an evaluator’s actual decision.