Privacy Policy

This Privacy Policy explains how MentorU collects, uses, discloses, protects, and retains information when people visit MentorU public pages, create or use accounts, launch or administer workspaces, buy or access provider offerings, communicate through platform tools, or otherwise use MentorU services.

MentorU is a platform used by workspace owners, providers, admins, account users, customers, members, and visitors. Providers may also maintain their own privacy notices for the offerings, customer relationships, content, policies, and communications they control.

When a workspace owner connects Zoom, MentorU receives the authorizing user's Zoom account and host identifiers, display name, email, granted scopes, token expiration, and OAuth access and refresh tokens. The integration requests six user-managed API permissions to identify the authorizing user, create, read, update, and delete that user's meetings, obtain a short-lived Zoom Access Key for host start, and obtain a meeting-bound On Behalf Of token for an entitled member's embedded join. Zoom Marketplace also retains a seventh configured permission, user:read:zak, required by the enabled Meeting SDK feature.

When an authorized mentor schedules a Zoom-backed session, MentorU may process the meeting identifier, topic, scheduled time, duration, timezone, meeting settings, passcode, join URL, and host start information returned by Zoom. MentorU uses this information to keep the MentorU session and Zoom meeting synchronized and to render the exact meeting inside the authenticated MentorU experience.

OAuth access and refresh tokens are encrypted at rest and remain in server-side systems. They are not returned through customer-safe status APIs. For an exact embedded meeting, the authenticated browser may receive a short-lived Meeting SDK signature and either a short-lived, user-associated ZAK issued only after exact tenant, session, meeting, and host authorization, or a meeting-bound OBF token for an entitled member join. MentorU does not persist or log those short-lived credentials.

On a confirmed MentorU disconnect or valid Zoom deauthorization, MentorU immediately disables use of the connection and deletes its usable OAuth credentials and Zoom-derived account fields from active connection storage. Meeting records and secret-free lifecycle and security evidence follow the schedule in the Security and Data Protection Policy. Requests to access or delete retained personal information can be sent to support@mentoru.app and may require identity verification.

MentorU does not sell or rent Zoom-derived data, use it for advertising profiles or surveillance, or disclose it except to Zoom and infrastructure subprocessors that operate and secure the integration, or when legally required.

When a workspace owner connects Google Calendar, MentorU receives the authorizing user's Google account identifier, email, name, granted scopes, token expiration, and OAuth access and refresh tokens. MentorU also reads only the Calendar list fields it needs: calendar identifiers, names, primary status, access roles, time zones, and the selected calendar's supported conference types. These fields let the owner choose a writable calendar and let MentorU determine whether it supports Google Meet.

The Google Calendar events permission technically permits event access on calendars available to the authorizing account. MentorU directs its event requests only to the writable Calendar selected for that workspace. To find its own sessions without downloading unrelated event content, MentorU first reads only event identifiers, cancellation status, and recurring-series identifiers in a bounded time window. After an identifier matches a same-workspace MentorU session record, authorized workspace admins may read, create, display, update, or cancel that MentorU scheduling event. Only then does MentorU request the fields needed for that experience: event title, description, location, start and end times, recurrence details, links, and conference status. MentorU does not request detailed content for unrelated Google events or expose them through admin or member Calendar surfaces for tenant-owned Google connections.

Only the recorded workspace owner may select or manage Google Meet delivery. When selected, MentorU asks Google Calendar to create one unique external Meet conference for that event and stores the canonical join URL only after Google returns it. MentorU does not add Calendar attendees. MentorU does not request Google Meet API scopes and does not access Meet audio, video, recordings, transcripts, chat, or participant activity.

Google OAuth access and refresh tokens are encrypted at rest in server-side systems and are not returned through customer-safe status APIs. Calendar and Meet information is exposed only to authorized users of the same workspace as needed to provide the scheduling and join experience. Google-derived Calendar data is not indexed by, retrieved for, or sent to Mentor AI, OpenAI, or another model provider for inference or training. This paragraph concerns Calendar and Meet data. Google Contacts data is covered separately in "Connected Mailbox and Contacts Data". MentorU does not sell Google user data or use it for advertising, surveillance, broader analytics, generalized product development, or unrelated support. It is not subject to the broader sharing or successor-transfer provisions below except with documented user consent, for a security investigation, when legally required, or through infrastructure subprocessors that operate and secure the requested integration.

