TrustCloud
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by TrustCloud S.L. · trustcloud.ai
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
TrustCloud at a glance
- Vendor
- TrustCloud S.L.
- Headquarters
- Incorporated in the United States source, captured 16 Nov 2026
- Data hosting
- Outside the EU by default source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates TrustCloud 2.5/5, the mean of 6 judges. TrustCloud is an AI-native continuous control monitoring platform, strongest on integrations and automation at 7-8: 150+ integrations across cloud, hybrid and on-premises, a documented API and SDK for regulated environments, ServiceNow-native operation, and automatic evidence collection from Jira, Snyk, KnowBe4 and BambooHR with human approval on every action. how scores are made
- As of
- Vendor pages captured 29 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
TrustCloud is an AI-native continuous control monitoring platform, strongest on integrations and automation at 7-8: 150+ integrations across cloud, hybrid and on-premises, a documented API and SDK for regulated environments, ServiceNow-native operation, and automatic evidence collection from Jira, Snyk, KnowBe4 and BambooHR with human approval on every action. Framework coverage at 6-7 rests on 18+ out-of-the-box standards, unlimited custom frameworks and auto-generated cross-mappings; we found no public information on NIS2, TISAX, DORA or BSI IT-Grundschutz. Audit readiness at 6-8 centres on AuditLens — one-click auditor access, progress visible in real time. Sovereignty at 1-2 and pricing transparency at 1-2 score lowest: the privacy policy places headquarters in the United States and says personal information may be transferred to the United States or other locations; we found no public information on hosting location, an EU hosting option or a data processing agreement; the captured pages show no price figures, the route being Schedule a Demo. Spreads stay narrow; information security management spans 4-6, pairing a live risk register with no public information on a risk methodology or in-product incident register.
Speaks for it
- Integrations and automation scored 7-8, on 150+ integrations across cloud, hybrid and on-premises plus a documented API and SDK
- Evidence collection runs automatically from Jira, Snyk, KnowBe4 and BambooHR with deterministic pass-or-fail outcomes and human approval on every action
- One satisfied control auto-generates progress toward SOC 2, ISO 27001 and HIPAA, across 18+ out-of-the-box standards and unlimited custom frameworks
- AuditLens gives auditors one-click access to controls, evidence and policies against a standard, with progress visible to the client in real time
- Controls and statement of applicability scored 5-7, each failing control carrying an owner, an SLA and a dollar figure, with remediation tasks synced into ServiceNow and Jira
Held against it
- Sovereignty scored 1-2: the privacy policy places headquarters in the United States and says personal information may be transferred to the United States or other locations
- We found no public information on hosting location, an EU hosting option, a data processing agreement or a subprocessor list for the platform itself
- Pricing transparency scored 1-2: the captured pages show no price figures, editions or billing terms, and the entry point is Schedule a Demo
- We found no public information on a statement of applicability generated from control status or on a revision-safe change history
- The captured pages give different pictures for CMMC, PCI-DSS, GDPR, CCPA and HITRUST, one update listing mappings as coming soon while the frameworks page presents them as supported
Best for
- Your teams already run ServiceNow, Jira and Splunk and want continuous monitoring that feeds ServiceNow IRM, Archer and Jira rather than replacing them
- You carry several frameworks at once and want satisfying one control to earn progress toward SOC 2, ISO 27001 and HIPAA simultaneously
- You want your external auditor working inside the product, invited with one click, with their progress visible in real time
Avoid if
- Your risk register must remain under European control, given a United States headquarters and a policy that personal information may be transferred to the United States or other locations
- You need a cost figure before engaging sales, since the captured pages show no prices and the entry point is Schedule a Demo
- You need a settled answer now on CMMC, PCI-DSS, GDPR, CCPA or HITRUST mappings, where the captured pages give different pictures of their status
The scores
| Criterion | Panel median |
|---|---|
| Asset & risk management depth | 2 of 5 |
| Controls, SoA & measures | 3 of 5 |
| Framework & standard coverage | 3.5 of 5 |
| Audit readiness & evidence | 3.5 of 5 |
| Integrations & automation | 4 of 5 |
| European sovereignty | 1 of 5 |
| Pricing transparency | 1 of 5 |
Asset & risk management depth
Show reasoningHide reasoning
How this is scored
The ISMS core: asset inventory, risk methodology (identification, assessment, treatment), inheritance of protection needs (Schutzbedarf) across assets, and security incident handling with its reporting deadlines.
0 — Not an ISMS tool; the product has no asset or risk management.
3 — A risk register with likelihood and impact, and an asset list that can be imported.
5 — Asset inventory and risk management with a configurable risk matrix, risk treatment with owners and measures, and a register for security incidents.
8 — A documented risk methodology (ISO 27005, BSI 200-3 or equivalent), protection needs inherited across asset relations, incident workflows with the NIS2 reporting deadlines (24h/72h), and risk acceptance with named owners.
10 — Risk management a certifier works inside: the complete asset-risk-treatment chain with inheritance, business continuity planning (BIA, ISO 22301 or BSI 200-4), incident reporting with export for the authority, and risk reporting for the executive level.
The CISO
The risk register is real: likelihood, impact, treatment, residual and target ratings, ownership assignment, continuous monitoring driven by control effectiveness, and board-ready risk quantification, with the control graph holding an application inventory and linking risks to controls and policies. I found no public information on a documented risk methodology, inheritance of protection needs across asset relations, an in-product incident register with the 24h/72h clocks, or risk acceptance with a named owner — the captured breach material is a downloadable template and a how-to article, not a workflow. 3 4 5 2
The GRC Consultant
TrustRegister is a genuine risk engine — automated quantification of likelihood, impact and exposure, treatment with status and residual risk, ownership assignment, forecasting and board-ready reports — and the Control Graph carries an application inventory with risks linked to controls and contracts. I found no public information on a documented risk methodology such as ISO 27005 or BSI 200-3, protection-needs inheritance across assets, or an incident register with the 24/72-hour reporting workflows; breach handling appears only as a downloadable template. Solidly above a plain register, but not the certifiable ISMS core I build for. 3 4 2
The Drafted IT Officer
TrustRegister gives me a real register — likelihood, impact and residual-risk fields, treatment status, owners, automated risk quantification and board-ready reports — plus an application inventory in the Control Graph and third-party vendors ranked by the risk they carry into crown-jewel applications. I found no public information on a security-incident register with the 24- and 72-hour reporting deadlines, a documented risk methodology, or protection needs inherited across assets, so it stops short of the full ISMS my world needs. 3 4 1 1
The Lead Auditor
TrustRegister is documented as a live risk register with likelihood and impact quantification, treatment status, residual risk, ownership assignment and forecasting, and the Control Graph lists an application inventory and risk register among its artifacts. We found no public information on a documented risk methodology, inheritance of protection needs across asset relations, an in-product security incident register with reporting deadlines, or risk acceptance with named owners; the breach-notification material captured is a downloadable template, and NIS2 deadlines appear nowhere. 3 4 2
The Evidence Integrator
TrustRegister runs a live risk register — likelihood, impact, treatment status, residual risk, named ownership — driven by control effectiveness and translated into board-ready dollar figures, while the Control Graph holds an application inventory fed from CMDB records and cloud configs. We found no public information on a documented risk methodology such as ISO 27005, on protection-need inheritance across asset relations, or on incident workflows with the 24-hour/72-hour reporting deadlines; breach notification appears only as a free downloadable template. 3 4 1 2
The Skeptic
TrustRegister is documented as a continuous risk register that quantifies likelihood, impact and exposure, tracks treatment status and residual risk in dollars, and assigns ownership, with an application inventory named among the Control Graph artifacts. However, we found no public information on a security-incident register, a documented risk methodology such as ISO 27005, or inheritance of protection needs; the breach material on the captured pages is a downloadable template plus a how-to article, not a module. That puts the asset-and-risk core between a basic register and a full ISMS. 3 4 1 2
Controls, SoA & measures
Show reasoningHide reasoning
How this is scored
Control catalogues, the statement of applicability, measure tracking and internal audit — whether the control side of the ISMS is operable or a checklist.
0 — No control catalogue or measures in the product.
3 — Control catalogues (such as ISO 27001 Annex A) with an implementation status per control.
5 — Controls linked to risks and to measures with owners and due dates, a statement of applicability generated from the control status, and internal audits supported with checklists.
8 — A statement of applicability always current from live control status, measure tracking with delegation and escalation, internal audit workflows with findings and corrective actions, and evidence attached to each control.
10 — The control fabric as a living system: catalogue updates versioned, audit programmes with recurring schedules, and every control answerable with linked, current evidence at any moment — all documented.
The CISO
Controls carry an owner, an SLA and a dollar figure, are tested continuously with deterministic pass/fail outcomes, and map across frameworks automatically; findings become auditable remediation tasks synced into ServiceNow and Jira. The statement of applicability — the artifact my certificate hangs on — appears on no captured page, and internal audit is documented only as a duration statistic (28 to 3 days), so the control fabric is live but the certificate's core output is undocumented. 1 4 5 7
The GRC Consultant
The control side is a living system rather than a checklist: technical, documentation and process controls modelled together and mapped to policies, risks, applications and contractual commitments, each failing control carrying an owner, an SLA and a dollar figure, remediation delegated into ServiceNow and Jira, and evidence collected and cited automatically. I found no public information on a statement of applicability generated from live control status, on escalation paths, or on an internal audit workflow with findings and corrective actions, though the vendor reports internal audits cut from 28 days to 3. Strong fabric, missing the classic SoA artifact. 4 5 1 9
The Drafted IT Officer
The control side looks operable rather than a checklist: controls are linked to risks, policies and applications in the Control Graph, each failing control carries an owner, an SLA and a dollar figure, and evidence arrives with citations, including audit-ready Jira tickets pulled automatically. We found no public information on a statement of applicability generated from control status, which is the first thing my ISO 27001 auditor would ask for. 4 1 9
The Lead Auditor
Controls are documented as linked to risks, policies and applications through the semantic Control Graph, continuously tested with deterministic pass or fail outcomes, failing controls carrying an owner, an SLA and a dollar figure, and evidence collected automatically per control; AuditLens extends the mapping engine to auditor review with completion flags. We found no public information on a statement of applicability generated from control status, and internal audit support is documented only as a marketing figure of days to complete one. 4 1 8 9
The Evidence Integrator
The control fabric is live rather than a checklist: every control mapped to policies, applications, risks and contractual commitments in the Control Graph, each failing control carrying an owner, an SLA and a dollar figure, remediation tasks synced into ServiceNow and Jira, and evidence collected automatically from Snyk, BambooHR and Jira with deterministic pass-or-fail outcomes and human approval. We found no public information on a generated statement of applicability or on internal-audit workflows with findings and corrective actions; the only internal-audit evidence is a days-to-complete statistic. 4 5 9 11 1
The Skeptic
The control side looks operable rather than a checklist: continuous monitoring tests technical, documentation and process controls, each failing control carries an owner, an SLA and a dollar figure, the Control Graph links controls to policies, risks and obligations, and the Jira and Snyk integrations automate evidence per control. AuditLens adds audit workflows with items flagged for follow-up and a '28→3 days' internal-audit figure. We found no public information on a statement of applicability generated from live control status, which keeps this short of the top anchors. 1 4 5 9 8 7 11
Framework & standard coverage
Show reasoningHide reasoning
How this is scored
Which regimes the product operationalises — ISO 27001, NIS2, TISAX/VDA ISA, DORA, BSI IT-Grundschutz, SOC 2 — and whether one control maps across them or each framework is a fresh island.
0 — No security framework built in; a generic task or document tool.
3 — One recognised framework (typically ISO 27001) delivered with its requirements and controls.
5 — Several named frameworks for its market (for example ISO 27001, NIS2, TISAX or BSI IT-Grundschutz), with controls mapped across at least two of them.
8 — Broad current coverage including NIS2, TISAX and DORA where relevant, one control satisfying many frameworks through a documented mapping, and updates published when a standard changes.
10 — Framework coverage as a living product: dozens of regimes, multi-compliance on one data basis, per-industry profiles, and a documented update cadence when the standard moves.
The CISO
Eighteen-plus out-of-the-box standards including SOC 2, ISO 27001, CMMC, FedRAMP, HIPAA, NIST CSF, PCI DSS and ISO 42001, delivered through a common control framework with auto-generated cross mappings and a published case mapping 400 controls to NIST 800-53 under one graph. For a European buyer the list stops at GDPR: I found no public information on NIS2, TISAX, DORA or BSI IT-Grundschutz, which is precisely the ground my certificate and my regulator stand on. 6 6 7 4
The GRC Consultant
This is the answer-once model I optimize for: eighteen-plus out-of-the-box standards plus unlimited custom frameworks, with satisfying a control auto-generating progress toward SOC 2, ISO 27001 and HIPAA, and a published case mapping 400 controls to NIST 800-53 on one graph. For my European benches the catalogue is US-centric — I found no public information on NIS2, TISAX, DORA or BSI IT-Grundschutz — and no documented cadence for updates when a standard changes. Multi-compliance on one data basis is well proven; European regime coverage is not. 6 7 4
The Drafted IT Officer
Eighteen-plus frameworks out of the box — SOC 2, ISO 27001, CMMC, FedRAMP, HIPAA, PCI DSS and more — with auto-generated mappings so satisfying one control makes progress toward several, plus unlimited custom frameworks and a documented case mapping 400 controls to NIST 800-53. But I found no public information on NIS2, TISAX, DORA or BSI IT-Grundschutz, and those are exactly the regimes a European shop like mine is being audited against. 6 7 4
The Lead Auditor
Eighteen-plus out-of-the-box standards including ISO 27001, SOC 2, HIPAA, CMMC, FedRAMP and the NIST family, unlimited custom frameworks, a common control framework, and auto-generated cross-mappings where satisfying one control progresses several regimes at once; a published case maps 400 controls to NIST 800-53. We found no public information on NIS2, TISAX or DORA — the regimes I certify against — nor a documented update cadence when a standard moves, beyond a public roadmap. 6 6 7 4
The Evidence Integrator
Eighteen-plus out-of-the-box standards — SOC 2, ISO 27001, CMMC, FedRAMP, HIPAA, HITRUST, PCI DSS, NIST CSF, ISO 42001 and more — sit on one common control framework with auto-generated mappings, so satisfying a control earns credit toward several regimes at once, evidenced by a customer case mapping 400 controls to NIST 800-53. We found no public information on NIS2, TISAX, DORA or BSI IT-Grundschutz, and no documented update cadence when a standard changes, though a public roadmap is published. 6 6 7 4
The Skeptic
Eighteen-plus out-of-the-box standards (SOC 2, ISO 27001, CMMC, HITRUST, HIPAA, PCI DSS, NIST CSF, ISO 42001 and more) plus unlimited custom frameworks, with auto-generated cross-mappings — satisfying one control yields progress toward SOC 2, ISO 27001 and HIPAA — and a 400-control NIST 800-53 mapping in a customer case. Two cautions: the captured pages give different pictures for CMMC, PCI-DSS, GDPR, CCPA and HITRUST (one product update presents mappings to them, with NIST 800-53, as coming soon, while the frameworks page presents them as supported), and we found no public information on NIS2, TISAX, DORA or BSI IT-Grundschutz. 6 6 7 4 8
Audit readiness & evidence
Show reasoningHide reasoning
How this is scored
Whether the system produces defensible proof: change history, evidence collection, and reports for auditors, authorities and management.
0 — No reports, history or evidence; the product only stores the current state.
3 — PDF or Word reports of risks and controls, and documents attachable to records.
5 — Versioned records or a change history, standard report generators (SoA, risk report, management report), and evidence attached per control.
8 — A revision-safe change history, audit evidence packs generated on demand, management reports at a click, and read-only auditor access.
10 — Audit readiness as a standing state: evidence status shown continuously per framework and scope, proof packs an external auditor accepts as they are, and any record reproducible as it stood on a given date.
The CISO
Auditors get one-click access through AuditLens with a mapping engine to review controls, evidence and policies against a standard, automatic progress reporting, and audit-ready evidence pulled automatically from Jira tickets; outputs carry citations to graph nodes and residual risk reaches the board in financial terms. I found no public information on a revision-safe change history or on reproducing any record as it stood on a given date, which an ISO 27001 surveillance auditor will eventually ask me for. 8 9 5 3
The GRC Consultant
AuditLens gives auditors one-click access to controls, evidence and policies reviewed against a chosen standard, lets them mark items complete or flag follow-up, and shows the client their progress in real time, while evidence collection is automated — Jira tickets pulled audit-ready, Snyk tests collected — with every output cited to a graph node and control status monitored continuously. What I found no public information on is a revision-safe change history or reproducing any record as it stood on a given date, the piece an external auditor eventually demands. Near standing-state audit readiness, short of the archival proof. 8 9 5 11
The Drafted IT Officer
AuditLens is the part I would actually use: click a button to invite the auditor, who then reviews controls, evidence and policies mapped to the standard, marks items complete or flags follow-up, while I watch their progress; internal audits are quoted at '28→3 Days' and every output carries cited evidence. We found no public information on a revision-safe change history or on reproducing a record as it stood on a given date, which is what an authority eventually asks me for. 8 5 9
The Lead Auditor
AuditLens is documented as one-click auditor access where the auditor reviews controls, evidence and policies against a standard with visible progress, and Jira evidence is pulled automatically in audit-ready form; board-ready reports come out of TrustRegister. We found no public information on a revision-safe change history, evidence packs as a standing state per framework and scope, or any record reproducible as it stood on a given date — the defence I require before I accept a system in an audit. 8 9 5 3
The Evidence Integrator
AuditLens gives an auditor one-click access to a workspace where they review controls, evidence and policies against a standard, mark items complete and flag follow-ups with the client watching progress in real time; evidence is pulled automatically — a Jira link becomes an audit-ready ticket instead of a screenshot — and every output is cited and traceable to a specific graph node with no sampling. We found no public information on a revision-safe change history or on reproducing any record as it stood on a given date. 8 9 5 3
The Skeptic
AuditLens invites an auditor with one click, gives them a mapping engine over controls, evidence and policies, and shows the client the auditor's progress in real time; Jira links pull an audit-ready version of a ticket as evidence in place of screenshots, and board-ready reports put residual risk in dollars. What I cannot find is the backbone: we found no public information on a revision-safe change history or on reproducing any record as it stood on a given date. 8 9 3 1 5
Integrations & automation
Show reasoningHide reasoning
How this is scored
Whether the platform feeds from the real IT estate — directory import, CMDB, ticketing, scanners, SSO, API — and automates evidence collection instead of re-typing it.
0 — No import, export or integration; data is typed in and printed out.
3 — CSV or Excel import and export, and reminders for recurring reviews.
5 — Single sign-on, a documented API or a few named connectors (directory, ticketing or CMDB), and recurring tasks with reminders and assignment.
8 — A documented REST API for the core objects, a named connector set (Jira/ServiceNow-class ticketing, CMDB, cloud and endpoint sources), webhooks, SSO with SCIM provisioning, and automated evidence tests with human review.
10 — The platform behaves like infrastructure: API coverage of the whole data model, events or webhooks for every object, continuous control monitoring against the live estate, and recurring evidence collection automated and documented.
The CISO
A documented API and SDK retrieve systems, policies and control health and continuously test data feeds from on-premises and regulated environments; 150-plus integrations cover ServiceNow, Splunk, Jira, Snyk, KnowBe4 and BambooHR, CMDB and identity data are listed sources, and automated checks run with human approval before any agent acts. I found no public information on webhooks, SCIM provisioning, or API coverage of the full data model. 10 5 11 9
The GRC Consultant
The estate side is unusually deep: a documented API and SDK covering systems, policies and control health plus continuous testing of on-premises feeds, 150+ integrations across cloud, hybrid and on-prem, ServiceNow-native operation with ServiceNow as investor and customer, Splunk, Jira, Archer, Snyk, KnowBe4 and BambooHR, and CMDB records, identity data and telemetry as sources, all under deterministic pass/fail outcomes with human approval. I found no public information on webhooks for objects or SCIM provisioning. Automating evidence instead of re-typing it is exactly what makes client twelve cheaper than client one. 10 5 1 11
The Drafted IT Officer
This is the strong suit for someone who already runs ServiceNow, Jira and Splunk: 150+ integrations across cloud, hybrid and on-premises, an API and SDK that reach on-premises and regulated environments, CMDB and identity data as sources, and connectors like Snyk, KnowBe4 and BambooHR automating tests and evidence — all with human-in-the-loop approval on every action. I found no public information on webhooks or SCIM provisioning, but the named connector set and the documented API are solid. 5 10 11 9
The Lead Auditor
A documented API and SDK retrieve systems, policies and control health and connect on-premises environments; named connectors cover ServiceNow IRM (native), Splunk, Jira, Snyk, KnowBe4 and BambooHR among 150+ integrations, with CMDB records, cloud configs, identity data and vulnerability findings as sources. Continuous control monitoring against the live estate with human-in-the-loop approval on every action is the documented core; we found no public information on webhooks or SCIM provisioning. 10 5 11 9
The Evidence Integrator
This is the closest to infrastructure behavior in this evaluation: 150-plus integrations across cloud, hybrid and on-premises, a Hybrid Data Fabric normalising CMDB records, cloud configs, identity data, security telemetry and vulnerability findings into one schema, continuous control monitoring against the live estate, and an API and SDK that continuously test data feeds from on-premises and regulated environments with human approval on every action — no CSV drawbridge in sight. We found no public information on webhooks or SCIM provisioning, and the API's documented objects cover systems, policies and control health rather than a claim of full data-model coverage. 5 10 10 9 11
The Skeptic
This is where the evidence is thickest: a documented API and SDK covering systems, policies and control health with on-premises connectivity, 150+ integrations, ServiceNow-native operation (ServiceNow is named as both investor and customer), Splunk, Jira and Archer feeds, and Snyk, KnowBe4 and BambooHR automating named evidence tests — with human approval required on every agent action. We found no public information on webhooks or SCIM provisioning, so it stops short of the infrastructure tier. 10 10 5 11 1 4
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the security posture of the whole company actually lives and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, AI features, email, support tooling), DPA. The risk register is itself a target. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.
0 — Proven non-EU end to end: non-EU entity and non-EU hosting with no EU option, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist; hosting location and subprocessors are not stated, or EU hosting is offered only on request or on top tiers.
5 — EU hosting stated as the default, a data processing agreement and a subprocessor list published; a parent company or a subprocessor may sit outside the EU.
8 — EU entity, EU hosting in named data centres, a subprocessor list with no non-EU processor touching customer content, and the DPA and TOMs published.
10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors, an on-premises or sovereign-cloud option, and the whole chain documented publicly.
The CISO
The privacy policy places the company's headquarters in the United States and states personal information may be transferred to the United States or other locations; I found no public information on an EU hosting option, a data processing agreement, a transfer impact assessment, or a subprocessor list covering customer content. On the evidence captured, the risk register of a European ISMS would live with a US corporation under US-transfer terms — for me that is a procurement stop sign, softened only because the processing agreement chain is undocumented rather than disproven. 12 10
The GRC Consultant
The privacy policy states the vendor is headquartered in the United States and that personal information may be transferred to the US or other locations, and we found no EU hosting or region option on the captured pages; the contracting entity appears as TrustCloud Corporation. Named service providers in the policy — HubSpot for chat, Google and Microsoft for login — sit outside Europe, and the data processing agreement status is unknown to me. For a European client's risk register, that is a posture I would have to treat as a risk itself. 12 10
The Drafted IT Officer
The entire company's risk posture would live with TrustCloud Corporation, headquartered in the United States, under a policy that says personal information 'may be transferred' to the United States or other locations, with HubSpot for chat and Google or Microsoft for login. I found no public information on hosting location, a data processing agreement, or an EU hosting option, so on what is published I cannot put my risk register under European control. 12
The Lead Auditor
The privacy policy states the company is headquartered in the United States and that personal information may be transferred to the United States or other locations, and no EU hosting or region option is mentioned on any captured page; a data processing agreement, a subprocessor list for the service and named hosting data centres are unknown. Because the default hosting location is never stated, a fully proven non-EU end-to-end picture is not established either — it simply is not documented. 12
The Evidence Integrator
The privacy policy places the company's headquarters in the United States and says personal information may be transferred to the United States or other locations, and no EU hosting or region option appears on the captured pages; the data processing agreement, default hosting location and the subprocessor chain for customer content are unknown. A risk register that holds the company's whole posture under a US-headquartered entity with possible US transfers is itself a target a European buyer must weigh. 12
The Skeptic
The captured privacy policy proves a US entity — 'headquartered in the United States', TrustCloud Corporation — and states personal information 'may be transferred' to the United States or other locations, with HubSpot, Google and Microsoft named among service providers. We found no public information on hosting location, an EU hosting option, a data processing agreement, or a subprocessor list for the platform itself, so a European buyer's risk register would sit with a US controller under possible US transfers with the rest of the chain unstated. 12 1
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.
0 — No public prices at all; every configuration is a sales conversation.
3 — A public "from" price or one priced edition; the other editions, modules or scale steps are not public.
5 — Public prices per edition or tier with the billing period (monthly or annual) stated and the main inclusions listed.
8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated, software separated from consulting, and VAT treatment given; only genuine corporate-group contracts are custom.
10 — Complete price computability: modules, scale steps, service packages and renewal rules public, so the invoice for a 100-employee company and a certification project is a two-minute exercise.
The CISO
A pricing page exists on the site, but the captured pages show no prices, editions or billing terms, and the documented next step is scheduling a demo. I found no public information on what any configuration costs, so the real invoice is not computable from what was captured. 8 1 3
The GRC Consultant
A pricing page exists on the site and the entry point shown is 'Schedule a Demo', but the captured pages contain no price figures, edition tiers, billing periods or inclusions — I found no public information on actual prices. With a platform spanning six named modules plus API, monitoring and intelligence layers, a buyer cannot compute an invoice from what was captured. Unpublished pricing is the market norm here, but nothing was captured to work with. 1 8 3
The Drafted IT Officer
The captured pages show a link labelled 'Pricing' and a 'Schedule a Demo' invitation, and I found no price figure, edition, billing period or module cost on any page we read — this is pitched at Fortune 500 CISOs, so my budget conversation would start with a sales call. Only the existence of the pricing page is public in what we captured. 1 8 3
The Lead Auditor
A pricing page exists on the site, but no price, edition, billing period or inclusion is stated anywhere in the captured content, and the documented path to evaluation is scheduling a demo. We found no public information on per-module, per-entity or consulting pricing, so the real invoice cannot be computed from public pages. 8 1 3
The Evidence Integrator
A pricing page is published in the product navigation, but the captured pages show no edition, price figure or billing period, and the route to a number runs through "Schedule a Demo". We found no public information on per-module or per-entity pricing, setup fees, VAT treatment, or the separation of software from consulting. 8 1 3
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in US
unverified
Why unverified?The privacy policy states the company's headquarters rather than a register of incorporation, and no imprint or company-register citation is provided on any page. |
0/2 pts | 12 Report an error |
|---|---|---|---|
| Hosting location |
Outside the EU
unverified
Why unverified?The policy only says personal information 'may be transferred' to the United States or other locations and never states the default hosting location for customer data; no EU hosting or region option is mentioned anywhere. |
0/4 pts | 12 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about TrustCloud
Is TrustCloud European?
Not determined: the vendor’s pages as captured do not say where TrustCloud is based. Its vendor, TrustCloud S.L., is incorporated in the United States, per the vendor’s page captured 16 Nov 2026.
Where does TrustCloud store data?
TrustCloud stores customer data outside the EU by default, per the vendor’s page captured 16 Nov 2026.
Does TrustCloud have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to TrustCloud?
As of 18 Nov 2026, the panel rates preeco | informationssicherheit (3.5/5), 6clicks (3.5/5) and Secfix (3.5/5) highest among the other 35 Information Security products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is preeco | informationssicherheit (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: TrustCloud alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. The privacy policy states the company's headquarters rather than a register of incorporation, and no imprint or company-register citation is provided on any page.
- Weak sourcing — Hosting location. The policy only says personal information 'may be transferred' to the United States or other locations and never states the default hosting location for customer data; no EU hosting or region option is mentioned anywhere.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 11 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page trustcloud.ai Checked 16 Nov 2026 +1 earlier capture: 29 Sep 2026 Details →
- 2 Asset & risk management depth — found from sitemap www.trustcloud.ai Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 3 Asset & risk management depth — found from sitemap www.trustcloud.ai Checked 16 Nov 2026 Details →
- 4 Controls, SoA & measures — found from sitemap www.trustcloud.ai Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 5 Controls, SoA & measures — found from sitemap www.trustcloud.ai Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 6 Framework & standard coverage — found from sitemap www.trustcloud.ai Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 7 Framework & standard coverage — found from sitemap www.trustcloud.ai Checked 16 Nov 2026 Details →
- 8 Audit readiness & evidence — found from sitemap www.trustcloud.ai Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 9 Audit readiness & evidence — found from sitemap www.trustcloud.ai Checked 16 Nov 2026 Details →
- 10 Integrations & automation — found from sitemap www.trustcloud.ai Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 11 Integrations & automation — found from sitemap www.trustcloud.ai Checked 16 Nov 2026 Details →
- 12 Privacy policy — found from the homepage www.trustcloud.ai Checked 16 Nov 2026 Details →