Privacy Policy

Version 2.0 · 21 September 2026

Contact support@monomixai.com about privacy. Publisher contact details are displayed with this document below. This policy covers the MixPipe iPhone/iPad app, its direct BYOK requests and information you send to support. The publisher is responsible for processing it determines; external providers also have their own responsibilities.

1. Local workspace and credentials

MixPipe has no mandatory online account or MixPipe cloud library. The app stores projects, prompts, workflow/timeline settings, generation history/status, references, results, characters and personal templates locally. Preferences, profile name, avatar and installation identifier are also local; creating them does not automatically upload them.

Provider credentials and agreement version/date/permission flags are stored in device-only Keychain entries. Credentials are used in authentication headers, requests or signatures required by the provider. Local key storage does not mean credentials are never transmitted. They are not sent to a MixPipe cloud-generation server.

2. What AI services receive

The assistant summary is limited to 24 project steps, prompt excerpts of up to 180 characters and 3,000 characters overall. Planning may make one correction request if its structured response is invalid. Fetching a model list is a separate network request without your image.

Providers and their delivery/storage endpoints can receive connection metadata, including IP address, and associate requests with your provider account. A provider may route data to other model operators. Requests are not anonymous merely because MixPipe has no account. Returned job identifiers/status are saved locally for recovery; results are downloaded locally.

OpenRouter retains token counts, latency and similar request metadata for reporting and model ranking; its settings also affect input/output logging. See OpenRouter's data-use explanation.

The actual recipient follows your selected model/account/endpoint. Its policies and settings govern its retention, safety review, training uses and onward processing. We do not promise universal zero retention, no training, EU-only processing or a particular transfer agreement for every provider. Review the selected provider's current terms before submitting sensitive material.

3. Support, diagnostics and sharing

Export diagnostics prepares app/OS versions, device type, locale, theme, available/configured provider names and preferred model. It excludes credential values, project prompts and media. You choose a destination in the system share menu; there is no automatic diagnostics upload.

Report a problem previews technical context, timestamp and job identifier where available. Prompt attachment starts off and is included only if enabled. Pattern filtering masks recognised secrets and paths, not every possible piece of sensitive text. Review what you send. Your mail app adds the sender address; the receiving mailbox/mail services process your message and any additions.

Profile export includes local profile fields and installation ID, not keys or media paths. Media sharing sends the chosen file to your chosen recipient. There is no public user-template upload. The app contains no advertising or third-party analytics/crash-report SDK; this does not describe Apple's independent collection or external API/website logs.

4. Purposes, legal bases and controls

We process what is necessary to provide requested app functions and related support to perform our agreement. Optional extra content supplied for support is provided with your consent. Other enquiries and security/abuse handling serve our legitimate interests in responding and protecting the service, subject to your rights. A legal obligation applies only where an applicable law requires processing. External providers' bases depend on their own role; UI permission does not establish every recipient's legal basis.

Withdraw AI-sharing permission in Settings → About & Support → Accepted agreements. New protected AI actions then require permission again. Terms acceptance and local work remain. Already accepted jobs can finish and their results be downloaded. Withdrawal does not undo earlier transfers, provider charges or retained copies. If persistence fails, new AI actions are blocked for that session; retry saving before closing the app.

Local editing does not require AI transmission. Removing saved credentials is separate; revoke the key itself with its issuer.

5. Retention and deletion

Local workspace data remains until removed using the available controls or app-storage removal. Deleting one item does not necessarily delete shared references, exported copies or intermediate provider-result files. The latter currently have no automatic time-based expiry. Keychain records are separate; do not assume uninstall/reinstall removes them. Media and provider-result folders are backup-excluded, which does not exclude every app file or export.

Support correspondence is retained as needed to resolve the request and necessary follow-up, with longer retention only where needed for applicable legal obligations or claims. Access and retained content should be limited to those purposes. External providers determine their own periods/criteria and deletion procedures; local deletion does not send them a deletion request. Ask the holder of an external copy to delete it. Contact us for support records we hold; there is no MixPipe account containing a recoverable cloud library.

6. Security, rights and young users

The app uses HTTPS for AI calls, Keychain for credentials and device storage protections for local files. No system or shared file is guaranteed secure. Protect your device, credentials and exports.

Where GDPR applies, you can request access, correction, erasure, restriction, objection or portability subject to its conditions; withdraw consent; and complain to a competent supervisory authority. Withdrawal does not change prior lawful processing. Responses normally take one month, with lawful extensions and notice where needed. Contact support without sending keys.

The Terms require age 13+ and guardian agreement below 18; this is not a claim that 13 is a universal data-consent threshold. Contact support about a child's data. Updated policies state their version/date and remain available locally in Settings. New uses must be reflected in appropriate disclosures and permissions.