Comprehensive Privacy Notice

Account, identity, and organization

• Name, email, phone, photo, language, time zone, protected credentials, login provider, and basic Google or Microsoft profile data when you choose those sign-in options.
• Company, team, role, permissions, invitations, preferences, configurations, and administrative workspace activity.

Billing and commercial relationship

• Plan, usage, credits, invoices, tax details, billing address, payment history, and commercial support.
• Full card details are processed by payment providers such as Stripe; NuTalk receives identifiers, status, brand, and last digits rather than the complete card number.

Communications, contacts, and campaigns

• Names, phones, emails, platform identifiers, contact lists, messages, files, delivery status, notes, labels, conversation history, and CRM data.
• Call audio, recordings, transcripts, summaries, voicemail, telephony metadata, campaign results, and actions performed by agents.
• Purchased or connected phone numbers, phone-system and extension settings, routes, line status, NuTalk AiBox or gateway identifiers, and regulatory documents required by carriers.
• Data about customers managed by resellers, client portals, catalogs, services, availability, appointments, leads, pipelines, evaluations, and agent metrics.
• Information included by customers or end users in conversations, which may contain sensitive data. It should be uploaded only for a legitimate purpose and, where required, with express written consent.

Google and Microsoft scheduling data

• Host identity, calendar email, account and calendar identifiers, calendar names, OAuth grants, and protected access/refresh tokens.
• Free/busy periods, time zone, titles, dates, times, descriptions, location, attendees, responses, video-meeting links, and event status needed to schedule, reschedule, or cancel appointments.
• Each host connects their own account. NuTalk accesses it only after authorization, limits use to the selected scheduling functions, and lets the host disconnect through the dashboard or revoke access with Google or Microsoft.

Configuration, integrations, and support

• Prompts, voices, models, knowledge bases, goals, competencies, test scenarios, webhooks, encrypted keys or tokens, channels, APIs, automations, and settings for connected providers.
• Support requests, forms, emails, attachments, diagnostics, and feedback.

Technical and usage data

• IP address, browser, device, operating system, session identifiers, cookies, pages and features used, timestamps, audit logs, errors, performance measurements, and security signals.

Primary and necessary purposes

• Create, authenticate, and secure accounts; administer teams, permissions, and workspaces.
• Deliver contracted AI, voice, recording, messaging, campaign, CRM, evaluation, scheduling, calendar, telephony, phone-system, device, API, and reseller-portal features.
• Check availability and create, update, or delete authorized events; send invitations and meeting links.
• Process payments, measure usage, issue records, prevent fraud, and meet accounting, tax, contractual, and regulatory obligations.
• Provide support, diagnose failures, and maintain Service availability, security, auditing, and continuity.
• Respond to privacy rights, complaints, and legally valid requests.

Secondary and optional purposes

With consent where required, we may send product news, offers, surveys, or recommendations and analyze aggregated usage to improve the experience. These purposes are not necessary to deliver the Service. You can limit them through the unsubscribe link or at privacy@nutalk.ai without losing contracted features.

What NuTalk receives from Google

• Sign in with Google: your name, email address, and profile picture, to create your NuTalk account and sign you in.
• Google Calendar account: your Google email address and account ID, to show which account is connected and to avoid connecting the same account twice.
• Calendar list: the IDs, names, and colors of your calendars, which one is your main calendar, and which ones you can edit, so you can choose which calendars count as busy and which one receives appointments.
• Free/busy: when the calendars you choose are busy, so NuTalk offers only times when you are free.
• Events: the times of events in the calendars you choose and, in NuTalk’s calendar view, their ID, title, location, link, and whether they were canceled. For the calendar view, NuTalk asks Google for these fields only, never an event’s description, guest list, attachments, or call details. In clinic scheduling, NuTalk reads only what shows whether and when an event takes time (its times, ID, and time zone, whether it shows as busy, and the replies to the invitation without who sent them, to find your own), never its title or details.
• Events NuTalk writes: NuTalk creates, changes, and deletes only the events of appointments booked through NuTalk, plus the short test event of the clinic “Check connection” button (see below).
• NuTalk does not ask for access to Gmail, Google Drive, Google Contacts, or any other Google data.

How NuTalk uses it

• To offer only free times in the dashboard, through your workspace’s API and MCP, and to the AI agents that book appointments for you by phone, WhatsApp, or chat.
• To add each appointment booked through NuTalk to the calendar you chose, with a Google Meet link when the meeting type asks for one, and to send the invitation to the customer when they give an email address. Moving or canceling the appointment in NuTalk updates or removes that event.
• To show your Google events next to your NuTalk appointments in NuTalk’s calendar view.
• In clinic scheduling: to keep a doctor’s busy time out of the clinic’s agenda and to put the clinic’s appointments in the calendar the doctor chose. For that calendar, the “Check connection” button adds a short test event in the past and removes it right away.
• Sign-in data (your name, email address, and profile picture) becomes your NuTalk account profile, and NuTalk uses it like the rest of your account data (sections 2 and 4): to sign you in, show your name to your teammates, send you emails, bill your workspace, give support, and keep security and monitoring records.
• Apart from your account profile, NuTalk uses Google user data only for the features above. We do not sell it, use it to show ads or build ad profiles, or use it to decide credit or lending, and we do not use it, or anything derived from it, to create, train, or improve AI models.

