Privacy Policy

How Manu Labs, LLC handles personal information when you use Patch Outbound, and when an AI assistant using Patch Outbound calls you. Effective October 28, 2026.

1. Who this covers
2. What we collect
3. How we use it
4. Who we share it with
5. Verification messages
6. If you received a call
7. How long we keep it
8. Cookies and links
9. Security
10. Your choices and rights
11. Children
12. Where data is processed
13. Changes
14. Contact

1. Who this covers

Two kinds of people are covered. Users verify a phone number with Patch Outbound and connect an AI agent to it. People called answer, or are recorded on, a call placed through the Service. Visitors who simply browse sales.patchmcp.com are covered too. Manu Labs, LLC is the controller of this information. It does not cover the AI client you connect (Grok, Claude, ChatGPT and so on), which handles your conversation with your agent under its own privacy policy.

2. What we collect

From users

Phone number. The mobile number you verify. It identifies your account and is the default outbound caller ID. We also store any owned Patch numbers and their direction settings. We also record whether it is verified.
Name and call defaults. The name used in the call introduction, your default language and region, saved voices by region, and any custom call agent instructions.
Custom voices. If you choose voice cloning, we process the audio you record or upload, send it to ElevenLabs to create your clone, and store its name, provider identifier, status, consent timestamp, and a short generated preview. Recording alone does not upload audio; you must choose Create my voice.
Outbound prospect lists. If you upload a list for outbound calling, we store the prospect phone numbers and any names, companies, titles, email addresses, time zones and notes you provide, along with call attempts, outcomes and callbacks you record.
Billing details. If you subscribe, the email address you give Stripe, your Stripe customer and subscription identifiers, your plan, its status and billing period. Card numbers go directly to Stripe; we never see or store them.
Connected apps. Which MCP clients you have authorized, when, and the tokens that let them act for you (stored hashed).
Sessions and device data. A session cookie, your browser's user-agent string, and your IP address, which we use for sign-in, security and rate limiting.
Text messages. Verification request details and status (section 5).
Usage records. For every call, what your plan was charged for it and what it cost us to carry: connected minutes and the tokens and seconds of audio our AI provider billed. They are what your account page's usage figures are made of.
Support messages. Anything you send to leko@patchmcp.com.

From calls

Call records. For every call: the destination number and name your agent supplied, the objective and any context, the maximum length, when it was placed, answered and ended, how it ended and why, its duration, whether a machine or a person answered, and any carrier error.
Audio and transcript. LiveKit records session audio and produces transcripts. The Patch playback copy starts at detected telephone pickup and excludes conversation after a direct transfer out of the agent session; recordings may be unavailable if processing or upload fails. The transcript, a structured result extracted from it (outcome, summary, commitments, follow-ups, key facts) and a link to the recording are attached to the call.
Do-not-call requests. Numbers that ask for no more calls, whether during a call or on the do-not-call page, together with the reason and the call it came from.

We do not collect information from data brokers. Our first-party acquisition measurement is described in section 8.

3. How we use it

to place your calls from your number, run the voice assistant during them, and return results to you and your agent;
to verify that you control your number, sign you in, and keep your account and connected apps secure;
to screen each objective before dialing, enforce the opt-out list and your plan's allowance, and investigate abuse;
to send the verification codes you request;
to meter calls and plan usage, take payment, and send receipts;
to run, monitor, debug and improve the Service, and to keep logs of requests and errors;
to respond to you, notify you of changes to the Service or these policies, and comply with law, carrier and regulatory requirements.

Personal information is never sold or used by us to train AI models. Phone numbers and call content are never used for advertising. Advertising measurement uses only the limited data described in section 8. We send call content to the AI providers described below to conduct and review your calls.

The Service runs on the following providers, each of which receives only what its role requires and is bound by its own terms and privacy policy:

