Privacy Policy

Last updated: October 29, 2026

1. Who we are

Mebot AI Corp, a Delaware corporation ("Mebot", "we", "us"), makes Mebot Selfware, available at selfware.mebot.ai and through our integrations (the "Service"). This policy explains what personal information we handle when you visit www.mebot.ai, use the Service, or interact with someone else's Mebot, and the choices you have.

For personal information about our account holders, Mebot is the controller (the "business" under California law). Section 7 explains how we handle information about people who interact with a user's Mebot.

2. What we collect

Account information

We use a third-party sign-in provider to sign you in. When you create an account we receive your email address, your name, your profile picture if your sign-in provider has one, and a sign-in account ID. If you choose "Sign in with Google", Google shares only your basic profile (name, email address and profile picture) with us through our sign-in provider. We do not get your Google password, and signing in does not give us access to your Gmail, Drive or Calendar.

Content you give the Service

• Documents, notes and transcripts you upload or paste, including meeting and call transcripts.
• Answers you give in the onboarding interview and in chat.
• Photos, videos and voice recordings you provide so we can create your avatar and a voice for it.
• Information about other people that appears in your content, such as contacts, colleagues and meeting attendees, and contacts you add (names, phone numbers, email addresses, notes).

Information we derive from your content

The Service uses AI to extract memories, facts, values, preferences, relationships and a communication style from your content. Together these make up your profile ("digital self"). You can review this profile in the Service, and you choose which memories stay private and which may be shared or made public.

Conversations and activity

• Chat history with your Mebot, and chats that other people you have shared it with have with it.
• Video and voice sessions with your avatar. While a video session runs, the avatar provider may analyse the camera image (and, if shared, the screen) to respond naturally. That can include reading facial expressions and apparent emotional state. The owner of a Mebot can turn camera perception off.
• Phone calls and texts handled by your Mebot, if you turn on telephony: phone numbers, call times and durations, message content, and a transcript of the call. Calls are transcribed as they happen. We do not record call audio.
• Meetings you send a Mebot meeting bot to: the meeting link, attendee names, the transcript and, where the bot records, the recording. The recording is held by our meeting-bot provider.

Connected services (only if you connect them)

• Google Calendar: your calendar list and the events on the calendars you select (see section 5).
• Slack: messages in the channels and conversations you choose to sync, and your Slack workspace's member names.
• AI tools (MCP): requests that AI tools you authorise, such as Claude, make to your Mebot.

Billing

If you buy a plan or credits, our payment processor handles your payment. We receive your name, email address, what you bought and the payment status. We never see or store your full card number.

Usage and technical information

We record which features you use and how much (for example AI tokens, call minutes and video minutes) so we can bill, set limits and keep costs under control. Our servers log requests (IP address, browser type, the page or API called, timestamps), and we collect error reports so we can fix bugs. We do not use third-party analytics or advertising trackers.

Messages from us

We send account and access emails (for example, when you come off the waitlist) through an email delivery provider. These use your email address and first name.

3. How we use it

• To provide the Service: build and update your profile, answer as you in chat, voice and video, run the meeting bots, calls and texts you ask for, and work with the services you connect.
• To share on your terms: to let people you choose, or visitors to links you publish, talk to your Mebot, limited to what you have marked shared or public.
• To run the account: sign-in, waitlist and access, billing, usage limits and customer support.
• To keep the Service safe and working: security, abuse prevention, debugging, and preventing runaway costs.
• To meet legal obligations and enforce our Terms of Service.

We do not sell personal information. We do not "share" it for cross-context behavioural advertising, and we do not use it for advertising of any kind.

4. AI processing and model training

Mebot works by sending parts of your content to AI model providers when a feature needs it. For example, when your Mebot answers a question, the relevant memories and the conversation go to a language model. When we index your content for search, its text goes to an embedding model. We use several AI providers: language models (including some for fast or backup replies), an embedding model, voice, and video avatars. The subprocessor page describes what each kind of provider receives, and we will name them on request.