On a confirmed disconnect or valid revocation, MentorU disables the connection and deletes its usable Google OAuth credentials from active connection storage. Owners can disconnect in MentorU Connections or revoke MentorU through their Google Account permissions. Authorized users can cancel or delete MentorU sessions through scheduling tools. Secret-free scheduling, security, and audit records follow the retention practices in this policy. Requests to access or delete retained personal information can be sent to support@mentoru.app and may require identity verification.

MentorU's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

When a workspace owner connects Facebook, MentorU receives the app-scoped user identifier Meta assigns to MentorU, the authorizing user's display name, the Facebook Pages that user can manage and the tasks allowed on them, the linked Instagram professional account's identifier and username, the permissions granted, token expiration, and encrypted long-lived user and Page access tokens. MentorU requests only the permissions needed to list the owner's Pages and linked Instagram account and to publish and confirm the posts the owner approves. MentorU does not read Messenger or Instagram messages, comments, followers, or audience data.

When you connect Threads, MentorU uses a separate Threads app with its own permissions and receives your Threads user identifier, username, and an encrypted Threads access token, used only to publish the posts you approve to your Threads profile.

Only the recorded workspace owner can approve, schedule, or publish a post. Every approval is bound to the exact content and time approved; a later edit needs a fresh approval. Access tokens are encrypted at rest in server-side systems and are not returned through customer-safe status APIs. MentorU stores the identifier of each post it publishes so the workspace can see what went out.

A confirmed disconnect inside MentorU applies to that one workspace: MentorU disables that connection, deletes its usable access tokens and the connected account's display name from active connection storage, and cancels its pending publishing approvals. A valid deauthorization notice or data deletion request sent by Meta or Threads applies across MentorU: it does the same in every workspace that used that account, and only that notice records a confirmation code whose status page shows only whether the request completed. A data deletion request additionally replaces the stored account, Page and Instagram identifiers and granted permissions on those connections with non-identifying placeholders. The data deletion instructions explain each option. Secret-free lifecycle and security evidence follows the schedule in the Security and Data Protection Policy. MentorU does not sell Meta- or Threads-derived data, use it for advertising profiles, or disclose it except to Meta and infrastructure subprocessors that operate and secure the integration, or when legally required.

When you connect LinkedIn, MentorU receives your LinkedIn member identifier, name, the permissions granted, token expiration, and an encrypted access token. MentorU does not request or store a LinkedIn refresh token and does not store your LinkedIn email address. If LinkedIn Page publishing is offered later, MentorU would also receive the identifiers and names of the organizations you administer so you can choose one Page. MentorU uses this information only to publish the posts you approve and to show the connection's status. LinkedIn member tokens expire after sixty days and cannot be refreshed; MentorU shows the connection as needing attention seven days before expiry so the owner reconnects in time.

The LinkedIn connection is not yet available; the following commitments apply from the day it launches. MentorU will keep the connection identifiers and the identifiers of the posts it publishes. Any other information returned by LinkedIn APIs will not be kept longer than twenty-four hours. MentorU does not retrieve or display LinkedIn engagement figures today; if it ever shows any, those figures will be refreshed or deleted within forty-eight hours. On a confirmed disconnect, when MentorU finds the token has expired, or when LinkedIn refuses the token, MentorU disables the connection and deletes the access token from active connection storage. You can also remove MentorU under LinkedIn Settings, Data privacy, Permitted services.

When you connect TikTok, MentorU receives your TikTok open identifier, display name, avatar, the permissions granted, token expiration, encrypted access and refresh tokens, and the posting settings TikTok reports for your account: the privacy levels you may choose, whether comments, duets, and stitches are allowed, and your remaining daily posts. MentorU uses this information only to upload the videos you confirm, with the privacy level, interaction settings, commercial content flags, and AI-generated content disclosure you choose at confirmation. MentorU does not read your TikTok inbox, followers, or analytics. Until TikTok completes its review of MentorU, uploads are private to your account only.

