Legal
Last updated August 29, 2026
NotaryBoard helps title agencies see which notaries are free and dispatch signings to them. Doing that means touching two genuinely sensitive things: a notary's calendar and the details of a signing. This policy explains exactly what we take, what we do with it, and what we deliberately don't.
NotaryBoard ("NotaryBoard", "we", "us") is a service operated by 247 Closers LLC, a New Jersey limited liability company. This policy covers the NotaryBoard web application at notaryboard.io and everything we do with data you or your calendar provider give us. We are the data controller for that information.
NotaryBoard has two kinds of users, and what we collect differs between them: agencies (title companies dispatching signings) and notaries (the people accepting them).
Account information. When you sign up we collect your name and email address. Authentication is handled by Clerk — if you sign in with Google or Microsoft, we receive your name and email from that provider. We never see your password.
Notary profile. If you use NotaryBoard as a notary, you tell us your legal name, commission state and expiration, whether you're NNA-certified, background-screened, or E&O insured, your coverage area (state, counties, ZIP codes), your travel radius, your approximate home location (used only to compute travel distance), your scheduling buffer, and — optionally — a mobile number so we can text you about signings. The phone number is optional; without it you simply get email instead.
Agency and signing information. Agencies give us an organization name, office addresses, and, for each signing, a title, an optional order or escrow number, the appointment address, the scheduled time and duration, the fee, and any notes the agency adds. Bear in mind that notes are free-text — please don't put borrower Social Security numbers, account numbers, or other sensitive personal data in them.
Calendar data. Described in detail in the next two sections.
Billing information. Subscription payments are processed by Stripe. Stripe handles your card details directly — we never see or store card numbers. We keep only a Stripe customer identifier, your subscription status, and your plan.
Tracking: the app and the marketing site are different. The signed-in application runs no analytics, advertising, tracking, or profiling tools of any kind — no Google Analytics, no advertising pixel, no session recorder. The only cookies the app sets are the ones required to keep you signed in. (One narrow server-side exception, a single agency-signup event, is described under "Who we share it with.") Our public marketing pages (the homepage, articles, and other pages you can view without signing in) use the Meta Pixel to measure our advertising, described under "Who we share it with."
If you connect a Google Calendar, we request exactly two scopes, and we use each one narrowly:
calendar.freebusy — read only when you are busy. We call Google's Free/Busy API, which by design returns nothing but start and end times of your existing commitments. It does not return event titles, descriptions, attendees, locations, or organizers, and so we never receive them. We store these busy periods as start/end timestamps and nothing else.calendar.events.owned — write our own hold events. When you accept a signing, we create a single calendar event on your primary calendar so the time is blocked in your real calendar. If the signing is cancelled, we delete that same event. We use this scope only to create, update, and delete NotaryBoard's own hold events, each tracked by its event ID. We do not use it to read your other events.We deliberately request calendar.events.owned — which covers only calendars you own — rather than the broader calendar.events, because we only ever write to your own primary calendar. A narrower scope isn't viable: calendar.app.created manages events only on a separate app-created calendar, so your real calendar wouldn't show the appointment as busy and you could be double-booked — and there is no write-only Calendar scope. Blocking the notary's real calendar is the core function of the product. On the read side we request the narrowest scope that exists for availability — calendar.freebusy — rather than a broader calendar read scope, specifically so that event contents never reach our servers.
Connecting an Outlook or Microsoft 365 calendar works the same way. We request Calendars.ReadWrite and call Microsoft Graph's getSchedule endpoint for availability, which — like Google's Free/Busy API — returns availability status and times only, never event subjects or attendees. We use the write half of that permission solely to create and delete NotaryBoard's own hold events. Microsoft does not offer a free/busy-only scope, which is why the permission name is broader than what we actually do with it.
We use what we collect only to run the service:
We do not use your data to train machine learning models, build advertising profiles, or for any purpose unrelated to operating NotaryBoard.
Between agencies and notaries. This is the point of the product, so be clear on where the line sits. An agency you are connected to can see your name, your coverage area and credentials, your contact details, and your free/busy times. An agency cannot see what any block of busy time actually is — not the title, not who else is involved, not where. Agencies see only notaries who have accepted a connection with them.
Service providers. We use a small set of vendors to run NotaryBoard. They process data on our behalf, under contract, and may not use it for their own purposes:
Advertising measurement (marketing pages only). Our public marketing pages use the Meta Pixel, a small piece of code from Meta Platforms, Inc. It sets cookies and tells Meta which of our public pages you visited, so we can measure our advertising and reach people who have visited notaryboard.io. Some privacy laws treat this as "sharing" personal information for cross-context behavioral advertising, and this paragraph is that disclosure. The pixel exists only on pages you can view without signing in — it is not present inside the application. Apart from the single agency-signup event described next, nothing about your account, your signings, or your calendar is ever sent to Meta. To opt out, use your browser's cookie controls or an ad blocker, or adjust your preferences at facebook.com/adpreferences. Meta describes its own use of this data at facebook.com/privacy/policy.
One agency-signup event. When a brand-new agency account is created, our server sends Meta a single signup event so we can measure whether our advertising brought us agencies. That event contains the event name, the time, the same Meta advertising cookies our marketing pages already set, and your IP address and browser type for matching — never your name, email, account contents, signings, or any calendar data. No event of any kind is sent for notaries. The opt-outs above apply here too: without the Meta cookies, the event carries no advertising identity.
Legal. We may disclose information if we're legally required to, or where we believe it's necessary to protect our rights or someone's safety.
Business transfers. If NotaryBoard is acquired or merged, your data may transfer with it, subject to this policy.
We never sell your personal information. Aside from the marketing-page Meta Pixel described above, we don't share it for advertising or cross-context behavioral advertising — and data from inside the app, including calendar data, is never shared for advertising at all.
Disconnecting a calendar deletes its data immediately. When a notary disconnects a calendar in NotaryBoard, we delete the stored access and refresh tokens and every free/busy block that came from that calendar. Hold events we already wrote to your real calendar stay there — they're your events, on your calendar, and you can delete them yourself.
You can also revoke NotaryBoard's access directly with your provider at any time, at myaccount.google.com/permissions or myapps.microsoft.com. Revoking there stops all future syncing.
Otherwise we keep your account data for as long as your account is open. Signing records are retained while the account is active, because both sides usually need the history. To delete your account and the data attached to it, email us at the address below and we'll take care of it. We may keep limited records where we're legally required to — billing records for tax purposes, for example.
No system is perfectly secure, and we won't pretend otherwise. If you find a vulnerability, please tell us at the address below.
You can, at any time:
Depending on where you live — for example California, or the EU and UK — you may have additional rights to access, correct, delete, or port your personal data, to object to or restrict certain processing, and to be free from discrimination for exercising them. We honor these requests regardless of where you live. Email us and we'll respond within the time the applicable law requires.
NotaryBoard is operated from the United States and your data is stored there. If you're accessing it from elsewhere, you're sending your data to the United States.
NotaryBoard is a business tool for commissioned notaries and title professionals. It's not directed at children, and we don't knowingly collect data from anyone under 18. If you believe a child has given us data, contact us and we'll delete it.
If we change this policy we'll update the date at the top. For changes that materially affect how we handle your data, we'll tell you by email or in the app before they take effect. If a change would broaden how we use Google or Microsoft calendar data, we'll ask for your consent again rather than assume it.
Questions about this policy, or want your data exported or deleted? Email support@247closers.com and a human will answer.
247 Closers LLC
300 Main St, Suite 21 PMB 654
Madison, NJ 07940
United States