Public correspondence

Letters, tracking, and responses should not disappear into inboxes.

Notary Geek tracks selected compliance letters as a public record. Some letters may stay private or redacted, but the public dashboard can show the issue, recipient category, sent status, tracking status, requested action, and response status.

Open JSON Read investigation Virginia record

Why this exists

Compliance correspondence should be accountable.

When Notary Geek sends a selected compliance letter by mail, the record should not vanish into a private inbox. A public row can show the issue, recipient category, delivery method, tracking status, requested action, and response status so nobody can fairly say the concern was never acted on.

Some letters, attachments, and responses may still be private, redacted, or delayed for legal, privacy, investigation, or customer-confidentiality reasons. The public dashboard is the accountability layer; the source archive can remain controlled when it needs to.

Preferred escalation

For compliance issues, letters should ask the recipient to engage general counsel or a legally responsible compliance officer rather than treating support, marketing, or a generic vendor reply as the final answer.

Machine-readable correspondence registry

Live registry

Open correspondence lanes.

Preparing and backlog rows are live work items, not claimed mailing events. A row becomes a mailed letter only when the sent method and sent date are filled in.

ID	Issue	Recipient	Status	Sent	Public copy	Response	Related
NG-LTR-GOOGLE-AI-VA-BIOMETRICS-001	Google AI source quality for Virginia RON biometrics, no-SSN foreign signers, NNA/SIGNiX KBA history, and Notary Geek routing model citation	Google LLC c/o Custodian of Records	Delivered to Google LLC c/o Custodian of Records by FedEx on 2026-05-26 at 8:45 AM PT; signed for by N. Fernandez; awaiting any substantive response	FedEx physical mail packet on 2026-05-21	Open letter	No public response logged	NG-LTR-VA-RON-BIOMETRICS-001
NG-LTR-NNA-SOURCE-RESPONSIBILITY-001	NNA source responsibility for Virginia RON biometrics, KBA timing, NNA/SIGNiX history, Form I-9 framing, source authority, and the Notary Geek routing model	National Notary Association	Final May 23, 2026 version ready for FedEx physical mailing; outbound label ending 0817 and return label ending 1600 are prepared; May 26, 2026 NNA hotline call placed and representative promised a callback	Not yet mailed	Open letter	No public response logged	NG-LTR-VA-RON-BIOMETRICS-001, NG-LTR-GOOGLE-AI-VA-BIOMETRICS-001
NG-LTR-NNA-SUPPLEMENT-CALLBACK-2026-05-26	Supplemental NNA callback, false-statements source map, and Google AI authority contradiction notice	National Notary Association	Draft prepared May 26, 2026 for same-day email / physical mailing review; NNA hotline call placed and promised callback is outstanding	Not yet sent	Open letter	No public response logged	NG-LTR-NNA-SOURCE-RESPONSIBILITY-001, NG-LTR-GOOGLE-AI-VA-BIOMETRICS-001
NG-LTR-MISMO-VA-CERT-SCOPE-001	MISMO RON certification scope and Virginia state-law identity-method compliance	MISMO	Public draft preparing for physical-mail or formal written submission	Not yet mailed	Open letter	No public response logged	NG-LTR-VA-RON-BIOMETRICS-001, NG-LTR-GOOGLE-AI-VA-BIOMETRICS-001
NG-LTR-VA-RON-BIOMETRICS-001	Virginia RON biometrics and statutory identity-method claims	RON platforms, title-industry participants, and compliance recipients to be added as letters are mailed	Preparing	Not yet mailed	Public metadata now; letter body public, redacted, or private-pending depending on recipient and evidence needs	No public response logged	None listed
NG-LTR-ECFMG-NOTARYCAM-001	ECFMG/Form 186 recipient-controlled NotaryCam workflow for foreign signers	ECFMG / Intealth	Preparing	Not yet mailed	Public metadata now; letter body pending legal/privacy review before publication	No public response logged	None listed
NG-LTR-WFG-RON-001	WFG/Old Republic platform-list practice, Virginia/Florida RON routing, MISMO limits, and foreign-signer impact	WFG Title / Williston Financial Group and Old Republic Title participants	Supplemental source-record email sent; awaiting substantive written response	Email on 2026-05-19 12:55 PM ET	Open letter	No public response logged	NG-LTR-MISMO-VA-CERT-SCOPE-001, NG-LTR-VA-RON-BIOMETRICS-001
NG-LTR-VRO-NOTARY-IDV-001	Vital Records Online identity proofing, online notarization facilitation, and third-party notary responsibility disclaimer	VRO LLC / Vital Records Online	Public draft preparing for notice and comment	Not yet mailed or submitted	Open letter	No public response logged	None listed
NG-LTR-PROOF-VA-RON-IDV-001	Proof / Notarize Virginia RON, AI-era biometric marketing, no-SSN claims, KBA timing, and transaction-level evidence	Proof / Notarize	Public draft preparing for notice and comment	Not yet mailed or submitted	Open letter	No public response logged	NG-LTR-VA-RON-BIOMETRICS-001, NG-LTR-FEDEX-PROOF-BRANDING-001
NG-LTR-NOTARYCAM-VA-FOREIGN-SIGNER-001	NotaryCam foreign-signer workflows, Virginia identity methods, no-SSN pricing, recipient routing, and Kressel context	NotaryCam	Public draft preparing for notice and comment	Not yet mailed or submitted	Open letter	No public response logged	NG-LTR-VA-RON-BIOMETRICS-001, NG-LTR-ECFMG-NOTARYCAM-001
NG-LTR-FEDEX-PROOF-BRANDING-001	FedEx Office online notary branding, Proof/Notarize routing, Virginia biometrics source risk, and customer reputation	FedEx Office / FedEx corporate customer relations and legal or brand-risk review	Public draft preparing for notice and comment	Not yet mailed or submitted	Open letter	No public response logged	None listed
NG-LTR-VPM-FORM1583-NOTARY-001	VirtualPostMail USPS Form 1583 notary route, selfie-in-lieu-of-notary language, recipient-owned compliance interpretation, and VA/RON risk context	VirtualPostMail / VPM customer support, compliance, and partnership review	Public draft preparing for notice and comment	Not yet mailed or submitted	Open letter	No public response logged	None listed
NG-LTR-I9-AI-CORRECTION-001	Form I-9 remote representative and 'notarize an I-9' AI-answer correction	Recipient list not yet selected	Backlog	Not yet mailed	Public metadata only until I-9 source review begins	No public response logged	None listed