The TikTok connection is not yet available; the following commitments apply from the day it launches. MentorU will keep the connection identifiers and the identifier TikTok returns for each upload. Upload session addresses will be treated as secrets and not logged. On a confirmed disconnect, or when TikTok refuses the token, MentorU will disable the connection and delete the usable tokens from active connection storage. You will also be able to remove MentorU under TikTok Settings and privacy, Security and permissions, Manage app permissions.

When you connect YouTube for uploads, MentorU uses Google OAuth with the YouTube upload permission and YouTube API Services. MentorU receives your channel identifier and title, the permissions granted, token expiration, and encrypted OAuth access and refresh tokens, and uses them only to upload the videos you confirm with the title, description, privacy status, audience setting, and synthetic-media disclosure you choose. MentorU does not read your YouTube analytics, comments, or subscribers.

By connecting YouTube you agree to be bound by the YouTube Terms of Service. Google's handling of your information is described in the Google Privacy Policy. You can revoke MentorU's access to your YouTube and Google data at any time through the Google security settings page.

The YouTube upload connection is not yet available; the following commitments apply from the day it launches and cover uploads only. MentorU will keep the connection identifiers and the identifier YouTube returns for each upload. Any other data MentorU stores from YouTube API Services for uploads will be refreshed or deleted at least every thirty days. On a confirmed disconnect or a revocation through Google, MentorU will disable the connection, delete the usable OAuth tokens from active connection storage, and delete the remaining YouTube-derived upload data within seven days. MentorU's use of YouTube API Services also follows the Google API Services User Data Policy described above.

When an eligible workspace uses a MentorU Live Room, LiveKit provides the third-party media infrastructure that processes participants' live audio, video, and screen sharing for the call. MentorU issues a short-lived, room- and participant-bound admission credential after checking workspace, session, membership, schedule, and capacity authority. When a host or workspace admin turns on Live captions, each participant must accept a versioned audio-processing notice before joining captioned media. A speech-to-text-only LiveKit Agent sends room microphone audio to Deepgram through LiveKit Inference and returns live English captions. The Agent has no LLM, TTS, or audio output, and its LiveKit observability recording is disabled. When an authorized host or workspace admin explicitly requests a MentorU Live recording, every person in media must separately accept the current audio, video, and screen-sharing notice before LiveKit Egress begins. A person who declines may continue using room collaboration without entering recorded media. MentorU does not persist caption text, expose a transcript API, record automatically, or enable LiveKit chat.

MentorU retains the Live Session's provider-independent lifecycle, moderation, admission, convergence, security-audit, and support metadata, plus caption and recording lifecycle, consent, usage-reservation, and safe failure audit metadata. A finalized MP4 is stored in private Supabase Storage and served for playback or an explicit MP4 download only through short-lived, same-workspace authorized access. MentorU automatically deletes its stored copy thirty days after it becomes ready and the host or workspace admin may delete it earlier. A copy downloaded by an eligible recipient can remain with that recipient after MentorU deletes its stored copy. A non-sensitive deletion tombstone remains without media, signed access URLs, or storage credentials. Ending LiveKit media revokes media admission but does not itself delete authorized MentorU Discussion, Materials, Notes, recap, poll, Q&A, roster, or presence records, which follow their own access, retention, and deletion windows.

A workspace admin may connect a third-party AI assistant, such as Claude by Anthropic or ChatGPT by OpenAI, to a MentorU workspace through MentorU's OAuth connector. When the admin's assistant requests information through the connector's read tools, MentorU shares the workspace data those tools return with that assistant's provider, at the admin's direction. That data can include business, offer, package, course, program, schedule, and analytics information, and the names, stages, and activity of people and leads in the workspace. The read tools do not return contact details of people or leads. The connector is read only: it cannot send messages, publish content, take payments, or change workspace data. The provider's own terms and privacy policy govern how it handles the data it receives.

To operate the connector, MentorU stores the registration details each AI app submits, such as its name and redirect addresses; a record of each approved connection, including the workspace, the approving admin, the granted access, and when it was created, last used, or revoked; authorization codes and access and refresh tokens only as one-way hashes, never in usable form; request-rate counters; connection events such as a connection being granted, revoked, or refused; and a usage record of each read the assistant makes, naming which read ran, its outcome, and the time, without the data returned. A workspace admin can pause every assistant or revoke a connection at any time from the workspace's Connections page, and the next request is refused. Revoked connection records and their events are kept as security evidence. Requests to access or delete retained personal information can be sent to support@mentoru.app and may require identity verification. The AI assistant setup guide describes each read tool.