• Mebot does not use your content to train AI models, its own or anyone else's. Your profile is used only for your Mebot.
• Our main language-model and embedding providers do not use data sent through their business APIs to train their models under their current commercial terms.
• AI output can be wrong. Your Mebot is an AI system that imitates how you communicate. It is not you, and it can make mistakes about facts and about you. See our AI disclosure.

5. Google user data

If you connect Google Calendar, we ask Google for two permissions: to see and edit events on your calendars (calendar.events) and to see your list of calendars (calendar.calendarlist.readonly). We also receive your Google account's email address and ID so we can tell connected accounts apart. We do not ask for access to Gmail or Google Drive through this connection.

We use this data only to show your calendar in Mebot, to let you send a Mebot to meetings on it, to let your Mebot answer your own questions about your schedule, and to create or change events when you confirm it. Calendar details are shown only to you. They are never given to people you share your Mebot with or to public-link visitors. We read events from Google when they are needed and keep them only in a short-lived cache. Calendar events are not turned into memories. When your Mebot answers you using your calendar, the relevant events are sent to our language-model provider to write that answer.

Mebot'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. In particular:

• We use Google user data only to provide and improve the user-facing features described above.
• We do not transfer it to others except as needed to provide those features (for example to our hosting and language-model providers), to comply with the law, for security, or as part of a merger or acquisition with notice to you.
• We do not use it for advertising, and we do not sell it.
• No person at Mebot reads it unless you ask us to, it is needed for security or to comply with the law, or it has been aggregated and anonymised for internal operations.
• We do not use Google Workspace or Google user data to develop, improve or train generalised AI or machine-learning models.

Your Google access tokens are stored encrypted. When you disconnect Google Calendar, we revoke our access at Google and delete our copy of the tokens. You can also remove Mebot's access at any time from your Google Account permissions.

6. Who we share it with

• Service providers (subprocessors) who host, run or support the Service for us, under contract, and only for that purpose. The kinds of provider and what each receives are on our subprocessor page; contact us for their names.
• People you choose. When you share your Mebot, publish a public link, send it into a meeting or let it call or text someone, those people see what your Mebot says. That is limited to what you have marked shared or public, plus what you tell it to say.
• Services you connect, such as Google, Slack or file storage services, and AI tools you authorise, receive what you direct them to receive.
• Legal and safety: where we must by law or legal process, or to protect the rights, safety or property of our users, the public or Mebot.
• Business transfers: if Mebot is involved in a merger, acquisition or sale of assets, personal information may be transferred under this policy. We will tell you before it becomes subject to a different policy.

7. People who talk to a Mebot

You may meet a Mebot without having an account: a user's Mebot may call or text you, join a meeting you attend, or answer you on a link the user shared. A Mebot always says it is an AI acting for its owner (see our AI disclosure).

When that happens, we process what you say and share in that conversation (for example your voice transcribed to text, your messages, your phone number or name, and in video sessions the camera image), and the transcript is kept in the owner's account. The owner may also store notes about you as a contact. We do this to provide the Service to that owner. We do not create voiceprints to identify you, and we do not use your conversations for any other customer or to train AI models.

You can ask us what we hold about you, ask us to correct or delete it, or object to it, even without an account, by emailing support@mebot.ai. To stop calls or texts from a Mebot, see how to opt out.

8. Where your data is stored

The Service is hosted by a cloud hosting provider in the United States. Our database and the files you upload are stored there. Encrypted backups of the database and uploaded files are kept with a separate cloud storage provider in the United States. Our subprocessors may process data in other countries; contact us to find out where each is based. If you use Mebot from outside the United States, your information is transferred to and processed in the United States.

9. How long we keep it