What NuTalk stores, and for how long

• While a calendar is connected, NuTalk stores your Google email address and account ID, the access and refresh tokens Google issues (kept protected and never shown in the dashboard), the IDs, names, and colors of your calendars, which one is your main calendar and which ones you can edit, and the IDs and Google Meet links of the events NuTalk created.
• NuTalk does not save your other events or your busy times in its database: it reads them from Google when it needs them. In clinic scheduling, the server reuses busy times (never event details) from its memory for at most 30 seconds so repeated lookups stay fast; that memory is overwritten as new lookups come in or when the server restarts. Times an AI agent offered or booked stay in that conversation’s record, like the rest of the conversation.
• When you disconnect the calendar, NuTalk deletes the connection right away, including its tokens (the audit record described below stays). If that calendar still holds upcoming NuTalk appointments, NuTalk first asks you to move them or stop sending appointments there. Events of past appointments that NuTalk created stay in your calendar until you delete them.
• If access is revoked in Google (for example, you remove NuTalk from your Google Account), NuTalk stops using the connection and asks you to reconnect it. Until then NuTalk can’t change or remove the events it already created, upcoming appointments included: they stay in your calendar until you delete them, even if you then disconnect the account in NuTalk.
• Our security audit log records each change to a calendar connection, with the Google email address, account ID, and calendar IDs and names (never the tokens). These records stay in our database for 90 days, then are archived and kept indefinitely as security evidence, even after you disconnect the calendar.
• Sign-in details stay with your NuTalk account, as described in section 10.
• Copies in our backups disappear as those backups expire.

Who can see it

• People in your NuTalk workspace who can open scheduling see your busy time and, in the calendar view, the events from the calendars you chose. Clinic staff see a doctor’s busy time as “Busy” blocks, without event titles or details.
• If a NuTalk partner (a reseller) manages your workspace, its team can see what people in your workspace see.
• Your workspace’s API and MCP keys can read your free times, the connected Google account’s email address, and your calendars’ IDs and names, so your own tools can book and choose where appointments go.
• Customers you meet with receive the Google Calendar invitation with the details of their appointment.
• AI agents see only the free times NuTalk works out from your calendar, never your events. Those times are part of the agent’s conversation, so they reach the AI providers and conversation records described in section 5.
• The providers that run NuTalk process this data for us under confidentiality and security obligations: hosting providers such as Supabase and Vercel store and serve it, and for your account profile, Resend delivers the emails we send you, Stripe receives your email address when you set up billing for your workspace, and Langfuse receives the Copilot’s records, which include your email address.
• Each connection and its tokens belong to one workspace and one host; only that workspace, or the partner that manages it, can use them.
• Nobody at NuTalk reads your Google data unless you ask us to help with it, to investigate security problems or abuse, or when the law requires it.
• We do not share Google user data with anyone else, including advertisers, data brokers, and information resellers.
• If NuTalk is ever part of a merger, acquisition, or sale of assets, we will ask for your explicit consent before transferring your Google user data.

Google API Services User Data Policy

NuTalk’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

• Google API Services User Data Policy
• Limited Use requirements
• Google Workspace user data and developer policy

Your controls

• Disconnect a Google account in NuTalk from the host in Business scheduling or from the doctor’s calendar card in Clinic scheduling.
• Remove NuTalk’s access from your Google Account at any time at myaccount.google.com/linkedapps. From then on NuTalk can no longer read or write your calendar, so the events it already created, upcoming ones included, stay there until you delete them.
• To learn what Google data we hold about you, or to have it deleted, write to privacy@nutalk.ai (the security audit records described above are kept as evidence).

Microsoft Outlook

When you connect Microsoft Outlook, NuTalk reads and writes the same kinds of calendar data, with Microsoft Teams links instead of Google Meet, and applies the same rules for storing, sharing, and deleting it. You can remove NuTalk’s access in your Microsoft account settings.

What NuTalk receives from Meta

• Connecting Messenger with Facebook Login: the Facebook user ID of the person who connects, the Pages they manage and can message from (each Page’s ID and name, and the access token Meta issues for it), and the permissions they granted: pages_show_list, pages_manage_metadata, pages_messaging, and business_management. NuTalk uses business_management only to list the Pages a business portfolio owns.
• Connecting Instagram with Instagram Login: the professional account’s ID, username, name, and profile picture, the access token Meta issues, the ID Instagram gives the person who logged in, and the permissions they granted: instagram_business_basic and instagram_business_manage_messages.
• From each person who writes to the connected Page or account: the ID Meta assigns them for that Page or account, the name and profile photo Meta shares (Messenger: first and last name and photo; Instagram: name, username, and photo), what they send (text, photos, audio, video, files, and locations; posts, reels, stories, and other shares arrive as links), the buttons they tap, opt-ins and referrals (such as the ad or link that brought them), and delivery and read receipts for the business’s replies.
• On Instagram, Meta also sends NuTalk the messages the business sends from the Instagram app, so the conversation stays complete.
• NuTalk does not ask for access to the Page’s or account’s posts, comments, insights, ads, or followers.

