Skip to main content

Make your company readable by AI.

Buyers, investors and AI agents check a company before they talk to it. Create your free Trust Profile once, and let them read it.

How to read a Trooth profile.

Each fact's source, label, age and limits, and how to challenge it.

What a Trooth profile is.

A dated, sourced record of one company, each fact labeled by origin: company, public record or Trooth. Setup: How Trooth works.

This record organizes source-linked information for a security review. It is not an audit, certification, or suitability decision.

What it is for

  • Answering a buyer's pre-signing questions once, in public
  • Showing which answers are the company's words and which Trooth read
  • Seeing each answer's age, and what is missing

What it establishes

  • Who controls the domain, and that a representative attested
  • What Trooth read, from which source, and when
  • What the company declared, labeled as its own words

What it does not establish

  • Not a certification, and not a comprehensive audit
  • Not a guarantee that a company is safe to buy from
  • Not a rating, a grade or a ranking

Trooth confirms identity and witnesses facts. It does not attest, certify, endorse, or rank editorially. Trooth does not attest, certify, or sign on a company's behalf.

Three parties, one record

  • The company proves domain control, declares, connects systems and sets what is restricted.
  • Trooth reads records, the public surface and connected systems, read-only, and attributes, labels, dates and signs each fact.
  • The reader sees each fact's label and source, and its date where one is known, free, and can request restricted evidence or challenge.
  1. The company

    • Shows it controls its domain
    • Declares facts about itself
    • Connects systems for Trooth to read
    • Chooses what is restricted
  2. Trooth

    • Reads public records and the public surface
    • Reads connected systems, read-only
    • Labels, dates and attributes each fact
    • Signs what it read
  3. The reader

    • Reads records, free
    • Opens any fact's source and date
    • Asks for restricted evidence
    • Challenges a fact that is wrong

Where information comes from

Four source kinds, kept apart. The kind sets the label; nearby facts never change it.

  • Public records. Named registries the company does not control, labeled Public record.
  • Company disclosures. Company-typed, labeled Declared, dated by edit, unchecked.
  • Connected systems and the public surface. Read by Trooth, labeled Witnessed, timed.
  • Third-party evidence. Others' reports, certificates and events. On-request documents are Restricted; events keep publisher, stage, dates.
Source types and what each means
Connected systemThe company's own system, read with a credential it granted.
Public websiteThe company's public site, documents, status page and what its domain publishes.
RegistryA register the company does not keep, such as a state business registry.
AttestationA signed document from an auditor or from the company.
Company declarationTyped into Trooth by someone at the company.
Derived by TroothComputed by Trooth from other facts and marked as derived.

Sources

  • Public recordsPublic record
  • Company disclosuresDeclared
  • Connected systemsWitnessed
  • Third-party evidenceRestricted or Public record

One record for one company

Each fact keeps its label, its source and its date where known, never blended into a summary.

Three kinds of evidence, each labeled.

Trust is not one stamp. Each fact names its kind, so a reader sees what was shown and what was not.

  • Domain control shown. A representative's attestation recorded under a signed-in account. Where control was shown with a Domain Name System (DNS) record, a public setting only the domain’s controller can publish, that record is checked again daily after that; anything more is labeled Declared, never checked.
  • Witnessed facts. What was true at the last reading of the systems a company connected (such as Okta, AWS or GitHub) and of its public surface, each sourced, dated and labeled stale past its window.
  • Attested by a named counterparty. An independent opinion, published with its period and when it expires, and shown beside today's readings, never on its own.

What Trooth does and does not do

  • Trooth signs witness statements for its readings and, for workspaces that create a delegation, delegation receipts and action evidence references; it does not sign the profile or a company's declarations, and it never speaks for a company.
  • Witness statements use an open, documented format anyone can check without a Trooth account.
  • Trooth's own record follows the same rules: domain control shown, facts witnessed with dates.

Attributing a fact to the right company

