Trust and methodology

What we are doing first: information, not promises

• Intent-first routing by county, city, and state to keep context accurate.
• Queueed processing for leads and provider submissions.
• Clear status indicators so users know when a request is in review vs. ready for follow-up.

Quality and moderation controls

• Manual review gates before public listing changes and feature visibility upgrades.
• Structured validation on intake payloads to reduce invalid, duplicate, or malformed captures.
• Audit logs capture moderation and routing state changes for accountability.
• Spam and abuse controls are enforced with timing checks, tokenized request checks, and payload anomaly handling.

Data trust and retention posture

• Form and inquiry data is retained for operational and legal utility windows, then pruned or redacted per policy.
• PII is not embedded in analytics events.
• Consent events include version, method, and timestamp for every marketing-opt-in decision.
• Deletion and redaction workflows are routed with authorization controls and audit visibility.

EEAT and trust signals in content

• County and state pages include local process details and local readiness context before action.
• Listing claims are explicitly separated from queue status and moderation state.
• Provider status includes review context instead of unqualified placement messaging.

Supporting pages