Provider	Role	What it receives
Telnyx	Telephony and verification: delivers verification codes, provides telephone connectivity, retains historical recordings, and holds your number as a verified caller ID	Your number, verification request details, destination numbers, and call audio and recordings handled by Telnyx
LiveKit Cloud and its inference providers	Call sessions, speech recognition, language-model responses, structured results, session recordings and diagnostics	Call audio, objectives, context, transcripts and usage metadata
ElevenLabs	Speech synthesis for the LiveKit voice agent; optional voice cloning and voice previews	Text spoken by the assistant, the selected voice, and voice samples you choose to submit for cloning or preview generation
TypeSafe AI	JEV decisions for call objective screening, first-turn classification and call closing	Call objectives, context, destination and callee names for screening; spoken conversation excerpts needed to classify the answer or farewell
Private recording storage	Stores the playback copy uploaded from the LiveKit session	Call audio and call-scoped recording identifiers
Stripe	Payments, subscriptions, receipts and the billing portal	Your email, plan, payment method and billing history
Railway	Hosting: the application, its database and cache	Everything stored by the Service
Google Ads	Advertising measurement	Ad click IDs, random event IDs, milestone timestamps and paid-subscription value and currency; no phone numbers or call content
Google Analytics	Website and app measurement described in section 8	Pseudonymous browser identifiers, generic page labels, milestone events and ordinary browser/connection information; no phone numbers or call content

We also share information with your connected AI clients (account call history, statuses, transcripts, results and call links), with the people you call (your name as given in the call introduction and your phone number as the caller ID), and when required with carriers, regulators, law enforcement or courts, or to protect the rights and safety of users, people called, or Manu Labs, LLC. If Manu Labs, LLC is acquired or the Service is transferred, this information may move with it under the same commitments.

5. Verification messages

We send one-time codes when you request verification of your number. We store verification request details and status to complete sign-in and prevent abuse. Our telephony provider delivers the code.

No mobile information will be sold or shared with third parties for promotional or marketing purposes. Your number is used to run the Service and is shared with the providers listed in section 4 only as needed to provide it. Existing message records from the retired messaging feature remain subject to the account deletion policy in section 7.

6. If you received a call

A call from an AI assistant using Patch Outbound was requested by one of our users. The default opening identifies who the assistant is calling for and why, and its instructions require a recording disclosure in the first spoken turn that advances the objective, including an answer, question or request. The default instructions also require it to confirm that it is an AI if asked. Everything said on the call is recorded and transcribed, and the recording, transcript and a summary go to the user who requested the call. The number on your caller ID is the user’s selected outbound number, which may be their verified personal number or an owned Patch number.

You can:

tell the assistant you would rather not continue, and it will end the call;
ask the assistant for no more calls, or enter your number on the do-not-call page, after which no user of the Service can reach it;
email leko@patchmcp.com to ask what we hold about a call to your number, or to ask us to delete the recording and transcript. We will need to confirm you control the number.

7. How long we keep it

Account, settings and call records (including transcripts and results) are kept for as long as your account exists so you and your agents can review your history, and deleted within 30 days of a verified deletion request.
Outbound prospect lists and call outcomes are kept with your account. Email leko@patchmcp.com to request deletion of your account or this information.
Voice clones remain in your account until you delete them in Voice studio. Patch does not persist the original uploaded sample; ElevenLabs stores the clone and its samples. Deleting a clone requests their removal from ElevenLabs and removes its metadata and generated preview from Patch. If deletion fails, the studio retains the request so you can retry. Downgrading pauses access without deleting clones.
Recordings for new calls are finalized by LiveKit and copied to private storage for Patch playback. LiveKit also retains session recordings and diagnostics under the project’s retention settings; its retention does not delete the Patch copy. The private copy is not processed by LiveKit Cloud’s PII redaction. Older recordings may remain with Telnyx. Patch playback uses signed links that expire after about an hour, or token-free links while the call is public. Recording deletion is a support process that must remove provider and private-storage copies as well as the call record.
Do-not-call numbers stay on the list for good; a block we forgot would be no block at all.
Historical text messages to and from your number are kept with your account, deleted within 30 days of a verified deletion request, and a recorded STOP is kept for good so the opt-out is not lost. Pictures attached to those messages were hosted by Telnyx for 30 days.
Sessions expire after 30 days; connected-app tokens are removed after they expire or when you disconnect the app; verification codes expire within 10 minutes.
Server logs (request metadata, errors, call identifiers; never call audio) are kept for a limited period for security and debugging.
Billing and usage records are kept as long as tax and accounting law requires.

8. Cookies and links

We also use Google Analytics 4 across our public website and customer app, including verification, connection, account, call and upgrade pages to measure visits, traffic sources, and whether visitors connect an AI client, complete a first successful call, or make a first subscription payment. This runs automatically using Google Analytics browser cookies with a 90-day expiration. We send generic page labels (for example, /listen/call rather than a call ID), referring origins, public-page campaign labels and validated Google ad click identifiers, pseudonymous browser identifiers, clicks on connection controls identified only by a fixed placement label, successful phone verification and acquisition milestone events; payments include the amount and currency. Google receives ordinary browser and connection information when its tag loads. We do not send phone numbers, verification tokens, private account or call URLs, names, call objectives, transcripts or recordings. Automatic form and outbound-link collection, Google signals and ad personalization are disabled. Global Privacy Control prevents the Google tag from loading and removes our saved browser association. Previously submitted data is subject to Google’s privacy policy.