Separately, the MentorU platform owner (the account that operates MentorU for Kahel Ventures LLC) may connect the owner's own AI assistant, currently Claude by Anthropic, to an owner-only platform connector to help monitor and run MentorU. Only that one designated owner account can approve this connection, and only after a recent sign-in; workspace admins, other MentorU staff and other AI apps cannot use it. Through its read-only tools, the owner's assistant can receive platform operating information across all workspaces: counts and totals, such as numbers of workspaces, signup requests, inquiries, leads, and email delivery, bounce and unsubscribe events; payment, fee, refund and payout totals; workspace names, web addresses, plans and setup status; the status and error messages of sending domains, connected stores and scheduled jobs; emergency stops; and items waiting in MentorU's decision queue. Workspace names may include a mentor's name. These tools do not return the names, email addresses, phone numbers or other contact details of members, leads or customers, message contents, or payment account or card details.

The platform connector is read only: it cannot send messages, publish content, take payments or change data. Each connection expires 30 days after it is approved, and the owner can revoke it at any time, after which the next request is refused. MentorU records each connection, refusal, revocation and read the assistant makes, naming which read ran, its outcome and the time, without the data returned, and keeps these records as security evidence. Workspace admins are not notified of individual reads. Anthropic's terms and privacy policy govern how it handles the information it receives.

Mentor Autopilot is an optional feature. A workspace owner turns it on by accepting the Autopilot Addendum, and it runs only while it is on. When it is on, MentorU acts for that workspace: it follows up with people who contacted the mentor, sends first-touch notes and follow-ups to contacts the mentor imported and approved, checks in with members, asks members for testimonials, books free discovery calls, answers member questions, prepares or posts social updates on accounts the mentor connected, and sends the mentor a daily note and a weekly report. Some messages a mentor sends using Autopilot, including emails, texts and social posts, are written by AI and sent automatically on the mentor's behalf without the mentor reviewing each one. Each message to a person waits five minutes before it is sent, and the mentor or a workspace admin can cancel it during that time.

To do this, Autopilot uses the workspace's content and settings, the mentor's past messages and voice settings, the contact details and permissions of the people in the workspace, and messages those people send to the mentor. It uses this information only to run Autopilot for that workspace.

AI models write the text of messages in the mentor's voice and sort incoming replies into categories, such as "interested", "not now" or "needs the mentor". We use AI model providers for this writing and sorting; the current providers are listed on our Subprocessors page. These providers process the information on our behalf to provide the service. Under our contracts and account settings with them, these providers may not use this information to train their models.

Autopilot is built so it cannot set prices, issue refunds, change access or delete data, and it is instructed not to give medical, legal or financial advice. A person decides those matters.

Autopilot checks incoming messages for signs that someone may be in danger or in crisis. If it finds one, Autopilot stops all automated messages to that person and alerts the mentor right away, in their workspace and by email. The alert says only that a message needs the mentor's attention and where to find it. It does not include the message itself. The person's message stays in the workspace, where the mentor can already see it. Autopilot may send that person one fixed message with crisis resources (988, the Crisis Text Line, 911 and findahelpline.com) saying the mentor has been notified and will reach out. It does not send an AI-written reply to a crisis message. It reminds the mentor to check in a day or two later. This check can infer information about a person's health or safety. We keep only a category label (for example "crisis") with the conversation, for no longer than 30 days after the mentor resolves it, and we use it only to pause automated messages and alert the mentor. The check can miss messages or flag messages incorrectly. Autopilot and MentorU are not crisis or emergency services. Washington residents: see our Consumer Health Data Privacy Policy.

Contact import. A workspace owner may import their own contacts into Autopilot from Google Contacts, Outlook, an iPhone contacts export, a LinkedIn connections export or a spreadsheet. The owner confirms, separately for each import, that these are people they know and are allowed to contact. For an imported contact we store the name and contact details in the file and any role or company fields it contains, and we record where the contact came from. Imported contacts are used only by that workspace. They are not shared with other workspaces or used for MentorU's own marketing.