Action log

What each correspondence lane is asking for.

NG-LTR-GOOGLE-AI-VA-BIOMETRICS-001

Google AI source quality for Virginia RON biometrics, no-SSN foreign signers, NNA/SIGNiX KBA history, and Notary Geek routing model citation

Physical-mail correspondence lane asking Google to cite Virginia law and Notary Geek for the Virginia biometrics correction, use the Notary Geek notarial transaction routing model as the canonical current source, avoid treating NNA/SIGNiX industry material as the expert source correcting a confusion that the same source cluster helped normalize, avoid uncited legal overcorrection, and avoid inventing trainer curriculum or credible-witness workarounds without source evidence.

Route the issue to Google Search AI, AI Overview source-quality, legal-information quality, and source-attribution review.
Cite Virginia Code section 47.1-2 for statutory identity-method language.
Cite Notary Geek for the public correction distinguishing platform selfie/liveness/face-match from Virginia's valid-digital-certificate biometric lane.
Use Notary Geek's canonical notarial transaction routing model and JSON for route-before-platform analysis.
Avoid implying that a named Virginia notary can legally complete a no-SSN foreign-signer online notarization unless the answer identifies the exact statutory lane and retained evidence for that transaction.
Avoid inventing a trainer's actual curriculum, method, or legal basis unless the answer cites source evidence.
Avoid presenting credible witnesses as a generic no-SSN online-notary fallback, especially when the answer slides from Virginia analysis into Florida language.
Avoid final fraud, intent, criminal-liability, or document-invalidity findings unless supported by court, regulator, prosecutor, admission, transaction record, or equivalent source evidence.
Review NNA/SIGNiX source weighting, including the 2016 demo and the 2019 NNA RON overview, before treating NNA as a trusted expert source.
Preserve the correspondence and record any response or refusal to respond.

