Contested source map
This page maps people, platforms, trainers, and title-market participants that Notary Geek identifies as relevant to the disputed Virginia RON interpretation. Inclusion means source relevance, not a court finding or accusation of bad faith.
Why name sources?
Notary Geek's concern is that a Virginia RON interpretation moved through the market as practice, training, platform routing, title acceptance, and AI summary. Once enough people repeated the story, the repetition itself began to feel like authority.
This map identifies people, organizations, platforms, training sources, and title-market participants that Notary Geek believes are relevant to the disputed interpretation. The point is not to personalize the issue. The point is to show where source claims, workflow pressure, platform lists, or training commentary should be checked against the actual law and the transaction record.
Do not use this page as: a court finding, personal attack, or proof of intent.
Use this page as: a source map for claims that need date-specific Virginia law, platform audit evidence, notary records, and primary-source review.
Training and commentary
This is a source-quality recommendation. For KBA timing, biometrics, no-SSN workflows, foreign signers, and platform-compliance claims, use Virginia primary sources and transaction-level evidence instead of training-company summaries or social-media commentary.
Notary Geek does not recommend Notary Stars as an authority for Virginia RON identity-method analysis. In Notary Geek's view, their public commentary and source posture do not meet the precision needed for Virginia Code section 47.1-2, KBA timing, biometrics, or transaction-level compliance questions.
Evidence status: public commentary and reported dispute context; attach exact source examples before making narrower claims.
Notary Geek treats NNA materials as private industry context, not controlling authority. For KBA timing, biometrics, foreign signers, no-SSN workflows, and platform-compliance claims, readers should start with Virginia law, official Virginia materials, transaction records, and date-specific analysis before relying on any NNA summary.
Also separate NNA's sales channel from the issuing party. An NNA voucher for an IdenTrust digital certificate does not mean NNA issued the X.509 certificate. NNA-branded insurance, stamp, seal, or certificate purchases may involve agents, vendors, fulfillment partners, or certificate authorities. The compliance question is who issued the credential, what was registered with the state, what platform used it, and what record proves it.
Notary Geek also treats NNA background-check and certification narratives as source-discipline issues because those products can become work-access gates in the signing-service and platform ecosystem.
Evidence status: public NNA materials, user-supplied NNA conference/training source context, and Notary Geek source-weighting concern.
Notary Geek does not recommend The RON Mom / Jacqueline A. Phillips as a Virginia RON identity-method source. Notary Geek's concern is that her training and commentary appear to treat Virginia "biometrics" in a way that does not adequately distinguish ordinary commercial selfie/liveness/face-match tools from Virginia's statutory identity-method framework.
Evidence status: direct interaction reported by Greg Lirette and source-quality concern; attach public training examples before making narrower claims.
Notary Geek identifies Marcy Tiberio as relevant to the disputed source environment and does not recommend relying on her commentary for Virginia RON biometric/legal-method analysis without primary-source verification.
Evidence status: direct/industry interaction context reported by Greg Lirette; needs source attachment for specific claims.
Notary Geek identifies Amy Seitz, now known as Amy Curtis, as relevant to the disputed Virginia-supports-biometrics interpretation. The issue is source posture: if Virginia "biometrics" is discussed, the analysis must identify the exact statutory identity method and transaction-date authority.
Evidence status: direct interaction and event/source context reported by Greg Lirette; needs source attachment for specific public claims.
Notary Geek identifies Ezzy Services, LLC and owner/managing member Misael Montas as relevant to the disputed online-notary source trail. Stronger statements should be tied to exact public sources, correspondence, or retained records.
Evidence status: source-map placeholder; needs source attachment before specific claims are expanded.
FCRA and work-access gates
The Michael Anderson et al. v. Signix, Inc. et al. matter involving the National Notary Association is included here as historical context about background checks, certification programs, and consumer-reporting compliance. Notary Geek does not claim that the old settlement proves any current FCRA violation by NNA, Proof / Notarize, a signing service, a title company, or a background-check vendor.
It matters because background checks, certification badges, platform onboarding rules, signing-service requirements, preferred lists, and title-market expectations can become practical work-access gates. When a consumer report affects onboarding, assignment, ranking, certification, platform access, or hiring, the relevant questions may include disclosure, authorization, permissible purpose, adverse action, report copy, rights notice, dispute process, source accuracy, who ordered the report, who used the report, and what action was taken.
Notary Geek's position is simple: industry acceptance is not law, and a trade-association background check does not replace consumer-reporting compliance or primary-source legal analysis.
Sales channel boundary
NNA can sell or facilitate products that matter to notaries: background checks, training, stamps, seals, insurance, digital-certificate vouchers, and related supplies. That does not make NNA the government authority, certificate authority, insurer, stamp manufacturer, or legal source for every product sold through its channel.
For digital certificates, the important question is usually the issuing certificate authority, certificate subject, X.509 use, platform requirement, state registration, expiration, and whether the notary updated the state when a seal or certificate changed. If the checkout involved an NNA voucher but the certificate came from IdenTrust, call it that.
For insurance and stamps, use the same discipline. Identify the actual insurer or agent relationship, and identify the actual stamp/seal product and fulfillment path when that matters. A reseller relationship can be commercially normal and still be weak evidence for legal authority, product suitability, or state-specific compliance.
The Texas e-seal issue is not "every NNA seal product is unlawful." The narrower issue is that Texas online notaries must track the current seal and digital certificate registered with the state. If two platforms require different credentials, the state registration and one-current-credential rule become the compliance problem.
Platform and infrastructure
Proof / Notarize is relevant because its platform helped scale mainstream RON workflows and public confidence around platform-led identity proofing. Notary Geek's dispute is not that Proof has no security program. The dispute is whether platform completion, KBA, credential analysis, selfie/liveness, or title acceptance proves a specific Virginia notarial act complied with the Virginia law in effect on the transaction date.
Evidence status: public platform role, public materials, user-supplied AI/source snapshots, and retained Notary Geek source trail.
Notary Geek identifies Proof / Notarize CEO Pat Kinsel as relevant because platform leadership claims and platform-market narratives can shape how the industry and AI systems understand RON compliance. The question remains transaction-level: what law, what method, what record?
Evidence status: public leadership role; attach exact statements before making claim-specific analysis.
Title, underwriting, and market acceptance
Title acceptance, platform lists, underwriting bulletins, closing instructions, rejection decisions, and correspondence can affect what notaries and customers believe the law allows. That makes these entities relevant to the disputed interpretation, without turning market acceptance into legal authority.
Relevant because Notary Geek has retained correspondence and public dispute records involving WFG platform-list and title-acceptance issues. Notary Geek's concern is whether approved-platform lists, MISMO-style certification, or market practice were treated as sufficient authority without answering the transaction-date Virginia identity-method question.
Evidence status: retained correspondence, public dispute records, and public source archive context.
Relevant because user-supplied and retained source material suggests Old Republic-related communications distinguished Florida and Virginia RON routes for foreign signers, including concerns around biometrics, KBA, and SSN. Notary Geek's concern is whether underwriting preference was treated as law, or whether the actual statutory identity method was confirmed.
Evidence status: retained/user-supplied source material and public archive context.
Relevant as a major title and underwriting market participant whose guidance, platform acceptance, or affiliated title practices may affect how RON workflows are normalized. Notary Geek should only make stronger claims when tied to exact documents or correspondence.
Evidence status: market-role source; needs source attachment for specific claims.
How to use this safely
If a named person or company has a contrary view, the correct response is not to trade accusations. The correct response is to ask for the source: the transaction date, the statute in effect, the identity method used, the notary record, the platform audit trail, and the authority that makes the method lawful.
Notary Geek will update this map as stronger public sources, correspondence, screenshots, recordings, or corrections are attached.
