Versioned intent
Brief revisions and the selected source inputs stay attached to the project that produced the run.
Security boundaries
FluxVision applies one authorization model across web sessions, API keys, projects, assets, and results, with explicit boundaries around external generation providers.
Brief revisions and the selected source inputs stay attached to the project that produced the run.
The required generation credits are shown before a paid request is submitted.
Workflow steps, bounded retries, model routing, and provider state remain traceable while a job runs.
A result stays connected to its generation attempt and review state before it is kept in the project archive.
The audit trail is product provenance, not a compliance certification or a guarantee that an output is correct. It does not replace rights clearance, editorial judgment, disclosure requirements, or a final human review.
When an output needs another pass, the creator can return to the project context instead of reconstructing the prompt, source media, cost, and approval history from separate tools.
Web authentication uses configured Google or Apple OAuth. Revocable sessions protect browser access, while device and API secrets are stored as hashes rather than recoverable plaintext credentials.
Project access is checked against the workspace that owns the project and its media.
Uploaded media and generated results are stored in private Cloudflare R2 buckets.
Prompts and related job data are sent to the configured provider only when a generation is requested.
Deletion revokes access immediately and queues eligible media objects for retryable removal.
This is a product-security summary, not a claim of third-party certification. Provider retention may continue under that provider’s disclosed terms when it offers no deletion API. For data handling and retention details, read the full Privacy Policy.