Maya privacy notice
Effective 13 October 2026 · Version 2026-10-13
This notice explains how Metaworkers, Inc., operating under the Metaworkers brand, handles information for Maya’s standalone web service, Microsoft Teams integration and support.
Your organization chooses the workspaces, meetings, people and resources for which Maya is enabled. Its policies and any applicable written data-processing agreement also apply. Contact info@metaworkers.ai with the subject “Maya privacy request”.
Information we process
Accounts and purchases
Account email, password hash, Stripe customer and payment references, credit and usage ledger, session timestamps and outcomes, and records of terms acceptance and meeting consent. Stripe handles payment card details; the Maya service does not receive or store those card details.
Teams messages and connection information
Messages and task content delivered to Maya, earlier Maya exchanges in the same thread when used for a response, and tenant, team, channel, conversation, user and activity identifiers used to authenticate, restrict, route and respond to requests. The current integration does not provide general search across unrelated channel conversations or calendars.
Meetings and outputs
Meeting links and context, live audio while Maya is participating, transcribed speech, generated responses, documents and revisions, document-generation request payloads and delivery records. Installing the Teams channel app alone does not enable meeting audio processing.
Operations and support
Request and security logs, timestamps, errors, diagnostics and information supplied to support. Diagnostics and task records can contain message text, meeting identifiers or links.
Why we process information
We use information to provide the requested service, authenticate users and restrict access, answer channel questions, run enabled meeting and document workflows, recover work and deliver outputs, meter usage and process payments, investigate security or reliability issues, and respond to support and privacy requests. We may preserve records required for accounting, disputes or other applicable legal obligations.
Supply only information you are authorized to share. The customer or meeting organizer must inform participants and obtain any consent required before Maya processes their meeting.
Providers, sharing and processing locations
- Microsoft operates Teams and Microsoft 365. Maya uses Azure Bot Service for channel messaging and, where enabled, Microsoft Graph and SharePoint for file access and delivery.
- OpenAI processes content for channel answers and enabled document tasks. The current meeting service streams live meeting audio to OpenAI to understand speech and generate replies; it can also send transcript content for document and action requests.
- Amazon Web Services hosts the current Maya application and service data in the Canada Central region (
ca-central-1).
- Stripe handles payments and receives the customer and payment information needed for that purpose.
AI processing occurs outside Microsoft 365 and outside your organization’s own infrastructure. The AWS hosting region does not establish the locations used by Microsoft, OpenAI or Stripe. Provider processing, retention and use of information depend on their applicable terms, account settings and agreements. This notice does not promise local-only processing, zero provider retention or a particular AI processing region.
Channel replies and shared files are visible to people permitted by the destination’s access settings. Review the destination before sharing sensitive content. We may disclose information when required by law or necessary to respond to a security incident or protect lawful rights.
Storage, retention and deletion
Maya stores account, billing, session and consent records; channel conversation and workflow state; queued delivery content and receipts; generated documents and revisions; document-job payloads that can contain transcript text; and operational diagnostics. These records can persist after a meeting ends. Ending a meeting or destroying its runtime container does not delete every transcript, job payload or document copy.
We currently handle deletion through a verified support request. We do not apply or promise one automatic expiry period for all records. Service records remain stored until they are removed through the applicable operational process; accounting, security, dispute or legally required records may need to be preserved.
To request access, correction, export, account closure or deletion, email info@metaworkers.ai. Identify your account and organization and describe the scope. We verify your identity and authority, and may need to coordinate with your administrator. Our target is to complete the verified request within 30 days; if a legal exception or another limitation prevents full completion, we will explain the affected records and status.
For deletion requests, we review copies under our control, including service state, document-job payloads, generated files and applicable logs. Copies held in Teams or SharePoint are subject to your organization’s Microsoft 365 controls. Other recipients and providers control their own copies. Backup or preserved copies may not be removed immediately; support will identify the handling that applies rather than treating removal from the active service as proof of deletion everywhere.
Removing Maya from Teams, deleting a Teams post or ending a meeting does not automatically close your web account, refund credits or erase all stored copies. A meeting participant who does not have a Maya account should normally contact the meeting organizer; we will help route a request where we can.
Security and your choices
Public service endpoints use HTTPS. Passwords are hashed with scrypt. The Teams bridge authenticates incoming requests and restricts configured tenant and channel access. Customer dashboard access checks protect session information and documents; enabled Microsoft 365 file delivery also follows the configured destination permissions. Access must be configured correctly for each deployment, and no system can guarantee absolute security.
You can stop sending content, ask your administrator to disable the connection, or have the organizer remove Maya from a meeting. Do not use Maya for information whose required processing or retention restrictions have not been confirmed with your organization and Metaworkers.
Updates and contact
We publish changes here with an updated effective date. Any additional notice required by your agreement or applicable law will also apply. Questions and requests: info@metaworkers.ai. See support and the terms of use.