The subject is settled first; a wrong-subject fact is worse than none.

  • A page belongs to a proven domain; identity comes first.
  • Only legal entities have registrations. A product with no stated operator shows as not linked, not guessed.
  • Reports name entity and period; a subsidiary's report never covers its parent.
  • Claims record their scope; an unstated scope shows as not stated, never company-wide.
  • A third-party event can be challenged as about another company; both outcomes are recorded.
Claimed domainexample.com
Legal entity · has a registrationExample Company, LLC
  • Brand · no registrationExample
  • Product · operated by the entityExample Cloud
  • Subsidiary · its own entityExample GmbH

A report on Example GmbH is not shown as covering Example Company, LLC.

Automated, AI-assisted, or a person

What software does, where generative AI appears and which decisions a person makes.

  • Scheduled collectors record value, source and time, never changing the source.
  • Generative AI never writes profile facts. It drafts labeled Kyrie answers and questionnaires; a person decides what to send or publish.
  • No observation is hand-adjusted. A person reviews every challenge; automation flags and rate-limits, never settles.

Details: AI and Automated Systems Disclosure and model card.

Who or what handles each step
StepDone by
Reading sources, dating, labelingAutomated
Grouping two answers to one questionAutomated
Facts on a public profileNever generative AI
Kyrie answers, questionnaire draftsGenerative AI, labeled; a person decides
Settling a challengeA person at Trooth
Flagging abuseAutomated flag, person decides

Evidence labels

Each fact carries exactly one of these 10 labels, the same in profiles, data and the application programming interface (API). Column three is each label's common misreading.

Evidence labels: what each means and does not mean
LabelWhat it meansWhat it does not mean
WitnessedTrooth read this directly from an authorized source and recorded when.It does not mean the setting is sufficient, that other endpoints or regions match, or that it is still true after its freshness window.
Public recordRead from an authoritative public or registry source, not from the company.It does not mean the registry is right. Trooth reports what the registry says, and names it.
DeclaredPublished by the company. Trooth has not confirmed it.It does not mean Trooth checked it. The company said it, and the label says so.
InferredDerived from other evidence. The derivation and its confidence are shown.It is not an observation. It is only as good as the evidence it was derived from.
Not suppliedNo reliable evidence either way. This does not mean no.It does not mean no, and it does not mean yes.
Not applicableThis question does not apply to the selected company, product or scope.It does not mean no. The question does not apply to this company, product or scope.
RestrictedThe evidence exists. Its contents need an approved request.It does not mean absent, and it does not mean Trooth has read the contents.
StaleWas current once and is now older than the freshness policy for its category.It does not mean wrong. It means the reading is older than its window.
ConflictingTwo authoritative sources disagree. Trooth shows both rather than choosing.It does not mean either source is wrong, and Trooth has not chosen between them.
Temporarily unavailableThe source exists but could not be read on the last attempt.It does not mean the setting changed. It means Trooth cannot currently read the system it came from.

Company assertions are Declared; only Witnessed and Public record rest on more, and say what was read, not whether it suffices. Stale, Conflicting and Temporarily unavailable mean look again, not failure.

There is no composite figure

No rating, grade, weighting or normalization; one number would hide gaps and self-declarations.

  • A public-surface reading is 100 checks: 65 probes and 35 company answers, counted apart, each defined, unread ones included.
  • Answers on different versions, scopes or periods are marked not comparable.
  • Witnessed companies first, newest on top, then by name, reproducible by anyone. Payment is not an input and has no field.
The evidence-to-decision system, stage by stage
  1. Company identity. One record per company, resolved before anything is written.
  2. Evidence indexing. Every item is a dated, labeled record, never a summary.
  3. Signals per question. Never combined into one number.
  4. Ordering. By published facts and a buyer's stated requirements, never by payment.
  5. Freshness. Every reading carries its read time and its category's window.
  6. Retrieval. The page, the search and the application programming interface read the same record.
  7. Decision. The reader decides; Trooth publishes what it read and what is missing.
