AI and Connector Data Policy

• The current native app requires iOS or iPadOS 27. It does not require a Memrov account or offer a Memrov subscription. OpenRouter and connected services have their own accounts, terms, availability, and charges. OpenRouter requires users to be at least 18 to use its service, including the account used for Memrov chat.
• Conversations, selected attachments, profile answers, and profile documents are stored on your device. Memrov uses your private iCloud database to synchronize supported app records when iCloud is available. Apple operates iCloud under your Apple Account and iCloud settings.
• When you send a chat request, the conversation context, relevant profile context, selected images or extracted document text, and any integration results included in that request go to OpenRouter and the model provider used for the response. These requests go directly from the app to OpenRouter.

• OpenRouter processes chat content and request metadata, including the model, token usage, timing, and identifiers used to associate requests with your provider account and conversation. Retention and training depend on your OpenRouter settings and the provider or endpoint that serves the request. Memrov does not enforce a universal zero-retention setting.
• When Web search is enabled in Chat, OpenRouter can process search queries and return web results through its search tool. Relevant conversation context and search results may be included in the model request.
• Optional integrations connect through Composio. Composio and the services you authorize process connection information, tool requests, arguments, and results needed for the integration. This can include content from a connected service, such as messages or documents, depending on the permissions and action you choose. Results used in chat are also sent to the AI provider.
• OpenRouter and Composio authorization credentials are kept in the device Keychain using device-only protection. Connecting a provider requires its authorization flow. Disconnecting locally does not delete your provider account or guarantee revocation of every permission at that provider.

• OpenRouter privacy policy
• OpenRouter terms and age requirement
• OpenRouter data collection controls
• Composio privacy policy

AI responses can be incomplete or wrong. Review answers and proposed actions before relying on them. Edit your profile when stored context is inaccurate, and only send content you are authorized to share.

AI Help can send conversation context and OpenRouter call diagnostics to the AI provider for troubleshooting. Email Support prepares a separate report for you to review and send through your email app. Memrov receives that report only when you send it; provider retention and training controls continue to apply to the AI Help request.

The sections below describe the Memrov web service, including Auth0 accounts, web imports, Safe AI, and Stripe billing where available. They were last updated May 25, 2026. Those account and billing workflows do not describe the current native iOS launch. General company, rights, acceptable-use, and legal-contact provisions still apply where relevant.

Direct user input is the strongest signal in Memrov. If a user corrects a statement through Memrov, contradicting provider-authored statements are kept for audit where appropriate but are not delivered as connector truth.

• Claude memories, ChatGPT bio rows, and similar provider artifacts are treated as what an AI system wrote or stored about the user.
• Memrov may parse, bucket, and display provider-authored statements for review, but the provider remains the author until the user approves, edits, or replaces them.
• Raw conversations and pasted documents are evidence and SQL context first, not default connector context.

• Unresolved conflicting statements may be shown with author labels and relative order when doing so helps the receiving agent understand uncertainty.
• After a user chooses or writes the correct statement, Memrov suppresses conflicting provider statements from connector delivery.
• Conflict handling is not a claim that Memrov discovered truth. It is a governance rule that protects user authority.

• Safe AI is separate from the connector profile. It may route prompts to selected third-party models through configured providers.
• Memrov tracks usage and cost so users cannot accidentally run up excessive spend.
• Where available, Memrov prefers provider settings that minimize retention and training use.

Memrov does not train a Memrov-owned foundation model on private imports. Third-party model providers may have their own processing rules for requests you choose to send through Safe AI or validation flows.