MWM MCP Privacy Policy
Last updated:
This policy explains how MWM handles personal information when you connect an AI client, including ChatGPT, to the MWM Model Context Protocol (MCP) service and use its tools for mobile app research, content creation and store operations.
It covers the MCP service and information needed to operate your connected MWM account. Other MWM websites, app creation services and mobile SDKs have their own privacy notices. Your AI client, Apple and Google also apply their own privacy policies to the services they provide.
1. Who is responsible
MWM SAS is responsible for the processing described in this policy. MWM is registered in France under number 513 627 299, with its registered office at 1, Cours de l'Île Seguin, 92100 Boulogne-Billancourt, France.
For privacy questions and requests, contact our data protection officer at dpo@mwm.io.
2. Information we process
| Category | Information and source |
|---|---|
| Account and authorization | Your MWM account identifier, email, workspace memberships, the connected client and the permissions you authorize. Sign-in and authorization take place through MWM's account and Console pages. |
| Tool inputs | The instructions, app identifiers, countries, languages, text, images or other materials sent with the specific tool operation you request. |
| Saved content and files | Generated icons, screenshots, listing texts, privacy policies, terms, websites and other saved app materials. Supported Android release operations can also involve a build file uploaded through a dedicated upload link. |
| Store information | Connection status and account identifiers, plus app metadata, listing content, reviews, replies and release information accessed for the app and operation you request, subject to your store permissions. |
| Technical and security information | Request timestamps, IP addresses, operation names, execution status, errors and infrastructure audit records needed to operate the service, investigate failures and prevent unauthorized access. |
MWM receives the information sent with individual MCP tool calls. We do not retrieve your complete conversation history from your AI client. Content can contain personal information if you or another person includes it.
Do not provide passwords, API keys, authentication codes, private keys, payment card information, government identifiers or protected health information through the conversation or an MCP interface. Store credentials are entered and managed on MWM Console, outside MCP. The MCP tool checks connection status and returns a Console setup link when configuration is needed.
3. Purposes and legal bases
- Provide the requested service: authenticate access, apply the permissions you grant, execute tool operations, produce and save content, and perform supported store actions you request.
- Maintain reliability and security: diagnose errors, investigate incidents, prevent abuse and protect accounts and infrastructure.
- Meet legal obligations: handle privacy requests and retain or disclose information when legally required.
Where the GDPR applies, processing necessary to provide the service you request is based on performance of a contract. Security and reliability processing is based on our legitimate interests, subject to your rights. Legally required processing is based on the applicable legal obligation. We obtain consent where a specific use requires it.
MCP information is not sold or used for targeted advertising, behavioral profiling or optional analytics. MWM does not use MCP inputs or outputs to train or fine-tune AI models. Limited technical logs serve the operational and security purposes described above.
The MCP service does not collect payment card details or perform checkout. If a paid MWM account becomes a condition of access, subscription and payment arrangements take place separately from the MCP connection and are covered by the relevant account and payment notices.
4. Recipients and service providers
Information is accessed by authorized MWM personnel and shared with providers as needed for the feature or operation you request. Each provider receives only the information relevant to its role; not every provider receives every request.
| Provider | Role and relevant information |
|---|---|
| Google Cloud | Cloud hosting, computing, databases, file storage and technical logging for the service. Information can include account records, saved content, uploaded files and operational logs. |
| OpenAI, Anthropic and Google Gemini / Vertex AI | AI generation for supported features. The selected provider can receive the relevant instructions, text, images and contextual materials needed to generate the requested result. |
| Apple and Google | App Store Connect and Google Play operations. Relevant app identifiers, listings, screenshots, replies, release information and supported build files are transmitted or retrieved for the requested operation. |
| Fastly | Content delivery for hosted assets and websites. Fastly can process delivered content and connection information needed to serve it. |
AI providers can have their own retention, security review and model training rules, depending on the service, contract and settings used. The linked provider information explains these practices. Not retaining raw MCP inputs at MWM does not mean that every provider deletes them immediately.
Some features depend on third-party services and are subject to those providers' applicable terms and policies. MWM may adapt or limit these features to comply with those conditions. Your AI client and app stores process information under their own notices and applicable responsibilities.
Content you ask us to publish, such as a website, store listing or developer reply, becomes accessible to its intended audience. Information may also be disclosed when required by law or necessary to protect legal rights.
5. How long we keep information
| Information | Retention period |
|---|---|
| Raw MCP tool inputs | Processed for the requested operation and not retained by MWM as raw MCP inputs after execution. Saved outputs and operational records follow the periods below. |
| Account records and saved content | Retained for the lifetime of the account to keep the service and saved materials available, until account deletion. This includes saved icons, screenshots, listing texts, legal documents and websites. |
| Store connection settings | Managed in Console and retained until you remove the integration or delete the relevant account or workspace. Disconnecting an AI client does not itself remove store integrations. |
| Uploaded Android builds | Retained for the requested release workflows until account deletion or a deletion request. Build files already stored for the account are removed as part of account deletion. |
| Operational logs | 30 days. |
| Required Google Cloud audit logs | 400 days under Google Cloud's required audit log retention. |
| Account deletion backups | 365 days from the backup creation date. These copies contain account and related workspace records collected during deletion and expire automatically by daily partition. |
Deletion of active account records does not immediately erase the limited backups and logs with the separate retention periods above. A workspace shared with other members can retain its shared information when an individual member deletes their account.
An upload link issued before account deletion can remain valid until its expiry, for up to 30 minutes after issue. A transfer already in progress can finish after the deletion request. To request deletion of information from such a transfer, contact dpo@mwm.io.
We may retain specific information for longer where a legal obligation or legal hold requires it, only for the relevant purpose and duration. External recipients apply their own retention and deletion rules, including to content already published to their services.
6. Your controls and deletion
- Review permissions before connecting. The MWM authorization page identifies the AI client and the access it requests.
- Disconnect a client or revoke its authorization. You can manage connected clients in MWM Console and disconnect the integration in your AI client. Revoking authorization stops future access through that authorization.
- Manage store connections separately. Add, replace or remove store credentials in Console. Store integrations and saved materials are not deleted merely because you end a chat or disconnect an AI client.
- Request account or content deletion. Use the account deletion controls in Console, or send a request concerning particular information to dpo@mwm.io.
- Control what you submit and publish. Share only the materials needed for the requested task and review proposed external actions before authorizing them.
Your AI client's conversation history and retention are controlled through that client's settings and privacy policy. Removing information from MWM does not automatically remove it from a conversation, an app store or another external service.
This privacy page uses no analytics scripts, advertising pixels or tracking cookies. Other Console pages and MWM websites have separate website and cookie disclosures in the MWM website Privacy Policy.
7. Security and international transfers
We use access controls, encrypted connections and cloud storage protections to safeguard information. No security measure eliminates every risk. Contact us if you suspect unauthorized access or disclosure.
MWM is established in France. Providers may process information outside your country, including outside the European Economic Area. Where applicable law requires safeguards, transfers are subject to appropriate mechanisms, such as adequacy decisions or Standard Contractual Clauses. Contact us for information about the safeguards applicable to your data.
8. Your privacy rights
Depending on the law applicable to you, you may request access to your personal information, correction, deletion, restriction of processing or portability, and object to certain processing. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing.
Send requests to dpo@mwm.io. We may need proportionate information to verify your identity and will respond within the applicable legal timeframe. Do not send passwords, private keys or identity documents through an MCP tool or AI conversation.
You can complain to your local data protection authority, including the CNIL in France. We do not discriminate against you for exercising applicable privacy rights.
9. Changes and contact
We update this policy when our MCP data practices or applicable requirements change. The revised version and its update date will appear on this page. We will provide additional notice where required.
For questions about this policy, contact dpo@mwm.io.