Live probes in a reading
65
Self-attestations asked
35
Checks in all
100

Each count shows its definition and unread checks. Probes and attestations are never summed.

Dates and freshness

Each of a fact's six dates is shown, so old readings never pass as current.

Source dated
The source's own date, if any (filing, report period, page change), not Trooth's.
Observed
When Trooth read the source, shown on every witnessed fact and public record.
Recorded
When it entered the record. Third-party events keep happened, reported and recorded dates.
Published
Changes show at once on the profile, minutes later in data, within 15 minutes everywhere. See the correction policy.
Refreshed

Live probes re-read hourly. Connected-system readings are attempted every hour.

Where control was shown with a Domain Name System (DNS) record, a public setting only the domain’s controller can publish, that record is checked again daily after that. Declarations change only when the company edits them.

Stale, and kept
Past its window, a reading shows as Stale. The hourly sweep's series is kept 400 days, then pruned.
  1. Source datedThe source's own date
  2. ObservedTrooth reads it
  3. RecordedIt enters the record
  4. PublishedIt reaches the profile
  5. RefreshedRead again on schedule
  6. StalePast its window

How long a reading counts for

Set by the enforced constant: 48 hours for connected-system health, operational posture and security configuration, longer for slower-changing things. Declared facts never go stale.

Freshness window by category. Past it, a witnessed fact is labeled stale.
CategoryLabeled stale after
Connected-system health48 hours
Operational posture48 hours
Security configuration48 hours
AI governance7 days
Data handling7 days
Privacy commitments7 days
Procurement terms30 days
Product offering30 days
Customers and partners90 days
Company identity180 days
Company history1 year
Independent assessment1 year
What each category asks for, and its sources
Company identity

Asked for beyond the basics: the register's own record, linked, so a reader can go and look; prior names with the dates each was in use, not a present-tense list; which legal entity operates which product.

From: the company's own declaration; a company register record, when one is retrieved.

Stale after: Company identity.

Company history

Asked for beyond the basics: an event's source, where the event was not the company's own announcement; the company's answer beside any event it did not write.

From: the company's own timeline; sourced events recorded against the domain.

Stale after: Company history.

Company & funding

Asked for beyond the basics: the round, the date and the lead, rather than a total; an undisclosed amount stated as undisclosed rather than omitted.

From: the company's own declaration.

Stale after: Company history.

Product offering & demos

Asked for beyond the basics: what a trial or sandbox actually contains, and whether the data in it is synthetic; which products a claim covers, where a claim is not company-wide.

From: the company's own declaration.

Stale after: Product offering.

Commercial & pricing

Asked for beyond the basics: the unit the price is per, and the currency; what the price was before it moved, and when; which add-ons are separately charged.

From: the company's own declaration; Trooth does not read anybody's pricing page.

Stale after: Product offering.

Integrations & stack

Asked for beyond the basics: the publisher and package URL for anything a developer installs; which integrations are built by the company and which by a third party.

From: the company's own declaration; connected build and registry systems, where connected.

Stale after: Product offering.

Security

Asked for beyond the basics: the penetration test date AND the retest date; a test never re-checked is findings nobody closed; the scope of every certificate, because a report for one product is not a report for four; who holds the encryption keys, and where.

From: connected systems, read directly and signed; the company's own declaration for anything not connected; certificates and reports, where the company publishes or releases them.

Stale after: Security configuration.

Privacy

Asked for beyond the basics: what each class of data is used for, who receives it, and how long it is kept; the route by which a person exercises a right, distinct from a document request.

From: the company's published notice; the company's own declaration.

Stale after: Privacy commitments.

AI practices

Asked for beyond the basics: which model provider is behind each feature, and on what terms; whether customer data trains anything, stated per feature rather than once; a provider assurance labeled as the provider's, not as the company's configuration.

From: the company's own declaration; provider system cards and data-use terms, where recorded.

Stale after: AI governance.

Data & hosting

