.png)
Trust Center
A living index of how ReliablyME validates privacy, security, and coaching-data claims. It shows what is public now, what is request-only, and what still needs verification before it is promoted.
How we validate claims
The rule is simple: a public statement must map to a source we can check.
Source of truth
- Every public claim should map to source code, a signed agreement, or a verified operational record.
- If the source is missing, the claim stays off the public page.
Bounded publication
- Publish only the parts that are already confirmed.
- Mark unresolved items as verification required instead of filling gaps with assumptions.
Review loop
- Recheck the pages whenever AI usage, subprocessors, or data flows change.
Current public coverage
The site already carries the core legal pages. This table shows how the incremental requirements are being handled without over-claiming.
Published indicates document availability, not independent verification of security controls.
| Requirement | Public surface | Status | Notes |
|---|---|---|---|
| Published privacy policy | Privacy Policy | Published | Public policy already covers collection, use, sharing, retention, and rights. |
| Data processing and subprocessors | DPA and Subprocessors | Published | Public summary exists, and the current vendor list can be shared on request. |
| Cookie handling | Cookie Notice | Published | Public notice explains essential cookies and browser controls. |
| Data visibility matrix | Coaching Data & AI | Published | Public matrix now shows who can see what by data type. |
| AI use disclosure | Coaching Data & AI | Published | Public page explains what AI can do and what it cannot decide. |
| Evaluation methodology | Coaching Data & AI | Published | Public page limits measurement claims to follow-through and workflow signals. |
| Support and escalation | info@reliablyme.com | Published | Public contact path exists; any SLA language should stay tied to verified operations. |
What still needs confirmation
These items should remain verification required until the source of truth is checked.
Unconfirmed claims
- SOC 2 or similar framework status, if any, should be stated exactly as verified.
- Retention periods by data class should be confirmed before they are published as commitments.
- The live subprocessor list should be checked whenever a vendor changes.
- Regional transfer language should match the actual hosting and processing footprint.
Monitoring and rollback
- Watch for broken legal links, changed processors, new AI vendors, and copy-runtime drift.
- If a claim becomes stale, remove it from the public page first and re-publish only after verification.
- Keep the verification register and the public page in sync so the site tells one story.
Need the current agreement set?
Start with the public Privacy Policy, DPA and Subprocessors, and Coaching Data & AI, then email info@reliablyme.com if you need a request-only artifact for procurement or coaching governance.
Want the full privacy and legal set?
Use the published legal pages for routine review and request the missing artifacts when a customer or auditor needs more detail.