Data privacy & security
How Mnemos handles the data it reads: what it can access, where it is kept, who can see it, and what happens when you leave. Written for the person who has to check, in the order they usually ask.
Six things that are true.
Each row is a fact about how the service is built, not a policy setting. The detail below says what each one means in practice; the Privacy Policy and Terms of Service are the binding versions.
| No. | Topic | What is true | Detail |
|---|---|---|---|
| 01 | Access | Read-only Shopify scopes. No write scope is requested, so nothing in your store can be changed. | §01 ↓ |
| 02 | Credentials | Store tokens and connected-system keys are encrypted at rest and never shown in plain text. | §02 ↓ |
| 03 | Isolation | Each workspace's data is kept apart at the database level. One workspace cannot read another's rows. | §03 ↓ |
| 04 | AI model providers | Process data under contract, on our instructions. Your commerce data is not used to train general models or to serve other customers. | §04 ↓ |
| 05 | Leaving | Uninstalling ends access at once. Shopify's redaction requests delete the shop's data, credentials, and named customer records. | §05 ↓ |
| 06 | Contact | Security questions, data requests and vulnerability reports go to support@mnemos.ai. A person reads them. | §06 ↓ |
Read-only access to Shopify
The Mnemos Shopify app requests read scopes and only read scopes: orders, products, inventory, locations, fulfillments, returns, the customer records attached to orders, and shipping. It holds no write scope. It cannot change a price, edit or refund an order, adjust inventory, or message a customer — not as a setting that could be switched, but as a limit on what the access token can do at all.
The full list of scopes, and why each one is needed, is on the Shopify page. Where you connect other systems — an ERP, an accounting tool, a help desk, a warehouse — the same rule applies: read-only credentials, used only to answer questions inside your workspace.
Credentials
The Shopify offline token and any credential you connect for another system are encrypted at rest. They are never shown back in plain text — not to you in the app, and not to us. They are decrypted only when Mnemos needs to read from the system they belong to.
When you uninstall the Shopify app, the offline token is discarded. When you disconnect any other system, its credential is deleted with the connection.
Per-workspace isolation
Every record Mnemos holds is tagged with the workspace it belongs to, and the database enforces that boundary on every query: a request from one workspace cannot read another workspace's rows. Inside the product, your data is visible only to the people you have invited into your workspace.
The same boundary applies when you ask from your editor. An MCP access key is scoped to one workspace, and to reading.
AI model providers
Answering a question involves sending the relevant records to an AI model provider acting on our behalf, under contract, limited to processing data on our instructions. Your commerce data is not used to train general models, and it is never used to answer another customer's question.
Beyond model providers, we use a small number of subprocessors to run the service — cloud hosting and infrastructure providers — each under contract and each limited in the same way. We do not sell personal information and we do not share it for advertising.
Uninstall, redaction and deletion
When you uninstall the Shopify app:
- Access ends immediately. The store connection is disabled, the offline token is discarded, and syncing stops.
- Shopify then sends a mandatory
shop/redactrequest. On receiving it we delete that shop's commerce data and stored credentials. - A
customers/redactrequest deletes the records we hold for the named customer. Acustomers/data_requestis answered with what we hold for that customer. - Backups age out on their own schedule, within 90 days.
If you disconnect a system other than Shopify, we stop syncing it and delete the data derived from it within 30 days. The same terms are stated, in full, in the Privacy Policy.
Access, incidents and who to write to
Access to production systems is limited to the people who run the service, and it is logged. No system is perfect; if we ever have a security incident affecting your data, we will tell you promptly and plainly — what happened, what it touched, and what we did about it.
Mnemos is operated by Jesshao LLC, doing business as Mnemos. Security questions, data requests and vulnerability reports go to support@mnemos.ai. A person reads them, not a queue.