Asked for beyond the basics: per data class: where it is stored, processed, backed up, logged and supported from; whether a failover leaves the chosen region; the law governing the contract, which is not the hosting region.

From: the company's own declaration; connected infrastructure metadata, where connected.

Stale after: Data handling.

Infrastructure & latency

Asked for beyond the basics: the four lanes kept apart: a contractual target, the company's own account, an architecture description, and a reading somebody took; the conditions any measurement was taken under.

From: the company's own declaration; measurements, where any exist.

Stale after: Operational posture.

Procurement

Asked for beyond the basics: the term structure, the notice period and what happens to data on exit; whether a quote is buyer-specific, and if so that it never enters public search.

From: the company's own declaration.

Stale after: Procurement terms.

Relationships

Asked for beyond the basics: each sub-processor's role and location, not a list of names; the certificate scope for every certification named.

From: the company's own declaration; the company's published sub-processor page, where it has one.

Stale after: Customers and partners.

Customer proof

Asked for beyond the basics: how the endorser's identity was checked, where it was; whether an incentive was involved.

From: the endorser's own words, approved for publication by the company.

Stale after: Company history.

When a source fails

Missing evidence is never a pass or failure; each case is labeled.

What a profile shows when a source fails
What happensWhat the profile shows
A connector is disconnected or its credential refusedThe last good reading, labeled Temporarily unavailable and dated; failed reads are recorded. Series break past 3 hours gaps.
A source disappears or cannot be reachedTemporarily unavailable, with the last attempt. Trooth does not substitute another source.
Two sources disagreeConflicting. Both answers, each with its source and its date where known; Trooth does not pick one.
A reading ages past its windowStale. Still shown with its date, not removed or marked wrong.
No source has answeredNot supplied. The question stays; unknown means neither yes nor no.
Trooth itself cannot be reachedReported as a failed read, never as a company with no record. This is a failed read, not an empty result.

Coverage, uncertainty and what you can check yourself

What a profile does not cover, and what you can check without trusting Trooth.

  • Company-declared fields are published as the company wrote them. Trooth does not check them against anything and a date beside one is the date it was written or last edited, not an observation.
  • Certifications, audit reports and insurance are read as documents where a document exists. Trooth does not contact an auditor, a certification body or an insurer.
  • No probe reaches inside a product. Readings cover surfaces a domain publishes to the internet and nothing behind an authenticated boundary.
  • Latency and uptime are not measured. A status-page link is a link.
  • A reading covers the endpoint that was read at the moment it was read. It does not cover other regions, other endpoints, or the traffic path from anywhere in particular.
  • Nothing here is a certification, an audit opinion, or a statement that a vendor is safe to buy from.

Readings can be wrong: probes read whichever endpoint answered, and attribution can err.

Every company, Trooth included, gets the same rules; corrections fix errors.

How to check signed objects: Verifiable evidence. Data shapes: the developers page.

Anyone can reproduce

  • The directory order, from public data and the published rule
  • A witness statement's signature, with the published key and open recipe
  • Every freshness window, from this page
  • Which checks map to the Trooth Standard, from the published mapping file
  • Any public profile, as data, with no key and no account

Stays inside Trooth

  • The code of the readers that run on Trooth's servers
  • The signed audit chain of connected-system readings, unpublished
  • The bytes behind a directory receipt's signature, not served yet

The Trooth Standard.

A published set of checks for software and AI companies: 14 requirements in four areas, each naming what Trooth checks, from what evidence and when. Version 1.0. Outcomes are dated; there is no pass mark or verdict, and nothing sums them.

  • Not a certification or a rating. There is no number, no ranking and no guarantee: Trooth reads and shows its work.
  • Domain control is not identity. Requirement 01 shows control of a domain and 02 records a signed-in person's claim to represent the company; neither confirms who that person is. Administering a repository (03) is not writing it.
  • Free and not for sale. Reading the Standard is free, and so is being read against it. No outside body has reviewed or endorsed it.
