Introduction
This article states what happens to the content you put into ARVO Studio and to the output it generates. It is written to match the Bluefort Intelligence EULA and the Data Processing Agreement, which remain the authoritative statements of the position.
What Bluefort does not do
Four commitments cover the point.
- Bluefort does not use identifiable customer content or generated output to train AI models.
- Bluefort does not contribute identifiable customer content or generated output to third-party foundation-model training.
- Bluefort does not sell customer data.
- Bluefort does not retain identifiable customer content for product improvement.
Telemetry
Telemetry is a separate matter from the content of your projects. It covers activation, environment and product usages, which is information about how the product is licensed and used rather than the business data inside it. Keeping the two apart is deliberate and the commitments above concern customer content and generated output.
AI on your own account
As identified already in previous articles, AI operations run through your own Azure AI Foundry deployment or your own Anthropic account, under your agreement with that provider. That agreement governs the AI service itself, so read it alongside this article. You can also stop AI operations for the environment at any time and revoke the application’s consent in your own tenant.
The EULA
The Bluefort Intelligence EULA governs the licence and the Data Processing Agreement governs data processing. Where this article appears to differ from either document, those documents apply. If you need the position in contractual terms, ask your Bluefort contact for the current versions rather than relying on this summary.