Data Protection
TerraTrue
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by TerraTrue Inc. · terratrue.com
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.
TerraTrue at a glance
- Vendor
- TerraTrue Inc.
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Panel verdict
- The AI panel rates TerraTrue 2/5, the mean of 6 judges. TerraTrue is a data-protection platform built around design-time review: it reads draft PRDs and opens privacy and security reviews before code is written, screening AI features against the EU AI Act and US state AI and automated-decision rules. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 4 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
TerraTrue is a data-protection platform built around design-time review: it reads draft PRDs and opens privacy and security reviews before code is written, screening AI features against the EU AI Act and US state AI and automated-decision rules. Its strongest scores land in integrations and automation at 7-8, crediting a data catalog spanning 25 sources, bi-directional Jira, Slack and Ironclad syncs, an AWS scanning agent that keeps data and credentials inside the customer's VPC, and an MCP server exposing review history to Claude, Gemini, Copilot and ChatGPT. Privacy management scores cluster at 4: DPIA, ROPA and PII-discovery automation is documented, but no public information shows TOMs, legal-basis linkage or an authority-ready register output. Rights and incidents is weakest at 0-1; five judges found no public information on data subject requests, breach registers or the 72-hour clock. Audit readiness spans 2-4, higher scores crediting drift alerts and GitHub pull-request checks, lower ones citing no evidence packs or auditor access. Sovereignty scores range 0-2, only a subprocessors page disclosed. Persona-weighted totals range 3.3-5.2; no price figures were captured.
Speaks for it
- Reviews open at design time, with TerraTrue reading draft PRDs to find sensitive data flows and AI dependencies before code is written.
- Data catalog connects to 25 sources including Snowflake and Databricks and flags drift when production stops matching the approved state.
- Bi-directional Jira, Slack and Ironclad syncs trigger risk reviews with AI-pre-populated intake questionnaires.
- A client agent runs in the customer's own Kubernetes to scan AWS datastores without data or credentials leaving the VPC.
- AI governance screening assesses proposed AI features, models and vendors against the EU AI Act, US state AI and automated-decision rules and internal policy.
Held against it
- We found no public information on data subject request handling, deletion tracking, breach registers or the 72-hour notification clock, and rights and incidents scores sit at 0-1.
- Privacy management scores cluster at 4, with no public information on TOMs, legal bases linked into records, or an authority-ready register output.
- No sovereignty attributes are on record; the only proven disclosure is a subprocessors page, and we found no public information on hosting location, contracting entity or a data processing agreement.
- We found no public information on national law variants such as BDSG, Swiss nDSG or UK GDPR, or on a published legal-update cadence, leaving framework coverage at 4-5.
- We found no public information on a documented REST API, webhooks or SCIM user provisioning.
Best for
- You run privacy and security reviews inside engineering tools and want reviews triggered from Jira, Confluence, Notion, Google Docs or Slack with AI pre-filled intake.
- You need automated discovery and drift detection across a data estate of 25 connected sources, from Snowflake to Databricks.
- You screen AI features, models and vendors at proposal time against the EU AI Act and US state AI and automated-decision rules.
- You want review history queryable inside Claude, Gemini, Copilot or ChatGPT through an MCP server whose permissions an administrator can revoke.
Avoid if
- You need rights and incident operations as a running capability — the captured workflows happen before code is written, and rights and incidents scores sit at 0-1.
- You must hand a supervisory authority evidence packs or register reports — audit readiness scores span 2-4, with the visible evidence resting on drift alerts, GitHub pull-request checks and a Google Sheets export.
- Your screening must cover national privacy law variants such as BDSG, Swiss nDSG or UK GDPR — the named screening content covers the EU AI Act and US state AI and automated-decision rules, and framework coverage scores range 4-5.
- You must know where your compliance record is hosted and under whose law it contracts — sovereignty scores range 0-2 and the only disclosure is a subprocessors page.
The scores
| Criterion | Panel median |
|---|---|
| Records & DPIA depth | 2 of 5 |
| Data subject rights & incidents | 0.5 of 5 |
| Privacy regime coverage | 2.5 of 5 |
| Audit readiness & evidence | 2 of 5 |
| Integrations & automation | 3.5 of 5 |
| European sovereignty | 1 of 5 |
Records & DPIA depth
Show reasoningHide reasoning
How this is scored
The DSMS core: records of processing activities (RoPA/VVT, Art. 30 DSGVO), data protection impact assessments (DSFA, Art. 35), processor and DPA management (AVV), and technical and organisational measures (TOMs) — how deeply the legal artefacts are modelled and connected.
0 — Not a privacy management tool; at most a set of document templates with no structured records.
3 — A structured record of processing activities with templates, and a DPIA questionnaire or checklist.
5 — Records of processing and DPIAs as modules with templates, processors and their DPAs recorded, and TOMs documented and assigned to processing activities.
8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA need derived from the record, reusable templates across companies, and outputs (Art. 30 register, DPIA report) ready for a supervisory authority.
10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client capability for external data protection officers, and the documentation is audit-ready without manual assembly.
The External DPO
The Enterprise Privacy module names DPIAs, records of processing and PII discovery, and the Ironclad sync scans contracts and DPAs, so the core artefacts exist as modules. But we found no public information on TOMs, legal bases tied to processing activities, reusable templates across companies, multi-client capability, or an authority-ready register output — everything rests on one-line marketing claims, which is thin for running thirty mandates from one system of record. 1 2
The In-House Counsel
The Enterprise Privacy module automates DPIAs, RoPAs and PII discovery, a third-party inventory is synced from Okta, and AI scans uploaded contracts and DPAs via Ironclad — the core registers exist as modules. But the captured pages say nothing about TOMs, templates, or a register output I could hand a supervisory authority, so I cannot place this in the upper band. 1 2
The Drafted Generalist
The Enterprise Privacy module is described as automating DPIAs, records of processing and PII discovery for teams that have outgrown spreadsheets, and the Ironclad connection scans contracts and DPAs, so structured records clearly exist. 1 2
The Lead Auditor
The Enterprise Privacy module is documented as automating DPIAs, records of processing and PII discovery, and the third-party risk module with Ironclad scans contracts and DPAs, so the core artefacts exist as modules rather than templates. We found no public information on TOMs documentation, legal-basis linkage or Art. 30-ready register outputs, which is what would make the record audit-defensible rather than just collected. 1
The IT Integrator
The Enterprise Privacy module automates DPIAs, ROPAs and PII discovery, and the Ironclad integration scans contracts and DPAs to extract risk exceptions, so structured records do exist. But nothing captured shows a processor register with DPAs, TOMs assigned to processing activities, or an Article 30 register generated as an authority-ready output — the product is built around design-time launch reviews rather than a standing record of processing. 1
The Skeptic
The legal-records claim rests on a single line — automate DPIAs, ROPAs and PII discovery — backed by a 25-source data catalog and a third-party inventory synced from Okta with DPAs scanned through Ironclad. Nothing captured shows TOMs documented and assigned, legal bases linked into a record, or an authority-ready register produced, so the depth of the legal artefacts is a headline the pages do not detail. 1 2
Data subject rights & incidents
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
The operational half of the DSMS: handling data subject requests within the Art. 12 deadline, a breach register with the 72-hour notification of Art. 33, and deletion concepts that are carried out.
0 — No handling of data subject requests or data breaches in the product.
3 — A log of data subject requests and a register of data breaches, with templates for the responses.
5 — Request workflows with the one-month Art. 12 deadline tracked and reminders, a breach register with the 72-hour clock and a risk assessment per breach, and deletion periods recorded per processing activity.
8 — An intake form or portal for requests with identity verification, deadline escalation, breach severity assessment producing the authority notification, and deletion rules tied to the RoPA with execution tracked.
10 — Rights and incidents as operations: end-to-end request handling an authority audit can walk through, breach workflows that produce the Art. 33 and Art. 34 notifications, and deletion automation with evidence that the deletion happened.
The External DPO not rated — no public information
We found no public information on data subject request handling, the one-month deadline, breach registers, 72-hour notification or deletion concepts in the captured pages. The product speaks to design-time reviews before code is written, not to rights and incidents as operations. 1 2
The In-House Counsel not rated — no public information
We found no public information on data subject request handling, deletion periods, or a breach register with the 72-hour clock on the captured pages. A breach workflow that produces the Art. 33 notification is non-negotiable for me, so this is reported as unproven rather than scored. 1 2
The Drafted Generalist not rated — no public information
We found no public information on data subject request handling, breach notification workflows, or deletion tracking on the two pages captured here — the vendor's home page and its integrations page. 1 2
The Lead Auditor not rated — no public information
We found no public information on data subject request handling, breach registers, the 72-hour notification clock or deletion execution. The pages we read — the vendor homepage and the integrations catalogue — describe launch-time privacy and security review, not rights or incident operations. 1 2
The IT Integrator not rated — no public information
We found no public information on data subject request handling, a breach register, the 72-hour notification, or deletion concepts and their execution — the captured homepage and integrations pages describe launch reviews, DPIA and ROPA automation, and data source scanning only. 1 2
The Skeptic
Every captured workflow happens before code is written — draft PRDs read, documents risk-rated, remediation steps handed to developers — which describes a product-launch review tool. We found no public information on data subject request workflows, a breach register with the 72-hour clock, or deletion tracking. 1
Privacy regime coverage
Show reasoningHide reasoning
How this is scored
Which privacy regimes the product operationalises — DSGVO/GDPR, BDSG, TTDSG/ePrivacy, Swiss nDSG, UK GDPR, EU AI Act privacy duties — and whether one record maps across them or each regime is a fresh island.
0 — No privacy regime built in; a generic task or document tool.
3 — GDPR implemented with its registers, templates and checklists.
5 — GDPR plus the national law of its market (BDSG, nDSG or UK GDPR) named and supported with their own templates or requirements.
8 — Several regimes on one record with requirements mapped across them, newer duties (AI Act, ePrivacy/TTDSG) covered as maintained content, and updates published when a regime changes.
10 — Regime coverage as a living product: many privacy regimes and per-country variants on one data basis, and a documented update cadence when the law moves.
The External DPO
The EU AI Act, US state AI and automated-decision rules are named screening targets assessed alongside internal policy, and the DPIA and records-of-processing vocabulary points at GDPR operationalisation. We found no public information on BDSG, Swiss nDSG, UK GDPR, per-country variants, or a published update cadence when a regime changes — a concern for my German and Swiss clients. 1
The In-House Counsel
The captured pages name DPIAs and RoPAs plus screening against the EU AI Act and US state AI and automated-decision rules, which is more than a single-regime checklist. But no national privacy law variant — BDSG, nDSG, UK GDPR or TTDSG — appears on the captured pages, and nothing shows one record mapped across regimes or updates when a regime changes. 1
The Drafted Generalist
The pages name the EU AI Act plus US state AI and automated-decision rules as screening content, and the DPIA and records-of-processing work sits squarely in GDPR territory. We found no public information on BDSG, nDSG, TTDSG or UK GDPR support, or on one record mapping requirements across regimes, so the German homework would stay on my desk. 1
The Lead Auditor
DPIA and records-of-processing modules put the GDPR artefacts in the product, and AI governance screening explicitly covers the EU AI Act alongside US state AI and automated-decision rules. We found no public information on national variants such as BDSG, Swiss nDSG or UK GDPR, on requirements mapped across regimes on one record, or on an update cadence when a law changes. 1
The IT Integrator
DPIA and ROPA automation implies the GDPR registers, and the AI governance module explicitly screens against the EU AI Act plus US state AI and automated-decision rules as maintained assessment content. We found no public information on BDSG, Swiss nDSG, UK GDPR or ePrivacy coverage, or on one record mapping requirements across regimes. 1
The Skeptic
Screening is named against the EU AI Act, US state AI and automated-decision rules and internal policy, with the DPIA and RoPA modules carrying the GDPR artefacts — several regimes inside one assessment. We found no public information on national variants such as BDSG, Swiss nDSG or UK GDPR, or on maintained legal-update content with a named source. 1
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 the registers, and documents attachable to records.
5 — Versioned records or a change history, report generators for the core registers (RoPA, DPIA, TOMs), and evidence attached per processing activity or measure.
8 — A revision-safe change history, audit evidence packs generated on demand, management and data protection officer reports at a click, and read-only auditor access.
10 — Audit readiness as a standing state: documentation status shown continuously per regime and scope, proof packs an auditor accepts as they are, and any record reproducible as it stood on a given date.
The External DPO
Documents attached to a review are read and risk-rated, GitHub pull requests can be verified against what was approved, drift from the approved state is detected, review history is queryable through the MCP server with revocable permissions, and launch data pushes to Google Sheets for custom reporting. We found no public information on revision-safe change history, read-only auditor access, or report generators producing a client-ready register — the thing I bill hours assembling today. 1 2
The In-House Counsel
What the captured pages show is thin: review history surfaced through the AI agents, an alert when production stops matching what was approved, and launch data pushed to Google Sheets for custom reporting. We found no public information on versioned records, evidence packs, auditor-facing reports or read-only access — for defensibility I need more than a Sheets export. 1 2
The Drafted Generalist
Review history is kept — it can even be surfaced inside Claude and ChatGPT — every document attached to a launch gets risk-rated, and you are told when production drifts from what was approved. We found no public information on register reports, evidence packs, or auditor access, so I cannot see how I would produce proof an authority accepts without assembling it by hand. 1
The Lead Auditor
Review history is exposed through the MCP server into Claude, Gemini, Copilot and ChatGPT, the data catalog flags drift from the approved state, and GitHub links let you check what shipped against what was approved — genuine evidence hooks. We found no public information on revision-safe change history, on-demand evidence packs, read-only auditor access, or reproducing any record as it stood on a given date, and that reproducibility is the test I apply. 1 2
The IT Integrator
Evidence is indirect: launch data and workflow responses push to Google Sheets for custom reporting, the data catalog detects drift from the approved state, GitHub pull requests link to reviews to verify what shipped matches what was approved, and review history is exposed to the assistant tools. We found no public information on revision-safe change history, read-only auditor access, or generated evidence packs. 1 2
The Skeptic
Documents attached to a launch are read and risk-rated, production drift from the approved state is flagged, pull requests can be checked against approvals, and review history is exposed to the AI assistants. We found no public information on versioned records, generated register reports, or read-only auditor access, so defensible proof rests on drift alerts rather than documented evidence packs. 1 2
Integrations & automation
Show reasoningHide reasoning
How this is scored
Whether the platform feeds from the real IT estate — directory import, ticketing, SSO, API — and automates the recurring privacy work 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), and recurring tasks with reminders and assignment.
8 — A documented REST API for the core objects, a named connector set (directory, ticketing, HR or asset sources), webhooks, SSO with SCIM provisioning, workflow automation with delegation and escalation, and AI assistance with human review.
10 — The platform behaves like infrastructure: API coverage of the whole data model, events or webhooks for every object, two-way sync with the estate, and recurring work (reviews, attestations, evidence collection) automated and documented.
The External DPO
This is the platform's centre of gravity: automated schema discovery across Snowflake, BigQuery, Databricks, Postgres and roughly twenty other sources, a client agent scanning AWS datastores inside the customer's own VPC, bi-directional Jira, Slack, Ironclad, Zip and Okta syncs, SAML single sign-on across major identity providers, and AI that pre-populates intake questionnaires. We found no public information on a documented REST API, webhooks or SCIM provisioning, which keeps it off the top band. 1 2
The In-House Counsel
This is the strongest area: bi-directional Jira and Ironclad syncs, a client agent scanning AWS datastores inside the customer's own VPC, live schema capture from a wide set of data sources, SAML SSO across the major identity providers, and AI that pre-populates intakes alongside human review. We found no public information on a documented REST API for core objects, webhooks or SCIM provisioning, which keeps it below the top band. 1 2
The Drafted Generalist
The breadth here is real and documented: 25-plus named data sources from Snowflake to Postgres, bi-directional Jira, Slack and Ironclad sync, SAML single sign-on through Okta, Entra and OneLogin, an agent that scans AWS datastores from inside your own cloud, and AI assistants reached through a permissioned server an administrator can revoke. 1 2
The Lead Auditor
Twenty-five-plus named connectors across data warehouses, databases, Kafka and ML platforms, bi-directional sync with Jira and Ironclad, SAML SSO across five identity providers, an in-VPC AWS scan agent, and agentic AI behind configurable, revocable permissions — this platform feeds from the real estate rather than re-typing. We found no public information on a documented REST API for core objects, SCIM provisioning or a general webhook framework, which is what separates this band from infrastructure grade. 1 2
The IT Integrator
This is where the product earns its keep from my seat: bi-directional Jira sync with AI-prefilled intake, launches from Confluence, Notion and Google Docs, Okta vendor-application sync, SAML SSO through Microsoft Entra, JumpCloud, OneLogin and AWS SSO, twenty-plus live data-source connectors from Snowflake to Postgres, and a Kubernetes agent scanning AWS datastores without credentials leaving the VPC. The MCP server on a configurable, revocable dedicated API user is a real automation surface, but we found no public information on a documented REST API, webhooks or SCIM provisioning, which keeps it short of the top of this scale. 1 2
The Skeptic
This is the strongest page: a catalog of 40-plus connectors spanning data stores (Snowflake, BigQuery, Postgres, an AWS scanning agent that never leaves your VPC), SAML single sign-on across identity providers, bi-directional ticketing and docs syncs, and AI assistants reached through an MCP server whose permissions an administrator can revoke. We found no public information on a documented REST API, webhooks, or SCIM user provisioning. 1 2
European sovereignty
panel opinion
n/r
n/r
Show reasoningHide reasoning
How this is scored
Where the compliance record 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. A platform that maps your processing is itself your most concentrated processing. 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 External DPO
The only proven dimension is a published subprocessors page. We found no public information on the contracting entity's location, hosting region, a data processing agreement, or which of the many AI and data-source integrations touch customer content — for a platform that maps a client's entire processing, that gap is decisive, and the picture reads as unknown rather than European. 2
The In-House Counsel not rated — no public information
No sovereignty attributes are on record: we found no public information on the contracting entity's jurisdiction, hosting location, subprocessor chain or a data processing agreement. The captured pages show only that a page titled Subprocessors exists — a platform that maps my processing must itself be jurisdictionally clean, and here nothing is proven. 1 2
The Drafted Generalist not rated — no public information
We found no public information on the contracting entity's jurisdiction, hosting location, or a data processing agreement — the captured pages carry no sovereignty details beyond a link to a subprocessors page whose contents were not captured. Nothing here lets me say where my compliance record would actually live or under whose law. 1 2
The Lead Auditor
The only proven fact is that a subprocessors page exists on the vendor's site; its contents, the contracting entity, hosting location and any data processing agreement are unknown from the captured pages. As an auditor I cannot say under whose law this record of a company's processing would actually sit. 2
The IT Integrator
All that is confirmed is that a subprocessors page exists; we found no public information on hosting location, the contracting chain, a data processing agreement, or which subprocessors touch customer content. Nothing here is proven non-European — it is simply unknown, and a platform that maps your processing should be expected to state it. 2
The Skeptic
The only disclosure the captured pages confirm is a page titled Subprocessors; nothing states where the compliance record is hosted, under which entity the customer contracts, or whether a data processing agreement is published. Hosting, subprocessor detail and contractual basis are all open questions on this evidence. 2
Pricing transparency
not rated — the vendor publishes no price
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 entity counts 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 10-client consultancy is a two-minute exercise.
The External DPO
A pricing page is confirmed in the footer navigation, but the captured pages show no prices, editions, modules, user or entity boundaries, or a software-versus-consulting split. For a ten-client consultancy the real invoice is not computable from anything public. 1
The In-House Counsel
The homepage navigation lists a Pricing page, but the captured pages state no figures, editions, billing terms or whether consulting is unbundled. A buyer cannot compute an invoice from what we captured, and I record only that the page exists. 1
The Drafted Generalist
A Pricing page is listed in the footer navigation, but no price, edition, billing period or setup fee appears anywhere on the captured pages. From what is public here, I cannot begin to compute the invoice for an 80-employee firm — I would have to call sales. 1
The Lead Auditor
A pricing page is listed in the site navigation, so pricing is not entirely a sales conversation, but we found no public price figures, editions, billing periods or separation of software from consulting anywhere in the captured pages. A buyer cannot compute an invoice from what we read. 1
The IT Integrator
A pricing page is listed in the site footer, but no prices, editions, billing periods, user or entity boundaries, or setup fees were captured on any page we read, so a buyer cannot compute even a rough invoice from public information. 1
The Skeptic
A Pricing link appears in the footer navigation, and that is the whole of the pricing evidence: no figure, edition, module price, billing period, or consulting boundary appears on the pages we captured. A buyer cannot compute any invoice from this. 1
Questions about TerraTrue
Is TerraTrue European?
Not determined: the vendor’s pages as captured do not say where TerraTrue is based.
Where does TerraTrue store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does TerraTrue have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to TerraTrue?
As of 4 Nov 2026, the panel rates preeco | datenschutz (4/5), Dastra (3.5/5) and caralegal (3.5/5) highest among the other 43 Data Protection 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 | datenschutz (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: TerraTrue alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- 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.
- We found no public information on compliance on the pages we read (terratrue.com, terratruehq.com/integrations). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
Sources (2)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page terratrue.com Checked 3 Nov 2026 Details →
- 2 Integrations & automation — found from sitemap terratruehq.com Checked 3 Nov 2026 Details →