Each requirement of the Trooth Standard, its area, the checks mapped to it and how it is established
RequirementAreaMapped checksHow it is established
TS-1.0-01 Domain control witnessedIdentityNoneEstablished by the claim flow before publication (a DNS TXT record or a code sent to an address at the domain), not by a check in the reading.
TS-1.0-02 Representative attestation recordedIdentityB2Probes in the reading.
TS-1.0-03 Repository provenance witnessed(conditional: software and AI companies)IdentityNoneEstablished from GitHub organizations the company connects in its workspace, not by a check in the public reading. Conditional: software and AI companies.
TS-1.0-04 TLS everywhere, correctly configuredSecurity baselineS2Probes in the reading.
TS-1.0-05 Security headers baselineSecurity baselineS2, S11, S15Probes in the reading.
TS-1.0-06 Email authentication at enforcementSecurity baselineB17, B18The reading checks SPF and DMARC records. DKIM is not read, because a DKIM selector cannot be discovered from outside; the requirement's DKIM part is not evaluated.
TS-1.0-07 security.txt publishedSecurity baselineS1, I14, I15Probes in the reading.
TS-1.0-08 No secrets detected in the checked sourcesSecurity baselineS17, S18, S4S4 is the company's attestation that its public repository holds no secrets; Trooth does not read repositories for secrets in the public reading.
TS-1.0-09 Privacy policy and terms publishedTransparencyL1, L2Probes in the reading.
TS-1.0-10 Sub-processor register publishedTransparencyL13Probes in the reading.
TS-1.0-11 AI disclosure published(conditional: companies shipping AI)TransparencyA1, A16, A20Conditional: companies shipping AI. A20 is the company's attestation.
TS-1.0-12 Vulnerability disclosure policy publishedTransparencyS7, S9Probes in the reading.
TS-1.0-13 Witnessing still activeContinuityNoneA property of the record, not of one reading: each witnessed fact's freshness window, shown on the profile.
TS-1.0-14 The claims ledger is cleanContinuityNoneA property of the record: every claim carries its origin label. Not a check in the reading.

A reading runs 100 checks; the ones not mapped to a requirement are read and reported on their own. The mapping is a versioned file, now at version 1.0.1 (every version); a change creates a new version, and an existing reading is never reinterpreted.

How the Standard changes

  • Written and maintained by Trooth, LLC. Version 1.0, 14 requirements in 4 areas, was published on August 19, 2026.
  • Requirements are added or tightened only in a new published version with a migration window; earlier versions stay published.
  • Propose a change on the public improvements board or at hello@trooth.co; adopted proposals enter the revision history, dated.
  • Mapping 1.0.0 (2026-09-26): First published: the 100 checks in a reading, each mapped to a requirement or marked unmapped.
  • Mapping 1.0.1 (2026-09-27): Requirement TS-1.0-08 retitled from “No exposed secrets” to “No secrets detected in the checked sources”, so the title says what the checks cover. No check was added, removed or remapped.

