Privacy policy

Privacy Policy

How Memrov for iPhone and iPad handles your data, provider connections, private iCloud sync, and deletion controls.

Last updated September 9, 2026

Plain-English summary
  • Your native app records are stored on your device and support private iCloud sync.
  • Chat sends selected content and context to OpenRouter and the serving model provider; integrations use the services you connect.
  • Settings provides export and deletion controls. Separate provider accounts have their own privacy controls.
Memrov for iPhone and iPad
  • 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.
AI providers and optional integrations
  • 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.
Your native app data controls
  • In Settings, Export all Memrov data creates a JSON export of profile answers, the profile rendered from those answers, conversations, messages, supported attachments, and conversation summaries. Profile also offers Markdown export. Keep exported copies in a location you control.
  • Delete Chat History removes conversations and their attachments from the app data store and private iCloud sync while preserving your profile and settings.
  • Delete Memrov data removes the app's conversations, attachments, profile records, local profile files and caches, saved OpenRouter and Composio credentials, and integration preferences. Deletions of synchronized records depend on iCloud becoming available and completing synchronization.
  • These controls do not delete exports you saved elsewhere, revoke all permissions in connected services, or delete separate OpenRouter, Composio, or other provider accounts and records. Use each provider's account and privacy controls for those requests. Apple manages iCloud and device backups under your Apple Account settings.
Device features and support
  • Voice input uses Apple's local speech transcription after microphone permission. The transcript can become chat text when you send it; the microphone recording is not sent to OpenRouter by this voice-input flow.
  • Photo selection, document scanning, Share Sheet input, and text recognition operate on content you choose. Selected images or extracted text may be sent when included in a chat request. Local conversation search and Spotlight indexing make supported app content searchable on your device.
  • If you contact admin@memrov.com, Memrov receives the contact details and information you choose to include and uses them to respond and handle your request. Do not send passwords, provider tokens, or unneeded private content.
  • Memrov is not directed to children under 13. If you believe a child has provided personal information to Memrov, contact admin@memrov.com. Provider age requirements also apply to their services.
Optional support reports
  • AI Help sends the relevant conversation and available OpenRouter call diagnostics to OpenRouter and the serving model provider to help investigate an issue. The provider controls described above also apply to Help requests.
  • In the current native app, Email Support prepares a report on your device. It contains the conversation messages and timestamps, Help analysis, available OpenRouter call details, app and build versions, OS version, locale, time zone, and conversation identifier. Review the report before opening the email composer. If Apple Mail is not configured, you can share the report with another email app.
  • The report is not sent to Memrov until you send the email. Your email provider handles delivery. Memrov receives your sender address, the report, and any note you include and uses them to respond and investigate your support request. Do not include passwords, provider tokens, or unnecessary private information.
  • Earlier TestFlight builds could send support reports through an authenticated Memrov AWS endpoint when an Apple-derived session already existed. That path uses Amazon Simple Email Service to deliver the report and the authenticated account identifier, with account email when available, to Memrov Support.
  • Deleting data inside the app does not delete a support email already sent to Memrov or copies held by your email provider. Contact admin@memrov.com for access or deletion requests concerning support information Memrov holds.
Separate web service policies

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.

Who we are

Memrov, Inc. is a Delaware C Corporation. You can contact customer service at admin@memrov.com. Legal notices may be sent through our registered agent.

Information we collect
  • Account information such as name, email address, phone number, Auth0 user identifier, sign-in method, and communication preferences.
  • Provider import data that you choose to upload, including ChatGPT exports, Claude exports, memory files, conversation files, project files, manifests, and related metadata.
  • Profile edit data, including generated bucket drafts, manual edits, hides, conflicts, user corrections, connector scopes, and deletion requests.
  • Connector and API activity, including which connector requested access, the scopes used, facts returned, policy decision, request id, and operational timestamps.
  • Billing data handled through Stripe, including customer id, checkout or portal events, invoice metadata, usage or credit records, and fraud-prevention signals.
  • Safe AI usage data when you use that feature, including prompts, responses, selected model, tool calls, usage counters, cost metadata, and safety/admission decisions needed to operate the service.
  • Device, browser, security, and operational data such as IP address, user agent, session cookies, error logs, rate-limit events, and audit records.
How we use information
  • To authenticate users, secure accounts, and keep sessions scoped to the right owner.
  • To inspect provider exports, preserve source evidence, create bucketed profile summaries, and compile a compact connector profile.
  • To let you edit, hide, correct, export, delete, and govern information about yourself.
  • To serve connectors, APIs, SQL access, Safe AI, and future mobile integrations according to your scopes and settings.
  • To process payments, credits, refunds, chargebacks, taxes, and billing support through Stripe.
  • To detect abuse, debug reliability problems, maintain audit logs, and enforce our terms and acceptable use rules.
  • To send account, security, import, connector, billing, and optional SMS or email notifications.
How connector sharing works
  • The default connector layer is intentionally small. It is designed to provide useful context without handing agents your raw history.
  • Memrov may withhold unclear, malformed, sensitive, or source-only information from connectors even when it remains available for audit or SQL evidence paths.
  • Direct user corrections are treated as the strongest authority in the connector layer. Contradicting provider-authored statements are held back from connector delivery after a user correction.
  • SQL or business access, if enabled, is a separate deeper path with its own scopes, logs, and user-granted controls.
When we share information
  • With service providers and subprocessors that help us host, secure, authenticate, bill, message, analyze, or operate the product.
  • With connectors, agents, or partner APIs only according to the scopes, settings, and product surface you choose.
  • With model or API providers when you use Safe AI or when a specific processing step requires a narrowly scoped model call.
  • With authorities, courts, or others when legally required, to protect rights and safety, or to prevent fraud or abuse.
  • In a business transaction such as financing, merger, acquisition, or sale of assets, subject to continued privacy protections.
What we do not do
  • We do not sell personal information.
  • We do not use raw imports to build ad profiles.
  • We do not let consumer connectors browse raw provider exports by default.
  • We do not train a Memrov foundation model on your private imports.
  • We do not treat provider-authored memories as user truth after you correct them.
Retention and deletion
  • We keep account, import, profile edit, connector, billing, and audit data for as long as needed to provide the service, comply with law, resolve disputes, prevent abuse, and maintain security records.
  • You can request deletion from the app or by contacting support. Active data is deleted or de-identified according to the deletion workflow, with limited hashed receipts retained for proof of completion and abuse prevention.
  • Some records may remain where legally required, such as payment records, tax records, fraud-prevention logs, dispute records, security logs, and backups until they expire in the normal backup cycle.
Your choices and rights
  • You can edit profile facts, hide information from connectors, revoke connector access, request export, request correction, request deletion, and opt out of optional SMS messages.
  • Depending on where you live, you may also have rights to access, correct, delete, port, restrict, object to, or appeal decisions about personal information.
  • To make a request, use the app privacy controls or email support with the subject line Privacy Request.
Children

Memrov is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child provided us personal information, contact us so we can delete it.

International users

Memrov is operated from the United States. If you use the service from another country, your information may be processed in the United States and other locations where our service providers operate.

Contact
Send legal, privacy, billing, SMS, security, and account requests to Memrov.

Memrov, Inc.

admin@memrov.com

Registered agent

Legalinc Corporate Services Inc.

131 Continental Dr

Suite 305

Newark, DE 19713

United States