Privacy
Execution data is collected to debug and replay backend failures.
This product privacy overview describes FluxRun's current data-handling model. It is written for launch readiness and should receive final legal review before procurement use.
Account data
Email, name, provider identity, organization membership, app metadata, billing status, and support messages.
Execution metadata
Function name, status, timestamps, duration, request IDs, trace IDs, SDK version, route labels, and event counts.
Protected execution data
Request, response, console, fetch, random/time, host-call, and error details needed for deterministic replay. Sensitive fields are encrypted or masked before dashboard display.
Retention
Retention follows the active plan: Free keeps 7 days, Pro keeps 30 days, and Team keeps 90 days of captured executions. Deleted apps stop new capture, and deletion requests can remove account or organization data where we are legally permitted to do so.
Replay boundary
Replay and protected payload unlocks run through the customer-configured FluxRun agent. The dashboard requests short-lived agent authorization; private replay keys stay in the customer's server runtime.
Access and deletion
Customers can request export, correction, deletion, or retention questions by emailing privacy@fluxrun.dev . We may need to verify ownership before acting on an app, organization, or execution.
Service providers
FluxRun uses infrastructure and communication providers for hosting, storage, auth, email, analytics, and payments. These providers process data only to operate FluxRun and support the customer account.
Launch note
This page is intentionally plain-language and product-specific. It should be reviewed by counsel before being treated as a final legal privacy policy.