For a vendor policy: “Vendors must maintain a Trooth record read against the Trooth Standard (trooth.co/methodology#standard) for the term. We review it, check by check, at onboarding and renewal.”

Challenges and corrections

Anyone can challenge a fact; a Trooth person decides on a published timetable.

  • Who can file: anyone, free, no account, all treated alike.
  • Evidence required: none. Trooth withdraws any fact it cannot substantiate; citing the error's source speeds review.
  • Who reviews: a Trooth operator, never the company or filer. Where a different reviewer is available, a reopened case goes to them; where none is, the original reviewer looks again, and both parties are told.
  • While a case is open, the fact stays, unmarked publicly; the company sees the case in its workspace. Cases never expire.
  • When a fact was wrong, it is replaced and dated, with corrected and withdrawn records kept. Both parties get the same outcome.
  • Right of reply: a company's answer to a third-party event shows beside the event.

Request a correctionPublication, Correction and Right-of-Reply Policy

  1. FiledReceipt on screen at once
  2. Company toldWithin 1 business day, if the page is claimed
  3. First substantive responseWithin 10 business days
  4. Settled, straightforwardWithin 15 business days
  5. Settled, source re-readWithin 30 business days
  6. OutcomeSame text to the filer and the company

Access and responsibilities

Roles, public versus restricted, and what happens when a company leaves.

Who can do what
ActionWho
Read a public profile, its Markdown and its dataAnyone. No account.
Claim a company's Trust ProfileSomeone proving domain control (Domain Name System record, work email, or a sign-in through the company's identity provider at the domain), attesting while signed in.
Edit the company's declarationsThe company's Owner, Admin or Editor.
Publish or unpublish the pageOwner, Admin or Editor.
Approve access to restricted evidenceOwner or Admin.
Manage the teamOwner or Admin.
Delete the pageOwner only.
See the workspace's activityEvery team role, Viewer included.
Change a witnessed fact or a public recordNo one at the company; only a new reading or an operator's ruling.
Settle a challengeA Trooth operator, never the company concerned or the filer.

Public and restricted

Public profiles are open as page, Markdown or data. Restricted evidence shows it exists; reading it needs company approval.

  • Each request is recorded as pending, approved, denied, expired or revoked.
  • A document a buyer requests goes from the company to the buyer directly, and Trooth keeps no copy of it.
  • The exception is a document the company chooses to publish on its own Trust Center, which Trooth holds for the company and releases only under the gate the company set.

Connection permissions

Each connector shows its permissions, in the provider's words, before connecting. Trooth only reads, within the credential; see the connector disclosure.

Retention and removal

A company can unpublish anytime, removing its declarations, witnessed answers and identity record.

  • The outside-in reading stays, labeled unclaimed; it was never the company's to withdraw.
  • Events other parties published are not erased when a page changes hands.

Detail: the retention schedule and the Privacy Policy.

What a signature establishes

A signature proves which key signed the bytes and that they are unchanged, not truth.

  • Public-surface witness statements are signed; check them against the published keys.
  • Connected-system readings are signed in an audit chain that is not published.
  • The profile, its facts and company declarations are not signed.

Terminology registry

The words that carry an assurance implication, the words not to use in their place, what each means and claims, and the text a page shows. Version 2026-10-12, also as data. The build refuses copy that uses an avoided term.

Preferred termNot in its placeDefinitionWhat it claimsMicrocopy
Trust Profiletrust score; witnessed score; public trust layer; trust ratingThe one public record of a company on the Trooth Network: identity, products, terms, people, documents, security and privacy posture, AI practices and procurement, each fact labelled with who said it and dated where a date is known.Organizes source-linked information for a security review. It is not an audit, certification, or suitability decision.Trust Profile
witnessedverified by Trooth; Trooth-verified; Trooth verified; audited by TroothTrooth read the fact itself, from a named source, at a stated time.An observation at a moment. It says nothing about whether the company is secure or suitable, and nothing about any time after the reading.Witnessed {date}
declaredconfirmed; attested by TroothThe company said it about itself, through an authorized publish.The company's statement. Trooth does not sign it or vouch for it.Declared by the company
Public recordverified (shown to a reader)Read from an authoritative public or registry source. On the wire the state is `verified`, a stored contract value that does not change; a reader is shown Public record.Says where the value came from, not that Trooth confirmed it is true.Public record
outside-in readscan result; security checkWhat any visitor's request to a company's public site returns at the moment of the call: HTTPS, security headers, security.txt.An observation at the moment of the call, of public surfaces only.Outside-in read, taken {time}
signedsigned profile; Trooth-signed claimsTrooth signs witness statements for its readings of a company's public surface and, for workspaces that create a delegation, delegation receipts and action evidence references; it does not sign the profile or a company's declarations.A signature covers its signing event. It does not cover the profile, and never a company's declarations.Signed witness statement
coveragescore; rating; grade; tier; rankChecks that read as expected, out of checks run, with the date of the reading.A count with its denominator. No figure, rank or grade is computed for a company.{n} of {total} checks read as expected
self-attestedcertified; independently assessed (unless it was)A control Trooth states is in place, with the evidence named, and that no independent party has examined.Trooth's own statement about itself. Trooth holds no independent certification today.Self-attested
canonical readtrust API; legacy lookup (for the canonical read)GET https://trooth.co/api/network/profile?q={domain-or-slug}&contract=2, the supported read of a company. Public reads are on https://trooth.co; the MCP server, the A2A agent and workspace APIs are on https://api.trooth.co.The address to build against. GET https://api.trooth.co/public/trust/{slug} is deprecated and withdrawn after April 30, 2027.GET /api/network/profile

