Privacy and what data we access

Your calendar is one of the most sensitive datasets you own, and a scheduling tool is an odd thing to hand it to. This page is the plain-English version of what Neos Meet can see, what it stores, and how to take it back. The binding documents are the privacy policy and the terms.

Every permission, separately

Sign-in

Your name, email address, and profile photo. Nothing else, and no calendar access whatsoever. This is all you grant by signing in.

Google Calendar — The start and end times of your busy blocks

So a booking link can't offer a slot you're already committed to. We request the granular free/busy scope, which cannot return event titles, guests, descriptions, or attachments — that limit is enforced by Google, not just promised by us.

Google Calendar — The list of calendars in your account — their names, not their contents

So you can tick which calendars should be checked for conflicts, instead of copying a Calendar ID out of Google's settings and pasting it to us. It returns the list and nothing else: this scope cannot read a single event, and your busy times still come from the free/busy scope above, which Google keeps incapable of returning titles or guests. It is read-only — we cannot add or remove calendars from your list. What it does mean, plainly: we see what your calendars are called.

Google Calendar — Permission to create and manage events on calendars you own

So a confirmed booking becomes a real calendar invite with a Google Meet link. Google publishes no Calendar scope restricted to the events an app created, so this is the narrowest write scope that lets us book at all — unlike the free/busy line above, this is a limit we keep, not one the API enforces. Our code only ever creates and manages the events Neos Meet books, and never lists or reads your other events. It does not cover calendars merely shared with you.

Outlook / Microsoft 365 — Read and write access to the calendars in your Microsoft 365 mailbox

So a booking link can't offer a slot you're already committed to, and so a confirmed booking becomes a real Outlook invite with a Teams link. Microsoft publishes nothing narrower that can do both: it has no equivalent of Google's title-blind free/busy scope, and creating an invite needs write access to the whole mailbox, with no scope restricted to the events an app created. So unlike our Google free/busy grant, this is a limit we keep rather than one the API enforces. What our code actually does with it: read the calendars you tick to find the times you're busy, and create, move and cancel the events Neos Meet books. When we read a calendar we ask Microsoft for four fields only — start, end, busy/free status, and whether the event was cancelled — so your titles, guests and notes are never sent to us at all. That is a stronger limit than promising to look away, and it is still ours to keep rather than Microsoft's to enforce: this permission would allow the wider read, and only our own request stops it.

Calendar grants are requested only when you choose to connect a calendar, and only for the provider you connect. Revoke them at any time from your Google Account permissions page or your Microsoft My Apps page, or by disconnecting in Settings.

Disconnecting a Googlecalendar asks Google to revoke the grant and tells you if Google didn't confirm it, so you know whether the permissions page still needs a visit. Disconnecting a Microsoft calendar deletes our copy of the credential, but we cannot revoke the consent on your behalf: Microsoft offers no per-application revoke for a delegated grant — the only alternatives are an administrator action or signing you out of every application you have ever authorised, which is not ours to do. So for Microsoft, finish the job on the My Apps page above. We would rather say that plainly than let you assume we did something we cannot.

What we store

• Your account: name, email address, profile photo, booking handle.
• Your configuration: event types, availability hours, timezone, team links, and host pools.
• Your bookings:the meetings booked through your links, including the invitee's name, email address, timezone, and any answers to your custom questions.
• A calendar credential for each connected calendar, used server-side only to make requests to Google on your behalf.

Free/busy data itself is not warehoused — it is read when a booking page is rendered, used to decide which slots to show, and discarded.

What your invitees experience

• They do not need an account, and one is not created for them.
• They see the times you are free, never the reason you are busy.
• Booking pages carry no session recording and no advertising trackers.
• They provide their name, email, and any answers you asked for; that goes to you and onto the calendar invite, not to anyone else.

Who else processes your data

We do not sell data. We use a small set of sub-processors to run the service — hosting, database, payments, transactional email, product analytics, and Google itself for calendar and video. The current list is maintained in the privacy policy, which is the authoritative version.

Analytics

We measure product usage, but hosts are identified to our analytics provider by an anonymous identifier or one-way hash rather than by email address, calendar data is never sent, and invitee booking details are never sent. Public booking pages are not session-recorded.

Deleting your data

• Disconnect a calendar from Settings at any time. This removes the stored credential and stops all access.
• Export your data from Settings → Data & privacy. The download is a JSON file containing your profile, event types, availability, bookings and their invitees, team links, calendar connections, and a billing summary. Invoices are not in it — download those from the billing portal.
• Delete your account from Settings → Data & privacy. This is immediate and cannot be undone. It cancels your upcoming meetings and emails your invitees, revokes our access to your Google account with Google, cancels any subscription, and removes your payment profile from Stripe. Export first if you want a copy — the download is gone once the account is.
• What survives deletion: paid invoices and receipts, which tax and accounting law require us to keep; database backups, which age out on their normal retention cycle rather than being edited; a deleted-account marker, stored as a one-way hash of your email rather than the address itself, so your booking handle is not silently reassigned during its quarantine window and the account cannot be re-created behind your back; and — if you had ever unsubscribed or an email to you had bounced — the email-suppression record that keeps us honoring that, since deleting your account does not license us to email you again. Each keeps the minimum needed to honor a promise to you.
• Revoke everything from Google's side at myaccount.google.com/permissions, which cuts access immediately regardless of anything on our end.

What we don't claim

Neos Meet is not SOC 2 certified, not ISO 27001 certified, and does not offer HIPAA business associate agreements. Do not put protected health information into booking questions or meeting notes. The security page keeps the full, current list of what we do and do not hold — including the things we would rather you learned from us than from a procurement questionnaire.

Still stuck?

Email support@neos.network with your booking link and, if there is one, the exact time an invitee tried to book. A real person reads it — there is no bot in front of us.