Description of software services - Fusion
Last updated: 07.10.2026
Fusion is an AI-assisted app builder within the Flip AI platform. From a natural-language input (prompt), a ready-to-use application (the “generated app”) is created in a single step. The generated app runs entirely within the Flip AI platform and uses its functions, in particular user management, roles and permissions, and integrations. Fusion provides the following functions:
App creation
Generation from natural language. A working application is generated from a prompt in a single step and is executed within the Flip AI platform.
Iterative refinement. Generated apps can be adjusted and developed further iteratively through a dialogue-based (chat) interaction; the relevant chat history is passed to the language model only to the extent required for generation or adjustment.
Preview and approval. Generated apps are displayed before they are rolled out and are approved by the Customer. The Customer decides on productive use at its own responsibility, following prior review and functional acceptance.
Roll-out to user groups. Generated apps are rolled out to defined user groups via the role and permission management of the Flip AI platform. The number of apps that can be rolled out is governed by the contractual agreements with Flip AI (by default two (2) per Flip AI tenant). The agreed number may be exceeded; any excess is invoiced separately at the prices for additional apps set out in the offer.
Resolution of tenant-specific references. To resolve app dependencies, Fusion can resolve tenant-specific references (e.g. channels, users, pages, tasks) via the Flip AI APIs of the Customer tenant.
Image and media embedding. For generated apps, images can be embedded via an optional image search based on search terms derived from the input; uploaded reference images can be used as a design template. Images embedded via the image search are loaded directly by the respective user’s end device from the external image service (Section 3.3 of the DPA).
Integration into the Flip AI platform
User management, roles and permissions. Generated apps use the existing user management and the role and permission model of the Flip AI platform. A separate user or permission administration within the generated app is not required.
Platform binding. Generated apps are functionally self-contained but technically bound to the Flip AI platform. They are not separate, portable artefacts; there is no export as a standalone application or as source code.
External integrations
Review and approval. External integrations are only possible to a limited extent. Complex external API integrations are not part of the standard scope and are reviewed and approved on a case-by-case basis by the Fusion team solely in the interest of the technical integrity and security of the Flip AI platform.
Secure connection. API keys stored by the Customer are securely stored server-side via the dedicated connection function and are in principle not included in inputs to the language model; this does not apply to interfaces where the key is technically part of the call URL and is therefore processed in the context of the generated app (Annex 2 to the DPA). Associated API documentation (name, base URL, document content) can be uploaded. Where the Provider makes connectors available, the Customer can use them to set up connections to third-party systems of its choosing. Sign-in is performed with the Customer's respective user account at the third-party system; actions are logged there under that identity. Calls are made server-side via a proxy operated by the Provider; response data is passed through and is not stored.
AI processing
Model-based code generation. Code generation is performed using large language models (LLM inference). Processing is performed via Azure AI Services deployments; the place of computation is not restricted to the European Union. Storage at rest follows the region of the Provider's Azure resource and takes place within the European Union. Section 10 of the DPA governs the transfer.
Optional web and image search. Fusion can use an optional web and image search for research. The search terms transmitted to external search and image services may be processed outside the EU or the EEA. These functions are not intended for the input of personal data.
No training on personal data. Flip AI does not use personal data from Fusion processing to train, fine-tune or improve AI models; the model providers used likewise do not use inputs and outputs to train their models. Details are governed by the Data Processing Agreement (DPA).
Operation, security and data protection
Activation and deactivation. Fusion is deactivated by default for the Customer’s tenant and is only activated upon the Customer’s documented approval. The Customer can deactivate Fusion again at any time at tenant level.
Logging and key management. The content of inputs and outputs is not logged at the AI gateway; technical metadata (in particular timestamps and status information) is not affected by this. API keys stored by the Customer are stored securely and are in principle not included in inputs to the language model; Annex 2 to the DPA remains unaffected.
Data protection. The processing of personal data is carried out in accordance with the Provider's Data Processing Agreement (DPA) (processing on behalf under Art. 28 GDPR). The provider-side requirements of Regulation (EU) 2024/1689 (EU AI Act) are complied with.
Hosting. Fusion is operated within the European Union as part of the Flip AI platform; LLM inference is performed via Azure AI Services deployments, the place of computation is not restricted to the European Union and storage at rest takes place within the European Union. The search terms transmitted to external search and image services as part of the optional web and image search may be processed outside the EU or the EEA (see the “AI processing” section and Section 3.3 of the DPA). Generated source code is additionally stored in a source code repository outside the EU or the EEA.
Availability reporting. The availability status can be viewed at any time at getflip.com/status/.
Retention and export
The retention periods for the individual data categories are set out in the table below. Retention periods marked as configurable can be set by the Customer within the limits provided for. Customer content can be exported in the formats and via the routes stated. In all other respects, deletion after the end of the contract is governed by the main agreement and the data processing agreement.
| Data category | Retention | Configurable | Export |
| Chat histories and builder states | 12 months from collection, then deleted or anonymised | No | No self-service export; on request |
| Fusion-related log data | 12 months from collection, then deleted or anonymised | No | No export |
| Backups | Overwritten no later than 30 days after deletion in the productive system | No | No export |
| Inputs and outputs held by the model provider (in particular abuse detection) | Up to 30 days, stored within the EU | No | No export |
| Deployed apps | Deployment automatically deleted after 30 days without use | No | No export as a standalone application or as source code |
| Source code of generated apps | For the term of the contract; additionally stored in the source code repository outside the EU or the EEA; final deletion no later than 60 days after deletion of the session; deletion after the end of the contract in accordance with the DPA | No | No export as a standalone application or as source code |
| Draft and version states of apps | For the term of the contract; previews are rendered client-side and are not stored | No | No export |
| Data captured by the generated apps themselves | Deleted when the app or the session is deleted | No | No self-service export; on request |
| Images embedded via the image search | Not stored by the Provider | No | No export |
| Stored API keys | For the duration of the respective connection, at the latest for the term of the contract | No | No export |
| Uploaded API documentation | For the duration of the respective connection, at the latest for the term of the contract | No | No self-service export; on request |
| Access and refresh tokens for connectors, where made available | Until the respective connection is disconnected | No | No export |
| App usage data | Not collected | – | – |
No self-service export is available for Fusion. Upon the Customer’s request via support, the Provider makes the Customer content stored in Fusion available in a common electronic format; this includes in particular supporting the Customer in fulfilling data subject rights under Art. 15 and Art. 20 GDPR in accordance with the data processing agreement. Generated apps are not exported as a standalone application or as source code. The entries in the “Export” column refer to the export functions available during the term of the contract; the Customer’s rights under the main agreement (switching support) and under the data processing agreement remain unaffected.
For the data categories marked as “No export”, no export function is available; where they contain Customer Content within the meaning of clause 1 of the Terms, the Provider makes it available upon request via support in a structured, commonly used and machine-readable format. Clause 9.5 of the Terms and the Customer’s rights under clause 16.2 of the Terms (switching support) remain unaffected.
System requirements
The following minimum requirements apply to the operating systems and browsers of end devices:
Operating systems
Windows: last 3 major versions
macOS: last 3 major versions
iOS: last 3 major versions
Android: last 6 major versions
mobile app: iOS last 2 major versions, Android last 2 major versions
Browsers
Chrome desktop & mobile: last 3 major versions
Edge desktop: last 3 major versions
Firefox desktop: last 3 major versions
Safari desktop: last 3 minor versions
Fusion is used within the Flip AI platform; the system requirements of the Flip AI platform apply in addition.
Legal framework
This software service description sets out the characteristics of the Fusion software service. Which functions are owed in a specific case follows from the offer in conjunction with the main agreement; the Fusion Terms of Use (Fusion Terms) apply as the Special Terms of the module and prevail over this description in accordance with clause 18.1 of the GTC. Fusion requires the use of the Flip AI platform; the software service description of the Flip AI platform applies in addition. The service quality and availability owed are governed by the Service Level Agreement for the Flip AI platform; that agreement applies to the availability and operation of the Fusion environment (builder, runtime environment and storage). No service level applies to the apps generated with Fusion. Their functionality, quality and availability are the responsibility of the Customer, as they depend materially on the Customer’s inputs (prompts) and on connected third-party systems. The Service Level Agreement does not apply to the trial provision under the Fusion Terms. The Provider may develop the service further within the scope of the contractual provisions (modifications). The current version of this software service description is available at https://www.getflip.com/legal/softwaredescription-fusion/.