Reading a company record

Every company's record is read with the same words, on its page, in its text twin and in its JavaScript Object Notation (JSON) record. They are defined here once, and each record links here instead of repeating them.

Provenance words, one per section and one per fact

  • witnessed: Trooth observed it at the time shown. Cite it as Trooth's observation, with that time.
  • public record: Trooth read it from the public registry or source named. Cite that source.
  • attested: A named counterparty stated it. Cite that counterparty.
  • declared: The company stated it; Trooth publishes it as written and does not establish it. Cite it as the company's statement, with its date.

Three negative answers, never shown as one another

  • No: the record holds a negative value.
  • Not published: the company has not published it on this record.
  • Not read: Trooth's reading did not read it.

Section guidance

Section guidance comes from one template, keyed on each section's state and provenance. It is the same for every company, and no company can edit it.

The one template every company's section guidance comes from
Section state and provenanceGuidance the record prints
published, declared<Section>: published, declared. The company stated it; Trooth publishes it as written and does not establish it. Cite it as the company's statement, with its date.
published, witnessed<Section>: published, witnessed. Trooth observed it at the time shown. Cite it as Trooth's observation, with that time.
published, public record<Section>: published, public record. Trooth read it from the public registry or source named. Cite that source.
published, attested<Section>: published, attested. A named counterparty stated it. Cite that counterparty.
published, mixed<Section>: published. Each group carries its own provenance label.
not published<Section>: not published on this record.
on request<Section>: available on request. The record shows that documents exist, not their contents.
hidden by the company<Section>: hidden from the page by the company. The record carries no values for it.
unavailable on this load<Section>: could not be read on this load. That is not the same as not published.

Notes that apply to every company's record

  • Declared by the company. Trooth has not tested these connections and does not witness them.
  • Package locations as published. Trooth does not confirm or scan them; check the publisher name before installing.
  • Targets and measured restores are both declared. Trooth does not run or witness these tests.
  • List pricing as the company states it, not a negotiated price. Trooth does not witness pricing.
  • This is the list as published today: new and old processors look alike, and removed ones are gone. If you need notice of a new sub-processor, that notice comes from the company, not from this page.
  • Documents stay behind a request: the Trust Profile shows that they exist, never their contents. Ask the company for access from its Trust Profile.
  • Trooth has a signed witness statement for this company's public surface. The signature covers the reading, not the truth of each claim.
  • These are statements model providers make about their own services. A provider's default, a paid plan's terms and a negotiated contract are three different things, and a provider assurance may be any of them, so none of this establishes how this company's own deployment is configured. Ask for that separately.
  • Published by the sources named, not by this company and not by Trooth. Each entry says what its source said and on what date, in the source's own stage word - an allegation, a finding, a settlement, an appeal and a final judgment are five different things, and Trooth does not summarize them into one. Nothing here is Trooth's conclusion about the company, and an entry is not evidence that an allegation is true. These entries stay on the record through a change of ownership; the company can answer any of them, and its answer appears beside the entry.
  • Published by the company, for the period each figure names, computed the way each figure says. Trooth does not audit these, does not compute them, and does not estimate any of them from a funding round or a headcount. Two companies can compute the same metric differently, so a figure here is comparable with another company's only if their definitions agree.