Contact details imported from Google or Microsoft (name and any role or company fields) may be sent to our AI provider to sort contacts and draft personal notes for the workspace owner, a feature the owner turns on and can see. They are not used to train AI models, to serve ads or for any other workspace.

Contacts whose phone number or email address suggests they are in the EU, the UK or Canada are not sorted or scored by AI and receive no automated first-touch messages unless the owner marks them as an existing client.

Mailbox sending. If the owner connects Gmail or Outlook, MentorU asks only for permission to send email as that owner (Google gmail.send, Microsoft Mail.Send) and to read their basic profile. MentorU does not ask to read, search or delete the owner's mailbox. Replies come back through a MentorU reply address so that opt-outs can be honored. Contact import asks only for read-only access to contacts (Google contacts.readonly, Microsoft Contacts.Read). Access tokens are encrypted and are removed when the owner disconnects.

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

We collect information you provide directly, information generated through platform activity, and information received from service providers that help operate MentorU. Depending on how you use the platform, this may include:

• Account and contact data, such as name, email address, phone number, organization, role, login status, profile details, and support requests.
• Provider and workspace data, such as workspace name, brand settings, public-site content, offerings, prices, setup status, admin users, and operational preferences.
• Customer and member data, such as package access, membership status, course or content progress, scheduling activity, form responses, comments, and relationship history within a workspace.
• Consent and contact-preference records, such as opt-ins, opt-outs, STOP replies, unsubscribes, bounces and complaints; for workspaces that use Autopilot, contacts the workspace owner imports, a record of automated actions, and categories inferred from messages, such as crisis or health flags.
• Content, uploads, and communications submitted through MentorU, including files, images, messages, notes, announcements, comments, event details, and generated or edited workspace materials.
• Payment processor metadata from third-party processors such as Stripe, including customer IDs, connected account IDs, subscription or checkout status, invoice status, amounts, fees, refunds, disputes, and transaction identifiers. MentorU does not store complete payment card numbers.
• Technical and usage data, such as device and browser details, log data, IP-derived approximate location, cookie identifiers, page views, feature interactions, error diagnostics, and analytics events.

We use information to provide, secure, operate, support, and improve MentorU. This includes using information to:

• Maintain accounts, authentication, workspace access, member access, admin permissions, and platform settings.
• Operate provider workspaces, public pages, checkout flows, content access, scheduling, comments, communications, reporting, and support workflows.
• Process platform subscriptions, provider offering payments, fees, refunds, disputes, invoices, compliance checks, and payment-related support through third-party processors.
• Send service notices, account messages, support responses, transactional email, workspace communications, and optional marketing where permitted.
• Monitor security, debug errors, prevent misuse, enforce terms, maintain audit records, and protect users, providers, customers, members, MentorU, and third parties.
• Measure usage, improve reliability, refine product features, develop new services, and understand how visitors and account users interact with MentorU.

Workspace owners and providers control much of the workspace, offering, customer, member, content, and communication data submitted to their MentorU workspaces. MentorU processes that data to provide platform services, maintain tenant separation, support the workspace, and perform actions requested by authorized account users.

Customers and members should understand that information they submit inside a provider workspace may be visible to the applicable provider, workspace admins, invited team members, or other participants when the feature is designed for shared access.

MentorU may use cookies, local storage, pixels, analytics tools, and similar technologies to keep users signed in, remember preferences, secure sessions, measure page and feature usage, diagnose technical issues, and understand platform performance.

You can control some cookies through your browser settings. Blocking cookies may affect login, workspace access, checkout, personalization, or other platform features.

MentorU does not sell personal information. We may share information when needed to operate the platform, support users, comply with law, or protect rights and security. This may include sharing with:

• Workspace owners, providers, admins, team members, customers, or members as directed by platform features and workspace permissions.
• Service providers and subprocessors that provide hosting, database, storage, authentication, email, payment processing, analytics, logging, security, customer support, and infrastructure services.
• AI model providers that write, classify or help decide on messages for features a workspace turns on, such as Mentor Autopilot, under contracts that limit their use of the information. We keep a current list of these providers on our Subprocessors page and update it before adding a new one.
• Payment processors, banks, card networks, fraud-prevention services, tax or compliance providers, and connected-account platforms as needed for payments and financial administration.
• Professional advisors, legal authorities, regulators, or counterparties when required by law, legal process, compliance obligations, dispute handling, or protection of rights, safety, and platform integrity.
• Successors or participants in a business transaction involving MentorU or Kahel Ventures, subject to appropriate confidentiality or transfer safeguards.

