Privacy
Minimal data retention by design
FlyDex stores the minimum metadata needed to authenticate accounts, route traffic, and run billing. Session content is not stored at rest in the FlyDex control plane.
Stored
Service metadata
Name, email, auth provider identifiers, and timestamps.
Trial/subscription status and Stripe customer/subscription references.
Machine name, platform, connector version, and online state.
Operational events for pairing, approvals, and machine lifecycle actions, exported as privacy-scrubbed pseudonymous telemetry.
Not persisted at rest
Session content
Chat messages and Codex output are not stored at rest in FlyDex control-plane storage.
Thread previews, token usage summaries, and project-path previews are not stored at rest.
Prompt bodies and approval payload details are retained only while in flight.
Providers
Infrastructure services
Clerk
Stripe
Cloudflare