MCP integration
Privacy Policy
Last updated: 20 October 2026
This policy explains how AppCreator24 processes information received through its Model Context Protocol (MCP) integration. The service is operated by Vinebre Software, S.L., tax identification number B55734172, based in 43792 Vinebre (Tarragona), Spain.
1. Information we receive
When your AI assistant calls the integration, it sends the app specification needed to create or update your app. This can include:
- App name, description, welcome message, language and theme.
- Section titles and content, such as HTML, quizzes, forum categories and links to external resources.
- An app identifier and management code when updating an existing app.
The integration does not request your full conversation history or an AppCreator24 password. Personal information may be included if you or your assistant place it in an app specification. Your AI provider controls what it sends to the tool under its own settings and policies.
2. How the information is used
App specifications are processed and stored to create, configure, compile and update Android apps, prepare app assets and provide download and editing links. The dedicated MCP log records the date and time, connection IP address, MCP method, and the Origin and User-Agent headers when supplied, for monitoring service use and troubleshooting. The connection IP may belong to your AI provider rather than to you. This log does not record the complete app specification or management code. Infrastructure logs may separately record request status and error information.
3. Retention and deletion
Apps and their configuration are deleted from the active service when the user requests deletion or when an app has had no users for more than six months. The dedicated MCP log is retained for two years.
Backups are retained indefinitely in securely archived storage. Archived backups are not deleted as part of routine deletion of an app from the active service. Deleting an app therefore does not remove all copies of its information from archived backups.
4. Information returned and other services
The integration returns the result of the request to the AI client that called it. Successful results include the app identifier, download link and editing link. Your AI provider processes these results under its own privacy policy.
Content included in a generated app may be visible to people who use or receive that app. External websites, media sources and feeds used in an app may process data under their own policies.
5. Your choices and requests
You can stop further MCP calls by disabling or removing the connection in your AI client. Disconnecting does not itself delete an app or previously stored information.
You may request correction or deletion of your information through AppCreator24’s support channels. Depending on applicable law, other data-protection rights may also be available. An app identifier can help locate the relevant record; it is not necessary to provide your AI account password.
6. Security and app-management links
The public MCP endpoint uses HTTPS. App identifiers and editing links contain app-management information and should be kept private. App content is intended for the app’s audience; this integration is not a place to submit passwords or other confidential material unrelated to creating your app.
7. Scope and contact
This policy covers the MCP integration. It does not replace your AI provider’s privacy policy or the policies that apply to people using an app you create.
For privacy requests, contact AppCreator24 through MCP help and support. Company details and the designated support contact route are described in the AppCreator24 legal notice. Further information about the platform is available in the MCP Terms of Service.