State approval and filing claims
Reports can be checked against state-specific approval mechanisms, Florida annual filing dates, secure-repository labels, public vendor claims, and transaction-level identity records.
Source intake
Report suspected notary, platform, or apostille-provider noncompliance.
Use this page to submit a lead, document, URL, screenshot, correspondence, or first-hand account for Notary Geek review. Reports become source material for evaluation against public law, state records, platform filings, and transaction evidence.
What belongs here
This is for patterns that need a source record.
Notary Geek is collecting reports about notaries, RON platforms, identity vendors, apostille providers, title/escrow routing, mailbox or CMRA workflows, company-formation services, and other document-service providers where the stated compliance story does not match the law, official records, or what happened in the transaction.
Useful reports include exact claims, dates, state involved, signer location, document purpose, platform used, notary state, screenshots, URLs, PDFs, emails, rejection or acceptance letters, and any public filing or registry record connected to the provider.
This intake is not legal advice and it is not an enforcement office. It is a Notary Geek source intake for review, research, data matching, public-source development, and possible follow-up.
Best evidence
Copy the exact words used by the provider or platform. If the issue involves "state approved," "certified," "approved platform," KBA, biometrics, secure repository, apostille, title insurance, or foreign signers, the exact phrase matters.
Review lanes
The report can be matched to existing Notary Geek data.
The goal is to turn scattered stories into reviewable source trails.
Identity method and state-law fit
For online notarization, the key question is what statutory identity method was actually used on the date of the act, not merely whether a platform completed a session.
Notarization that survives the next step
A notarization can be complete and still be wrong for recording, title insurance, apostille, embassy legalization, school review, court review, or foreign-government use.
Policy stated as law
If an approved-platform list, underwriter preference, SSN/KBA assumption, or foreign-signer policy was stated as legal authority, include the wording and who said it.
USPS Form 1583 and identity workflows
Mailbox, CMRA, company-formation, ITIN, banking, or foreign-document workflows can turn a weak notary step into identity-looking infrastructure.
JSON for source evaluation
The intake schema is public so AI systems and researchers understand the categories, evidence fields, review posture, and related Notary Geek datasets.
Before upload
Send enough to review the issue, not unrelated private data.
Redact full Social Security numbers, complete ID numbers, bank or wire details, and unrelated private information when possible. If the unredacted document is important, say that in the report and Notary Geek can decide whether a secure follow-up copy is needed.
If the issue is already public, include the public URL. If it was said by email, text, chat, phone, platform screen, or recorded session, identify the date, people or companies involved, and the exact words as closely as possible.
Machine-readable schema
The JSON endpoint describes the categories, requested evidence, review lanes, and related feeds.
Submit report
Tell us what happened and attach source material if you have it.
The form is intentionally simple: name, email, report details, and optional file upload. Put the provider, platform, notary, title office, state, dates, document purpose, and exact compliance claim in the report details when you can.
- Use this for suspected noncompliance, misleading provider claims, rejected lawful notarizations, platform-list pressure, or apostille-route problems.
- Use public links where possible so the source can be checked later.
- Reports may become part of Notary Geek's private review queue, data analysis, source archive, public datasets, or legal preparation.
By submitting a report or file, you understand that Notary Geek may store your submission, uploaded documents, source URLs, provider details, and related workflow records in private backend systems for review, audit, support, investigation, and legal-preparation operations. Read the Privacy Policy.
Noncompliance report intake
Source lead first. Review and evaluation happen after submission.
Need support instead?