• Your account and content (profile, memories, documents, transcripts, chat history, avatar and voice materials) are kept while your account is open, because the Service exists to remember them. You can delete individual items in the Service.
• When you ask us to delete your account, we delete it from our live systems, and ask the vendors who hold copies (for example the avatar and voice providers) to delete theirs, within 30 days of confirming your request.
• Backups are encrypted and expire on a rolling schedule. Every copy is gone within about four months.
• Detailed usage records are kept for 90 days and then summarised. Server logs are kept for about 30 days.
• Security and audit records (for example that an account was deleted, or that a sharing permission was granted) and billing records are kept as long as we need them for security and legal obligations, such as tax law.

10. Security

We protect your information with measures that include: encryption in transit (HTTPS); connected-service tokens (Google, Slack) stored encrypted; every database query limited to the account it belongs to; sharing that is off by default and checked on every request; backups encrypted before they leave our hosting; and access to production systems limited to the people who need it. No system is perfectly secure. If a breach affects your personal information, we will tell you and the authorities as the law requires.

11. Your rights and choices

Depending on where you live, you may have the right to:

• know what personal information we hold about you and get a copy, in a portable format;
• correct information that is wrong;
• delete your information or your account;
• object to or restrict some processing, and withdraw consent where we rely on it;
• not be treated differently for using these rights.

How to make a request: email support@mebot.ai from the address on your account, or tell us how to reach you. We will confirm your identity before we act, for example by replying to your account email or, for someone who talked to a Mebot by phone, by asking you to confirm from that number. You may use an authorised agent; we will ask for proof of their authority. We reply within one month (within 45 days for California requests), and will tell you if we need longer and why.

You can also review and edit your profile, change memory sharing, delete content, disconnect integrations and turn off camera perception in the Service.

12. EU and UK users

We process your personal information on these legal bases:

• Contract: to provide the Service you signed up for.
• Consent: to create an avatar or voice from your face and voice, to connect third-party services, and for optional features. You can withdraw consent at any time; this does not affect processing before you withdrew.
• Legitimate interests: to secure the Service, prevent abuse, control costs and improve the product, and to process information about people who interact with a user's Mebot so that the user can use the Service. You can object to processing based on legitimate interests.
• Legal obligation: for tax, accounting and responding to lawful requests.

Your information is transferred to the United States. Where the law requires it, we rely on a lawful transfer mechanism such as the European Commission's Standard Contractual Clauses (and the UK Addendum). You have the right to complain to your local data protection authority, though we would like the chance to help first.

13. California residents

In the past 12 months we have collected these categories of personal information, for the purposes in section 3: identifiers (name, email, phone number, account IDs, IP address); customer records and commercial information (plan and purchase history); internet activity (usage of the Service, logs); audio, electronic and visual information (voice recordings, photos, video sessions, call transcripts); professional information contained in content you provide; inferences drawn to build your profile; and sensitive personal information, namely account log-in details and the contents of communications you give us. We use sensitive personal information only to provide the Service you request, as permitted by law.

We disclose these categories to the kinds of service provider described on our subprocessor page, for business purposes. We have not sold or shared personal information, and we have no actual knowledge of selling or sharing information of anyone under 16. You have the rights to know, delete, correct and limit the use of sensitive personal information, and not to be discriminated against for exercising them. Make a request as described in section 11.

14. Cookies and local storage

The www.mebot.ai website sets no cookies. The Service uses only the cookies it needs to work: a sign-in session cookie (lasting up to 30 days) and short-lived cookies that protect the connect step when you link a service such as Google or Slack. It also stores some of your display preferences in your browser. We do not use advertising or analytics cookies.

Our pages load fonts from Google Fonts and some code libraries from public content networks, which means your browser contacts those services and they receive your IP address.

15. Children

Mebot is for adults. You must be at least 18 years old to use the Service. We do not knowingly collect personal information from anyone under 18. If you believe a child has given us information, contact us and we will delete it.

16. Changes to this policy

We will update this policy as Mebot changes. We will post the new version here with a new "Last updated" date. If a change is material, we will tell account holders by email or in the Service before it takes effect.

17. Contact

Mebot AI Corp
3135 SE Ankeny St
Portland, OR 97214
United States
Email: support@mebot.ai