The notarial act
The commissioned notary owns satisfactory evidence, journal entry, certificate wording, seal/signature, and state-law compliance for the act.
Responsibility and data stewardship
The market acted as if someone checked. Who actually did?
Who sold the customer a lawful outcome, and who actually verified the method? Notary Geek's concern is that the RON market behaved as if legal verification had happened, but the transaction-level answers have not appeared.
The allegation
Responsibility theater is the problem.
If a business sells the customer a lawful online notarization service, it should be able to explain who owns provider responsibility, which state law applies, which identity method was used, what record proves it, and who can see the customer's private data.
Notary Geek has not found the person, platform record, title record, notary record, regulator record, or vendor answer showing who actually verified the legal identity method for the challenged workflows. The market acted as if verification had happened. Greg Lirette asked simple questions. The answers did not appear.
Say it cleanly
A vendor name, a title-company comfort list, MISMO certification, a training badge, or a completed session is not the same thing as checking the law.
The transaction-level question remains: which statutory identity method was actually used, who verified it, and what record proves it?
Responsibility chain
Everyone had a lane. Nobody gets to hide behind the next person.
The represented controls
The RON platform/provider owns identity-proofing configuration, audio-video session, audit trail, credential analysis, KBA, certificate events, and record handling.
The customer offer
The customer-facing service provider owns advertising, intake, routing, vendor choice, payment path, and whether the workflow it sells can lawfully serve the customer's facts.
The product truth
The technology vendor owns the truth of its product capability, logs, configuration, API limits, and technical claims.
The acceptance policy
Title, escrow, agencies, mailbox providers, and recipients own their acceptance policy. Acceptance policy does not cure a missing statutory identity method.
State-approved claim review
If the state has no simple platform approval list, "state approved" is a red flag to source-check.
Some vendor pages explain a state's remote-online-notary law and then invite businesses to use the vendor. That can be legitimate marketing, but it is not the same thing as a state approval record. A Texas or Virginia state-legislation page from a RON vendor does not, by itself, prove that Texas or Virginia approved that platform.
The source question is concrete: what official state page, rule, filing, registration, certification, or approval mechanism is being claimed? If the answer is only a vendor landing page, a private certification list, a title-company comfort list, or a sales statement, the claim has not reached legal authority.
Capture the claim
Preserve the exact words, URL, screenshot, capture date, state named, transaction date if known, and whether the claim is platform approval, notary commission status, private certification, title acceptance, or ordinary legal marketing.
Useful contrast: Florida has a public service-provider filing surface, while Michigan publishes an approved-vendor process. Texas, New York, and Virginia should not be flattened into that same model without an official source.
Concrete evidence lane
Online Notary Center shows why badges are not enough.
Notary Geek preserved a December 2024 recording involving Online Notary Center, a Florida notary session, intentionally fake test values, identity/KBA-style screens, a completed notarial view, and a later payment/account step.
Online Notary Center appears on MISMO's certified RON provider list. MISMO's own materials say certification does not verify compliance with any particular federal, state, county, or other governing law or rule. That combination is the point: private certification and a completed session do not answer who actually verified the legal method.
Data stewardship
The customer is not only buying a notarized PDF.
The customer is handing over passports, government IDs, financial papers, company documents, recordings, audit trails, support messages, recipient instructions, and shipping details. A high-volume marketplace can feel like Uber for notary: convenient routing, but a data path the customer may not understand.
Customers should ask where the data is stored, who can view it, whether support or operations teams are outsourced or offshore, what subprocessors exist, who owns secure repository duties, and how records are retained or retrieved.
Notary Geek's counter-position
Notary Geek is intentionally tighter and owner-operated. Greg Lirette is directly involved in the Azure, Microsoft 365, identity-document, upload, workflow, and support architecture. Access is tight, direct accountability is part of the product, and that is not changing any time soon.
How many RON company owners are personally configuring their Azure/Microsoft environment, reading the law, reviewing the identity method, and answering customer workflow questions themselves?
Public-safe boundary
Strong claim, careful limits.
This does not prove every individual RON transaction was invalid. It does not mean MISMO certification is worthless. It does not claim every marketplace platform uses the same data-access model. It means the burden is on the people selling, routing, certifying, accepting, and completing the workflow to show the actual statutory method and the actual data-stewardship path.