How NuTalk uses it

• To connect the Page or account the person chooses, subscribe it to Meta’s message notifications, renew Instagram access before it expires, and check that the connection keeps working.
• To show the business’s Messenger and Instagram conversations in its NuTalk inbox, with each customer’s name and photo, so its team knows who is writing and can answer.
• To let the business’s AI agent answer, and to send its team’s replies, read receipts, and typing indicators back through Meta. Replies go out only within Meta’s messaging window, which closes 24 hours after the customer’s last message, and NuTalk uses no message tags.
• Photos are described and voice notes transcribed so the AI agent can understand them. The agent’s replies, those descriptions, and those transcriptions are produced as described in section 5.
• NuTalk uses Meta Platform Data only for these features. We do not sell, license, or buy it; use it for advertising or to build profiles, to decide anyone’s eligibility for credit, housing, employment, or insurance, or for surveillance; and we do not use it to train AI models.

What NuTalk stores, and for how long

• Each connected Page’s or Instagram account’s access token, while the channel is connected. It is kept on NuTalk’s servers in a table only those servers can read, and it is never shown in the dashboard.
• While you finish connecting, the tokens Meta issued for your login and the list of your Pages or your account. They are deleted as soon as the channel is connected; an attempt you don’t finish within 15 minutes is deleted within the following hour.
• The conversations: the messages, each customer’s ID, name, and photo, and delivery and read times, kept as the business’s conversation history while the channel exists, according to its plan and settings (section 10).
• One saved copy of each customer’s profile photo per chat, because Meta’s photo links stop working after a few days. A copy that Meta has not shown again in 90 days is deleted.
• Photos, audio, video, and files from those conversations, in NuTalk’s file storage.
• When the business deletes the channel (Channels > the channel > Delete channel), NuTalk unsubscribes the Page or account from Meta’s notifications, deletes its access token, and permanently deletes its conversations, messages, and saved profile photos. Photos, audio, video, and files from those conversations stay in file storage until their deletion is requested at privacy@nutalk.ai.
• If a teammate links a chat to a contact in NuTalk, the contact keeps the person’s Messenger or Instagram ID with the rest of the contact’s details.
• Our security audit log records each connection, reconnection, and deletion of a channel, with the Page’s or account’s name and ID (never tokens). These records stay in our database for 90 days, then are archived and kept indefinitely as security evidence.
• Copies in our backups disappear as those backups expire.

Who can see it

• People in the business’s NuTalk workspace who can open Conversations, and a NuTalk partner (a reseller) that manages the workspace.
• The business’s own API keys and MCP connections, which can read its conversations, and its webhooks, which receive the conversation events it chooses.
• The AI providers and conversation records described in section 5.
• The providers that run NuTalk (section 9), only to provide the service and on our instructions.
• Meta, which delivers the business’s replies, read receipts, and typing indicators.
• NuTalk staff access it only to support the business, to keep the service secure and working, or when the law requires it.
• We do not share Meta Platform Data with anyone else, including advertisers and data brokers. A Page or Instagram account can be connected to only one NuTalk workspace at a time.

Meta Platform Terms

NuTalk processes Meta Platform Data only as this section describes and under Meta’s Platform Terms and Developer Policies.

• Meta Platform Terms
• Meta Developer Policies

Your controls and deletion requests

• A business can delete a Messenger or Instagram channel in NuTalk at any time (Channels > the channel > Delete channel), with the results described above.
• Removing NuTalk from the apps and business integrations connected to your Facebook or Instagram account ends NuTalk’s access: Meta tells NuTalk, and NuTalk disconnects the channel and deletes its access token, keeping only the IDs Meta knows you by so it can still honor a later deletion request. The conversation history stays in the workspace until the business deletes the channel.
• If you also ask Meta to delete the data NuTalk received from your login, Meta sends NuTalk that request: NuTalk ends the connection you authorized, deletes its access token, records the request, and tells the workspace’s owners, who decide in Channels whether to delete the conversation history. Meta shows you a confirmation code; write to privacy@nutalk.ai with it to follow up.
• People who wrote to a business through Messenger or Instagram can ask that business to delete their messages, or write to privacy@nutalk.ai. We pass the request to the business, which decides about its conversations (section 1), and help it carry the request out.
• Step-by-step deletion instructions are at nutalk.ai/data-deletion.

• Data deletion instructions

Consent to transfers

By accepting this Notice or activating an integration, you authorize the transfers described here when consent is required. Consent is not required in the cases permitted by Article 36 of Mexico’s LFPDPPP, including transfers needed to perform a legal relationship or a contract in your interest. You may refuse or withdraw consent at privacy@nutalk.ai; this may disable features that depend on the third party. Corporate transfers in a merger, acquisition, or reorganization remain subject to this Notice.