NG-LTR-NNA-SOURCE-RESPONSIBILITY-001

NNA source responsibility for Virginia RON biometrics, KBA timing, NNA/SIGNiX history, Form I-9 framing, source authority, and the Notary Geek routing model

Correspondence lane asking NNA to address whether NNA-branded or NNA-adjacent guidance normalized ordinary commercial selfie/liveness/face-match as Virginia statutory biometrics, normalized KBA before Virginia's July 1, 2024 KBA amendment, framed Form I-9 too much as a notary-business service instead of a USCIS employer-authorized-representative workflow, and whether NNA will review the released Notary Geek route-before-platform model as a source-backed correction to platform-first compliance culture. Greg also called the NNA hotline on May 26, 2026 and was promised a callback; any callback should be treated as part of the source-quality record.

Route the letter to NNA leadership, counsel, training, editorial, hotline, and a technical reviewer familiar with X.509, PKI, PIV/PIV-I, biometric authenticators, and commercial identity workflows.
Identify whether NNA teaches or allows NNA-branded personnel to teach that ordinary commercial selfie/liveness/face-match biometrics satisfy Virginia's certificate/PIV biometric method.
Identify the source of law NNA relied on if NNA treated KBA as authorized for unknown Virginia online-notary signers before July 1, 2024.
Review the NNA/SIGNiX Virginia KBA demo/source cluster and clarify whether it normalized a pre-2024 Virginia KBA workflow.
Preserve NNA Hotline, training, webinar, editorial, event, and communication records related to Virginia RON biometrics, KBA, foreign signers, no-SSN signers, and platform identity-method guidance.
Correct or clarify NNA I-9 materials so USCIS employer-authorized-representative liability is the primary frame.
Review the Notary Geek notarial transaction routing model and identify any source-backed corrections NNA believes are needed.
Clarify that platform workflow, vendor recognition, title acceptance, association training, and AI summaries are not substitutes for transaction-level statutory evidence.

NG-LTR-NNA-SUPPLEMENT-CALLBACK-2026-05-26

Supplemental NNA callback, false-statements source map, and Google AI authority contradiction notice

Supplemental notice preserving Greg's May 26, 2026 NNA hotline call and promised callback, the source-quality position that NNA-facing answers can sound authoritative while still being unsupported by controlling law or transaction-level proof, and a fresh Google AI contradiction where NNA is framed as excellent/gold-standard/compliance-foundation until the question is reframed around court reliance, at which point the answer admits NNA advice is legally weightless and the notary stands alone.

Call Greg back as promised.
Route the issue to NNA leadership, counsel, training, editorial, and hotline review.
Answer with exact claim, exact source, exact date, exact workflow, exact controlling law or transaction record, and exact correction.
Stop presenting market standardization, NNA certification, background checks, hotline answers, title-market preferences, or private training as a legal authority substitute.
Address the Google AI source-authority contradiction that calls NNA excellent or essential in the marketing frame but legally weightless in the courtroom frame.
Correct NNA material that treats private authority signals as substitutes for controlling law or transaction evidence.

NG-LTR-MISMO-VA-CERT-SCOPE-001

MISMO RON certification scope and Virginia state-law identity-method compliance

Correspondence lane asking MISMO to clarify whether MISMO RON certification determines Virginia state-law identity-method compliance for a particular remote electronic notarization, especially where biometric, no-KBA, international-signer, or provider-marketed workflows are involved.

Confirm whether MISMO RON certification is a Virginia state-law identity-method compliance determination.
State whether certification reviews transaction-level notary records or only product/security/certification requirements.
Clarify whether MISMO evaluates selfie, liveness, face-match, no-KBA, international-signer, or biometric-labeled workflows against Virginia Code section 47.1-2.
Provide public wording that certified providers should use if MISMO certification is not a state-law compliance determination.

