Flux LLC operates Flux and fluxcli.com. This policy explains how information moves through the website, desktop app, and hosted AI service. Contact support@fluxcli.com with privacy questions or requests.
Pilot applications and research
If you apply for the agency pilot, we store the contact, agency, technical-environment, access-readiness, proposed-task, and optional note information you submit. We use it to assess fit, prevent abuse, coordinate onboarding, and measure whether the pilot workflow is useful. Applying does not authorize us to publish your name, client identity, site content, screenshots, recordings, or results. We request separate written permission before recording a customer session for publication or using identifiable pilot evidence in marketing.
Account and payment information
We store your email, password hash, optional profile details, account status, workspace membership, and subscription records. Stripe processes payments and manages payment methods; Flux stores Stripe customer, subscription, invoice, and checkout identifiers rather than full card numbers. We use Resend to send account recovery and workspace invitations.
Your sites and local work
The desktop app keeps site connection details, local previews, conversations, and working files on your computer. Provider keys, Flux session tokens, and SSH credentials are stored in your operating system’s credential store and used in memory while needed. Your Flux workspace records site labels and a hash identifying each connected site to enforce plan limits. The workspace owner can see connected site labels and member account information.
AI requests
AI requests can include your prompts, selected files, tool results, and relevant site content. With your own key, the engine sends these requests directly to your selected provider. With Flux hosted credits, requests pass through the Flux gateway directly to Anthropic, OpenAI, or Google, according to the model you select. Choose content you have permission to share and avoid including unnecessary personal information or secrets.
The hosted gateway does not store prompts or generated code in its billing database. It stores provider request IDs, model names, token counts, costs, and the account that made a request. The selected model provider applies its own privacy and retention policies. Flux does not request stored conversations from OpenAI or Google. Provider-side processing and retention may still apply. Provider keys are not shared with your workspace teammates.
Service operation and security
Our hosting and database services process account information and technical request information needed to operate Flux. We use a session cookie for website sign-in and hashed network identifiers for abuse rate limits. Operational logs may include request metadata, errors, and diagnostic details. Support messages include information you choose to send us. Do not include passwords or provider keys in a support request.
Retention and your choices
We keep account and workspace information while it is needed to provide the service, and payment or security records for operational, accounting, dispute, and legal requirements. You can remove connected sites and workspace members in the dashboard, sign out of the app, and delete local app data on your computer. To request access, correction, or deletion of information held by Flux LLC, email support from your account address. We may need to verify your identity and retain records required for an outstanding payment, dispute, security investigation, or legal obligation.
Service providers and changes
Information is processed by service providers needed for hosting, database storage, payments, account email, and the AI route you choose. Processing may take place outside your location. We may also disclose information when required by law or to address abuse and protect the service. When we change this policy, we update the effective date and provide notice of material changes through the service or your account email.