Trust Center and Security pages
Dedicated trust portals, security overviews, report request flows, and customer assurance pages.
Public evidence directory
Trust Signal Directory
Track public trust and compliance evidence surfaces across SaaS and AI vendors.
The directory tracks public evidence surfaces such as Trust Centers, Security pages, Privacy policies, DPAs, Subprocessor pages, SOC 2 and ISO statements, AI data usage pages, enterprise security features, and compliance-related hiring signals.
A public evidence project by CodeYourCompliance, focused on reviewable trust, security, privacy, compliance, and enterprise-readiness signals.
Coverage
What this directory tracks
The public alpha focuses on reviewable evidence surfaces that often reflect trust, security, privacy, compliance, and enterprise-readiness work.
Privacy, DPA, and Subprocessor evidence
Privacy policies, data processing terms, subprocessor disclosures, and changes to legal evidence surfaces.
Regulated-industry and framework evidence
SOC 2, ISO, HIPAA, GDPR, and other framework or regulated-industry statements when publicly stated.
AI governance evidence
AI policy, responsible AI, model safety, and data usage pages that clarify how product and model data are handled.
Enterprise readiness features
Signals such as SSO, SCIM, RBAC, audit logs, data residency, and other control-oriented product capabilities.
Hiring and operating signals
Security, privacy, compliance, GRC, legal operations, and trust-related hiring that may indicate operational investment.
Interpretation
What the signal means
Raw public changes are not the final product. A useful signal combines the evidence itself with context about what changed, how strong the signal may be, and how cautious an observer should be.
Evidence URL
Every public interpretation starts with a reviewable source page.
Observed change
The useful question is often what appeared, changed, or disappeared over time.
Signal strength
Some changes are weak context, while combinations of signals can be more meaningful.
Why it may matter
Interpretation should connect the public evidence to practical trust, customer-assurance, or enterprise-readiness context.
False positive risk
Many public updates have benign or routine explanations and should be treated carefully.
Next signal to watch
Single pages are more useful when paired with the next evidence surface worth reviewing.
Boundaries
Public vs private layer
The public site explains evidence surfaces, sample interpretation, taxonomy, and methodology. Other research layers remain private and are not published here.
Public layer
- Evidence surfaces and page types
- Methodology and false-positive controls
- Sample interpretation format
- Public alpha company profiles after manual review
Private layer
- Buyer-specific fit ratings
- Custom watchlists
- Recommended GTM actions
- Outcome feedback and internal scoring logic
Current status
Early public alpha
The public alpha now includes category packages for AI Infrastructure and AI Coding Tools. Company profiles are added only after review against official evidence surfaces and conservative publication boundaries.