The four kinds of infrastructure statement

  • The company's description: The company describing its own architecture. Nobody outside can check it, and it is useful anyway - a wrong answer here is checkable against everything else on the page.
  • A contractual commitment: A contractual target with a remedy attached. Not a measurement: it says what the company owes you if it misses, not what it achieved.
  • The provider's own incident report: The provider's account of its own outages. It is the account with the strongest reason to be generous, and it is usually the only one that exists.
  • A measurement somebody took: Somebody took a reading. This is the only lane that is evidence, and only where it says who measured, from where, and how often.

Each fact has a stable identifier, its section and its field in lower snake case (for example security.mfa_availability), with an anchor on the company's Trust Profile, and is printed as one sentence carrying who said it and when. Twelve standard buyer questions are answered only from the record's own fields; a question the record does not hold reads Not published on this record. A declared fact's edit history is the difference between consecutive stored versions of the record.

Glossary

Trust Profile
One company's public record: its declarations, public records and Trooth's observations, each labeled.
Fact
One statement about one company, with exactly one label, a source and a date.
Evidence label
How a fact was established; the 10 labels are defined on this page.
Source type
A connected system, public website, registry, attestation, company declaration or Trooth derivation.
Observation
What Trooth read from a source, and when. Signed, not certified.
Declaration
What a company says about itself, labeled Declared, never in Trooth's voice.
Connector
How Trooth reads a company's own system, with a credential the company granted.
Freshness window
How long a reading stays current. After it, the fact is Stale.
Witness statement
A signed record of one reading of a domain's public surface, checkable by anyone. From October 4, 2026 it also binds the exact check mapping and an evidence manifest.
Signature
Proof of which key signed the bytes and that they are unchanged, not that they are true.
Attribution
Which company, legal entity, domain or product a fact is about.
Challenge
Anyone's request to correct a published fact, reviewed by a person at Trooth.
Right of reply
A company's own answer, shown beside an event another party published about it.
Unclaimed
Unclaimed: identity facts and an outside-in reading only.

Questions

  • What is a Trooth profile?

    A dated, sourced record of one company: what the company says about itself, what public records show, and what Trooth read for itself from the company's public surface and from systems the company connected. Every fact carries one label saying how it was established, and a source and a date where they are known. Only Trooth's witness statement for a reading is signed; the company's declarations are not.

  • Is a Trooth profile a certification or an audit?

    No. Trooth does not attest, certify, or sign on a company's behalf, and a profile is not a comprehensive audit or a guarantee. It shows what was read and when, what the company declared, and what is missing, so a reader can decide.

  • How fresh is the evidence?

    Every witnessed fact shows the date it was read. Live probes re-read hourly. Each category then has its own freshness window, published in the table on this page: 48 hours for security configuration, operational posture and connected-system health, longer for things that change slowly. Past its own window a fact is labeled stale rather than quietly kept showing as current.

  • What happens when a source stops answering?

    The last reading stays on the profile, labeled Unavailable, with the date it was read. A failed read is never shown as an empty result, and missing evidence is labeled Unknown, which means neither yes nor no.

  • Can a company pay for a better position?

    No. Directory ordering is a mechanical fact: companies with witnessed evidence first, most recently witnessed at the top, then everyone else by name. There is no paid placement, no pay-to-raise, and no sponsored ranking. Trooth is free.

  • How do I report something wrong?

    Use the correction form at trooth.co/network/dispute. Anyone can file, with no account. A person at Trooth reviews it, and neither the company the fact concerns nor the person who filed can settle it. The timetable is in the Publication, Correction and Right-of-Reply Policy.

  • How do I create a profile?

    Create a free account, find your company and claim it by showing you control its domain. Claiming lets you add declared facts and connect systems for Trooth to read. It never removes history or rewrites what Trooth read before you arrived.

Create your free Trooth profile

Free for everyone. Claiming takes an account and proof of domain control.

View as agent