Invalidity dossier
US 12536263
Message sender security in messaging system
Current assignee: FaceToFace Biometrics Inc
Added 9/30/2026, 4:00:51 AM
Active provider: DeepSeek · deepseek-v4-flash
Auto-generating section 1 of 2: Extensions…
Each section takes ~30-60s with web-search grounding. Keep this tab open — sections will fill in below as they complete.
Patent summary
Title, assignee, inventors, filing/issue dates, abstract, and a plain-language overview of the claims.
I'll search for authoritative information on this patent. Let me run several targeted queries.
Let me check for any litigation (CAFC 2026 or otherwise) and USPTO proceedings specifically involving this patent number.
I found a live 2026 litigation asserting this patent. Let me dig into that docket and check for any Federal Circuit activity.
US Patent 12,536,263 — Analyst Summary
Verification note: I located the patent on Google Patents and cross-checked it against USPTO-derived records (PACER Monitor, PTAB filings, patent-family data). A live 2026 district-court docket cites this exact number. I did not find any Court of Appeals for the Federal Circuit docket involving 12,536,263 — see "Litigation / CAFC" below.
Bibliographic data (from the patent front matter / Google Patents)
| Field | Value |
|---|---|
| Patent number | US 12,536,263 B2 |
| Title | Message sender security in messaging system |
| Inventors | Eric Leuthardt; Scott Stern |
| Assignee (original & current) | FaceToFace Biometrics, Inc. |
| Application no. | 18/654,228 |
| Filing date | 2024-05-03 |
| Issue / grant date | 2026-01-27 |
| Pre-grant publication | US 2024/0281513 A1 (2024-08-22) |
| Priority date | 2014-03-10 (provisional 61/950,423) |
| Anticipated expiration | 2035-03-10 |
| Status | Active |
| Representative CPC | G06F 21/32; G06F 21/60; H04L 63/0861; G06V 40/70 |
Continuation chain (this patent is the fifth in a family):
14/643,800 → US 9,817,960 → US 10,592,650 → US 11,334,653 → US 11,977,616 → 18/654,228 (this patent). A further child, US 19/415,112 (US 2026/0099577 A1), was filed 2025-12-10. Priority is claimed to three provisionals: 61/950,423 (2014-03-10), 61/985,059 (2014-04-28), and 62/042,561 (2014-08-27).
Abstract (verbatim)
"Some embodiments include a method of providing security and privacy for a message sender. The method can include a messaging application determining that a messaging interface of the computing device is active and is revealing or about to reveal the electronic message. The messaging application can identify a recipient account of a messaging server system that is associated with the electronic message according to the electronic message or the messaging server system. The messaging application can then monitor a data feed from a sensor of the computing device to detect a biometric pattern that matches against a biometric profile model associated with the recipient account utilizing a biometric recognition process. In response to determining that the detected biometric pattern does not match the biometric profile model associated with the recipient account, the messaging application can activate a privacy shield to prevent content of the electronic message from being revealed."
Important caveat: the abstract describes the older, broader family disclosure, not the narrow claims actually granted here. The issue claims are materially different from the abstract (see below).
Independent claims — plain-language overview
The patent has three independent claims: 1, 11, and 18. All three recite essentially the same subject matter in three statutory formats (device / method / non-transitory CRM).
Claim 1 — Receiver computer device (processor + memory programmed to):
- Receive, at the receiver device from a sender device, an electronic message that includes (a) electronic content and (b) identifying information of the sender;
- In response to the message and independent of any user interaction, instruct the receiver device to simultaneously display a privacy shield and the sender's identifying information on the display screen;
- Validate biometric data of the user against a stored biometric profile of the user; and
- Remove the privacy shield and display the electronic content if the biometric data is validated.
Claim 11 — Computer-implemented method: the same four steps (receive → auto-display shield + sender identity without user interaction → validate biometric data against stored profile → reveal content on validation).
Claim 18 — Non-transitory computer-readable storage media: the same four steps embodied as executable instructions.
Key point: Because claim 1 uses "in response to the electronic message and independent of any user interaction," the shield-plus-sender-identity screen is triggered automatically on message arrival — the user need not open or touch anything. The reveal condition is validation of the recipient/user's own stored biometric profile, not the sender's, despite the "message sender security" title.
Notable dependent claims:
- 2 / 12 / 19 — biometric data is a feature detected by a sensor of the receiver device; claim 19 further specifies the stored profile is a facial profile.
- 3 / 13 — stored biometric profile is a facial profile.
- 4 / 14 — monitor a sensor feed from the receiver device.
- 5 / 15 — detect more than one individual; prevent display if more than one is detected.
- 6 — receiver device is a smartphone.
- 7 / 16 — the message is an MMS message.
- 8 / 17 — prevent display until validated biometric data is detected.
- 9 — content revealed while the screen remains locked from additional access.
- 10 — content revealed on a lock-screen view.
- 20 — the privacy shield is displayed adjacent to the sender's identifying information.
Claims 2–10 depend from claim 1; 12–17 from claim 11; 19 from claim 18; 20 from claim 1.
Litigation / CAFC search results
- Asserted in a 2026 case: FaceToFace Biometrics, Inc. v. Apple Inc., No. 4:26-cv-01534 (E.D. Mo.), before Judge Catherine D. Perry. Per PACER Monitor, the complaint (Exhibit 2) attaches U.S. Patent No. 12,536,263. Source: https://www.pacermonitor.com/public/case/67037040/FaceToFace_Biometrics,_Inc_v_Apple_Inc
- ⚠️ Date caveat: PACER-derived sources list the filing date as 09/28/2026, which is later than the "current date" of April 26, 2026 stated in this task. I cannot reconcile that discrepancy — treat the filing date as reported by the source, not confirmed by me.
- No CAFC 2026 docket found for 12,536,263. The only Federal Circuit activity in this family that surfaced is appeal 23-1792 (FaceToFace Biometrics v. Apple), which concerned US 11,042,623 ("Expression recognition in messaging systems") — a different patent — and was disposed of by order (nonprecedential, 2023), not on the merits of this patent.
- Prior PTAB activity (IPR2023-00833, Apple v. FaceToFace) also targeted US 11,042,623, not 12,536,263, and was terminated on settlement in 2024. Relevant because the same district judge in the 2022 case (4:22-cv-00429) invalidated the '623 patent under § 101 as an abstract idea.
Uncertainty / flags
- Assignee and inventor names are taken from the patent front matter; I have not independently verified current ownership beyond the Google Patents record.
- Abstract vs. claims mismatch: the abstract and much of the specification describe sender-side privacy shields tied to a recipient account's biometric model, whereas the granted independent claims are directed to a receiver device validating the user's own stored biometric profile to unshield content — a narrower framing. Anyone relying on the abstract should read the claims.
- No CAFC 2026 docket for this patent was found. Absence of a result is not proof of absence; PACER/CAFC dockets for very recent cases may not index promptly.
- I have not located a final written decision, IPR, or validity ruling specifically addressing US 12,536,263. I cannot state its enforceability status with confidence.
Generated 9/30/2026, 4:01:13 AM
Cases on file (0)
Specific litigation cases in our database that name US patent 12536263. The free-form analysis below may also discuss cases beyond this list.
No cases on file mention this patent. Upload a CSV or add a case manually in Admin → Manage litigation cases.
Litigation summary
Past and pending lawsuits — plaintiffs, defendants, jurisdictions, outcomes, and notable rulings.
I'll run targeted litigation searches for this specific patent number.
Let me dig deeper into the specific docket and check for any other defendants or cases.
Litigation Involving U.S. Patent No. 12,536,263
Bottom line: I found exactly one litigation asserting U.S. Patent No. 12,536,263. I found no other district-court case, no Federal Circuit appeal, and no PTAB proceeding naming this specific patent. I did not count cases involving sibling family members (e.g., the '623 patent) as litigation against the '263 patent.
Case 1 — FaceToFace Biometrics, Inc. v. Apple Inc.
| Field | Value |
|---|---|
| Plaintiff | FaceToFace Biometrics, Inc. (patent owner / operating company) |
| Defendant | Apple Inc. |
| Jurisdiction | U.S. District Court, Eastern District of Missouri (Eastern Division) — Judge Catherine D. Perry |
| Case number | 4:26-cv-01534 |
| Filing date | 09/28/2026 (as reported by PACER-derived sources) |
| Cause / Nature of suit | Patent Infringement, 35 U.S.C. § 271; NOS 830 |
| Outcome / status | Open / active. Complaint filed with jury demand; summons issued. Docket entries to date are ministerial (disclosure statement, notice of process server, entry of appearance by Jeremiah W. Nixon, AO-120 report to the Commissioner). No motion, answer, or ruling appears in the accessible record. |
How I verified the patent number: The docket's complaint (Doc. 1, 14 pages) attaches Exhibit 2 — U.S. Patent No. 12,536,263, alongside Exhibit 1 (Infringing Devices) and the civil cover sheet. Sources:
- PACER Monitor docket: https://www.pacermonitor.com/public/case/67037040/FaceToFace_Biometrics,_Inc_v_Apple_Inc
- Ex Parte AI Lab docket record (4:26-cv-01534, "Facetoface Biometrics Inc v. Apple Inc," filed 09/28/26, status Open, source PACER): https://ai-lab.exparte.com/case/dct/moed/4:26-cv-01534/facetoface-biometrics-inc-v-apple-inc
Notes on the parties/counsel: Plaintiff is represented by Anthony G. Simon (The Simon Law Firm, P.C., St. Louis) — the same firm that represented FaceToFace in the earlier '623 dispute. Jeremiah W. Nixon has entered an appearance for the plaintiff.
⚠️ Date discrepancy — please read
The task states the current date is April 26, 2026, but multiple independent sources (PACER Monitor, Ex Parte, CourtListener/RECAP entries, and the system date of this session, 2026-09-30) place the filing of 4:26-cv-01534 at 09/28/2026. I cannot reconcile that inconsistency and, per the operating rule requiring literal interpretation, I am reporting the date as stated by the sources rather than normalizing it. If the true filing date were 2026, the case number prefix "26" and the 2026 docket entries are consistent, but the month/day is later than the date given in this task. Treat the filing date as source-reported, not independently confirmed.
Cases I explicitly excluded (wrong patent number)
These are related proceedings involving the same parties but a different patent — do not attribute them to 12,536,263:
| Proceeding | Patent | Relevance |
|---|---|---|
| FaceToFace Biometrics, Inc. v. Apple, Inc., No. 4:22-cv-00429 (E.D. Mo., filed 4/13/2022; Judge Perry) | U.S. 11,042,623 ("Expression recognition in messaging systems") | Dismissed/invalidated under § 101 as an abstract idea (Mar. 17, 2023). Not the '263 patent. |
| IPR2023-00833, Apple Inc. v. FaceToFace Biometrics, Inc. (filed 4/17/2023) | U.S. 11,042,623 | Instituted 11/17/2023; terminated on settlement 6/13/2024. Challenges the '623 patent, not the '263 patent. |
| CAFC Appeal No. 2023-1792, FaceToFace Biometrics, Inc. v. Apple Inc. | U.S. 11,042,623 | Dismissed with prejudice (order, 6/26/2023). Not the '263 patent. |
I mention these only because a search for "FaceToFace Biometrics v. Apple" returns them prominently, and they can be mistaken for litigation against the '263 patent.
PTAB / Federal Circuit — none found for 12,536,263
- No IPR, PGR, or CBM naming U.S. 12,536,263 surfaced. The only FaceToFace PTAB proceeding in the record (IPR2023-00833) is on the '623 patent.
- No CAFC appeal naming U.S. 12,536,263 surfaced. The only Federal Circuit activity in this family is 2023-1792 on the '623 patent.
- Note the '263 patent only issued 2026-01-27 (per the patent front matter), so a § 315(b) one-year IPR window from the new complaint would not close until roughly late 2027, and no petition would be expected this early.
Reporting caveats
- I could not directly retrieve the Unified Patents litigation caselist (portal.unifiedpatents.com) during this session — queries against it returned no matching case list. My identification of 4:26-cv-01534 rests on PACER-derived aggregators (PACER Monitor, Ex Parte AI Lab) that mirror the docket.
- PACER dockets for very recent cases may not index promptly, and my search may undercount if an additional suit asserts the '263 patent but has not yet been indexed by these aggregators. Absence of a second case is not proof that only one exists.
- The docket is in its earliest stages; there is no claim construction, no validity ruling (e.g., § 101), and no outcome for the '263 patent itself. I cannot state anything about the patent's enforceability as adjudicated in this case.
- Consistency with the earlier-generated section: This matches the prior section's finding (same case number, same parties, same exhibit attachment, same date caveat). No contradiction identified — the earlier section also flagged the date mismatch and the absence of CAFC '263 activity.
If your actual question is whether the '263 patent has been adjudicated: it has not. The only merits ruling in this family — the § 101 invalidity holding — was against the '623 patent, a different patent.
Generated 9/30/2026, 4:01:29 AM
Proceedings on file (0)
All PTAB activity →AIA trial proceedings (IPR / PGR / CBM) filed at the USPTO Patent Trial and Appeal Board against this patent. Sourced from the USPTO Open Data Portal and refreshed every six hours; each proceeding number deep-links to the PTAB E2E docket.
No PTAB proceedings on file. This patent has not been challenged via IPR, PGR, or CBM. The absence is itself a signal — well-asserted patents eventually attract IPRs. The LLM analysis below may surface filings the ODP feed hasn’t indexed yet.
PTAB challenges
AIA trial proceedings at the USPTO Patent Trial and Appeal Board — IPR, PGR, and CBM. Petitioners, judge panels, claim-level invalidation outcomes from Final Written Decisions, and Federal Circuit appeals. The single most important defensive datapoint after litigation history.
I'll verify the structured "no PTAB activity" baseline against the public record before drafting.
Let me confirm no recently-filed petition against the '263 patent exists in the 2026 pipeline.
Proceedings overview
There are zero (0) AIA trial proceedings on US 12,536,263. No IPR, PGR, or CBM has ever been filed against this patent, so there is no breakdown by status — no claims invalidated, none sustained, nothing settled, no institution denied. This is consistent across the canonical USPTO ODP-derived list in the prompt and every public source I could reach (Docket Alarm, IP Verse, PTAB E2E/Trial-institute listings).
The defensive posture this gives a defendant is therefore neither "hardened" nor "gutted" — it is untested. Nothing about the validity of claims 1–20 has been adjudicated at the Board. Two things materially soften the usual "the patent must be strong or it would have been IPR'd" inference: (1) the patent only issued on 2026-01-27, so the § 311(c) nine-month window has not yet run — the earliest lawful IPR petition date is approximately 2026-10-27; and (2) the one time Apple went to the Board against this patent owner, it settled rather than fight to a Final Written Decision.
⚠️ Critical scoping note: The single PTAB proceeding involving this patent owner — IPR2023-00833 — is against US 11,042,623, a different patent. It is not a proceeding on '263 and I do not count it as one. I include it below solely because it is the highest-value available intelligence about how this patent owner and Apple behave in AIA trials.
IPR2023-00833 — Apple Inc. v. FaceToFace Biometrics, Inc. ⚠️ (different patent — US 11,042,623, not US 12,536,263)
- Type: Inter Partes Review
- Filed: 2023-04-17
- Patent challenged: U.S. Patent No. 11,042,623 B2 ("Expression recognition in messaging systems") — a sibling of the '263 patent: same assignee (FaceToFace Biometrics, Inc.), same inventors (Eric Leuthardt; Scott Stern), same 2014-03-10 priority date to the common provisionals, but a separate continuation family (application 16/831,432).
- Status: Terminated-Settled (verbatim from the structured aggregator data: "Terminated-Settled"; IP Verse).
- Judge panel: Administrative Patent Judges Hyun J. Jung, Scott A. Daniels, and Cynthia L. Murphy; Judge Murphy authored the institution decision.
- Petition grounds: Apple requested review of claims 1–20. Grounds were § 102 / § 103 over, among others, U.S. Pub. 2013/0235045 (Corazza), U.S. Patent 8,620,850 (Brown), U.S. Patent 9,256,748 (Gates), U.S. Pub. 2006/0015812 (Cunningham), and U.S. Pub. 2004/0018858 (Nelson). Apple applied a 2014-03-10 priority date for the challenged claims.
- Institution decision: Instituted 2023-11-17. The panel found "a reasonable likelihood that [Petitioner] would prevail in establishing the unpatentability of at least independent claim 1 of the Challenged Patent." Patent Owner did not file a Preliminary Response. The parties identified the parallel E.D. Mo. case (4:22-cv-00429) and its Federal Circuit appeal (2023-1792) as related matters, and the panel expressly noted that in that district court case "summary judgment was granted to Petitioner on the basis that the asserted claims were not drawn to patent-eligible subject matter under 35 U.S.C. § 101." Source: Institution Decision, IPR2023-00833, Paper 7 (2023-11-17)
- Final Written Decision: None issued. The trial never reached the merits. Accordingly, no claim of the '623 patent was canceled or sustained by the Board, and the FWD record is silent on claims 1–20.
- Settlement / termination: The parties signed a settlement agreement 2024-04-30; a Joint Motion to Terminate was filed 2024-06-03 under 35 U.S.C. § 317 and 37 C.F.R. §§ 42.72, 42.74, asserting the agreement "completely resolves all pending controversies between Apple and FaceToFace concerning U.S. Patent No. 11,042,623." A concurrent Joint Request to Treat Settlement Agreement as Business Confidential Information was filed, and the agreement itself was lodged as confidential EX1019. The Board granted termination on 2024-06-13. Terms are confidential. Source: Joint Motion to Terminate, Paper 13; Termination Decision, Paper 15 (2024-06-13)
- Appeal: None. No FWD means nothing to appeal. (The only Federal Circuit activity in this portfolio, Appeal No. 2023-1792, FaceToFace Biometrics, Inc. v. Apple Inc., was the appeal of the § 101 summary judgment on the '623 patent — dismissed under Fed. R. App. P. 42(b), each side bearing its own costs, 2023-06-26 — not an appeal of any Board decision. Nonprecedential order)
- Defensive value: Low-to-moderate, and indirect. Because there was no FWD, no § 315(e) estoppel attached to Apple — the settlement bought peace, not estoppel, and Apple is not barred by the Board from re-raising the same art elsewhere. The more useful signal is behavioral: Apple filed only one petition against FaceToFace's portfolio ("Apple has filed no other petitions to institute inter partes proceedings concerning patents owned by FaceToFace," per the joint motion) and then bought its way out rather than litigate to judgment. For a defendant being sued on '263, that suggests this patent owner is settlement-oriented, and that the Board route was never road-tested against the Leuthardt/Stern priority-2014 disclosure.
Strategic summary
Claim status on US 12,536,263: all 20 claims UNTESTED. Claims 1 and 20 (device), 11 (method), and 18 (CRM) — the three independent claims and their dependents — have never been construed by the Board, never been the subject of an institution decision, and never appeared in any FWD. There are no canceled claims and no sustained claims on this patent. Any statement that claims of '263 "survived" or were "invalidated" at the PTAB would be false. The earlier-generated sections of this analysis reach the same conclusion and I find no contradiction.
Estoppel landscape: § 315(e)(2) estoppel is currently a non-factor. Estoppel under § 315(e) is triggered only by a final written decision, and no FWD exists on '263 (or on any FaceToFace patent). For a defendant now being asserted against in FaceToFace Biometrics, Inc. v. Apple Inc., No. 4:26-cv-01534 (E.D. Mo.), every prior-art ground is still available — in an IPR, in an ex parte reexam, and in district court. There is also no IPR to piggyback on or "join" under § 315(c), and no Board claim construction to adopt. On the flip side, the patent owner has no estoppel-based shield either: FaceToFace was not estopped by the '623 settlement, and it has not been estopped on '263.
Pattern signals:
- No serial-petitioner pattern. Apple has filed exactly one AIA petition against FaceToFace; there is no second, third, or follow-on petition against any face of this portfolio. IP Verse's competitive data (last updated 2026-08-17) lists FaceToFace with "PTAB Cases Faced: 1" and "PTAB Cases Filed: 0" — i.e., the company has never itself been a petitioner.
- No defensive aggregator in the chain. I found no Unified Patents, RPX, or other aggregator petition against any FaceToFace patent. (Unified appears in the 2026 landscape only as a general petitioner/exam requester in other matters.)
- Patent owner does not litigate PTAB appeals aggressively. FaceToFace's only Federal Circuit appearance in this portfolio, 2023-1792, was a voluntary Rule 42(b) dismissal with each side bearing its own costs — a negotiated exit, not a merits fight, and the dismissal order does not state whether it was with or without prejudice.
- Enforcement, not defense, is this owner's mode. FaceToFace is an operating company/NPE-adjacent enforcer (per aggregators: "Patent Owner / Operating Company") that asserts in E.D. Mo. and settles.
Recommended next steps
If you are a defendant and the patent has claims invalidated: it does not. There is no FWD to link to and no disposition to quote. Do not represent to a court or adversary that any claim of '263 has been held unpatentable; the only § 101 invalidity ruling in this portfolio (FaceToFace Biometrics, Inc. v. Apple, Inc., No. 4:22-cv-00429-CDP (E.D. Mo. 2023-03-17)) struck the '623 patent, and its related appeal was dismissed by agreement.
If you are considering an IPR on '263 — the timing is not yet yours to choose. Under 35 U.S.C. § 311(c), an IPR petition may be filed only after the later of (1) nine months after grant or (2) termination of any instituted PGR. The '263 patent issued 2026-01-27, so the earliest filing date is approximately 2026-10-27. Separately, service of the 4:26-cv-01534 complaint — source-reported as 2026-09-28, same date caveat as the earlier sections of this analysis — starts the § 315(b) one-year clock, which would close on or about 2027-09-28. A defendant therefore has a widening, but finite, window.
Trial-stage milestones: not applicable — no trial is pending. If a petition is filed after 2026-10-27, the ordinary cadence applies: PO Preliminary Response (~3 months), institution decision by ~6 months, PO Response, Petitioner Reply, Oral Hearing (~12 months), and a statutory FWD deadline of one year from institution (extendable up to six months for good cause). Watch for § 314(a) Fintiv-type discretionary-denial arguments tied to the E.D. Mo. case, and for the panel's treatment of the 2014 priority date — Apple's own '623 petition applied 2014-03-10, so the effective filing date is likely to be contested terrain again.
Also on your radar: given the 2025–2026 contraction in IPR institution rates described in the current practitioner literature (monthly IPR filings bottoming at ~22 in June 2026, institution grant rate 47.4% in June 2026 on a small base, and an all-time-high 336 ex parte reexam requests in Q2 2026), an ex parte reexamination may be the more viable validity channel for this patent — it carries no § 315(b) bar, no estoppel, permits anonymous filing, and is not subject to the § 311(c) nine-month gate.
Bottom line: there is no AIA trial history on US 12,536,263 — none. The absence is itself the signal. The patent is four months old and still inside its § 311(c) waiting period, so the missing IPR tells you nothing about its strength. The one Board proceeding in this portfolio (IPR2023-00833, on a sibling patent) ended in a confidential settlement after institution and before any merits ruling, leaving no estoppel, no claim construction, and no claim-level outcome to rely on. Treat '263 as a clean slate: validity positions are wide open, but so is the downside, because no tribunal has yet tested these claims.
Generated 9/30/2026, 4:01:59 AM
Ownership chain (1)
Asserters network →Structured records extracted from the assignment-history narrative below. Each entity links to its full ownership-network profile.
? · recorded 2024-05-03 · Assignment
Leuthardt, Eric; Stern, ScottFaceToFace Biometrics, Inc.
founder-to-company assignment
Assignment history
Inventors, original assignee, and the chain of ownership recorded with the USPTO — including the correspondent attorney who recorded each assignment, since shell-LLC chains often share one repeat-player attorney even when the entity names look unrelated. Surfaces NPE / patent-troll patterns: shell-entity transfers, known asserters in the chain, repeat correspondent fingerprints, pre-litigation assignments, and bankruptcy fire-sales.
I'll research the ownership chain, the assignee entity, and any NPE designation. Let me run several targeted searches.
Let me dig into the assignment record specifics and the corporate/entity background.
Inventors
| Inventor | Address of record | Employer at time of filing |
|---|---|---|
| Eric Leuthardt | St. Louis, MO | Not stated in the assignment record. The patent lists only a city. Widely reported as a Washington University in St. Louis neurosurgeon; I did not independently verify his employer in this session, so treat that as unconfirmed. |
| Scott Stern | St. Louis, MO | Not stated in the assignment record. Appears alongside Leuthardt as co-inventor on every patent in this family (e.g., the sibling '623 patent, US 11,042,623 B2, lists "Eric Leuthardt, St. Louis, MO (US); Scott Stern, St. Louis, MO (US)"). |
Unusual-pattern check:
- No inventor departure signal. The two inventors personally executed the conveyance to FaceToFace Biometrics, Inc. They are the same two inventors across the entire family (US 9,817,960 → '650 → '653 → '776,616 → '263), so there is no thinning of the inventorship team over the decade-long prosecution chain.
- The relevant pattern here is the inverse of a fire-sale tell: the named inventors are the assignors to the company, i.e., they are the founders/principals conveying rights into their own vehicle, not employees who walked away. I found no evidence either inventor ever assigned away from FaceToFace Biometrics or to any third party.
- ⚠️ Data gap: the Assignment Center record would confirm this (reel/frame plus execution date). I could not retrieve the reel/frame or the correspondent of record in this session — see "Assignment timeline."
Original assignee
FaceToFace Biometrics, Inc. — named as both original and current assignee. Source: Google Patents legal events for US 12,536,263 and the sibling companion record at https://www.ipqwery.com/ipowner/en/owner/ip/[445914](/patent/445914)-facetoface-biometrics-inc.html (which lists the inventor pair Leuthardt/Stern and owner "FACETOFACE BIOMETRICS, INC." across the family).
- Entity type / domicile: A Delaware corporation with principal place of business in the Eastern District of Missouri (St. Louis). Verbatim from FaceToFace's own complaint in FaceToFace Biometrics, Inc. v. Apple Inc., No. 4:22-cv-00429 (E.D. Mo.): "FacetoFace is a Delaware Corporation with its principal place of business in this judicial district." The '623 patent front page lists the applicant as "FaceToFace Biometrics, Inc., St. Louis, MO (US)."
- Primary line of business: Facial-recognition / expression-recognition software for electronic messaging. All of the entity's grants are classified in G06V (Image or Video Recognition or Understanding). Portfolio analytics (PlainPatent / USPTO PatentsView) show 6 granted patents across 5 technology areas, grant years 2017–2024; a PatSnap snapshot reports 9 patents total. Either way, this is a micro-portfolio (rank ~#40,154 of ~49,997 tracked US assignees).
- Did they ship a product embodying the claims? No product evidence found. I found no commercial release, App Store listing, marketing site, pricing page, or customer reference for a FaceToFace Biometrics messaging application. What the record does show is enforcement: FaceToFace asserted the '623 patent against Apple (Memoji/iMessage) in 2022 and now asserts the '263 patent in FaceToFace Biometrics, Inc. v. Apple Inc., No. 4:26-cv-01534 (E.D. Mo.), per the dockets discussed in the earlier sections of this analysis. Absence of a product is a negative finding, not proof of non-commercialization — but it is uncontradicted.
- Current status: Operating as an active patent enforcer; not dissolved and not in bankruptcy. No Chapter 7/11 filing, no receivership, and no dissolution surfaced. Note that the earlier "Patent summary" and "Litigation summary" sections already flagged a date discrepancy around the 2026 complaint (source-reported 2026-09-28 vs. the task's stated current date); that discrepancy carries over here and I do not resolve it.
Assignment timeline
One recorded assignment exists for US 12,536,263 — the founder conveyance to FaceToFace Biometrics, Inc., recorded on the application filing date. There are no post-issuance assignments and no transfers to any other entity.
2024-05-03 (executed date not retrievable) / recorded 2024-05-03 — Reel NNNNNN/NNNN ⚠️ reel/frame not surfaced in the fetched record
- Conveyance: Assignment of assignor's interest ("ASSIGNMENT OF ASSIGNOR'S INTEREST")
- Assignor: Leuthardt, Eric; Stern, Scott
- Assignee: FaceToFace Biometrics, Inc.
- Correspondent: ⚠️ not retrieved. The USPTO Assignment Center record exposes a correspondent of record; I was unable to retrieve the attorney/firm name in this session. I will not guess it.
- Context: Founder-to-company assignment executed concurrently with the filing of continuation application 18/654,228 — a routine title-clearing step, not an acquisition, fire-sale, securitization, or transfer-to-asserter.
Source for the event: Google Patents legal events for US 12,536,263 ("2024-05-03 Assigned to FaceToFace Biometrics, Inc. — reassignment — FaceToFace Biometrics, Inc. — ASSIGNMENT OF ASSIGNOR'S INTEREST — Assignors: STERN, SCOTT, LEUTHARDT, ERIC"), which mirrors the underlying USPTO assignment record. Verify directly at https://assignmentcenter.uspto.gov/ (search by patent number 12536263 or application 18/654,228).
Per your instruction, I am not stopping after this section — a record does exist — but two things you asked for are missing from the retrievable data: the reel/frame and the correspondent of record. Those are the two highest-value fields for the repeat-correspondent analysis, and neither was available to me. Flags:
- No predecessor instrument for this patent appears in the record. The '263 patent is the fifth continuation in a chain (14/643,800 → '960 → '650 → '653 → '776,616 → 18/654,228). If the USPTO Assignment Center shows a repeat correspondent filing an "ASSIGNMENT OF ASSIGNOR'S INTEREST" on each continuation's filing date, that recurrence would be a genuine pattern tell. I could not confirm this — it is the single most useful open query.
- No security interest, license, merger, change-of-name, or release was recorded against this patent. Notably, there is no security agreement encumbering the patent, which means there is no public evidence of third-party litigation funding secured by the patent — a commonly checked troll-financing tell.
- No SEC filings. FaceToFace Biometrics, Inc. is a private Delaware corporation; nothing in SEC EDGAR surfaced. I could not trace ownership to any public-company parent.
Timeline diagram
timeline
title Ownership of US 12536263
2014 : Provisionals filed by Leuthardt and Stern
2015 : First non-provisional filed in family
2017 : US 9817960 issued in family
2024 : Inventors assign to FaceToFace Biometrics
: Continuation application 18 654 228 filed
2026 : US 12536263 issued
: Suit filed against Apple
NPE / troll-pattern signals
1. Shell-entity transfer — NOT PRESENT.
The patent was never moved from an operating assignee to a licensing-only LLC. Title passed exactly once, from the individual inventors to FaceToFace Biometrics, Inc. (recorded 2024-05-03), and has sat there since. Google Patents lists FaceToFace Biometrics, Inc. as both original and current assignee. There is no "IP / Patents / Licensing / Holdings / Ventures" transferee anywhere in the chain — because there is no transferee at all. Note the important negative: a Delaware incorporation is not, by itself, a shell indicator, and I do not treat it as one.
2. Known asserter in the chain — PRESENT (strong).
FaceToFace Biometrics, Inc. is publicly designated an NPE by a recognized defensive aggregator. Verbatim: "a new PATROLL contest, with a $2,000 cash prize, was added seeking prior art on at least claim 11 of U.S. Patent 11,042,623, owned by FaceToFace Biometrics, an NPE," published 2022-06-08 (contest opened 2022-05-27). Source: https://www.unifiedpatents.com/insights/2022/6/8/2000-for-facetoface-biometrics-prior-art. Corroboration: RPX tracks the same owner's assertion campaign as patent litigation (FaceToFace Biometrics, Inc. v. Apple, Inc., 4:22-cv-00429, E.D. Mo., filed 2022-04-13) at https://litigation.rpxcorp.com/litigation/moedce-[194966](/patent/194966)-facetoface-biometrics-v-apple; and industry press (Biometric Update, 2022-04) reports Patently Apple characterizing FaceToFace as a "patent assertion entity." Caveat: FaceToFace is not one of the enumerated aggregators (Acacia, Marathon, IV, IPNav, Wi-LAN, Conversant, Vringo, Pendrell, Round Rock, etc.) — it is an original-owner asserter surfaced by Unified Patents/RPX, which is exactly the category signal 2 also captures.
3. Repeat correspondent across the chain — UNKNOWN / INSUFFICIENT DATA.
There is only one recorded assignment in this chain, so recurrence within the chain is definitionally absent (a single appearance is not a finding, per your rule). The upstream question — whether the same attorney/recording firm handled the assignments for the four earlier continuations ('960, '650, '653, '776,616) — is the one I could not answer: the correspondent-of-record field was not retrievable, and the reel/frame was not surfaced either. This is the material data gap in the analysis. Separately, and not a correspondent finding: litigation counsel Anthony G. Simon (The Simon Law Firm, P.C., St. Louis) recurs across FaceToFace's suits against Apple; litigation counsel of record is not the same as an assignment correspondent and I do not score it as signal 3.
4. Cascading transfers — NOT PRESENT.
Zero consecutive assignments, zero chained LLCs, and no common-principal assignee network — because there are zero transfers after the founding assignment. Nothing here resembles a <24-month multi-hop chain.
5. Pre-litigation transfer — NOT PRESENT.
No assignment is dated within 6 months of the 2026 complaint. The sole instrument (recorded 2024-05-03) predates the FaceToFace v. Apple assertion of the '263 patent by roughly two years, and it was a founder conveyance into the original owner — not a venue/standing-clearing transfer. This is the tell that is characteristically missing in clean original-owner assertion cases like this one.
6. Bankruptcy fire-sale — NOT PRESENT.
No Chapter 7/11, no assignment-for-the-benefit-of-creditors, no § 363 sale, no court-approved patent sale order involving FaceToFace Biometrics, Inc. or either inventor. No Kodak/Nortel/Polaroid-style event.
7. Privateering — NOT PRESENT.
Privateering requires an operating company to transfer patents to an NPE that asserts against the operating company's competitors. Here the inventors' own company is the asserter, and no upstream operating-company funder is visible in the chain or in any SEC filing. I found no evidence of a manufacturer or platform company directing this campaign. Note the nuance flagged below — FaceToFace may be a failed startup that pivoted to assertion, which is a different (and unverifiable-here) story from classic privateering.
8. Defensive aggregator — NOT PRESENT.
The chain does not terminate at RPX, AST, LOT Network, Unified Patents, or OIN. The inverse is true: Unified Patents ran a cash bounty against this owner's sibling patent in 2022, i.e., the defensive ecosystem is arrayed against this patent, not absorbing it.
Verdict
NPE — moderate confidence.
FaceToFace Biometrics, Inc. holds every claim of US 12,536,263 with no corporate parent, no product, and no recorded license — and the patent has been asserted against Apple in FaceToFace Biometrics, Inc. v. Apple Inc., No. 4:26-cv-01534 (E.D. Mo.), consistent with its 2022 campaign on the sibling '623 patent. That is one strong signal (signal 2: a recognized defensive aggregator, Unified Patents, publicly designated this exact owner "an NPE" on 2022-06-08, with RPX tracking the same campaign), and it is reinforced by the complete absence of any encumbrance, securities filing, or product. The conviction stays at moderate rather than high because the classic chain-based tells are all absent for an unusual reason: title never moved past the sole 2024-05-03 founding assignment (Google Patents legal events), so there is no shell transfer, no cascading LLC chain, and no pre-litigation transfer to cite — the entity asserts as original owner, which is the archetypal NPE posture but leaves me without the second independent signal your framework wants for high confidence. The most important open thread: I could not retrieve the reel/frame or correspondent of record for that 2024-05-03 instrument; if Assignment Center shows a single recurring correspondent across the five continuations in this family, that recurrence would likely upgrade the call.
Verification link: https://assignmentcenter.uspto.gov/ (search patent number 12536263, or application 18/654,228); mirrored index at https://assignment.uspto.gov/patent/index.html and legal events at https://patents.google.com/patent/[US12536263B2](/patent/US12536263B2)/en.
Consistency check against earlier sections: No contradiction with the prior "Patent summary" and "Litigation summary" sections — both correctly identified FaceToFace Biometrics, Inc. as original and current assignee, and this analysis confirms there is no intervening owner. The only open inconsistency remains the previously flagged 2026 complaint date discrepancy, which is unchanged by anything found here.
Caveats: (a) Reel/frame and correspondent are not fabricated — they were unavailable, and I have marked them as such rather than inventing them. (b) Characterization of FaceToFace as an NPE rests on third-party designations (Unified Patents, RPX, press), not on a court holding. (c) Absence of product evidence is a negative finding; a low-profile commercial offering cannot be conclusively excluded.
Generated 9/30/2026, 4:02:39 AM
Prior art
Earlier patents, publications, and products that may anticipate or render the claims unpatentable.
I'll research the prior-art citations for US 12,536,263. Let me run several targeted searches, starting with the patent's own citation record.
Let me retrieve the remaining citations and verify specific high-relevance references.
Let me attempt to retrieve the remaining portion of the citation list.
Prior Art for US 12,536,263 — Citation-by-Citation § 102 Analysis
Scope and method — read this first
I was asked to look at each patent citation of US 12,536,263. Two constraints shaped what follows, and I will not paper over them:
- The authoritative source text supplied for this task is truncated. The patent's front-matter citations block is styled "Citations (80)" (backward citations), but the fetched text stops partway through the list — the final visible entry is US 2011/0125844 A1 (Telcordia Technologies). I can therefore account for roughly 31 of the 80 cited references, and I have verified several of them against independent sources. I did not retrieve the remaining ~49 references (I hit the session step limit). I am not going to invent citations to fill the gap.
- The patent's own "Families Citing this family (54)" list is a forward-citation / family list, not prior art. Entries such as US10275583B2 and US9817960B2 (both FaceToFace's own) are the patent owner's own family members; I exclude them from § 102 analysis.
A mechanical but decisive point on legal posture: the '263 patent issued on 2026-01-27 over this exact art. Every reference below was before the examiner during prosecution of this continuation (or a family member). That means most of these references were cited as background or § 103 fodder, and a clean single-reference § 102 anticipation story is unlikely on the face of the record. Where a reference gets close to a limitation, I say so; where it does not, I say so.
Effective filing date for priority purposes: 2014-03-10. All references below published/filed well before that date and therefore qualify as prior art under AIA § 102(a)(1) (publication before the effective filing date) and/or § 102(a)(2) (U.S. patent/application effectively filed earlier).
The granted claims I am measuring the art against
Independent claims 1 (device), 11 (method), 18 (CRM) share four limitations:
- (A) receive, at the receiver device from a sender device, an electronic message having (i) content and (ii) identifying information of the sender;
- (B) in response to the message and independent of any user interaction, simultaneously display a privacy shield and the sender's identifying information;
- (C) validate biometric data of the user against a stored biometric profile of the user;
- (D) remove the privacy shield and display the content if the user's biometric data is validated.
Dependents: 2/12/19 (sensor-detected biometric; 19 adds facial profile), 3/13 (facial profile), 4/14 (monitor sensor feed), 5/15 (>1 individual → prevent display), 6 (smartphone), 7/16 (MMS), 8/17 (prevent display until validated), 9 (reveal while screen stays locked), 10 (lock-screen view), 20 (shield adjacent to sender ID).
Full citation list (verified portion), with § 102 relevance
Legend: *=Cited by examiner (per the patent text's own convention). "Anticipate?" = whether the reference could plausibly anticipate, alone, any claim of '263.
| # | Citation | Inv./Applicant | Title | Priority / Pub. date | Brief description | Potentially anticipates (§ 102)? |
|---|---|---|---|---|---|---|
| 1 | US 2002/0019852 A1 | Bahar, Reuben | Method and system for confirming proper receipt of e-mail transmitted via a communications network | 1999-12-15 / 2002-02-14 | Confirms delivery/receipt of e-mail | No. Only tangentially touches limitation (A) "receive message." No shield/biometric. |
| 2 | US 2002/0116508 A1 * | Khan, Sal | Method for secure transmission and receipt of data over a computer network using biometrics | 2001-02-20 / 2002-08-22 | Biometric-authenticated secure transmission and receipt of data over a network | Partial. Could anticipate limitation (C) (biometric validation gating access to received data) but not (B) shield. Weak standalone § 102; strong § 103. |
| 3 | US 2003/0014372 A1 * | Wheeler, Lynn Henry | Trusted authentication digital signature (TADS) system | 2000-08-04 / 2003-01-16 | Biometric-keyed digital signatures | No (auth only). § 102 candidate for (C) element in combination. |
| 4 | US 2003/0115151 A1 * | Wheeler, Lynn Henry | Person-centric account-based digital signature system | 2000-08-04 / 2003-06-19 | Account/person-centric signature infrastructure | No. Same family as #3. |
| 5 | US 2003/0135740 A1 * | Talmor, Eli | Biometric-based system and method for enabling authentication of electronic messages sent over a network | 2000-09-11 / 2003-07-17 | Biometric authentication applied specifically to electronic messages sent over a network | Partial. Discloses (A)+(C) for messages; does not disclose the auto-triggered privacy shield (B). § 103 candidate. |
| 6 | US 2003/0214535 A1 | Motorola (Hymel) | User interface for a messaging device and method | 2002-05-14 / 2003-11-20 | Messaging UI | No. Background. |
| 7 | US 2004/0018858 A1 | Nelson, Jonathan O. | Emoticon input method and apparatus | 2001-08-17 / 2004-01-29 | Emoticon input — Apple IPR2023-00833 reference (against sibling '623) | No as to '263 claims. Emoticon art. |
| 8 | US 6,836,846 B1 | International Business Machines | Method and apparatus for controlling e-mail access | 1999-10-21 / 2004-12-28 | Controls access to e-mail | Partial. Conceptually relevant to gating access to message content (D); no biometric, no shield UI. § 103 candidate. |
| 9 | US 6,873,710 B1 | Koninklijke Philips Electronics | Method and apparatus for tuning content of information presented to an audience | 2000-06-27 / 2005-03-29 | Audience-dependent content presentation | No. Background. |
| 10 | US 2005/0144451 A1 * | Entrust Limited | Method and apparatus for providing electronic message authentication | 2003-12-30 / 2005-06-30 | Electronic message authentication | No standalone; (C)-type element. |
| 11 | US 2005/0195927 A1 | Solonen, Juha | Method and apparatus for conveying messages and simple patterns in communications network | 2002-04-26 / 2005-09-08 | Messaging patterns | No. Family background. |
| 12 | US 2005/0251688 A1 | Nanavati, Samir H. | Identity verification method using a central biometric authority | 1999-05-14 / 2005-11-10 | Biometric identity verification against a stored authority | Partial. Maps onto (C) "stored biometric profile"; no message-shield (B). § 103 candidate. |
| 13 | US 2006/0015812 A1 | Cingular Wireless II (Cunningham) | Using emoticons, such as for wireless devices | 2004-07-15 / 2006-01-19 | Emoticons — Apple IPR2023-00833 reference (against '623) | No as to '263. Emoticon art. |
| 14 | US 2006/0075028 A1 * | Zager, Robert P. | User interface and anti-phishing functions for an anti-spam micropayments system | 2004-09-07 / 2006-04-06 | User-interface/anti-phishing | No. Background. |
| 15 | US 2006/0206725 A1 * | Milgramm, Michael | System and method for platform-independent biometrically verified secure information transfer and access control | 2002-04-23 / 2006-09-14 | Biometrically verified secure information transfer AND access control | Partial-to-moderate. Discloses biometric verification gating transfer/access of information, i.e., elements (C)+(D) in a communications context. Does not clearly show the auto-displayed dual shield+sender-ID screen (B). Best read as § 103. |
| 16 | US 2006/0282466 A1 | Konica Minolta Business Technologies | Image processing apparatus and image processing system | 2005-06-09 / 2006-12-14 | Image processing | No. |
| 17 | US 7,165,268 B1 * | Moore, Keith E. | Digital signatures for tangible medium delivery | 2000-10-17 / 2007-01-16 | Digital signatures | No. |
| 18 | US 2007/0074270 A1 * | Essential Security Software | Method and system for digital rights management of documents | 2005-09-28 / 2007-03-29 | DRM / access control of documents | Partial. Relevant to content-access control (D); no biometric, no message shield. § 103. |
| 19 | US 2007/0208610 A1 | Miva, Inc. | System and method for delivering advertising with enhanced effectiveness | 2006-03-06 / 2007-09-06 | Advertising | No. |
| 20 | US 2008/0218472 A1 | Emotiv Systems Pty. | Interface to convert mental states and facial expressions to application input | 2007-03-05 / 2008-09-11 | Facial-expression sensing as input | No standalone. Touches facial-biometric sensing only. |
| 21 | US 7,472,351 B1 * | Zilka, Kevin J. | E-mail manager interface with integrated instant messaging and phone call initiator feature | 2004-08-18 / 2008-12-30 | E-mail manager UI | No. |
| 22 | US 2009/0016617 A1 | Bregman-Amitai, Orna; Karmon, Nili (Samsung Electronics) | Sender dependent messaging viewer | 2007-07-13 / 2009-01-15 | Mobile device receives an electronic message and displays a sender-associated digital image (edits it per message text) | Partial. Directly discloses limitation (A)+( "identifying information of the sender" displayed on message receipt). No biometric shield. Useful § 103 partner for element (B). |
| 23 | US 2009/0141895 A1 * | Anderson, William R. (Oculis Labs) | Method and apparatus for secure display of visual content | 2007-11-29 / 2009-06-04 | Displays visual content comprehensible only to an authorized user | Partial-strong. Discloses a "privacy shield" for on-screen content tied to viewer authorization, i.e., element (B)/(D). No message-receipt trigger, no sender ID. § 103 candidate; possible § 102 on narrower shield-dependent claims only if combined content is read in. |
| 24 | US 2009/0171895 A1 * | Hackmann, Herbert | Method and system for generating dynamic associations to data objects | 2007-12-28 / 2009-07-02 | Dynamic data associations | No. |
| 25 | US 2010/0014720 A1 | Hoyos, Hector T. | Fraud Resistant Biometric Financial Transaction System and Method | 2006-10-02 / 2010-01-21 | Biometric transaction authentication | No standalone; (C)-type. |
| 26 | US 7,698,745 B2 | Voltage Security | Secure message system with remote decryption service | 2003-09-25 / 2010-04-13 | Secure message system with remote decryption | Partial. Content protection/controlled reveal (D); no biometric shield. § 103. |
| 27 | US 2010/0125799 A1 | Palo Alto Research Center (Roberts) | Physical-virtual environment interface | 2008-11-20 / 2010-05-20 | Environment interface | No. |
| 28 | US 2010/0141662 A1 | Amegoworld, Ltd. (Storey) | Communication network and devices for text to speech and text to facial animation conversion | 2007-02-05 / 2010-06-10 | Text-to-facial-animation | No. Family background. |
| 29 | US 2010/0177116 A1 | Sony Ericsson | Method and arrangement for handling non-textual information | 2009-01-09 / 2010-07-15 | Non-textual info handling | No. |
| 30 | US 2010/0205667 A1 * | Oculis Labs (Anderson, Turner, Pujia) | Video-Based Privacy Supporting System | 2009-02-06 / 2010-08-12 | Image sensor collects facial-recognition data proximate to the computer; a user security-parameter database stores profiles; a security processor controls the input/output device based on the facial-recognition data and the stored security parameters | STRONGEST candidate. Discloses (C) — facial recognition of the user validated against a stored profile — and (D) — controlling the display based on that validation. Missing only the message-receipt trigger and sender-ID display (A)/(B). Best § 103 primary reference. |
| 31 | US 2011/0125844 A1 | Telcordia Technologies (Collier et al.) | Mobile enabled social networking application to support closed, moderated group interactions for purpose of facilitating therapeutic care | 2009-05-18 / 2011-05-26 | Mobile, privacy-focused secure messaging/social network | Marginal. Touches "private, safe and secure" mobile communication but no biometric shield or sender-ID display. Background. |
⚠️ Gap. The remaining ~49 cited references (the list runs past US 2011/0125844 A1, including later-published art such as US 2013/… and US 2014/… documents that would be the most date-proximate to the 2014 priority date) were not retrievable and are not represented above. Their omission is a limitation of this analysis, not a finding that they are irrelevant.
§ 102 anticipation analysis — ranked
Tier 1 — closest to the granted claims (still short of full anticipation)
US 2010/0205667 A1 — Oculis Labs (Anderson, Turner, Pujia), "Video-Based Privacy Supporting System," pub. 2010-08-12.
Per the abstract and specification: an image sensor collects facial-recognition data near the computer, a security-parameter database encodes user security parameters, and a security processor controls the data input/output device in response to the facial-recognition data and the security parameters — including "preventing viewing of some or all of the display" when the authorized user's attention shifts.
- Potentially anticipates: element (C) and (D) of claims 1/11/18; and, in isolation, the subject matter of dependents 3/13 (facial profile) and arguably 5/15 (detecting the presence of another person near the device — the reference expressly addresses a person entering the office seeing the display).
- Does not disclose (A) receipt of an electronic message with a sender identifier, or (B) the automatic, user-interaction-independent simultaneous display of a privacy shield plus the sender's identifying information.
- Bottom line: this is the natural § 103 primary reference for the facial-validation + display-gating core, not a standalone § 102 anticipant of claim 1. Source: https://ie.espacenet.com/publicationDetails/biblio?CC=US&NR=2010205667A1
US 2009/0141895 A1 — Oculis Labs (Anderson et al.), "Method and apparatus for secure display of visual content," pub. 2009-06-04.
Displays visual content so it is "comprehensible only to an authorized user." Same inventor family as above.
- Potentially anticipates: the "privacy shield" concept of (B)/(D) and the "comprehensible only to authorized user" predicate of dependents 8/17.
- Does not disclose message receipt, sender ID, or biometric validation per se.
US 2002/0116508 A1 — Sal Khan, "Method for secure transmission and receipt of data … using biometrics," pub. 2002-08-22 (examiner-cited).
- Potentially anticipates: element (C) and the notion of biometric gating before a recipient can access received data — relevant to claims 1/11/18 element (C)+(D) and dependent 2/12.
- Does not disclose the message-shield-plus-sender-ID auto-screen (B) or facial-profile specifics (3/13).
Tier 2 — disclose the "sender identifying information" limitation
US 2009/0016617 A1 — Samsung (Bregman-Amitai & Karmon), "Sender dependent messaging viewer," pub. 2009-01-15.
- Potentially anticipates: the (A) "identifying information of the sender" element — it receives an electronic message and displays a sender-associated digital image on the receiving mobile device. Useful for claims 1/11/18 limitation (A) and dependent 6 (smartphone).
- Does not disclose any privacy shield or biometric validation. This is the reference the patent owner would need to couple with an Oculis-Labs-type reference to build a § 103 case against claim 1.
Tier 3 — biometric authentication of messages / information transfer
- US 2003/0135740 A1 — Talmor, "Biometric-based system and method for enabling authentication of electronic messages sent over a network," pub. 2003-07-17 (examiner-cited). Touches (A)+(C) for messages; no shield UI. § 103.
- US 2006/0206725 A1 — Milgramm, "… platform-independent biometrically verified secure information transfer and access control," pub. 2006-09-14 (examiner-cited). Biometric verification gating information transfer and access control — elements (C)+(D) in a communication context. § 103.
- US 2005/0251688 A1 — Nanavati, "Identity verification method using a central biometric authority," pub. 2005-11-10. Maps to the "stored biometric profile" of (C). § 103.
- US 2003/0014372 A1 and US 2003/0115151 A1 — Wheeler (examiner-cited). Biometric digital-signature / person-centric account systems; (C)-type only.
Tier 4 — access/content-control background (weakly relevant to (D))
- US 6,836,846 B1 — IBM, "Method and apparatus for controlling e-mail access," pub. 2004-12-28.
- US 2007/0074270 A1 — Essential Security Software, DRM of documents, pub. 2007-03-29 (examiner-cited).
- US 7,698,745 B2 — Voltage Security, secure message system with remote decryption, pub. 2010-04-13.
These support only the generic idea of gating access to content; none has a biometric shield, and none is a credible standalone § 102 reference to claim 1.
Tier 5 — not prior art to the '263 claims (family/emoticon/UI background)
US 2004/0018858 A1 (Nelson, emoticons), US 2006/0015812 A1 (Cunningham, emoticons), US 2005/0195927 A1 (Solonen), US 2010/0141662 A1 (Amegoworld), US 2008/0218472 A1 (Emotiv), US 2003/0214535 A1 (Motorola), US 2007/0208610 A1 (Miva), US 6,873,710 B1 (Philips), US 2002/0019852 A1 (Bahar), US 7,165,268 B1 (Moore), US 7,472,351 B1 (Zilka), US 2009/0171895 A1 (Hackmann), US 2010/0125799 A1 (PARC), US 2010/0177116 A1 (Sony Ericsson), US 2010/0014720 A1 (Hoyos), US 2005/0144451 A1 (Entrust), US 2006/0075028 A1 (Zager), US 2006/0282466 A1 (Konica Minolta), US 2011/0125844 A1 (Telcordia). These are background or bear on non-limiting aspects (emoticon/expression handling, generic messaging UI, generic biometric auth) and do not anticipate any claim of '263 as issued.
Direct answer: does any cited reference anticipate a claim?
On the verifiable subset of the citation record, no single cited reference discloses all four limitations (A)–(D) of independent claims 1, 11, or 18. The closest reference (US 2010/0205667 A1, Oculis Labs) supplies the biometric-validation-against-a-stored-profile and display-gating core (C)+(D) but not the message-receipt, auto-display, and sender-identification elements (A)+(B). The closest reference for (A)+sender-ID (US 2009/0016617 A1, Samsung) supplies none of (B)–(D). That pattern — two references each covering a different half of the claim — is the signature of a § 103 obviousness case, not § 102 anticipation.
Claim-by-claim summary (§ 102 potential only):
| Claim | Best single-reference § 102 candidate on the visible record | Assessment |
|---|---|---|
| 1, 11, 18 | US 2010/0205667 A1 (partial) | No complete anticipation; § 103 combination more likely |
| 2, 12, 19 (sensor biometric / facial profile) | US 2010/0205667 A1 | Plausible (facial recognition via image sensor; stored profile) |
| 3, 13 (facial profile) | US 2010/0205667 A1 | Plausible |
| 4, 14 (monitor sensor feed) | US 2010/0205667 A1 | Plausible |
| 5, 15 (>1 individual) | US 2010/0205667 A1 | Plausible (addresses others near the display) |
| 6 (smartphone) | US 2009/0016617 A1 | Plausible |
| 7, 16 (MMS) | — | No verified single reference |
| 8, 17 (prevent display until validated) | US 2009/0141895 A1 | Plausible |
| 9, 10 (content shown while screen locked / lock-screen view) | — | No verified single reference on the visible record |
| 20 (shield adjacent to sender ID) | — | No verified single reference |
Uncertainty and honesty flags
- Incomplete citation record. Only ~31 of 80 cited references are visible in the authoritative text I was given; I could not retrieve the rest before hitting the step limit. Any conclusion that "no cited reference anticipates" is therefore conditional on the visible subset and could change with the full list.
- Issue-over-art inference. These references were before the examiner and the claims issued anyway, so their citation denotes relevance (background/§ 103), not anticipation. I have treated them accordingly.
- Asterisk convention. The patent's own key defines "*" as cited-by-examiner and "†" as cited-by-third-party; I applied it as printed.
- Do not confuse families. The Apple IPR2023-00833 grounds (Corazza US 2013/0235045, Brown US 8,620,850, Gates US 9,256,748, plus Nelson '858 and Cunningham '812) targeted the sibling '623 patent (US 11,042,623), not '263. Only Nelson '858 and Cunningham '812 appear within the '263 citation list I can see; the others do not appear here. This is consistent with the earlier-generated sections of this analysis, which flagged that all PTAB/Federal Circuit activity in the portfolio concerns the '623 patent.
- No contradiction identified with the previously generated "Patent summary," "Litigation summary," "PTAB challenges," or "Assignment history" sections. Where those sections relied on the truncated citation block, this analysis is consistent (they did not attempt a full citation-by-citation § 102 review).
Primary sources: patent text from https://patents.google.com/patent/[US12536263B2](/patent/US12536263B2)/en (Citations (80) block, truncated at US 2011/0125844 A1); reference details cross-checked against Google Patents/Espacenet pages for US 2010/0205667 A1, US 2009/0016617 A1, US 2009/0141895 A1, and US 2002/0116508 A1.
Generated 9/30/2026, 4:03:47 AM
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
I'll verify the key prior-art references and look for any additional art relevant to the narrow granted claims before drafting the § 103 analysis.
Let me verify the Apple IPR grounds art and look for additional art on lock-screen/message preview gating and auto-display of sender identity.
This is significant — Apple's own redacted-content application appears to predate the '263 priority date. Let me verify its dates and scope.
Obviousness Analysis — U.S. Patent No. 12,536,263 B2
35 U.S.C. § 103
Date of analysis: April 26, 2026 (task date)
Reference date used for the claims: earliest claimed priority, 2014-03-10 (provisional 61/950,423)
Art base: the Prior Art section of this analysis, plus references verified during this session
0. Scope, method, and what this analysis builds on
This section builds directly on the previously generated Patent summary, Litigation summary, PTAB challenges, Assignment history, Timeline diagram, NPE / troll-pattern signals, and Prior art sections. I do not repeat their content. Consistent with the Prior Art section, I treat the art record as partially truncated — only ~31 of the 80 front-matter citations were visible — and I flag where that gap matters.
Two things changed in this session relative to the Prior Art section, and both are material:
- I located an additional reference that was not in the '263 citation list as fetched — Apple's US 2014/0089441 A1 (and its granted counterparts US 9,721,107 B2 / US 10,289,852 B2 / EP 3 005 212 B1 / WO 2014/197112 A1), "Using biometric verification to grant access to redacted content." I verified its dates and its specification and claims from multiple mirrors. This is the single most dangerous reference to the '263 claims.
- I confirmed the bibliographic details of the two Oculis Labs references (US 2010/0205667 A1 → US 10,282,563 B2, now Tobii AB; and US 2009/0141895 A1 → US 8,462,949 B2), including the facial-recognition + stored-security-parameters + display-control architecture.
No contradiction with the prior sections. The Prior Art section's conclusion — that the visible art supports a § 103 case rather than clean § 102 anticipation — is reinforced, but the identification of Apple's '441 changes the strength of that case substantially for the independent claims.
1. Legal framework applied
- Governing statute: AIA § 103 (the claims have a post-2013-03-16 effective filing date). Graham v. John Deere Co., 383 U.S. 1 (1966) — scope and content of the prior art; differences; PHOSITA level; objective indicia.
- Obviousness standard: KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007) — a combination is obvious where the improvement is "the predictable use of prior art elements according to their established functions." A motivation to combine may be found in the art, in the nature of the problem, or in market/design incentives, and "any need or problem known in the field … can provide a reason."
- Pre-AIA § 103(c)/AIA § 102(b)(2)(C) common-ownership exception: not available — the strongest art (Apple's '441) is not commonly owned with FaceToFace Biometrics, Inc.
- § 102(a)(2) eligibility of Apple '441: it names another inventor (Apple's inventors) and was effectively filed 2013-06-08 (US 13/913,403), before the '263 claims' 2014-03-10 effective filing date. Under AIA § 102(a)(2)/§ 102(d) it therefore qualifies even though it published 2014-03-27, i.e. after the priority date.
- Standard of proof for the challenger: clear and convincing evidence to invalidate an issued patent. This is a litigation standard; the analysis below assesses whether the grounds are substantively strong enough to carry that burden, not whether they are certain to.
2. Person of ordinary skill in the art (PHOSITA)
A person having ordinary skill in the art as of March 2014 would have: a bachelor's degree in computer science, computer engineering, or electrical engineering (or equivalent), plus 2–3 years of experience designing mobile operating-system user interfaces, notification/messaging subsystems, or biometric authentication features, or a master's degree with ~1 year of such experience. That person would be familiar with: (a) front-facing cameras and face detection on smartphones; (b) storing and matching a biometric template on-device; (c) lock-screen notification rendering and the ability to selectively redact/gate notification content; and (d) the design space of "privacy screen" products then on the market (Oculis Labs' PrivateEye/Chameleon, cited as prior-art product literature in US 10,282,563).
This is a low-to-moderate skill level. The combination at issue is a UI/system-integration combination, not an algorithmic advance — which weighs toward obviousness.
3. Claim interpretation of the four limitations that matter
All three independent claims (1, 11, 18) recite the same four-step sequence. Under Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc), and using the specification as the primary guide:
| Limitation | Text | Construction |
|---|---|---|
| (A) | "receive, at the receiver computer device from a sender computer device, an electronic message having an electronic content and identifying information of the sender" | Receipt of a networked message bearing (i) payload and (ii) sender-attribution data (name, number, avatar, handle). |
| (B) | "in response to the electronic message and independent of any user interaction, instruct … to simultaneously display … a privacy shield and the identifying information of the sender" | The shield screen is auto-generated on arrival — no tap, swipe, launch, or unlock by the user. "Privacy shield" is broad: the spec defines it as "a screen lock, a scrambling of the message content, a blur of the message content, a blackout of the message content, an alert …, capturing of a photograph …, or any combination thereof." |
| (C) | "validate biometric data of the user in view of a stored biometric profile of the user" | Match sensor-captured biometric against a locally/remotely stored template belonging to the device's own user (= the recipient). Note "the user" has no antecedent other than "the receiver computer device" / "any user interaction" — see §3.1. |
| (D) | "remove the privacy shield … and … display … the electronic content … if the biometric data … is validated" | Conditional reveal gated on (C). |
3.1 The pivotal construction point: whose biometric?
The patent is titled "Message sender security in messaging system," and the abstract/specification at length describe a system in which the sender's permission settings constrain the recipient's device (biometric profiles "authorized by the message sender"; "privacy shields … customized by privacy settings dictated by the sender"). None of that is in the granted claims. The granted claims validate "biometric data of the user" against "a stored biometric profile of the user" — and the only "user" in the claim environment is the user of the receiver computer device.
This is the decisive § 103 insight: the granted claims are device-owner (recipient-side) privacy claims, dressed in sender-security language. They cover, in substance:
"A phone that receives a message, automatically shows a locked/redacted notification bearing the sender's name, matches the holder's face against the enrolled owner's template, and reveals the content on a match."
That functionality is what the 2009–2014 art is saturated with. The patent owner's title and specification cannot be used to narrow "the user" to the sender — such a reading would exclude the disclosed embodiment (Phillips; claim differentiation; and the written description describes the recipient's profile being used to unshield).
3.2 Two secondary construction notes
- "instruct, the receiver computer device" / "instruct, the receiver computer device to …" — Claim 1 is a device claim in which "the at least one processor is programmed to … instruct, the receiver computer device, to simultaneously display…". The processor is instructing its own host device. This is best read as a drafting artifact meaning "cause the device to display" (a processor issuing a display command to the display subsystem). It is not drafted in means-plus-function form and I would not expect § 112(f) to be triggered.
- Antecedent basis: "the user" and "the biometric data of the user" lack strict antecedent basis. Under Energizer Holdings v. ITC, 435 F.3d 1366 (Fed. Cir. 2006), a claim is not indefinite merely for that omission if the meaning is clear — here it is clear (the device user). This does not help the patent owner on § 103.
4. The art — what each reference teaches, and why it is art
Legend: [P] = printed publication/patent qualifying under § 102(a)(1); [A2] = U.S. application publication qualifying under § 102(a)(2) (effectively filed pre-2014-03-10 but published later). "Cited on '263?" reflects only the truncated citation block — see the caveat.
| # | Reference | Date | § 102 basis | Cited on '263? | What it teaches against the four limitations |
|---|---|---|---|---|---|
| R1 | US 2014/0089441 A1 (Apple Inc.), "Using biometric verification to grant access to redacted content" — also granted US 9,721,107 B2, US 10,289,852 B2, EP 3 005 212 B1, WO 2014/197112 A1 | Filed (US 13/913,403) 2013-06-08; pub. 2014-03-27 | [A2] (effectively filed 2013-06-08 < 2014-03-10; different inventors) | Not in the visible list (list truncated at 2011) — ⚠️ unknown/possibly not of record | All four limitations. Content-redaction engine decides whether to redact based on whether the user is biometrically verified; compares received biometric data to a stored set of verified user biometric data (C); messages displayed in lock-screen mode with "some or all of the message content" redacted unless verified biometric data is received, without requiring the user to unlock (B, D); and expressly — claim 9 / claim 21 — "a sender of the message is not redacted while at least a portion of the message is redacted when the biometric verification data indicates the user is not verified" (B: simultaneous shield + sender identity). Redaction = blur / black bar / removal (shield definitions). Biometric reader "includes a camera" / "scanning camera" (claims 2, 14). Source: https://www.freepatentsonline.com/y2014/0366158.html ; https://patents.justia.com/patent/[10552617](/patent/10552617) ; https://patents.google.com/patent/WO2014197112A1 |
| R2 | US 2010/0205667 A1 (Oculis Labs) / US 10,282,563 B2 (Tobii AB), "Video-Based Privacy Supporting System" | Prio. 2009-02-06; pub. 2010-08-12 | [P] | Yes — examiner-cited | Image sensor collects facial recognition data; user security parameter database encoding stored security parameters; security processor at least partially controls the data output device in response to the facial recognition data and the stored security parameters; detects the presence of a third party in a region behind the user and modifies the display accordingly (C, D, and → claim 5/15). CPC G06F 21/32 — same CPC as '263. Sources: https://ie.espacenet.com/publicationDetails/biblio?CC=US&NR=2010205667A1 ; https://patents.justia.com/patent/[10282563](/patent/10282563) |
| R3 | US 2009/0141895 A1 (Oculis Labs) / US 8,462,949 B2, "Method and apparatus for secure display of visual content" | Filed 2008-11-29; pub. 2009-06-04 | [P] | Yes — examiner-cited | Displays visual content "comprehensible only to an authorized user"; content outside the authorized viewer's gaze is "obscured so as to be rendered unintelligible." Supplies the privacy shield concept and the "only comprehensible to authorized viewer" predicate → claims 8/17. |
| R4 | US 2009/0016617 A1 (Samsung; Bregman-Amitai et al.), "Sender dependent messaging viewer" | Prio. 2007-07-13; pub. 2009-01-15 | [P] | Yes | Mobile apparatus receives an electronic message from a sender, matches the sender to a user identifier, and outputs a digital image associated with the matched sender → limitation (A) + "identifying information of the sender," and smartphone (6). |
| R5 | US 2002/0116508 A1 (Khan), "Method for secure transmission and receipt of data … using biometrics" | 2001-02-20 / 2002-08-22 | [P] | Yes — examiner-cited | Biometric-authenticated secure transmission and receipt of data → (C) in a message-transfer context. |
| R6 | US 2005/0251688 A1 (Nanavati), "Identity verification method using a central biometric authority" | 1999-05-14 / 2005-11-10 | [P] | Yes | Biometric identity verification against a stored authority-held profile → "stored biometric profile" (C). |
| R7 | US 2003/0135740 A1 (Talmor), "Biometric-based system and method for enabling authentication of electronic messages sent over a network" | 2000-09-11 / 2003-07-17 | [P] | Yes — examiner-cited | Biometric authentication applied specifically to electronic messages → (A)+(C). |
| R8 | US 2006/0206725 A1 (Milgramm), "… platform-independent biometrically verified secure information transfer and access control" | 2002-04-23 / 2006-09-14 | [P] | Yes — examiner-cited | Biometric verification gating information transfer and access control → (C)+(D) in a communications context. |
| R9 | US 6,836,846 B1 (IBM), "Method and apparatus for controlling e-mail access" | 1999-10-21 / 2004-12-28 | [P] | Yes | Gating access to e-mail → (D) conceptually. |
| R10 | US 2007/0074270 A1 (Essential Security Software), DRM of documents | 2005-09-28 / 2007-03-29 | [P] | Yes — examiner-cited | Content-access control / conditional reveal → (D). |
| R11 | US 7,698,745 B2 (Voltage Security), "Secure message system with remote decryption service" | 2003-09-25 / 2010-04-13 | [P] | Yes | Controlled reveal of secure messages → (D). |
| R12 | US 2013/0235045 A1 (Corazza et al.) | Filed 2013-03-06; pub. 2013-09-12 | [P] | No (does not appear in the visible '263 list) | Unknown in detail to me. Verified only as the reference Apple asserted as Ground 1 § 102 anticipation of claims 1, 4–6, 8, 11, 14–20 of the sibling '623 patent in IPR2023-00833 (instituted 2023-11-17). I did not retrieve its disclosure text this session and will not characterize its teachings. Source: IPR2023-00833 petition (PTAB). |
4.1 Reference-date verification
- R1 (Apple '441) — priority/effective filing 2013-06-08 is verified from the Google Patents family table for WO 2014/197112 A1 ("US13/913,403 | 2013-06-08 | 2013-06-08 | Using biometric verification to grant access to redacted content") and from the granted US 9,721,107 B2 front matter. Publishing 2014-03-27 as US 2014/0089441 A1 / 2014-12-11 as US 2014/0366158 A1 / 2014-12-11 as WO 2014/197112 A1. Its § 102(a)(2) status therefore hinges on the effective filing date, not the publication date.
- R2/R3 (Oculis) — verified against Espacenet/Google Patents (R2 CPC G06F 21/32, 21/62, 21/84; R3 granted as US 8,462,949 with claim language "comprehensible only to an authorized user").
- All other references are pre-2014 publications (and thus § 102(a)(1) art) on the record as fetched.
5. The § 103 grounds
I set out the grounds in descending order of strength. Ground 1 is the load-bearing ground. Grounds 2–4 are secondary/backup and cover dependents.
GROUND 1 — Apple '441 (US 2014/0089441) anticipates; a fortiori renders claims 1, 11, 18 and dependents 2–10, 15, 17 obvious
Proposed: Claim 1 and its dependents 2–10; claim 11 and dependents 12–17; claim 18 and dependent 19 — each obvious over US 2014/0089441.
Because R1 alone discloses all four limitations (see the element map below), § 103 is satisfied a fortiori: whatever anticipates also renders obvious. I expect a challenger to plead § 102 first and § 103 in the alternative, because the § 102 characterization of limitation (B) — whether "in response to the electronic message and independent of any user interaction" is literally met by R1's notification rendering — is the one contested point, and § 103 supplies an independent basis even if the patent owner persuades a court that R1 does not literally disclose it.
Element map — Claim 1 vs. R1 (Apple '441):
| Claim 1 limitation | R1 disclosure |
|---|---|
| receiver computer device, processor + memory | "electronic device" (smart phone; FIGS. 3–4 depict phones) |
| receive, at the receiver device from a sender device, an electronic message having electronic content and identifying information of the sender | Message notifications received; FIG. 7 depicts "a notification center display with both an SMS message from Jane Doe and an e-mail from John Doe"; claim 9: "a sender of the message is not redacted" |
| in response to the electronic message and independent of any user interaction, instruct the device to simultaneously display a privacy shield and the identifying information of the sender | Content redaction engine automatically "redacts for display any content marked as redacted" for messages "displayed in a locked-screen mode"; the system "display[s] certain messages or portions of a message without requiring the user to unlock the device." Claim 9/21: sender shown, content redacted, simultaneously — i.e., shield + sender ID together. |
| validate biometric data of the user in view of a stored biometric profile of the user | "biometric verification engine … compares the received biometric data to stored biometric data for one or more verified users"; match → "user … is verified." Claims 2/14: reader "includes a camera"; claim 3/15: "scanning camera." |
| remove the privacy shield … and display the electronic content … if the biometric data … is validated | "when the biometric verification data indicates that the user is verified, displaying the set of content without any portion redacted while the device remains in the lock screen mode" (claim 1); redaction options = "blurring," "black bar," "removing" (claim 12). |
Dependents:
- 2 / 12 / 19 — biometric reader "includes a camera" / "scanning camera" (R1 claims 2, 14). 3 / 13 (facial profile) — camera-based biometric verification; facial templates are the canonical example. 4 / 14 (monitor a sensor feed) — the biometric reader continuously supplies verification data and the engine redacts "as soon as the biometric reader is no longer receiving verified data" (i.e., continuous monitoring).
- 5 / 15 (>1 individual → prevent display) — see Ground 2 (R1 + R2).
- 8 / 17 (prevent display until validated) — R1 claim 1/13 ("displaying the set of content with the marked portion redacted" absent verification).
- 9 (reveal while screen remains locked from additional access) — R1 claim 1 verbatim: "while the device remains in the lock screen mode."
- 10 (lock-screen view) — R1, same.
- 6 (smartphone) — R1 FIGS. 3–4 and the "portable electronic devices (e.g., smart phones, tablet computers)" passage.
- 7 / 16 (MMS) — R1's notification system receives message notifications including SMS/e-mail; MMS is the same class of carrier messaging notification and the claim adds no structural difference. See Ground 5.
Why this ground is dangerous to the patent owner:
- It is not in the '263 citation block as fetched (the visible list stops at US 2011/0125844 A1). If it is in fact absent from the record, the examiner never considered it, and the "issued-over-the-art" equity argument collapses for this reference. ⚠️ I cannot confirm presence or absence because ~49 of 80 citations were not retrievable — this is the critical open query.
- It is Apple's own patent — and Apple is the defendant in the live 4:26-cv-01534 action. That creates a distinctive posture: the defendant can practice the '263 claims under its own earlier '441/'107 disclosure while asserting that the same disclosure invalidates them.
- Its claims 9/21 ("a sender of the message is not redacted while at least a portion of the message is redacted") is a near-verbatim disclosure of the "simultaneously display … a privacy shield and the identifying information of the sender" limitation — the hallmark the '263 patent owner presumably regards as its inventive contribution (see '263 claim 20, "privacy shield is displayed adjacent to the identifying information of the sender"). R1 renders claim 20 a pure design choice — showing the sender line just above/next to the redacted body is the natural layout of a notification.
GROUND 2 — R1 (Apple '441) in view of R2 (Oculis '667/'563): claims 5 and 15, and reinforcement of 2/3/12/13/19
Proposed: Claims 5 and 15 obvious over Apple '441 in view of Oculis Labs '667.
R1 does not expressly describe detecting that more than one individual is present and suppressing display on that basis; R2 does:
- R2: an image sensor collects facial recognition data from the region including "the presence of a third party in a region behind the user," and the security processor "modify[ies] the operation of the video display upon detecting the presence of a third party in the region." → claims 5 / 15.
Motivation to combine. Both references are in the same field of endeavor — on-screen privacy control based on camera-derived facial data (R2 CPC G06F 21/32, the same CPC the '263 patent carries) — and address the same problem: "permitting display of information to authorized users, while detecting, limiting or preventing disclosure to others" (R2's own framing of the need). KSR: "if a technique has been used to improve one device, and a person of ordinary skill would recognize that it would improve similar devices in the same way, using the technique is obvious." Adding a third-party-presence check to R1's lock-screen reveal is the predictable application of a known privacy technique to a known notification system, with a reasonable expectation of success (both rely on the same front-facing camera and the same face-detection front end already present in R1). The '263 patent's own specification supplies the motivation — it declares that revealing content "when only the biometric profile of the recipient account is recognized without the presence of other detected human beings in the proximate area" is a desideratum — and a challenger may cite the inventor's own stated problem as evidence of what the PHOSITA would have wanted to build.
Note on "teaching away": R2 does not teach away from R1; it teaches in the same direction (more privacy, not less). No reference in the record teaches away from gating message content on biometric verification.
GROUND 3 — R2 (Oculis '667) as primary, in view of R4 (Samsung '617) + R5 (Khan) + R7 (Talmor) + R6 (Nanavati): claims 1, 11, 18
Proposed (backup to Ground 1): Claims 1, 11, 18 obvious over Oculis '667 in view of Samsung '617, further in view of Khan '508 / Talmor '740 / Nanavati '688.
This ground is the doctrinally safest (all references are of record and all are § 102(a)(1) art), though it faces a higher hurdle because the examiner cited R2 and R3 and still allowed the claims. Its value is as an independent fallback and as a demonstration that the combination itself was known.
- R2 supplies (C) (facial recognition data ↔ stored user security parameters) and (D) (processor controls the data output device in response to that data — including obscuring/withholding display), plus the express recognition that a person entering the room "may see the screen display … [which] might constitute an improper disclosure of private information."
- R4 (Samsung '617) supplies (A) and the "identifying information of the sender": a mobile device that receives an electronic message and outputs a digital image matched to the sender.
- R5 (Khan '508) / R7 (Talmor '740) supply biometric gating in the message-transmission/receipt context specifically — bridging R2's generic display-privacy system to the messaging domain.
- R6 (Nanavati '688) supplies the "stored biometric profile" with a security-parameter database architecture — the exact architecture of R2's "user security parameter database."
Motivation to combine (KSR rationales (A)–(D)):
- (A) Known elements, known methods, predictable result: each of R2, R4, R5, R6, R7 was a known, commercially deployed element (facial privacy screens; sender-image notifications; biometric message authentication; stored biometric templates). Combining them yields nothing more than the expected aggregate of their separate functions.
- (C) Improvement of a similar device in the same way: R2 is a display-privacy controller; R4 is a mobile messaging notification viewer. Making the notification viewer obey the display-privacy controller's rules is precisely "using a known technique to improve a similar device in the same way."
- (D) A known device ready for improvement: R2 itself identifies the unmet need ("[s]ome means of permitting display of information to authorized users, while detecting, limiting or preventing disclosure to others, is needed") and criticizes the "all-or-nothing" scope of prior screensavers and privacy filters. A mobile notification — which already carries sender identity and content — is the ready candidate for that improvement.
- Explicit art-based teaching: R3 (Oculis '895), incorporated by reference into R2's own background discussion, describes displaying content "comprehensible only to an authorized user" by obscuring data so it is "rendered unintelligible" — a literal "privacy shield," and a direct teaching to apply the shield to content (not just a whole-screen lock).
GROUND 4 — R1 + R3: claims 8 and 17 and the "shield" definition
Proposed: Claims 8 and 17 obvious over Apple '441 in view of Oculis '895.
R3 supplies express teaching that undesired viewing is prevented by "obscur[ing]" content so it is "rendered unintelligible" — reading directly on "prevent display of the electronic content … until detection of biometric data that is validated." R1 supplies the biometric-validation trigger and the lock-screen notification context. Same field (G06F 21/xx; on-screen privacy), same problem, same predictable solution; no teaching away.
GROUND 5 — R1 + R4 (and R5/R9/R10/R11) against the "access-control" and format dependents: claims 6, 7, 9, 10, 16, 20
| Claim | Ground | Rationale |
|---|---|---|
| 6 (smartphone) | R1 alone; alternatively R4 | R1 expressly addresses "portable electronic devices (e.g., smart phones, tablet computers)" and depicts phones; R4 is a "portable apparatus," an "exemplary cellular phone." |
| 7 / 16 (MMS) | R1 (+ R4) | R1's system handles notification of carrier messages generally (SMS/e-mail shown). Selecting MMS rather than SMS is an interchangeable, art-recognized messaging format, and the claim recites no structural or functional difference predicated on MMS. KSR: "simple substitution of one known element for another." |
| 9 (reveal while screen remains locked from additional access) | R1 alone | R1 claim 1: unredacted content shown "while the device remains in the lock screen mode" — i.e., the content is revealed without granting broader device access. |
| 10 (lock-screen view) | R1 alone | Id. |
| 20 (privacy shield adjacent to sender ID) | R1 (+ R4) | R1 claim 9/21 places the unredacted sender alongside the redacted body. Positioning the shield "adjacent to" the sender line is a pure aesthetic/design choice with no unexpected result — In re Harza, 274 F.2d 669 (CCPA 1960) (changes in shape/arrangement of parts with no new function are not patentable). |
GROUND 6 — Corazza (US 2013/0235045) — an unexamined alternative route
Apple's Ground 1 in IPR2023-00833 asserted that Corazza (US 2013/0235045, filed 2013-03-06, published 2013-09-12) anticipates claims 1, 4–6, 8, 11, and 14–20 of the sibling '623 patent; Ground 2 combined Corazza with Brown (US 8,620,850). I verified the grounds and dates from the petition but did not retrieve Corazza's disclosure and will not characterize its teachings. Its significance here is procedural and strategic, two-fold:
- It is prior art to '263 on its face (§ 102(a)(1), published 2013-09-12 < 2014-03-10) and appears not to be in the '263 citation block as fetched — i.e., a second potentially uncited reference.
- Apple already drafted an institution-quality § 102/§ 103 attack on FaceToFace's 2014-priority messaging disclosure using Corazza. Assuming Corazza's disclosure maps to the '623 claims as alleged, its content can be re-deployed against '263's overlapping limitations. ⚠️ This is an inference from the existence of the grounds, not from the reference's text. I have not verified what Corazza discloses.
6. Motivation to combine — consolidated
Under KSR, the motivation analysis does not require an express statement in a reference. For each ground above, the following independent rationales apply:
- Same field of endeavor / analogous art. R1, R2, R3 share CPC G06F 21/32 (user authentication using biometric data) with the '263 patent; R2/R3 are additionally classified G06F 21/62/21/84 (protecting access to data; on-screen privacy). R1 is classified in the notification/redaction space. Combining art within the same technical field is presumed to be within the PHOSITA's ordinary creativity.
- Same problem, expressly articulated in the prior art. R2 frames the need as "permitting display of information to authorized users, while detecting, limiting or preventing disclosure to others." R1 frames it as "others may be able to pick up the device and view the message or a portion of the message intended for the user." The '263 specification's stated problem is identical. A problem known in the field supplies the reason (KSR), and the inventor's own recitation of the problem is admissible as evidence of the PHOSITA's knowledge.
- Explicit teaching to integrate. R2's background expressly criticizes screensavers and privacy filters as "all-or-nothing," and R3 teaches content-level (not screen-level) obfuscation. A notification bearing sender identification plus body content is the obvious unit of application.
- Predictable result, no unexpected behavior. At the 2014 priority date, front-facing cameras, face detection, on-device biometric templates, lock-screen notifications, and content redaction were each individually conventional on smartphones. Combining them produces only their expected functions in series — biometric check → conditional reveal — which is the "predictable use of prior art elements according to their established functions."
- Design incentive / market pressure. The smartphone notification-preview feature created a recognized privacy externality (anyone picking up the phone sees the message). The incentive to gate preview on owner verification was a design need, not an invention.
- Reasonable expectation of success. Near-certain. Each step is a discrete, independently known technique; the combination requires ordinary engineering (calling the biometric engine's verification result as a boolean input to the redaction engine), exactly as R1 describes ("an interface with the biometric verification engine that allows the redaction engine to request whether the biometric reader is currently receiving verified biometric data").
- No teaching away anywhere in the record. None of the references criticizes or discourages the combination; all point the same direction (more gating).
7. Anticipated patent-owner rebuttals and responses
| Patent owner argument | Response |
|---|---|
| "The references are device-owner privacy art; the invention is about sender security — the sender's permission settings drive the shield." | The granted claims do not recite sender permission settings, sender-defined privacy shields, or sender biometrics. The claims validate "biometric data of the user" against "a stored biometric profile of the user" — the device user. The title and specification cannot import unclaimed limitations (Phillips; In re Van Geuns, 988 F.2d 1181 (Fed. Cir. 1993)). The claims are of a piece with the cited art. |
| "The examiner cited Oculis '667 and '895 (and Samsung '617) and allowed." | (i) Issuance is not evidence of non-obviousness; the question is whether clear and convincing evidence of obviousness exists, not whether the examiner erred. (ii) The strongest ground — Apple '441 — appears not to be among the visible citations, so the "considered and rejected" argument does not reach it. ⚠️ Verify the full citation list at the USPTO file wrapper before relying on this. |
| "Oculis '667 must be tethered to a desktop; the claims are a mobile notification." | R1 (Apple '441) is the mobile lock-screen notification system. R2's mobile applicability is also supported by its portable-computing discussion and by the later Tobii acquisition of the family. |
| "'Independent of any user interaction' requires zero user input; R1 requires the user to place a finger on the reader / look at the camera." | The limitation modifies when the shield + sender ID are displayed, not when biometric sampling occurs. R1's shield and sender line appear automatically on message arrival ("without requiring the user to unlock the device"); validation occurs only later. Even if the patent owner disagrees, this is the one genuinely debatable limitation, which is why Ground 1 is pleaded as § 103 in the alternative to § 102. |
| "'Simultaneously display shield and sender ID' is not disclosed." | R1 claim 9 / claim 21: "a sender of the message is not redacted while at least a portion of the message is redacted when the biometric verification data indicates the user is not verified." That is the limitation in substance. |
| "The combination is impermissible hindsight." | The motivation is documented in the references themselves (R2's express statement of the need; R3's content-level obfuscation; R1's lock-screen privacy rationale), not in the applicant's disclosure. |
8. Objective indicia / secondary considerations
Nothing supports patentability on the present record.
- No commercial success with nexus. As the NPE / troll-pattern signals section found, I located no product, App Store listing, marketing site, pricing page, or customer reference for a FaceToFace Biometrics messaging application. There is therefore no product to which the claims can be tethered for a nexus — and "[a]bsent a nexus, evidence of commercial success is unavailing." In re GPAC Inc., 57 F.3d 1573 (Fed. Cir. 1995). (Negative finding, not proof of non-commercialization — flagged as in the prior section.)
- No licensing. One recorded assignment (2024-05-03, founder→company); no license recorded; the only third-party interaction on the portfolio is Apple's terminated IPR and its settlement on the sibling patent.
- No copying. R1 (Apple '441) predates the '263 claims by roughly nine months and was filed by a different company — this is independent development, not copying. Copying is the one secondary consideration that could cut the other way, and it is absent.
- No praise, no industry recognition, no long-felt unmet need that the claims actually solved. The unmet need (notification-preview privacy) was identified and addressed in the art (R1, R2) before the critical date.
- Unexpected results: none. The claims produce the sum of their parts.
9. Claim-by-claim § 103 summary
| Claim | § 102 (summary) | Best § 103 ground | Strength |
|---|---|---|---|
| 1 | R1 (all elements; (B) arguable) | R1 alone; R1 + R2 | Strong (if R1 uncited); moderate on R2-based ground due to examiner citation |
| 2 | R1 (camera biometric) | R1 | Strong |
| 3 | R1 / R2 (facial) | R1; R2 + R4 | Strong |
| 4 | R1 (continuous reader); R2 | R1 | Strong |
| 5 | R2 (third-party detection) | R1 + R2 | Strong |
| 6 | R1 / R4 (smartphone) | R1; R4 | Strong |
| 7 | — | R1 + R4 (SMS→MMS substitution) | Moderate |
| 8 | R1 claim 1/13 | R1; R1 + R3 | Strong |
| 9 | R1 claim 1 (lock-screen reveal) | R1 alone | Very strong (verbatim) |
| 10 | R1 | R1 alone | Very strong (verbatim) |
| 11 | R1 (method) | R1 alone; R2 + R4 + R5 | Strong |
| 12 | R1 claim 2/14 | R1 | Strong |
| 13 | R1 / R2 | R1 | Strong |
| 14 | R1 / R2 | R1 | Strong |
| 15 | R2 | R1 + R2 | Strong |
| 16 | — | R1 + R4 | Moderate |
| 17 | R1 claim 1/13 | R1 + R3 | Strong |
| 18 | R1 (CRM) | R1 alone; R2 + R4 + R5 | Strong |
| 19 | R1 | R1 | Strong |
| 20 | — | R1 (+ R4) — design choice | Moderate-to-strong |
10. Honest weaknesses, gaps, and limits of this analysis
- Corazza (R12) is uncharacterized. I verified only that Apple asserted it as anticipation of claims 1, 4–6, 8, 11, 14–20 of the sibling '623 patent in IPR2023-00833, and its filing/publication dates. I did not retrieve its text. Do not rely on Ground 6 as more than a lead. Priority action: retrieve US 2013/0235045 and read it against '263 limitations (A)–(D).
- Whether Apple '441 is in the '263 record is unresolved. The fetched citation block ("Citations (80)") is truncated at US 2011/0125844 A1; I saw no 2013 or 2014 references. That is consistent with — but does not establish — that '441 was never cited. Priority action: pull the '263 (and '776,616) file wrapper citations / IDS and confirm. The entire strength of Ground 1 turns on this.
- Prior-art status depends on the effective filing date. If '263's independent claims are fully supported by the 2014-03-10 provisional, the critical date is 2014-03-10 and R1 qualifies only under § 102(a)(2). If instead the claims require the 2015-03-10 non-provisional filing, an additional year of intervening art (including R1's own US 2014/0366158 publication of 2014-12-11, and CN 2018/108668001-type lock-screen biometric art in later families) opens up. This is contested terrain: Apple's own '623 petition applied a 2014-03-10 priority date, so the challenger in the 2026 case will likely assume the earlier date; the patent owner has an incentive to argue for the earlier date to cut off intervening art, which conflicts with its pre-'263 provisional-support positions in the earlier continuations.
- The § 101 shadow. The family's only merits ruling — the § 101 invalidation of the '623 patent in FaceToFace Biometrics, Inc. v. Apple, Inc., No. 4:22-cv-00429 (E.D. Mo. 2023-03-17), discussed in the Litigation summary and PTAB challenges sections — suggests the more dangerous attack on '263 may be patent eligibility, not § 103, particularly for claims 9, 10 (revealing content on a lock screen while the device remains locked) and 20 (adjacency of a UI element), which have a strong "presentation of information / user interface arrangement" character. Nothing in this § 103 analysis displaces that observation.
- I have not performed a full-text element-by-element read of R2/R3's specifications or of R1's full specification — I worked from verified abstracts, claim language, and the specification passages returned by search. The R1 claim 9/21 quote and the R1 passage on lock-screen redaction are quoted as retrieved; a challenger should pin-cite paragraphs of the published specification before serving contentions.
- No assertion of outcome. I express no view on how a court or the PTAB would rule. Ground 1 is the only ground that appears capable of carrying a case by itself, and it depends on a reference whose presence in the prosecution record I could not confirm.
11. Bottom line
The granted claims of US 12,536,263 are vulnerable to § 103, and the vulnerability is concentrated in one reference.
The patent is titled for sender security, but its granted claims cover recipient-device biometric gating of a message notification — automatically showing a shielded notification bearing the sender's identity on message arrival, validating the device user's biometric against a stored profile, and revealing the content on a match. That subject matter was squarely developed by 2013–2014:
- Apple's US 2014/0089441 A1 ("Using biometric verification to grant access to redacted content," effectively filed 2013-06-08) discloses all four limitations of independent claims 1, 11, and 18 — including, in its claims 9 and 21, the simultaneous display of the unredacted sender identification alongside redacted message content when the user is not biometrically verified, and the reveal while the device remains in the lock-screen mode (claims 9 and 10 of '263 are met verbatim). If this reference was not before the examiner, it is a strong § 102 ground that is also, necessarily, a § 103 ground.
- Oculis Labs' US 2010/0205667 (US 10,282,563) and US 2009/0141895 (US 8,462,949) — both already of record — supply the biometric-plus-stored-security-parameters-plus-display-control architecture and the third-party-presence suppression that covers dependent claims 5/15 and 3/13.
- Samsung's US 2009/0016617 ("Sender dependent messaging viewer") supplies the receipt-and-display of sender identification on a mobile device, completing a fully-of-record § 103 combination for claim 1 that a challenger can advance independently of the Apple '441 theory.
The motivation to combine is not hindsight: it is written into the references themselves (Oculis's express statement that "[s]ome means of permitting display of information to authorized users, while detecting, limiting or preventing disclosure to others, is needed," and its criticism of "all-or-nothing" screensavers; Apple '441's framing of the same lock-screen-preview privacy problem), and the combination is the predictable use of known elements according to their established functions.
Two open items gate the strength of any invalidity contention and should be resolved first: (1) whether Apple US 2014/0089441 / US 9,721,107 appears in the '263 prosecution record (citation block was truncated at ~31 of 80); and (2) what Corazza US 2013/0235045 actually discloses, since Apple already asserted it as anticipation against the sibling '623 patent's overlapping claims. Absent (1), the case rests on art the examiner already saw — which is a materially weaker, though still viable, posture.
Generated 9/30/2026, 4:05:09 AM
Extensions
Patent term adjustments, term extensions, continuations, divisionals, family members, and expiration dates.
Derivative works
Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.
Keep exploring
Other patents in Software Technology & Computing Systems (T)
- US 4419734I'll search for this specific patent number as instructed. Let me run a couple more targeted searches to check for litigation and to confirm bibliographic details. Let me try to retrieve the complete claim set to identify all independent…
- US 6366912I'll search for authoritative information on this patent number, including any 2026 CAFC docket activity. Let me run additional targeted searches to confirm whether any 2026 litigation or CAFC docket activity exists for this specific…
- US 7295515I'll search for this specific patent number across USPTO and CAFC records. Let me run additional targeted searches to check for any litigation or CAFC activity involving this specific patent. Search results: US Patent 7,295,515 Important…
- US 6185586I'll search for current information on this patent, including any litigation activity. Let me check for any recent (2025–2026) litigation activity involving this patent. US Patent 6,185,586 B1 — Analyst Summary Sourcing note: The full…
- US 5737619I'll search for this specific patent number across USPTO and litigation sources. Let me dig deeper on the litigation history and current status. Let me check for any recent or 2026 Federal Circuit activity and confirm the litigation…
- US RE49176I'll start by verifying the patent record and checking for any litigation or CAFC docket activity. Let me dig into the claim text and any 2026 appellate activity. Let me try to retrieve the actual claim set (particularly independent claim…
- US RE48066I'll research this patent. Let me run several searches in parallel. Let me dig deeper on the litigation/CAFC dockets and the claim text. I have enough to answer, though I want to flag upfront an important limitation: my searches did not…
- US 9978413I'll verify the patent details and check for any litigation or CAFC docket activity. Let me check for any 2026 appellate activity. US 9,978,413 B2 — Verified Summary Search scope / confidence note. I searched Google Patents, the USPTO…