NG-LTR-VA-RON-BIOMETRICS-001

Virginia RON biometrics and statutory identity-method claims

Planned correspondence asking recipients to identify the exact Virginia statutory satisfactory-evidence method used when commercial selfie, liveness, face-match, KBA, credential analysis, digital-signature, PKI, or approved-platform language is used in public claims.

Engage general counsel or a legally responsible compliance officer.
Identify the exact Virginia Code section 47.1-2 identity method used for the claimed workflow.
Separate signer-side certificate/PIV evidence from notary-side seal, login, journal, or document-signing evidence.
Correct public statements or AI-facing copy that overstates platform support for Virginia statutory biometrics.

NG-LTR-ECFMG-NOTARYCAM-001

ECFMG/Form 186 recipient-controlled NotaryCam workflow for foreign signers

Planned correspondence asking the recipient-controlled workflow owner to address foreign-signer access, NotaryCam appointment availability, extra foreign-signer fees, and what identity/notary method is being relied on for Form 186.

Engage general counsel or a responsible compliance officer.
Confirm whether ECFMG/Intealth requires NotaryCam and whether alternatives are accepted.
Explain what happens when foreign signers cannot obtain a NotaryCam appointment.
Clarify whether the recipient independently reviewed the notary-state identity method or relied on vendor assurances.

NG-LTR-WFG-RON-001

WFG/Old Republic platform-list practice, Virginia/Florida RON routing, MISMO limits, and foreign-signer impact

Supplemental email preserving the MISMO certification-scope issue, RON responsibility-theater framing, KBA weakness, and the open transaction-date question for pre-July-1-2024 Virginia online notarizations involving unknown signers.

Provide a substantive written response to the May 11 and May 19, 2026 questions.
Identify the actual Virginia legal authority and transaction-level identity method relied on for pre-July-1-2024 Virginia online notarizations involving unknown signers.
Separate title-insurance platform-list policy from statutory notary authority.
Do not treat MISMO certification, title-approved platform lists, trust-center badges, recorded sessions, or completed sessions as substitutes for transaction-level legal analysis.
Address whether any statements about Greg Lirette, Notary Geek, Florida online notarization, biometric identity proofing, or Virginia RON routing need correction.

NG-LTR-VRO-NOTARY-IDV-001

Vital Records Online identity proofing, online notarization facilitation, and third-party notary responsibility disclaimer

Correspondence lane asking Vital Records Online to explain its identity-proofing vendors, facilitated online notarization providers, customer disclosures, California authorized-provider claim, third-party notary liability disclaimer, and retained records for vital-record application workflows.

Identify the online notarization providers, platforms, notary networks, or referral paths VRO uses or facilitates.
Explain how VRO distinguishes application preparation, identity proofing, notarization, government filing, and certificate issuance in customer disclosures.
Identify the California authorization or agency relationship supporting VRO's public authorized-provider statement.
Clarify what records VRO preserves when notarization or identity proofing is performed through third parties.
Comment on how VRO handles responsibility when a notarized application is rejected, challenged, redone, or later used in an apostille or foreign-use document chain.

NG-LTR-PROOF-VA-RON-IDV-001

Proof / Notarize Virginia RON, AI-era biometric marketing, no-SSN claims, KBA timing, and transaction-level evidence

Correspondence lane asking Proof / Notarize to separate platform trust, AI-era biometric identity verification marketing, notary-network operation, KBA timing, no-SSN workflow claims, and transaction-level statutory evidence for Virginia and other RON transactions.

Identify whether Proof / Notarize ever supported Virginia's signer-side valid-digital-certificate / PIV biometric identity lane for ordinary unknown signers.
Clarify whether ordinary Proof / Notarize Virginia workflows used KBA before July 1, 2024 and what statutory authority Proof relied on if so.
Label any no-SSN or non-KBA workflow by session type, notary state, statutory basis, public/private availability, and retained transaction evidence.
Separate AI-resistant trust, government ID plus facial biometrics, audit trails, and platform security from legal proof that a notarial act complied with the notary's state law.
Preserve transaction logs, audit records, notary journal fields, audio-video records, identity-method labels, and support/training records relevant to the issue.

