“The home of the AI Workforce” / “Scale GTM results, without scaling headcount”
Relevance AI is a low-/no-code platform for building, orchestrating, and operating AI agents and multi-agent workforces. The current focus is strongly on go-to-market processes such as sales, marketing, CRM enrichment, outbound, inbound qualification, customer success, and support automation.
Relevance AI
The home of the AI Workforce / Scale GTM results, without scaling headcount
Location: Australia ⓘ Australia. The contracting party is OnSearch Pty Ltd, an Australian company with ABN 33 637 909 409,
Team For teams with larger workloads; includes everything in Pro plus Credit Rollover, five Build Users, End Users, multiple Shared Projects, Calling & Meeting Agents, A/B Testing, Analytics Dashboard, and Priority Support.
Enterprise Custom enterprise plan with unlimited users and projects, Enterprise App Triggers, Agent Evaluations, Work Hour Controls, Multi-Org Management, Enterprise Security, Dedicated Account Manager, Custom Implementation, and Priority Early Access. Other Actions Usage units for agent and workflow executions; different monthly or annual quotas are included depending on the plan.
Vendor Credits Prepaid/quota model for third-party AI model usage; according to the Terms, Vendor Credits can be used for Third-Party-AI-Model-Usage and are tied to an active subscription.
Bring Your Own LLM Users can connect their own LLM accounts or API keys, for example for OpenAI, Anthropic, or Google; processing then additionally depends on the respective provider and its DPA/Terms.
Enterprise Data Retention Enterprise feature for the automatic control of the retention and deletion of Tool Runs, Agent Conversations, Workforce Tasks, and Asset Versions; according to the documentation, it must be activated by Relevance AI.
Target audience
Relevance AI is aimed at companies, revenue teams, sales teams, marketing teams, customer success teams, support teams, operations departments, agencies, and technical builders who want to automate recurring business processes with AI agents. The tool is particularly strong for go-to-market organizations that want to scale lead research, CRM enrichment, outbound sequences, inbound qualification, customer communication, and internal workflows without having to hire additional staff.
Outstanding features
The platform combines a low-/no-code agent builder, Workforces as visual multi-agent systems, tools, knowledge, scheduling, approvals, chat, Slack, API integrations, custom apps, and more than 2,000 integrations. Particularly outstanding are the focus on agentic workflows in the GTM area, the ability to equip agents with company knowledge and integrations, as well as enterprise features such as SSO, RBAC, audit logs, data retention, and data residency. Relevance AI also emphasizes that customer data is not used for model training.
Main use cases
Typical use cases include AI BDR, outbound SDR, lead routing, account research, CRM enrichment, inbound qualification, inbox management, customer support, lifecycle marketing, SEO content creation, data analysis, document processing, reporting, and internal workflow automation. Relevance AI is also suitable for teams that want to split more complex processes into several specialized agents, such as research agents, review agents, writing agents, CRM agents, and escalation agents.
Usage & notes
Relevance AI is used via the web platform. Users build agents, tools, and Workforces, connect integrations such as CRM, email, calendar, Slack, or data sources, and define when agents should act automatically or obtain human approvals. For serious productive use, companies should clearly define roles, data sources, API keys, agent permissions, escalations, and retention rules. When handling personal data, customer data, or sensitive business data, region, subprocessors, DPA, SCCs, deletion periods, and enterprise security documentation should be reviewed in advance.
| Target audience | Assessment |
|---|---|
| Private individuals | Rather no – too strongly focused on business, sales, GTM, and workflow automation. |
| Self-employed / freelancers | Conditionally – useful for technically savvy users with recurring sales, research, content, or automation processes. |
| SMEs | Yes – suitable for teams that want to use AI agents for sales, support, marketing, research, CRM maintenance, or internal workflows. |
| Large enterprises | Yes – especially with enterprise features such as SSO, RBAC, audit logs, data retention, multi-org management, security controls, and DPA/trust center documentation. |
| Developers / technical teams | Yes – suitable for API/MCP usage, custom integrations, BYO-LLM, custom tools, Python tool steps, and agentic workflows. |
| Sales and GTM teams | Very well suited – the core target audience is BDR/SDR, outbound, lead enrichment, CRM, meeting, and pipeline automations. |
| Privacy-sensitive organizations | Conditionally to well suited – positives include SOC 2 Type II, GDPR information, encryption, region selection, and no training on customer data; the specific region, DPA, subprocessors, and external LLM providers must be reviewed. |
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: indirect / not available
A true on-premise or self-hosting deployment on customer-owned hardware is not indicated on the website. It mentions 'single tenant or private cloud deployment' as well as self-hosted models by Relevance AI in its own AWS and Azure environments, but not a local customer installation.
Private cloud / data center: partial
For Enterprise, the website mentions 'single tenant or private cloud deployment' and describes more dedicated Enterprise environments with separate service and database for certain Enterprise configurations. However, specific technical and contractual details regarding the private cloud in the EU/EEA area are not provided.
EU SaaS / managed: partial
There is a managed SaaS service with region selection and a European region during registration. However, London is specifically named for Europe, i.e. the United Kingdom instead of the EU/EEA. This means there is European data residency in a broader sense, but no clearly substantiated EU/EEA data residency.
Hybrid: indirect / not available
There are references to private cloud, export functions, integrations, and Enterprise controls, but no clearly described hybrid operating model in which a defined part of the processing runs locally or in the customer's private environment and another part runs as an external service.
DPA / Data Processing Agreement: partial
In the Security section, the website says that the 'Data Processing Agreement (DPA)' can be viewed on the website. However, a clear, generally accessible customer DPA within the reviewed domain area was not unambiguously found. Therefore, it is only partially covered.
No training: covered
The Security overview explicitly states that customer data is not used to train the models or improve the services, except under a specific partnership agreement. In addition, it says metadata is never used for model training, and elsewhere 'No training on your data' is highlighted.
Open source / transparency path: partial
The website states that, in addition to its own hosted OpenAI models, Relevance AI also hosts open-source models such as 'LAMA' and Fireworks in its own AWS and Azure environments. However, a comprehensive open-source, self-hosting, or source-availability path for the platform itself is not specified.
Data processing
The website describes a multi-regional SaaS model with region selection during registration and logical tenant separation. For Enterprise, separate services and databases are mentioned for certain configurations, as well as 'single tenant or private cloud deployment'. Data export is possible in standard formats, deletion can be requested, and there are Enterprise data retention policies for data stored in the platform. At the same time, the Data Security Policy excludes data processing outside the platform, and the data retention documentation explains that retention policies do not apply to data held by subprocessors. For EU/EEA users, it is also relevant that the European region is listed on the website as London and therefore lies outside the EU and EEA.
Conclusion
On its website, Relevance AI offers several strong compliance building blocks for the European area: privacy policy, explicit GDPR statement, region selection, no training on customer data, export/deletion, SOC 2 Type II, as well as Enterprise options such as private cloud and single-tenant. However, for a reliable EU/EEA assessment, gaps remain: the stated European location is London instead of the EU/EEA, the specific customer DPA is not clearly discoverable, and the subprocessor details are not within the source base permitted here. Therefore, from an EU/EEA perspective, GDPR-compliant use is best classified as conditional, not clearly 'yes'.
Sources
- https://relevanceai.com/privacy-policy
- https://relevanceai.com/docs/admin/security
- https://relevanceai.com/data-security-policy
- https://relevanceai.com/
- https://relevanceai.com/ask-relevance
- https://relevanceai.com/enterprise
- https://relevanceai.com/docs/get-started/project-management/ids
- https://relevanceai.com/docs/get-started/enterprise/data-retention
| 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: indirect / not available
A true on-premise or self-hosting deployment on customer-owned hardware is not indicated on the website. It mentions 'single tenant or private cloud deployment' as well as self-hosted models by Relevance AI in its own AWS and Azure environments, but not a local customer installation.
Private cloud / data center: partial
For Enterprise, the website mentions 'single tenant or private cloud deployment' and describes more dedicated Enterprise environments with separate service and database for certain Enterprise configurations. However, specific technical and contractual details regarding the private cloud in the EU/EEA area are not provided.
EU SaaS / managed: partial
There is a managed SaaS service with region selection and a European region during registration. However, London is specifically named for Europe, i.e. the United Kingdom instead of the EU/EEA. This means there is European data residency in a broader sense, but no clearly substantiated EU/EEA data residency.
Hybrid: indirect / not available
There are references to private cloud, export functions, integrations, and Enterprise controls, but no clearly described hybrid operating model in which a defined part of the processing runs locally or in the customer's private environment and another part runs as an external service.
DPA / Data Processing Agreement: partial
In the Security section, the website says that the 'Data Processing Agreement (DPA)' can be viewed on the website. However, a clear, generally accessible customer DPA within the reviewed domain area was not unambiguously found. Therefore, it is only partially covered.
No training: covered
The Security overview explicitly states that customer data is not used to train the models or improve the services, except under a specific partnership agreement. In addition, it says metadata is never used for model training, and elsewhere 'No training on your data' is highlighted.
Open source / transparency path: partial
The website states that, in addition to its own hosted OpenAI models, Relevance AI also hosts open-source models such as 'LAMA' and Fireworks in its own AWS and Azure environments. However, a comprehensive open-source, self-hosting, or source-availability path for the platform itself is not specified.
Data processing
The website describes a multi-regional SaaS model with region selection during registration and logical tenant separation. For Enterprise, separate services and databases are mentioned for certain configurations, as well as 'single tenant or private cloud deployment'. Data export is possible in standard formats, deletion can be requested, and there are Enterprise data retention policies for data stored in the platform. At the same time, the Data Security Policy excludes data processing outside the platform, and the data retention documentation explains that retention policies do not apply to data held by subprocessors. For EU/EEA users, it is also relevant that the European region is listed on the website as London and therefore lies outside the EU and EEA.
Conclusion
On its website, Relevance AI offers several strong compliance building blocks for the European area: privacy policy, explicit GDPR statement, region selection, no training on customer data, export/deletion, SOC 2 Type II, as well as Enterprise options such as private cloud and single-tenant. However, for a reliable EU/EEA assessment, gaps remain: the stated European location is London instead of the EU/EEA, the specific customer DPA is not clearly discoverable, and the subprocessor details are not within the source base permitted here. Therefore, from an EU/EEA perspective, GDPR-compliant use is best classified as conditional, not clearly 'yes'.
Sources
- https://relevanceai.com/privacy-policy
- https://relevanceai.com/docs/admin/security
- https://relevanceai.com/data-security-policy
- https://relevanceai.com/
- https://relevanceai.com/ask-relevance
- https://relevanceai.com/enterprise
- https://relevanceai.com/docs/get-started/project-management/ids
- https://relevanceai.com/docs/get-started/enterprise/data-retention
Strengths & weaknesses at a glance
| Strengths | Weaknesses |
|---|---|
| • Very strong for GTM, sales, marketing, and revenue operations workflows | • Strong focus on GTM; less specialized for general enterprise processes outside Sales/Marketing |
| • Low-/no-code creation of agents and workforces | • According to the provider, many enterprise security documents are only made available to enterprise customers under NDA |
| • Broad integration coverage and API/custom integration path | • Complete official company address not clearly verifiable publicly |
| • Free version available for testing | • Depending on usage, region, and subprocessors, data may be processed internationally, including in Australia, the UK/EEA, and the USA |
| • Enterprise features such as SSO, RBAC, audit logs, data residency, and SOC 2 Type II | • No publicly clearly identifiable customer-related AVV/DPA for EU customers within the scope of the research |
| • No training on customer data according to the provider |
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?
For users in the EU/EEA, GDPR-compliant use is generally possible based on the information available on the website, but it is not fully unambiguous and is not easy to verify in every variant. Positive aspects include the selectable EU/UK region for data storage, the explicit statement regarding GDPR compliance, a documented commitment not to train on customer data, as well as references to a DPA and subprocessors. Limiting factors are that the specifically named European location, London, is in the United Kingdom and therefore not in the EU/EEA, that the actual subprocessors list is not disclosed within the reviewed domain area on the referenced website, and that additional checks remain necessary for parts of the processing outside the platform or with third-party providers.
Positive
The website documents a privacy policy, a security overview, EU/UK data residency at account creation, export and deletion options, SOC 2 Type II, DPA references, PII masking, as well as the statement 'We do not use your data to train our models or improve our services unless you have a specific partnership agreement with us'. In addition, Relevance AI mentions enterprise options such as 'single tenant or private cloud deployment' and multi-region deployment.
Negative
The website does not name an EU/EEA data center in the strict sense, but instead explicitly names London in the United Kingdom for Europe. A specific AVV/DPA with customers is not clearly findable as a clearly linked customer document within the reviewed domain area; there is only the note that a DPA can be viewed on the website. The subprocessors are only mentioned by reference to an external trust center subdomain, which was not used here as a source. In addition, the Data Security Policy explains that it does not apply to the processing, storage, or transmission of data outside the platform; the data retention documentation likewise states that retention rules do not apply to data processed or stored by subprocessors.
Server location
According to the website, depending on the selection made during registration, data storage is possible in Australia, the USA, or in the EU/UK region. For the European region, 'EU (London)' is specifically named. The website does not specify a data center within the EU or the EEA; for Europe, only London in the United Kingdom is mentioned.
