Data we collect
Public settlement records contain source-backed information such as title, brand, deadlines, proof requirements, official settlement links, payment status, administrator details, and eligibility summaries from public official sources.
Account workspace features may store your email address, password hash, saved settlements, reminder preferences, confirmation numbers, and optional eligibility answers that help you organize your own tracker.
How we use data
- Show verified public settlement records and official source context.
- Let signed-in users save settlements and manage reminders.
- Improve source quality, publication guardrails, and exception handling.
- Maintain security, auditability, and operational reliability.
AI verification
AI-assisted verification is limited to public official-source settlement documents and technical settlement context. User account data, saved claim details, confirmation numbers, and private eligibility answers are not sent to AI providers in this phase.
AI output cannot publish a settlement by itself. Publication also requires deterministic checks for official source evidence, source snippets, allowed values, confidence, conflict handling, and existing publishability rules.
Data we avoid
Do not store Social Security numbers, bank credentials, full payment card numbers, sensitive medical or legal records, or private claim documents in SettleSignal. Submit claim information only through official settlement administrator or government websites.
Your controls
You can manage saved settlements, reminders, and profile preferences from your account workspace. Account deletion is available from the profile page and permanently removes your profile, saved claims, eligibility answers, reminders, brand selections, and login tokens; audit records are retained without the user link (anonymized) to preserve catalog integrity. Data export and retention workflows remain to be finalized before a public production launch.
Security
Local MVP development uses environment-based secrets, password hashing, audit records, and conservative data boundaries. Production security controls, vendor contracts, retention settings, monitoring, and incident response must be reviewed before launch.