“The secure AI ecosystem to boost your creativity and productivity.”
Mindverse is a German all-in-one AI platform for text, research, images, audio, video, internal knowledge bases, assistants, and automated workflows. It provides various AI models through a single interface and is designed for individual users, teams, and businesses. Higher-tier plans enable custom agents, processes, integrations, and team management.
Mindverse
The secure AI ecosystem to boost your creativity and productivity
Location: Germany ⓘ Relativity GmbH, 25 Breite Straße, 13597 Berlin, Germany.
Content Suite Basic Text and image generation with an expanded request quota and limited AI image requests.
Content Suite Premium More extensive use with fair-use text generation and an increased image quota.
Content Suite Premium Plus Highest Content Suite quota, fair-use text generation, more images, and prioritized support.
Studio Starter AI chat, images, video, and Canva, unlimited internal knowledge, unlimited custom assistants, and Standard and Advanced models.
Studio Pro Starter features plus Expert and Sovereign models, custom agents, custom processes, and more than 500 integrations.
Studio Team Team sharing, role-based access, shared credit wallet, teams, and shared knowledge, assistants, agents, and processes. Other AI Credits Monthly credit for chat, models, images, videos, and other features; additional usage depends on the model.
Custom / Enterprise Custom AI environment with chat and voice bots, knowledge management, agents, workflows, API, integrations, branding, your own domain, and custom hosting.
Mindverse is a German AI platform that brings together various generative models and productivity features in a single, centralized environment. Users can create text, research content, generate images and media, analyze documents, and configure their own assistants or agents. For businesses, this is complemented by shared knowledge bases, roles, integrations, and process automation.
Target audience
Mindverse is ideal for freelancers, agencies, marketing teams, consulting firms, sales teams, service departments, knowledge workers, and companies with multiple AI use cases. The Content Suite is geared more toward individual creative and content users, while the Studio is designed for assistants, team knowledge, and business processes.
Outstanding features
The platform is not tied to a single language model. Depending on the task and data protection requirements, users can choose between top-tier external models, open models, and German-hosted models. Custom assistants can be connected to internal information and integrated with other applications via workflows.
Key Areas of Application
Mindverse is used for content production, research, SEO, translations, internal knowledge assistants, email communication, marketing, sales, and process automation. Image, audio, and video capabilities extend the platform beyond text-based AI.
Usage & Notes
Before going live, companies should determine which models are approved for which data categories. On-premises models can be selected for more sensitive content, while external models can be used depending on performance requirements. Roles, access permissions, and logging should be configured centrally before employees begin processing sensitive data.
| Target audience | Assessment |
|---|---|
| Individuals | Yes – Lite and Starter plans offer a relatively easy introduction to AI chat and content creation. |
| Self-employed / Freelancers | Very well suited – for text, images, research, customer communication, presentations, and content workflows. |
| SMEs | Very well suited – German platform, team features, knowledge bases, agents, processes, and numerous integrations. |
| Large enterprises | Yes – custom environments, custom domain, branding, API, integrations, roles, audit logs, and custom hosting are available. |
| Marketing and content teams | Very well suited – text editor, image and video generation, wizards, and reusable content processes. |
| Developers / IT teams | Yes – API, agents, processes, integrations, and customizable enterprise environments are available. |
| Knowledge-intensive departments | Very well suited – internal knowledge bases, RAG, documents, and custom assistants are key features. |
| Organizations with critical data protection requirements | Well-suited with the right model selection – hosting in Germany and non-training are positive factors; global image/video providers and third-party website providers must be reviewed separately. |
Hosting & Data
1) On-prem / local hosting
Meaning: The company operates the solution on its own hardware or within its own infrastructure. In the strictest sense, not only the application runs locally, but ideally the model as well.
2) Private cloud / data center
Meaning: The solution runs in a dedicated or more clearly separated cloud environment, often with a hosting provider or hyperscaler, but in a German data center or in a particularly controlled environment.
3) EU SaaS / managed
Meaning: The provider operates the solution itself as a service. The company uses the tool as a ready-made cloud service, ideally with EU data residency.
4) Hybrid
Meaning: One part of the processing remains internal / local / in a private cloud, while another part runs in an external cloud or EU SaaS.
5) AVV / DPA
Meaning: This is the data processing agreement or Data Processing Addendum. It governs that the provider processes personal data on behalf of the customer and is bound by the customer's instructions.
6) No training
Meaning: The provider does not use your prompts, uploads, attachments, chat histories, or outputs for training or improving the general model — ideally excluded by contract.
7) Open-source / transparency path
Meaning: There is a path toward greater technical transparency and sovereignty, for example through:
- open models
- documented components
- self-hostable parts
- traceable architecture
- export / switching options
| On-prem / local hosting | ❓ |
| Private cloud / data center | ❓ |
| EU SaaS / Managed | ⚠️ |
| Hybrid | ❓ |
| DPA / AVV | ❓ |
| No training on customer data | ❓ |
| Open source / transparency path | ❓ |
On-prem / local hosting: unclear
Not specified on the website. No reliable information was found regarding on-premises, local installation, or self-hosting on your own hardware.
Private Cloud / Data Center: Unclear
Not specified on the website. No clearly documented dedicated private cloud or isolated data center option was found.
EU SaaS / Managed: Partially
Several product pages advertise “Developed and hosted in Germany” and “GDPR-compliant”; the web privacy policy lists AWS with “Processing location: Germany.” However, this is not consistently substantiated across the entire ecosystem, as another TurboGPT privacy policy published on the domain also mentions processing in both the EU and the U.S.
Hybrid: unclear
Not specified on the website. No documented operating model was found that clearly combines internal or local processing with external SaaS.
Data Processing Agreement (DPA): Indirect / Not Available
The privacy policy refers to external parties that may be “designated as data processors” and to a list of data processors that can be requested. However, no publicly accessible DPA page, download, or clear process for obtaining the DPA was found on the website.
No Training: Unclear
Not specified on the website. No clear statement was found indicating that customer data, prompts, uploads, chat histories, or outputs are not used to train general models, nor was there a documented opt-out option.
Open Source / Transparency Path: Indirect / Not Available
A transparent sovereignty path is only indirectly discernible, for example through export instructions such as sharing and exporting mind maps. Open-source components, open models, or self-hostable parts are not specifically mentioned on the website.
Data Processing
The website provides a privacy policy for the general web application that mentions AWS and “Processing location: Germany,” as well as general information on potential data processors and transfers to third countries based on standard contractual clauses. In addition, product pages advertise hosting in Germany. At the same time, the TurboGPT privacy policy published on the domain paints a different picture, with EU storage on Firebase but processing in the U.S. via OpenRouter and Composio. While this suggests an EU-related hosting connection for users in the EU/EEA, the actual data processing for the entire Mindverse ecosystem remains only partially transparent.
Conclusion
For an EU/EEA tool directory, Mindverse’s hosting and data protection practices are positive but not conclusively documented. There are clear EU/Germany references and indications of GDPR compliance, but key evidence for a robust overall assessment is publicly missing: a data processing agreement (DPA), a published list of subprocessors, an explicit “no-training” commitment, consistent EU data residency across all product areas, and documented on-premises or private cloud options. Therefore, the overall classification is “conditional.”
Sources
| On-prem / local hosting | ❓ |
| Private cloud / data center | ❓ |
| EU SaaS / Managed | ⚠️ |
| Hybrid | ❓ |
| DPA / AVV | ❓ |
| No training on customer data | ❓ |
| Open source / transparency path | ❓ |
On-prem / local hosting: unclear
Not specified on the website. No reliable information was found regarding on-premises, local installation, or self-hosting on your own hardware.
Private Cloud / Data Center: Unclear
Not specified on the website. No clearly documented dedicated private cloud or isolated data center option was found.
EU SaaS / Managed: Partially
Several product pages advertise “Developed and hosted in Germany” and “GDPR-compliant”; the web privacy policy lists AWS with “Processing location: Germany.” However, this is not consistently substantiated across the entire ecosystem, as another TurboGPT privacy policy published on the domain also mentions processing in both the EU and the U.S.
Hybrid: unclear
Not specified on the website. No documented operating model was found that clearly combines internal or local processing with external SaaS.
Data Processing Agreement (DPA): Indirect / Not Available
The privacy policy refers to external parties that may be “designated as data processors” and to a list of data processors that can be requested. However, no publicly accessible DPA page, download, or clear process for obtaining the DPA was found on the website.
No Training: Unclear
Not specified on the website. No clear statement was found indicating that customer data, prompts, uploads, chat histories, or outputs are not used to train general models, nor was there a documented opt-out option.
Open Source / Transparency Path: Indirect / Not Available
A transparent sovereignty path is only indirectly discernible, for example through export instructions such as sharing and exporting mind maps. Open-source components, open models, or self-hostable parts are not specifically mentioned on the website.
Data Processing
The website provides a privacy policy for the general web application that mentions AWS and “Processing location: Germany,” as well as general information on potential data processors and transfers to third countries based on standard contractual clauses. In addition, product pages advertise hosting in Germany. At the same time, the TurboGPT privacy policy published on the domain paints a different picture, with EU storage on Firebase but processing in the U.S. via OpenRouter and Composio. While this suggests an EU-related hosting connection for users in the EU/EEA, the actual data processing for the entire Mindverse ecosystem remains only partially transparent.
Conclusion
For an EU/EEA tool directory, Mindverse’s hosting and data protection practices are positive but not conclusively documented. There are clear EU/Germany references and indications of GDPR compliance, but key evidence for a robust overall assessment is publicly missing: a data processing agreement (DPA), a published list of subprocessors, an explicit “no-training” commitment, consistent EU data residency across all product areas, and documented on-premises or private cloud options. Therefore, the overall classification is “conditional.”
Sources
Strengths & weaknesses at a glance
| Strengths | Weaknesses |
|---|---|
| • A very wide range of features in a single interface | • Different models and media features may have different data regions and provider terms. |
| • German provider and hosting in Germany for core operations | • No publicly documented full on-premises operation. |
| • Choice between powerful external models and proprietary models | • A dedicated enterprise model is not automatically equivalent to a customer-owned private cloud. |
| • According to the provider, customer data is not used to train the connected LLMs | • ISO 27001 certification is described as planned; completed certification has not been verified. |
| • Custom assistants, knowledge bases, and agents | • The public privacy policy and product information do not detail all model and subprocessor flows. |
| • Numerous integrations for business applications | • Credit and model logic can be complex for users. |
| • Role-based access control and audit functions for teams | • AI outputs require expert review. |
| • Terms of Service available upon request | • Some particularly powerful models and automations are reserved for higher-tier plans. |
| • Suitable for users with varying levels of technical expertise. |
Reviews
0 reviews in total
There are no confirmed reviews for this tool yet.
Submit review
Your review will only become visible after email confirmation. This protects the portal against abuse.
Report review
Please select the reason why this review should be checked.
GDPR-compliant usage possible?
The website includes a privacy policy, names a data controller in Germany, and refers to data processors as well as potential transfers from the EU to third countries via standard contractual clauses. For the standard web application, hosting via AWS is specified with “Processing location: Germany.” At the same time, the website does not provide a publicly accessible subpage for the Data Processing Agreement (DPA), a publicly viewable list of subprocessors, a clear statement regarding the exclusion of AI training using customer data, or a reliable description of on-premises, self-hosting, or private cloud options. For use throughout the EU/EEA, GDPR-compliant use is therefore not clearly established by default, but only subject to certain conditions and following additional clarification with the provider.
Positive
Positive aspects include the existing privacy policy, the explicit inclusion of the EU and EEA in the legal text, the specified processing location of Germany for AWS in the web privacy policy, and several product pages featuring statements such as “Developed and hosted in Germany” and “GDPR-compliant”. Furthermore, it is explained that external entities may be designated as data processors and that a current list of these parties can be requested from the provider.
Negative
A negative point is that the website does not mention a publicly accessible process for concluding a Data Processing Agreement (DPA), does not link to a published list of subprocessors, and contains no clear assurance that prompts, uploads, chat histories, or outputs will not be used to train general models, and there is no robust documentation regarding EU data residency for all product areas. Furthermore, the TurboGPT privacy policy found on the domain indicates that data processing for an app also takes place in the U.S. via OpenRouter and Composio; this argues against a blanket “EU-only” classification for the entire ecosystem.
Server Location
The general web privacy policy lists “Processing location: Germany” for AWS. Product pages additionally state “Developed and hosted in Germany.” However, the TurboGPT privacy policy published on the same domain states: Firebase in the EU, OpenRouter in the United States, Composio in the United States, and Apple worldwide. A uniform server location for the entire tool is therefore not consistently or fully specified on the website.