Subprocessors

The named third parties that process XMemo data in the hosted service, what each one receives, and where it is processed.

Persistent memory storage and the regional embedding deployment are provisioned in Azure Japan East. A separately configured GlobalStandard Azure OpenAI chat deployment may process explicitly requested AI operations in another Azure geography.
Memory text is sent to Microsoft Azure OpenAI Service for embedding or another AI operation requested through XMemo. Microsoft states that this customer data is not made available to OpenAI or used to train generative foundation models without permission or instruction; Microsoft content-safety and abuse-monitoring processing may still apply.
We name each hosted subprocessor rather than only a service category, and we update this page before a new subprocessor begins processing customer data.

Hosted subprocessors

These are the named third parties that process data in the hosted XMemo service.

Microsoft, for Azure compute, Azure Database for PostgreSQL, and Azure Key Vault, in the Japan East region. PostgreSQL stores memory, audit, identity, tenant, token, and DSAR control-plane data; Key Vault stores service secrets.
Microsoft, for Azure OpenAI Service. The production embedding deployment uses the regional Standard deployment type in Japan East. A separate chat deployment uses GlobalStandard and may process content in another Azure geography when an XMemo feature invokes it. [Microsoft documents](https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/data-privacy) that prompts, outputs, and embeddings are not made available to OpenAI or used to train generative foundation models without permission or instruction, while content-safety and abuse-monitoring processing may still occur.
Cloudflare, for DNS, TLS termination, edge proxying, delivery, security filtering, and Web Analytics page-view and performance measurement for public XMemo hostnames where proxying is enabled. The Web Analytics beacon is described in the Cookie Policy; it sets no cookie and receives no memory content. It may process source IP addresses, request and TLS metadata, hostnames and paths, security events, and request bodies transiting the proxy. Its edge network and related processing are global; exact storage and onward-processing locations depend on the enabled Cloudflare services and account terms.
GMO DigiRock, Inc. (Value-Domain), for the mail hosting behind Yonro's own mail domain, used to send transactional email such as sign-in verification codes, security notices, and account notifications. It processes recipient email addresses and the content of those messages, not memory content.
Google LLC, for Google Sign-In, only if you choose to sign in with Google. It processes the sign-in redirect and the account identifier, email address, verification status, and profile name described in the Privacy Notice.

Data residency

Persistent memory storage and regional embedding processing are configured in Japan; other disclosed service paths may involve other countries.

Persistent memory storage and the Standard embedding deployment are in Azure Japan East.
AI operations that invoke the GlobalStandard chat deployment may be processed in another Azure geography.
Database backups are the automated backups managed by Azure Database for PostgreSQL and remain within the Japan East region.
Cloudflare's global edge may process network and request data, including request bodies in transit when proxying is enabled.
Google Sign-In is optional, processes identity claims only, and does not receive memory content from XMemo.
International transfers are handled under the safeguards described in the Privacy Notice and applicable provider terms; resource location alone is not a promise that all operational or support processing stays in one country.

Components we operate

Some components run inside the deployment we operate rather than as a separate vendor relationship.

Redis runs within our deployment and processes rate-limit counters, queues, and transient worker coordination state.
Redacted operational evidence is retained according to operator policy.
No separate third-party observability vendor is currently configured. Microsoft Azure may process deployment and platform logs as part of the Azure services described above.
No payment provider is used while the service is free of charge, and no advertising or third-party browser analytics vendor is used.

Release and build

These process our software, not customer data.

GitHub/GHCR and Sigstore process release artifacts, SBOMs, signatures, and provenance for published images.
No customer memory content is included in release artifacts or build logs.

Storage you connect yourself

If you connect your own database to XMemo, that provider is not a Yonro subprocessor.

Data written to a database you control is processed under your own agreement with that provider.
You remain responsible for that provider's region, retention, and security configuration.

Change notice

We update this page before a new hosted subprocessor begins processing customer data, and we describe what changed.

Compiled from the production deployment configuration, runtime code paths, and operations documentation. Questions about a specific subprocessor: privacy@xmemo.dev.