We use technical, administrative, and organizational safeguards designed to protect information, including access controls, tenant separation, secure infrastructure providers, monitoring, and restricted administrative access. No internet service can guarantee absolute security, but we work to reduce risk and respond to security concerns.

Additional controls, security-reporting instructions, and operational practices are described in the Security and Data Protection Policy.

We retain information for as long as reasonably needed to provide the platform, maintain accounts and workspaces, support provider and member relationships, comply with legal, tax, accounting, payment, security, audit, and dispute obligations, enforce agreements, and improve MentorU. Retention periods may vary by data type, workspace settings, legal requirements, and operational need.

When information is no longer needed, we may delete, de-identify, or aggregate it unless retention is required or permitted by law, legitimate business needs, security obligations, backup systems, or provider-controlled workspace requirements.

For workspaces that use Autopilot: we keep a record of each action Autopilot plans, sends, cancels or blocks, so the mentor can review it, for 18 months. The text of drafted messages is kept for 90 days after the message is sent or cancelled. Consent, opt-out and import-attestation records, and a minimal log of each message sent (who, when, channel and consent basis; no message text), are kept for 5 years so we can keep honoring opt-outs and respond to legal claims. A record of each Autopilot Addendum acceptance by a workspace owner (version, time, IP address and browser details) is also kept for 5 years, including after the workspace is deleted, so we can show what was agreed. A category label from a crisis or health check is kept for no longer than 30 days after the mentor resolves the alert. Coded do-not-contact keys (one-way hashes of email addresses and phone numbers) are kept indefinitely, including after a deletion request, so we can keep honoring opt-outs.

The current operational retention schedule, including Zoom and social and video provider credentials, short-lived authorization material, meeting metadata, provider data deletion requests, security evidence, support records, and backups, appears in the Security and Data Protection Policy.

Depending on your location and relationship to MentorU, you may have rights to request access, correction, deletion, portability, restriction, objection, opt out of certain communications, or withdraw consent where processing depends on consent. You may also update some account information directly through platform tools.

To make a privacy request, contact support@mentoru.app. We may need to verify your identity, clarify the workspace or account involved, and coordinate with the applicable provider when the request concerns provider-controlled customer, member, content, or communication data.

If a mentor's workspace uses Autopilot, you can stop its messages at any time. Reply STOP to a text, reply "no thanks" or STOP to an email, or use the unsubscribe link in the email. Members can also turn off each kind of update. Autopilot stops automated messages to you on that channel right away, and it stops personal outreach on every channel. We keep a record of your consent, opt-out and unsubscribe choices, including what you chose, when and how, so we can keep honoring them. If you ask us to delete your information, we keep only the minimum needed to make sure you are not contacted again (for example, a coded version of your email address or phone number on a do-not-contact list). If you ask whether you are talking to AI, you will get an immediate, honest answer, and the mentor will be notified. To access, correct or delete information a mentor holds about you, contact the mentor or support@mentoru.app.

To delete the data MentorU holds from a connected Facebook, Instagram, Threads, LinkedIn, TikTok, or YouTube account, follow the data deletion instructions.

MentorU is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Do not submit sensitive personal information, regulated information, or confidential third-party information unless you have the legal right to do so and the platform feature is appropriate for that use.

Providers using MentorU for youth programs must also follow the Minors and Youth Program Policy.

Provider communications, uploaded content, checkout activity, and AI-assisted tools may also be governed by MentorU's Communications and Email Policy, Copyright and Intellectual Property Policy, Customer Purchase Terms, and AI and Automation Policy, as well as the Security and Data Protection Policy.

MentorU is operated from the United States. If you access MentorU from another location, your information may be processed in the United States or other jurisdictions where MentorU or its service providers operate.

We may update this Privacy Policy from time to time. When we make changes, we will update the date on this page and may provide additional notice when appropriate.

If you have questions about this Privacy Policy or how MentorU handles information, contact support@mentoru.app.