MyMage

Privacy Policy

Last updated:

Who we are

MyMage Ltd, registered at 10 Avenue des Pigeons, Sodnac, Quatre Bornes, Plaines Wilhems, Mauritius, operates the MyMage website at mymage.io and the MyMage Agent application at agent.mymage.io. Contact support@mymage.io about this policy, your information or a privacy request.

This policy explains how we handle information on our website and in MyMage Agent. In MyMage Agent, your business controls which information it supplies and which services it authorizes. MyMage provides the workspace and processes that information to deliver its features. MyMage Agent is currently available by invitation only.

Information we handle and why

Workspace access and connected services

Workspace members can access shared Sessions and their history, including answers containing evidence from connected services. Owners and admins manage membership, stores and connections. Authorized MyMage staff can access workspaces for support; staff access requires two-factor authentication, and supported management actions are recorded.

A connected QuickBooks company is available to members of that workspace. Optional store links provide context; they do not limit accounting access to one store. Use a separate workspace when the audience for accounting information should be different.

Our Magento, Adobe Commerce Cloud, Fastly, Cloudflare, New Relic, GitHub, Google Search Console, Google Merchant Center and QuickBooks connectors perform supported reads only. They do not change the connected business records, code or settings, or initiate payments. QuickBooks authorization uses Intuit's Accounting scope and Google Merchant Center authorization uses Google's Content API scope; both include write permissions at the provider, and MyMage restricts these connectors to supported read operations.

Google user data

A workspace owner or admin can connect Google Search Console or Google Merchant Center with Connect Google. Google then asks them to let MyMage see the email address of the Google account they choose, to show which account authorized the connection, and one of these:

We use Google user data only to provide the features the workspace uses: answering its members' questions, running its Workflows and showing what was read. We do not sell it, use it for advertising, or use it to develop, improve or train generalized AI or machine-learning models.

To prepare an answer, the relevant Google data is sent through our model gateway to the AI providers listed below, only to generate that answer for your workspace. For workspaces using memory, it can also become part of that workspace's learned context. Answers that contain Google data are visible to the workspace members who can open that Session. We do not otherwise transfer Google user data, except when the law requires it or as part of a merger, acquisition or sale of assets after notice to you.

Google authorization tokens are stored encrypted. Google data quoted in answers is kept with Session history, as described under retention below. MyMage staff do not read Google user data unless you ask us to for support, it is needed for security or to comply with the law, or it has been aggregated and anonymized for internal operations.

Disconnecting the connection in MyMage stops new reads and removes MyMage's copy of its tokens. You can also remove MyMage's access at any time from your Google Account's third-party connections page.

MyMage's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

AI processing and other service providers

To prepare answers, relevant questions, discussion, files and service evidence are sent through our model gateway to OpenAI. For workspaces using memory, selected content is also processed by OpenAI into learned context and search embeddings. This can include information read from your authorized QuickBooks company, Google Search Console property or Google Merchant Center account.

OpenAI is our only AI provider. Its models write answers, process memory and create search embeddings. OpenAI does not use data sent through its API to train its models unless the customer opts in. Its API data controls documentation describes retention for abuse monitoring and feature storage, with account-dependent controls.

OpenAI's retention and processing locations depend on the model, endpoint and account controls. Our own history and backup retention is separate from OpenAI's. Contact us for details relevant to your workspace.

We use Hetzner for hosting and storage in Germany, Cloudflare for network protection, sign-in spam protection and the website's contact-form check, Mailgun for email, including contact-form messages, and New Relic for monitoring MyMage Agent. Monitoring is configured to exclude request payloads and session replay. Connected GitHub repositories are read through GitHub. We also disclose information when necessary to comply with legal obligations, protect the service or respond to an authorized request. If MyMage is involved in a merger, acquisition or sale of assets, information can transfer to the successor, who must continue to protect it as this policy describes.

International processing and security

The website and the application are hosted in Germany and operated by a company in Mauritius. AI and other service providers can process information in additional countries according to the selected service and account. Hosting in Germany does not mean that every processing step takes place there.

We use access controls, encrypted transport and encrypted stored connection credentials to protect information. No system can eliminate every security risk. Protect your sign-in details and tell us promptly if you suspect unauthorized access.

Retention, disconnecting and deletion

Contact-form messages are kept in our email for as long as we need them to reply and to keep business records.

During the current pilot, Session history is retained indefinitely, including archived Sessions and evidence quoted in answers. Workflows, guidance, sent files and learned memory can also remain in retained workspace records. Archiving, signing out or disconnecting a service does not erase those records.

Disconnecting a connection stops new MyMage reads through it. Where supported, MyMage also requests provider-side token revocation and reports when that cannot be confirmed. You can revoke authorization through Google or Intuit as well. Existing Session history and backup copies are handled separately.

Database backups are configured for a rolling 30-day recovery window. Recovery chains and stored object versions can retain copies beyond that window; it is not a guarantee that every copy of information disappears after 30 days. Current stored files have no general age-based expiry. Unsent uploads and temporary working files have separate cleanup rules.

Contact support@mymage.io to request access, correction, deletion, restriction or an export of information, or to raise a privacy concern. We verify authority and coordinate requests across the affected records and providers. We explain applicable limitations, legal retention requirements and the steps needed; deletion is handled by staff and is not an automatic consequence of closing a workspace. If you use MyMage Agent as a member of a business's workspace, you can also contact that business.

Cookies and monitoring

MyMage Agent uses cookies needed for sign-in, security and application preferences. New Relic browser monitoring is configured without monitoring cookies or session replay. Cloudflare's security services may process browser and network information to protect sign-in.

The website sets two essential first-party cookies that contain no personal data: mymage_contacted, set for 30 days after a contact-form message is sent so the same browser is not offered another submission, and mymage_cookie_notice, set for 180 days when you dismiss the cookie notice. The contact form uses Cloudflare Turnstile to check that a person sent the message.

Neither the website nor MyMage Agent uses Google Analytics, advertising tags or remarketing tags.

Other websites and governing law

Links to other websites and services are governed by their own policies. This policy is governed by the laws of Mauritius; this does not limit rights you have under the privacy law that applies to you.

Changes and contact

We update this page when our practices change and provide notice of material changes as applicable. The same policy is published at mymage.io/privacy-policy. For questions or requests, contact MyMage Ltd at the address above or support@mymage.io. Read our Terms of Service and End-User Agreement for the conditions of using MyMage Agent.