Subprocessors
Last updated June 2026
Plain-language template. This document describes how mmmry actually works, in good faith and in everyday English. It is template text that has not been reviewed by an attorney. Have qualified counsel review and adapt it for your jurisdiction and entity before relying on it in production.
To run mmmry we rely on a small set of providers that process data on our behalf. We keep the list short on purpose. This page is the authoritative list referenced by our Privacy Policy.
Third-party processors
| Provider | Purpose | Data involved |
|---|---|---|
| AI model providers (via gateways we operate) | Summaries, auto-tags, OCR, semantic & image embeddings, goal-alignment scoring. Includes OpenAI (text embeddings), Google (Gemini language model, Vision OCR), and Replicate (CLIP image embeddings), reached through an LLM/AI gateway. | The content of a card being enriched (text, image, or extracted text), sent at save time and cached by content hash. |
| Resend | Sends transactional and (opt-in) reminder emails. | Your email address and message content (e.g. sign-in links, reminder digests). |
| Stripe | Payment processing and subscription management (paid plans only). | Billing details you enter (handled directly by Stripe), plus a customer/subscription identifier we store. |
| Hosting / infrastructure provider | Runs the servers and storage on which mmmry operates. | All service data, encrypted at rest as described in the Privacy Policy, resides on infrastructure we control at this provider. |
Self-hosted infrastructure
The following run on infrastructure we operate rather than as third-party SaaS, but we list them for transparency about where your data lives.
| Provider | Purpose | Data involved |
|---|---|---|
| PostgreSQL + pgvector | Primary database and vector search. | Encrypted card text, account data, derived search artifacts. |
| Object storage (S3-compatible / MinIO) | Stores image and file assets. | Your uploaded/captured assets, under a per-user prefix. |
| Headless browser (Browserless) + Redis | Renders page screenshots and runs the background ingest queue. | URLs you save and transient job data. |
| Sentry (optional, self-hosted) | Error monitoring, only if enabled by the operator. | Crash/exception details. Session replay and personal-data capture are disabled. |
Changes
We'll update this list when we add or remove a processor. Questions? Email [email protected].