Skip to content
FlagWire

Documentation

Browser quickstartRemote evaluation for framework-independent browser applications.React quickstartAdd FlagWire through a provider and type-safe hooks.Node.js quickstartValidate bundles and evaluate flags locally in services.Targeting referenceRules, segments, operators, rollouts, and evaluation reasons.REST APIAuthentication and implemented control-plane and edge routes.Bundle formatThe versioned environment bundle and compatibility contract.
↑↓ moveenter openesc close

Subprocessors

Subprocessors

Section titled “Subprocessors”

FlagWire currently relies on the following providers. The data processed depends on the feature a customer uses.

Provider Purpose Relevant data
Cloudflare Edge compute, network protection, database, object storage, key-value storage, aggregate analytics Account and customer configuration, runtime request metadata, aggregate usage
Dodo Payments Merchant of record, checkout, subscription, invoice, tax, refund, and dispute processing Billing contact, transaction, tax, and provider customer identifiers
Resend Transactional account and organization email Recipient email, message content, delivery metadata
Google Optional Google sign-in Identity and OAuth account data authorized by the user
GitHub Optional GitHub sign-in Identity and OAuth account data authorized by the user
Better Stack Availability monitoring and public service status Endpoint health and operational metadata; customer evaluation context is not intentionally sent

Provider locations and transfer mechanisms are controlled by their respective service terms and infrastructure. Material additions that expand customer-data processing will be reflected here before or when they take effect.

Questions can be sent to support@flagwire.dev.