Methodology
How we research employment law, ingest court rulings, and review content for accuracy.
How we research
Our employment-law content is sourced from primary statutes published in the federal and state codes, supplemented by regulatory guidance, agency procedural rules, and case law. We reference EEOC.gov extensively for federal anti-discrimination procedure, and Cornell Legal Information Institute (LII) for statutory text, regulatory cross-references, and definitional context.
For state and local jurisdictions, we work directly from each state’s code (e.g. Florida Statutes Chapter 760, California FEHA, New York State Human Rights Law) and the relevant state agency’s published procedures. We do not paraphrase from secondary commentary in place of citing the underlying statute.
Our rulings database
Workers’ Rights maintains a corpus of 142,000+ federal and state employment law court rulings. The corpus is ingested daily from CourtListener, a project of the Free Law Project — a 501(c)(3) nonprofit dedicated to keeping court records accessible. We retain the original opinion text, court identifiers, and date of decision; nothing is paraphrased into the ruling record itself.
For each ruling we display, we also derive structured fields — outcome (employee win, employer win, mixed, or procedural), dominant claim type (Title VII, ADA, FMLA, FLSA, etc.), and any cited statutes — using a large-language-model extraction pipeline with confidence thresholds. Extractions below the confidence threshold display as “Unclassified” rather than guessing.
LLM-extracted fields are not authoritative. They’re a navigation layer over the underlying opinions, which remain the source of truth. Anyone who spots a misclassified outcome can submit a fix on /corrections; corrections enter our editorial review queue and override the extraction once verified.
Update cadence
Different layers of the platform refresh on different schedules based on how often the underlying source material changes:
- Court rulings (CourtListener ingest): daily. New federal and state opinions appear within ~24 hours of publication.
- Federal legal-source monitoring: daily. EEOC guidance, federal regulatory updates, and major federal employment-law developments are checked every weekday morning.
- State legal-source monitoring: weekly. State agency announcements, statute amendments, and state-court precedent are checked once per week.
- Local (city/county) legal-source monitoring: monthly. Local ordinances and municipal commission rules are checked on the first of each month.
- Statute and rights pages: reviewed at least quarterly by editorial reviewers; flagged for immediate review when monitoring detects a material change.
The footer “Last reviewed” indicator on each legal page reflects the most recent editorial review, not the most recent automated source check.
Editorial review
Substantive legal content — statute summaries, rights pages, the EEOC process guide, and learning articles — is reviewed by independent JD-credentialed reviewers with employment law focus before publication and on a recurring cadence thereafter.
Reviewers verify that:
- Statute citations match the current code text.
- Filing deadlines and eligibility thresholds are accurate.
- Any changes since prior review are reflected.
- Plain-language summaries don’t materially distort the underlying law.
We do not publish the names of individual reviewers. This is a deliberate choice: it protects reviewers from being mistaken for counsel of record on any reader’s individual matter, and maintains the platform’s editorial independence by decoupling content credibility from any single person’s practice or affiliation. See our editorial standards for the full review process and conflict-of-interest policy.
Technical detail (for the curious)
Most users don’t need to read this section. The encryption is automatic and works without any action on your part.
How your data is encrypted
Every account has its own per-user data encryption key (DEK). The DEK is what actually encrypts your timeline events, journal entries, evidence metadata, and other personal data on your device before any of it is uploaded.
We use a pattern called envelope encryption: instead of storing your DEK in plaintext, we store it in a wrapped form. The wrapping is done with a separate master key that lives only in our application server’s runtime environment — never in the database and never in source code. So a Supabase backup or database dump, on its own, doesn’t expose any user’s data: an attacker would also need to extract the master key from our running infrastructure.
How cross-device works
When you sign in on a new device, the device authenticates with our server (Google OAuth or magic link), then asks our server to unwrap your DEK over the same authenticated TLS connection. The DEK is sent once over that connection and cached in your new device’s local storage. From then on, all encryption and decryption happens locally in your browser.
Anonymous mode
If you use Workers’ Rights without creating an account, the encryption key never touches our servers. It is generated in your browser, stored in your browser, and used only by your browser. Your data lives entirely on the device that created it.
Optional zero-knowledge mode
You can layer a recovery passphrase on top of the wrapped DEK. In that mode, your DEK is additionally wrapped client-side with a key derived from your passphrase before any cross-device sync. The passphrase itself is never sent to our servers. With this enabled, even our application servers (with master key in hand) cannot decrypt your data without your passphrase. The trade-off: lose the passphrase and the data is unrecoverable.
AI document analysis
When you choose to use AI analysis (it’s opt-in), your narrative text and any document text you choose to analyze are sent to Anthropic over an encrypted connection. Anthropic does not retain your data after processing and does not use it to train models. We never automatically send your evidence or journal entries; the AI seam is invoked only on the explicit actions you take in the app.
Disclaimer recap
Everything on Workers’ Rights is general legal information, not legal advice. Employment law varies by jurisdiction, by employer size, by claim type, and by the specific facts of each situation. Reading an article here does not create an attorney-client relationship.
For advice about your specific situation, consult a licensed employment attorney in your jurisdiction. Our attorney directory is one starting point, but you are responsible for evaluating and selecting your own representation. Full terms in our legal disclaimer.