How TeleServ uses data from Google

TeleServ'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.

What TeleServ reads

A business that uses TeleServ can connect one Gmail or Google Workspace mailbox, such as the shared mailbox its customers write to. An owner or admin of that business connects it by signing in as the mailbox and approving read-only access to Gmail (the gmail.readonly permission). That is the only Google permission TeleServ asks for. TeleServ never asks Google for permission to send, change or delete mail.

• TeleServ reads two parts of the one mailbox the admin connected, and only mail from after the connection: the inbox, for the email customers send, and the Sent folder, for the replies the company sends them.
• It never reads mail from before the connection, drafts, spam, chats or any other folder or label. Mail in the trash is not read from the inbox; a message the mailbox sent can still be read after it is moved to the trash.
• For each email in the inbox it reads the sender, recipients, subject, date, the message text and the names, types and sizes of attachments. It never stores attachment content.
• For each sent message it reads the sender, recipients, subject, date and the message text. It keeps a sent message only when it went to at least one person outside the company, came from the connected mailbox or another address of the company, and is not automated mail or a forward of someone else's email. Every other sent message, for example mail only to colleagues, is discarded without being stored. Attachments of sent mail are not stored.

How TeleServ uses it

• Only to provide TeleServ to the company that connected the mailbox: to summarize each customer email and flag complaints and other issues using the company's own rules, to show which customer emails were answered and how quickly, to link emails, calls and the company's own records about the same customer request, and to show those results and send alerts to that same company's staff inside TeleServ and by email.
• Sent replies are never flagged or scored. TeleServ uses them to show the company's side of each conversation, and gives the latest reply to the AI as context when it reads the customer's next email.
• TeleServ does not use Google data for advertising, does not sell it, and does not share it with data brokers or anyone else for their own purposes.
• TeleServ does not use Google data to train general AI or machine learning models. A correction a company gives TeleServ about one of its own emails is kept as that company's own instruction and used only for that company.
• TeleServ treats the text of every email as data, never as instructions. Hidden text is removed before analysis, and the AI must quote the email's own words for every flag, so text in an email cannot change what TeleServ does.

AI and your Google data

TeleServ uses AI (Anthropic's Claude, through its business API) to summarize and flag each email for the company that connected the mailbox. Data received from Google Workspace APIs is never used to develop, improve or train general AI or machine learning models, and is never sent to an AI service that trains on it: our AI provider's commercial terms do not allow training on our data. A correction a company gives TeleServ is kept as that company's own instruction only. The morning briefing, which can mention emails, is read aloud by ElevenLabs when someone plays it; ElevenLabs receives the briefing's wording only, never an email itself, and we have opted out of ElevenLabs using it to train its models. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

How TeleServ stores and protects it

• Card numbers, card details, passwords and PINs are masked before anything is stored, in received mail and sent mail alike.
• A copy of each customer email as received, masked, is kept for 90 days and then deleted by a daily job. The masked text, the stored replies and the results stay for as long as the company has a TeleServ account, unless the company deletes them sooner.
• The sign-in Google gives TeleServ is stored encrypted (AES-256), and all data is encrypted in transit and at rest.
• Each company's data is kept apart from every other company's, and TeleServ checks which company a person belongs to before it shows them anything.

Who can see it and who receives it

• The staff of the company that connected the mailbox, inside TeleServ, and the people that company chooses to receive its email alerts.
• TeleServ's service providers, each only to run TeleServ for the company and under contract to protect the data:
  • Hosting and database: Supabase, where the data is stored and processed, and Vercel, which runs the TeleServ app.
  • AI analysis: Anthropic, which receives the masked text only to analyze it for TeleServ, under terms that forbid using it for training.
  • Email delivery: Postmark, which delivers TeleServ's alert emails to the company's staff. When an admin has connected Microsoft 365 to send as themselves, an escalation can also go out through that admin's own Microsoft account.
  • Voice: ElevenLabs, which turns the morning briefing into speech when someone plays it. It receives the briefing's wording only, never an email itself.
  • Google itself, which TeleServ reads the mailbox from.
• No person at TeleServ reads it, except with the company's permission (given in our agreement) to provide support, where needed for security, or where the law requires. A TeleServ support session in a company's workspace ends on its own after 8 hours.
• TeleServ transfers Google data to no one else, except where the law requires it or, with the company's explicit consent first, as part of a merger or sale of TeleServ.

Deleting it

When an admin disconnects the mailbox in TeleServ, TeleServ asks Google to end its access, deletes its stored sign-in, stops reading the mailbox, and deletes every email and reply it read only through that mailbox, with the results. A company can also delete all its email data at any time from its Integrations page, or ask us in writing at privacy@teleserv.ai. The mailbox's own Google Account can also remove TeleServ's access at any time, under Security, Your connections to third-party apps; TeleServ then stops reading it, and what it already read is deleted when an admin disconnects the mailbox in TeleServ or asks us to delete it.

Changes to this page

When TeleServ changes how it uses Google data, it updates this page, with the date above and a note here, and tells the admins of every company with a connected Google mailbox by email.

• October 7, 2026: TeleServ now also reads the Sent folder of the connected mailbox, to show which customer emails were answered and how quickly. This page now names TeleServ's service providers.
• October 7, 2026: added AI and your Google data, which names the AI services TeleServ uses and how they may use the data.
• September 27, 2026: first version.

More

The TeleServ Privacy Policy covers everything else TeleServ processes. Questions about this page: privacy@teleserv.ai.