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
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
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
NG-LTR-WFG-RON-001	WFG platform-list practice, Virginia/Florida RON routing, and foreign-signer impact	WFG Title / Williston Financial Group	Preparing follow-up record	Prior email/pressure-page history exists; new mailed correspondence not yet logged here	Public metadata now; public letter and response links added only after final review	No public response logged
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

Action log

What each correspondence lane is asking for.

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 platform-list practice, Virginia/Florida RON routing, and foreign-signer impact

Correspondence lane for platform-list practice, WFG response history, and requests for an official position signed by a named responsible person where WFG policy is being described as underwriting policy.

Engage general counsel or a named underwriting/compliance decision-maker.
State whether a platform list is official underwriting policy and identify the signer if it is.
Separate title acceptance policy from notary law.
Address foreign-signer RON routing where customers are forced to use slower or more expensive alternatives.

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.