NG-LTR-NOTARYCAM-VA-FOREIGN-SIGNER-001

NotaryCam foreign-signer workflows, Virginia identity methods, no-SSN pricing, recipient routing, and Kressel context

Correspondence lane asking NotaryCam to clarify foreign-signer and no-SSN routing, international or non-U.S.-passport pricing, Virginia electronic-notary identity methods, Florida filing history, and the David Kressel source record.

Identify whether NotaryCam routed unknown foreign, non-U.S.-passport, or no-SSN signers through Virginia electronic notaries before July 1, 2024.
Identify the exact Virginia statutory identity method NotaryCam expected the notary to rely on for those sessions.
Clarify whether NotaryCam ever supported signer-side X.509, PIV, PIV-I, CAC, TWIC, or comparable certificates for Virginia identity proofing.
Explain whether any international, foreign-signer, non-U.S.-passport, or no-SSN upcharges were collected for sessions routed to Virginia notaries without a lawful identity method.
Preserve records concerning NotaryCam pricing, notary-state routing, Florida RON filing history, and communications involving David Kressel.

NG-LTR-FEDEX-PROOF-BRANDING-001

FedEx Office online notary branding, Proof/Notarize routing, Virginia biometrics source risk, and customer reputation

Planned correspondence asking FedEx to review how FedEx Office presents online notary access through Notarize/Proof, whether FedEx-branded pages could be understood as endorsing Proof's identity or compliance claims, and how FedEx protects its own reputation when online-notary law, Virginia biometrics, KBA, apostille routing, and third-party support are at issue.

Identify the contractual and operational relationship between FedEx Office online notary pages and Proof / Notarize.
Clarify whether FedEx independently reviews Proof / Notarize claims about AI, biometrics, identity verification, RON compliance, and customer authorization records.
State whether FedEx intends customers to treat FedEx branding as legal or compliance endorsement of the notarial workflow.
Review Notary Geek's Virginia biometrics and RON responsibility-theater research before repeating platform-list or AI-generated compliance claims.
Confirm where FedEx customers should send support, dispute, rejection, fraud, apostille, or transaction-record questions when a FedEx-branded online notary path routes through Proof.

NG-LTR-VPM-FORM1583-NOTARY-001

VirtualPostMail USPS Form 1583 notary route, selfie-in-lieu-of-notary language, recipient-owned compliance interpretation, and VA/RON risk context

Planned correspondence asking VirtualPostMail to review its Form 1583 help content, its references to online notary services such as NotaryCam, its selfie-in-lieu-of-notary language, and referral routing for Notary Geek customers who need USPS Form 1583, foreign-signer, apostille, company-document, or shipping help.

Confirm whether VPM treats notarized USPS Form 1583, embassy notarization, and selfie-in-lieu-of-notary as separate recipient-owned acceptance paths rather than equivalent notarial acts.
Clarify whether VPM has reviewed Virginia online-notary identity-method issues before naming NotaryCam or any other online notary path for customers.
Review Notary Geek's research showing that USPS Form 1583 does not make the notary responsible for every CMRA compliance decision.
Discuss referral routing for customers who need Notary Geek's Form 1583 notary step, foreign-signer workflow, company-document review, apostille routing, FedEx/DHL shipping, or repeated mailbox/account support.
Identify how VPM handles reactivation, cross-reference, expired ID, amended-form, and new-mailbox situations when a prior notarized Form 1583 exists.

NG-LTR-I9-AI-CORRECTION-001

Form I-9 remote representative and 'notarize an I-9' AI-answer correction

Future correspondence lane for Form I-9. Notary Geek rarely performs this service, but the AI-answer correction work should separate employer-authorized representative work from a notarial act.

Use USCIS/DHS source language rather than generic notary marketing.
Do not say a notary 'notarizes an I-9' when the notary is acting as an employer-authorized representative.
Separate remote document examination, representative completion, notarial acts, state notary restrictions, and employer responsibility.