sales.patchmcp.com uses a session cookie to keep you signed in for up to 30 days. First-party analytics runs automatically across public and customer app pages using generic page labels. We count page views and visits using random browser identifiers, group visits after 30 minutes of inactivity, and record the page path and source (such as direct, search, social, campaign or referring hostname). We do not collect full referrer URLs, search queries, private account or call-page URLs, or use fingerprinting. Browser traffic data is retained for up to 90 days. We honor Global Privacy Control by preventing capture, removing saved attribution and stopping pending reporting when we receive that signal. A separate, opaque cookie links Google ad click identifiers (GCLID, GBRAID or WBRAID), campaign tags or website source information to your account after you verify access. Attribution expires after 90 days. Direct, social, referral and organic source information stays in our first-party measurement and is not sent as a Google Ads click conversion. For advertising measurement, we send Google only click identifiers, milestone timestamps, random event IDs and, for a successful paid subscription payment, value and currency. Milestones are successful client tool discovery or use, the first completed call whose result says the objective was achieved, and the first successful subscription payment. We do not send phone numbers, names, call objectives, transcripts or recordings. Data already sent to Google is governed by Google’s privacy policy. Minimal milestone records remain with the account until deletion; source information, click identifiers and reporting payloads are removed when attribution expires.

Private links your agent gives you to your account, a live call or checkout carry a signed, expiring token. Public call links have no token or expiration and remain accessible while the call is public.

9. Security

Traffic to the Service is encrypted in transit. We store access tokens only as hashes, private share links to recordings and live calls carry a signature and an expiry, events our providers send us are checked against their signatures, and calls are private by default, visible to you or someone holding a valid private link. If you choose to make a call public, anyone with its permanent link can view the call details, transcript and result, and hear its recording or live audio. You can make it private again at any time to disable access without a token; existing private links remain valid until they expire. No system is perfectly secure; if we learn of a breach affecting your information we will notify you as the law requires.

10. Your choices and rights

From your account page you can change your name and call defaults, disconnect apps, and manage or cancel your subscription. By emailing leko@patchmcp.com you can ask for a copy of the information we hold about you, ask us to correct it, ask us to delete your account and calls, or object to a use of it. We will verify the request, usually with a code texted to the number concerned, and respond within 30 days. The law where you live (California, Canada and the European Economic Area, for example) may give you some of these rights, along with the right to complain to a supervisory authority; we extend them to everyone regardless, and exercising them never changes how we treat you.

11. Children

The Service is for adults. We do not knowingly create accounts for anyone under 18, and users may not direct calls at children. If you believe a child has an account or has been called improperly, contact leko@patchmcp.com and we will act on it.

12. Where data is processed

Manu Labs, LLC is based in the United States and the Service is hosted there. Calling coverage includes the Åland Islands, Albania, Andorra, Argentina, Austria, Belgium, Belize, Bolivia, Bosnia & Herzegovina, Brazil, Bulgaria, Canada, Chile, Colombia, Costa Rica, Croatia, Cyprus, Czechia, Denmark, Ecuador, El Salvador, Estonia, Falkland Islands, Faroe Islands, Finland, France, French Guiana, Germany, Gibraltar, Greece, Greenland, Guatemala, Guernsey, Guyana, Honduras, Hungary, Iceland, Ireland, Isle of Man, Italy, Jersey, Kosovo, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Mexico, Monaco, Montenegro, Netherlands, Nicaragua, North Macedonia, Norway, Panama, Paraguay, Peru, Poland, Portugal, Romania, Russia, San Marino, Serbia, Slovakia, Slovenia, Spain, St. Pierre & Miquelon, Suriname, Svalbard & Jan Mayen, Sweden, Switzerland, Ukraine, United Kingdom, United States, Uruguay, Vatican City, and Venezuela, subject to carrier and route availability. If you use the Service from elsewhere, your information is transferred to and processed in the United States, where privacy law may differ from your country's.

13. Changes

We may update this policy. The effective date at the top shows the current version. For material changes we will give notice on sales.patchmcp.com, or by email if we have one, before the change takes effect.

14. Contact

Manu Labs, LLC · leko@patchmcp.com. Please include the phone number concerned so we can find the right records.