Safety Check

Trust and security details

We show clear trust signals, not vague promises. This page shows current safety-check status, what is already being watched, and what still must pass before the public label can move to verified.

Current status: Attention NeededLast check: 10/26/2026, 11:46:46 AMOpen attention items: 2Auto-fixes logged: 3
What we tell users publicly
Latest browser safety check ran on 10/26/2026, 11:46:46 AM.
Browser-visible safety-check probes found active issues, so the public badge remains below verified.
Database protection checks are blocked until the public Supabase configuration is available.
Secrets posture checks found browser-visible configuration issues that block a stronger trust claim.
Badge language rule

We do not claim the site is 100% safe or formally certified unless a real external certification exists. Verified will only appear after the checkpoint program clears critical and high-risk findings and the latest browser checkpoint is still fresh.

Current safety-check board
Secrets and key safety
In Progress
Check details

Secrets posture checks found browser-visible configuration issues that block a stronger trust claim.

Database protection
In Progress
Check details

Database protection checks are blocked until the public Supabase configuration is available.

Permissions and admin access
In Progress
Check details

Protected table access still needs attention before the trust badge can advance.

Storage isolation
Not Started
Check details

Hosted file permissions need a separate review. This browser check does not verify storage policies.

Payment safety controls
Not Started
Check details

Payment processor integrity remains a later safety-check track.

Public trust UX
In Progress
Check details

Trust messaging stays in progress while safety-check findings remain open.

If you are paying through the site
  • Payment safety controls are part of the checkpoint program and are not treated as optional.
  • Hosted checkout or tokenized payment flows are the preferred direction so raw card data does not live inside the app.
  • Webhook authenticity, replay protection, and paid-status integrity must pass before public verified status is allowed.
Need help or want more detail?

If you have a trust or security question, use the contact path below. We would rather explain the current state clearly than pretend a safety check is farther along than it is.