Transparency Report
What WeWillHelp does with your data — and, more importantly, what we don't.
Privacy commitments — verifiable today
- We have never sold data — not search queries, not addresses, not user lists, not anything.
- We have never shared user data with advertisers. No third-party trackers, no ad pixels.
- We do not store tip-line submissions. Every "Report a tip" link in this app opens the agency's own form in a new browser tab. Your submission flows browser → agency. We never see the content.
- We do not track your location persistently. Your position is used while you're using the map and is never sold. It is never written down at full precision either: the request log keeps a grid square roughly 0.6 miles on a side, deleted after 30 days. Enough to spot abuse, never enough to place you at an address.
- We do not monitor your child's messages. Every device/app safety guide explicitly recommends preserving the child's right to private conversations with friends.
- We do not use your data to train AI. The AI features (safety briefings, security analysis) use only aggregate signals — never user content.
What we explicitly refuse to build
- Child-message content monitoring (Bark / Qustodio style)
- Persistent location tracking of family members (Life360 style)
- Predator-photo facial recognition from camera input (legal liability + misidentification harm)
- Real-name lookup databases (TruthFinder / BeenVerified style)
- Anything paid by ad revenue (would create incentive to track)
- AI chat with children (we shipped this then removed it — wrong shape)
- Community forum (becomes moderation nightmare + predator vector)
Vendors we use
Every vendor with access to any user data is listed here. We do not use any tracking, advertising, or analytics vendors except where noted.
Data sources we read from
- Offenders.io — registered sex-offender data. Public records aggregator.
- NCMEC Poster API — missing-child photos & details. Federally authorized.
- NamUs — federal missing & unidentified persons database (DOJ).
- Charley Project — long-term cold-case missing-persons (public-record, no PII beyond what's already published).
- Google Maps — map tiles + geocoding. Privacy policy
- Anthropic — AI safety briefings + security analysis. We send aggregate signals only, never user content. Privacy policy
Admin access controls
- Admin endpoints are gated by a hardcoded email allowlist (env-var driven since v157).
- Every admin endpoint call is logged to an internal
admin_audit table — success and denial. Includes admin email, endpoint, IP, timestamp. Never logs request bodies.
- The admin audit log is queryable only by another admin. Even Supabase service-role queries are gated.
- Two-factor authentication required on the admin's email account (operator self-policy).
- No third-party access. No contractors with login.
Tip-line legal posture
Every "Report a tip" surface in WeWillHelp is a deep link to the official agency's own form (FBI tips.fbi.gov, NCMEC report.cybertip.org, Polaris, RAINN, etc.). The link opens in a new browser tab. The user's tip submission goes from their browser to the agency. WeWillHelp servers are not in the loop.
We cannot be subpoenaed for tip content we never received, metadata we never logged, or evidence we never stored. Anyone reviewing our source code can verify this — there is no <form action="/api/..."> that submits tip content anywhere on our domain.
Your data rights
- Export: any signed-in user can download all data we hold about them via Settings → Legal & privacy → Data export. JSON format.
- Delete: any signed-in user can permanently delete their account + all associated data via Settings → Legal & privacy → Delete account.
- Anonymous use: every safety feature in the app is usable without an account. Account benefits are saved zones, email alerts, watchlist (Premium).
- CCPA / GDPR style request: email [email protected] with subject "Data Rights Request" — response within 14 days.
Security posture
Headers
HSTS
CSP
X-Frame-Options
X-Content-Type-Options
Referrer-Policy
Permissions-Policy
COOP
X-Permitted-Cross-Domain-Policies
Cross-Origin-Resource-Policy
Server controls
- Per-IP rate limits on every public + admin endpoint
- Server-side input sanitization on every user-content field
- Supabase Row-Level Security on every user-data table
- Service-role keys never exposed to client
- Stripe webhook signature verification
- Push subscription endpoints use platform-issued VAPID keys
Audit trail
admin_audit table — every admin endpoint callapi_errors table — every unhandled exception in API endpointsterms_acceptance_log table — versioned policy acceptances- Daily admin email surfaces any anomalies within 24 hours
Questions
Email [email protected] with any question about our practices. Every reply is read by a human (the operator) — there is no support-bot.