STLMNT — Consumer rights | An App Idea LLC

Verified open settlements, eligibility checks, and claim-form autofill — without auto-filing or hoarding your data.

Expo RouterFirestore default-denyCloud KMS encryptionIngestion + curation
Copy, never submitClaim assist
KMS-encryptedSensitive data
On-device onlyReceipts
TimelineFounder-led Expo build
TeamUser + admin curation
PlatformiOS · Android
ImpactVerified settlements · zero sensitive data
Problem

The challenge

Open class action settlements are real money left on the table: notices are scattered across administrator sites, eligibility is buried in legalese, and the apps that aggregate them tend to hoard personal data or quietly file claims on a user's behalf. STLMNT had to make settlements discoverable and claimable without becoming a data broker or a fake legal service.

Approach

How we built it

I built an Expo Router app on an "Editorial Ink" design system — newspaper masthead meets legal ledger — over a default-deny Firestore model. Ingestion workers (FTC RSS, JND/Atticus/Simpluris/Kroll, and a CourtListener webhook) feed a review queue that an admin curates, optionally with an Anthropic Claude drafting step, before anything reaches the public catalog. The autofill profile routes through a callable Cloud Function gateway that envelope-encrypts sensitive fields with Cloud KMS, and receipts stay on the device. Crucially, the app only ever copies a claim to the clipboard — the user submits it themselves on the official site, under penalty of perjury.

Outcome

What shipped

STLMNT turns a scattered, jargon-heavy process into one honest workflow: find a settlement, check eligibility, autofill and copy the official form, file it yourself, and track status through to payout. It collects the minimum to be useful — brand names for matching, payment handles instead of account numbers — and lets users erase everything in a single tap.

Results

Outcomes

  • Built a curated catalog of verified, open settlements fed by ingestion workers (FTC feed, court-administrator scrapers, CourtListener) behind an admin review gate — nothing publishes until a human approves it.
  • Shipped an autofill profile that envelope-encrypts sensitive fields (name, address, payment handles) with Cloud KMS, and never stores bank, SSN, or card numbers.
  • Kept the user in control end to end: an eligibility self-check, copy-to-clipboard claim assist (never auto-submission), on-device receipts, local deadline reminders, and one-tap account and data deletion.
Under the hood

The claims pipeline

STLMNT's admin dashboard tracks every claim through its lifecycle — saved, filed, confirmed, approved, paid, with rejected as a terminal state. Here is that claims-by-status visualization, refactored from the app for the web and wearing STLMNT's own Editorial Ink palette.

Claims by status1128 total
  • Saved41237%
  • Filed28625%
  • Confirmed17415%
  • Approved969%
  • Paid13812%
  • Rejected222%

Conversion 12% · Rejection 2%

The claims-by-status visualization from STLMNT's admin dashboard, refactored for the web in the app's Editorial Ink palette. Illustrative data.

Engineering

Tech stack

React NativeExpo RouterTypeScriptFirebaseFirestoreCloud FunctionsCloud KMSAnthropic Claude
Consumer RightsPrivacyMobileLegal Tech
← All workConsumer rights