Neos Meet uses the third parties below to run the Service. Each of them processes personal data on our behalf, under our instructions, and is bound by its own data processing terms. This page is the list referenced by our Privacy Policy and by Annex B of our Data Processing Addendum.
Vercel
EntityVercel Inc.
PurposeApplication hosting, serverless execution, and content delivery
DataAll data in transit through the Service, plus request metadata (IP address, user agent) in operational logs
LocationUnited States (functions pinned to US West)
Neon
EntityNeon Inc.
PurposeManaged PostgreSQL database — the system of record
DataHost accounts, booking links, availability, bookings and invitee details, calendar credentials
LocationUnited States (us-west-2)
Google
EntityGoogle LLC
PurposeHost sign-in, calendar free/busy lookups, booking events, and Google Meet links
DataHost identity (name, email, profile photo), free/busy intervals, and the events we create for confirmed bookings
LocationUnited States and Google's global infrastructure
Stripe
EntityStripe, Inc.
PurposeSubscription billing, payment processing, tax calculation, and invoices
DataBilling name, email address, billing address, payment method (held by Stripe, never by us), and invoice history
LocationUnited States
Resend
EntityResend, Inc.
PurposeTransactional email — booking confirmations, reminders, cancellations, and account notices
DataRecipient email address and the contents of the message (meeting title, time, host and invitee names). No open-tracking pixels and no click/link rewriting are enabled, so a message is not instrumented to report whether you opened it; the only links are plain first-party URLs, some tagged with a campaign source (utm_source) that names the channel, not you
LocationUnited States
PostHog
EntityPostHog, Inc.
PurposeProduct analytics — which pages and features are used, and which campaigns lead to signups
DataPageviews, feature events, and marketing attribution, keyed to an anonymous identifier. Never calendar data, never invitee details, never host email addresses
LocationUnited States (US cloud region)
Sentry
EntityFunctional Software, Inc. (Sentry)
PurposeError and performance monitoring
DataStack traces, error messages, and technical context. Configured not to attach request bodies, cookies, headers, or IP addresses
LocationUnited States
AI setup assistant
EntityAmazon Web Services, Inc.
PurposePowers the optional “Set up with AI” scheduling assistant, which turns a plain-English description of how you meet into a proposed booking-link and working-hours configuration.
DataSent only when a host uses the in-product setup assistant: Your side of the assistant conversation (what you type); The titles and descriptions of the event types it helps you edit; Any location detail on those event types — your own meeting URL, phone number, or address. Never sent: Any Google Calendar data — your free/busy times, your events, or any connected-calendar contents; Invitee names, emails, or anything an invitee entered; Your bookings. Amazon Bedrock does not use your inputs or outputs to train any model, and does not share them with model providers. No Google account data is sent to it, and nothing you send it is used to train or improve any AI model.
LocationUnited States
International transfers
All of the sub-processors above are United States entities and the Service is hosted in the United States. If you are in the EEA, the UK, or Switzerland, personal data you submit is transferred to the United States. Those transfers rely on the Standard Contractual Clauses (or the equivalent UK Addendum) as incorporated by each provider's data processing terms, and by ours.
Not sub-processors
Anything not on this list does not receive your data. In particular, we do not use advertising networks, we do not sell or share personal data for cross-context behavioural advertising, and we do not send Google Calendar data or invitee booking details to any analytics or AI provider.
