LexLens · NoticeSetu — 2026
PRODUCT PITCH
LexLens
NoticeSetu
Any legal notice.
Any language.
Understood in 60 seconds.
NO LOGIN · NO SIGNUP · NOTHING SAVED
⚿
LEGAL INFORMATION, NOT LEGAL ADVICE
ⓘ
LexLens turns a legal notice into a clear, deadline-aware action workflow — anonymously, in under a minute.
Live product — Section 138 cheque-dishonour analysis, India · Bihar
THE PROBLEM
You receive a legal notice.
What do you do next?
Notices arrive as pages of dense legal language. The three things a person needs most — what happened, what they must do, and by when — are buried inside it.
⚖
Legal language is impenetrable for most people
⊘
Critical dates are hidden mid-paragraph
⊘
Miss a statutory deadline and the consequences escalate
✦
Lawyers are expensive; generic AI chatbots summarise but invent dates and cannot be trusted
Confusing, stressful, and time-sensitive.
A real Section 138 demand notice — the answer is in here, somewhere.
THE SOLUTION
Upload. Understand. Act.
LexLens reads the notice, verifies the jurisdiction and notice type, extracts the facts, computes the exact legal deadline, and tells the user what to do next — without an account, in about a minute.
1
UPLOAD
paste text or upload PDF (OCR fallback)
→
2
UNDERSTAND
jurisdiction, classification, facts, deadlines
→
3
ACT
action center, reminders, evidence, lawyer handoff
Anonymous landing — no login, no signup, nothing saved
EVERYTHING IT DOES
Complete functionality map
21 features — every one visible and working in the product.
↑
Ingestion
01
paste notice text
.txt file upload
PDF upload with text extraction
OCR fallback for scanned notices
◯
Intelligence
02
jurisdiction auto-detection to state level (India → Bihar)
notice classification (Cheque Dishonour / §138 Demand Notice)
canonical fact extraction incl. Devanagari patterns
✓
Action Center
03
claimed amount, notice type, receipt date, exact deadline
recommended next actions
missing-information detector
◔
Deadlines & Reminders
04
deterministic deadline engine
live countdown
browser reminder creation
edit / cancel
⚖
Evidence & Legal Basis
05
evidence checklist (available vs missing)
chronological legal timeline
corpus-verified citations with Why? traceability
▤
Output & Handoff
06
full report PDF download
one-page lawyer case brief
English + हिन्दी interface and legal content
NO LOGIN / SIGNUP
⚿
TEMPORARY ANONYMOUS SESSION
◔
SESSION ISOLATION
⛨
⛨
PRIVACY ARCHITECTURE
Anonymous by design
No accounts exist anywhere in the product — isolation is enforced server-side, per session.
◯
STEP 1
Open the site
→
⚿
STEP 2
32-byte random session token (HttpOnly cookie)
→
⎙
STEP 3
Server stores only the SHA-256 hash
→
⚿
STEP 4
Every notice, report, file & reminder is session-scoped
→
✕
STEP 5
24h sliding TTL — cascade purge deletes everything
✕
No user history — start a new analysis and prior data is revoked instantly
✦
Foreign or expired IDs return a privacy-preserving 404 on every resource
✓
Verified by 27/27 automated privacy tests (cross-session isolation, forged tokens, direct-ID attacks)
UNDER THE HOOD
Nine-stage analysis pipeline
1
Upload & session attach
→
2
Text extraction
(PDF parse + OCR fallback)
→
3
Jurisdiction detection
(multi-signal: statutes, currency, cities, states, banks, courts, scripts)
→
4
Classification
with deterministic type override
→
5
Canonical fact extraction
(regex safety net incl. Devanagari)
6
Corpus matching
against curated statutes
→
7
Deterministic deadline computation
→
8
Eight-check validation gate
→
9
Report assembly
(EN/HI)
Live pipeline view — each stage surfaces real values
⚡
If the AI is unreachable, a deterministic offline engine completes the same pipeline — the product never hard-fails.
§
LEGAL SAFETY
Jurisdiction firewall
Legal systems are incompatible — LexLens never mixes them.
🏛
INDIA
✓
Negotiable Instruments Act, 1881 — §138 rule pack
✓
15-day statutory payment window
✓
state-level detection (demo: Bihar)
⚖
§138 notices are always classified cheque dishonour — the AI cannot override it
⚖
USA
✓
FDCPA applicability assessed from facts, never assumed
✓
state law scoped (e.g. New York corpus)
✓
separate rule pack, separate citations
?
UNKNOWN
CONFIRM REQUIRED
⊘
no rule pack runs
▤
report gated behind a confirm card (India / USA buttons)
◯
the system never guesses a jurisdiction
⛨
Cross-jurisdiction legal claims are rejected server-side — an Indian §138 notice can never cite FDCPA, and vice versa.
ACTION CENTER
Every important fact, in one place
A canonical caseFacts store is the single source of truth. Each fact carries its confidence and its source in the document — the Action Center renders it as plain answers.
$
Claimed amount
—
₹85,000
⚖
Notice type
—
Cheque Dishonour (Section 138 Demand Notice)
▦
Receipt date
—
19 September 2026
◔
Exact deadline
—
4 October 2026
◎
Jurisdiction detected: India → Bihar. Cheque No. 458721, State Bank of India, Patna.
Action center — generated from verified facts and statutory rules, never guesses
NEVER INVENTED
If a fact is missing, LexLens says so
Most tools would guess a deadline. LexLens refuses: with the receipt date unavailable it shows the empty state and waits.
Receipt date
—
⚠ Not provided
Exact deadline
—
⚠ Cannot calculate yet
“
Exact deadline cannot be calculated because notice receipt date is unknown. Add it below and LexLens will recalculate instantly.
⚿
Honesty is a feature: the user supplies the one missing date, and the deadline locks in.
The amber capture card — the single most important missing fact
DEADLINE ENGINE
Dates come from rules, not from AI
Receipt date
19 Sep 2026
+
Statutory payment window
15-day statutory payment window (NI Act §138)
=
Exact deadline
4 October 2026
✦
Deterministic code
“Computed by deterministic code from verified rules — never by the AI.”
✓
MISSING_REQUIRED_FACT state
the engine reports what it cannot compute instead of guessing
▤
30 vs 15 confusion guard
“The 30-day period mentioned in §138 concerns when the PAYEE must send the demand notice after the dishonour — it is not a dispute right for the recipient.”
Deadline recalculated instantly after the receipt date was added
REMINDERS
A temporary browser reminder — no account
Once the deadline is known, the user can set a reminder that fires as a real browser notification. It is temporary, session-scoped, and never touches an account.
⚡
Quick picks — Deadline day / 1 day before / 3 days before, or any date & time
⛨
Dialog states verbatim:
“This reminder is tied to the deterministically calculated legal deadline below — it is never generated by AI.”
✓
Confirm → “Reminder set successfully.” — then Edit or Cancel anytime
↻
Deadline recalculation automatically shifts the reminder
32/32 REMINDER TESTS PASS
✓
SESSION-SCOPED · EXPIRES WITH THE SESSION
⧗
Reminder dialog — anchored to the calculated deadline 4 Oct 2026
CHRONOLOGY & EVIDENCE
The case, in order — and what's still missing
Instead of re-reading the notice, the user gets a chronological timeline of the legal events, plus an evidence checklist that separates what exists from what must be gathered.
Cheque issued
—
5 Sep 2026
Cheque presented
—
10 Sep 2026
Cheque dishonoured
—
10 Sep 2026
(Return Memo: FUNDS INSUFFICIENT)
Legal notice issued
—
18 Sep 2026
Notice received
—
19 Sep 2026
Statutory payment window ends
—
4 Oct 2026
✓
Evidence checklist — legal notice: available ✓ · cheque copy, bank return memo, invoice/agreement, payment receipts: flagged as not uploaded
Legal timeline — every event dated and sourced
LEGAL SOURCES
Every claim traces to a source
Legal claims are tied to a curated statute corpus. Each citation can be expanded with a Why? explanation, and the product never presents itself as a lawyer.
🏛
Corpus-verified citation — Negotiable Instruments Act, 1881 — §138
✓
Citation whitelist — the model cannot invent statutes; unmatched citations are stripped
⇄
Conditional consequences explained in plain language
⛨
Standing disclaimer: “LexLens provides legal information, not legal advice.”
⚖
High-severity paths always add a consult-a-lawyer step.
Legal basis — corpus-verified, expandable Why? traceability
LANGUAGES
The same analysis in English or हिन्दी
Legal information should be understandable. LexLens presents the interface, the summary and the legal explanations in English or Hindi — the Hindi is transcreated legal language, not a raw translation.
CLAIMED AMOUNT
₹85,000 की राशि
STATUTORY WINDOW
15 दिन की भुगतान अवधि
DEADLINE
समा-सीमा 2026-10-04
⇄
Devanagari fact patterns also feed the extraction engine — Hindi notices are parsed natively.
पूरा रिपोर्ट हिन्दी में — same case, same deadline
OUTPUT & HANDOFF
Take it with you — or hand it to a lawyer
↓
Download Full Report PDF — a clean, branded report of the current analysis; contains no technical or AI jargon
✻
Prepare lawyer brief — a one-page case brief (facts, deadlines, evidence gaps) the user can hand to a lawyer
✎
Draft response with placeholder discipline — missing dates become [placeholders], never invented values
⧗
Temporary by design: the session expires in 24h; downloads are the user’s copy.
One-click PDF + lawyer brief
Generated report PDF, page 1 — branded, plain-language, free of AI jargon
ENGINEERING
Built to never fail quietly
A deterministic core wrapped in validation, with an AI fast path that can degrade gracefully.
38/38
◔
Deadline-engine tests — 15-day vs 30-day, MISSING_REQUIRED_FACT, firewall rejections
49/49
✦
Regression suite — across jurisdictions, languages and missing-date flows
27/27
⚿
Privacy & session-isolation — attacks
32/32
◔
Reminder lifecycle — set, edit, cancel, fire-once, cascade
12/12
▣
PDF contract — no jargon, correct pages, session-scoped
Never-fail
⚡
glm-4.6 fast path plus a deterministic offline engine when the AI is unreachable
NEXT.JS 16 · PRISMA · SERVER-SIDE SESSION FIREWALL
▦
8-CHECK VALIDATION GATE BEFORE ANY REPORT RENDERS
✓
§
“
ChatGPT can explain a legal notice.
LexLens turns it into a verified, deadline-aware, evidence-backed action workflow.
Understand. Act.
Don’t miss the deadline.
LEX LENS — NoticeSetu
Any legal notice. Any language. Understood in 60 seconds.
LEGAL INFORMATION, NOT LEGAL ADVICE
ⓘ