Summary
- If you create an account, we store your email, optional display name, preferences, saved presets (including custom contexts and tones), and glossary entries.
- Text you submit is sent to third-party AI providers so we can return a translation or rewrite. We do not store that text on our servers.
- Paddle processes paid checkouts. We keep limited customer, subscription, and webhook metadata so we can provision and support paid access.
- We keep limited usage metadata to apply request and monthly allowances. We do not store source text, prompts, or output text for metering.
- AI requests normally pass through Vercel AI Gateway. We restrict routing to providers that do not use submitted prompts or responses for model training. This does not guarantee zero retention: providers may retain content under their applicable service and abuse-prevention policies. An emergency direct route is permitted in production only after its complete path is separately attested for ZDR.
- We do not run analytics or ads, and we do not sell your data.
- You can correct or delete account data from Account settings. For help: [email protected].
Who we are
Matchum ("we", "us") is a preset-based writing assistant for Korean-English workplace writing. Contact: [email protected].
What we collect
Signed-in users. When you create an account we store:
- Email address, optional display name, and authentication credentials (via Supabase)
- Preferences (for example UI settings tied to your account)
- Saved presets
- Custom contexts and custom tones (labels and prompt text you write)
- Glossary entries (terms, preferred translations, and keep-as-is settings you add)
- Subscription or plan records, including Paddle customer, subscription, product, and price identifiers; status; and billing-period dates
Guests. Website guests cannot save presets. Extension guests can save up to 20 presets, including custom instructions, in browser sync storage. Browser preferences and limited server-side usage records are described below.
- Theme preference in browser localStorage (
matchum-theme) - UI language in a functional cookie (
matchum-ui-lang)
Technical. To enforce daily usage limits we process a hashed form of your IP address (HMAC). We do not store raw IP addresses for this purpose.
Guest usage records. Guest metering retains an HMAC guest identifier, UTC usage date, request count and update time. A request reservation also records its UUID, state, and creation, consumption, or refund timestamps. Guest records are deleted manually when no longer needed for quota enforcement, abuse prevention, or service operations.
Free usage measurement: we store daily aggregate request counts, token counts and estimated cost by guest/account tier and served model. These aggregate records contain no account IDs, guest identifiers, source text or generated text.
Usage metering. For signed-in paid access, we retain an opaque HMAC request fingerprint, request ID, plan and monthly-credit state, timestamps, requested model family and alias, router, served provider and model identifiers, token counts, latency, safe outcome codes, and an internal versioned cost estimate. This record does not store your source text, prompt or instructions, or generated output text for metering.
Billing events. We receive signed webhook events from Paddle to keep plan access current. The raw payload is cleared after an event is processed or intentionally ignored. A failed event payload may be retained while we diagnose or replay it.
We do not:
- Run analytics or advertising trackers
- Sell your data
- Store the source text you submit for rewrite or translation on our servers
How your text is processed
When you generate a result, we send your source text plus the task settings (mode, language, context, tone) to an AI provider. If you use a custom context or tone, its label and prompt text are included in that request.
Glossary: if you add glossary entries, they are stored in your account. When you translate or rewrite, only the entries whose terms appear in your text are sent to the AI model provider along with that text. A glossary may include other people’s names, such as colleagues’, so add only what you need. Delete entries at any time from Account → Edit glossary; they are also removed when you delete your account.
Vercel AI Gateway. Matchum normally sends requests through Vercel AI Gateway, which routes them to the configured Google, OpenAI, Anthropic, or another reviewed upstream provider. Every Gateway request sets the no-prompt-training restriction and fails closed when no eligible provider route is available. This prevents providers from using submitted prompts or responses for model training, but it does not guarantee zero retention. Providers may retain content under their applicable service and abuse-prevention policies. Zero-data-retention enforcement applies only when Matchum separately configures and verifies that privacy mode. See Vercel AI Gateway documentation.
Model choice and fallbacks. Auto may retry the same request with a different configured model family if the first route is unavailable. A manually selected family is not replaced with a different family. Exact model versions may change as we evaluate quality and availability. In an explicit emergency rollback mode, Auto requests may bypass Gateway only when the complete direct route and every fallback have been separately attested as ZDR-compliant.
We do not keep a server-side copy of your submitted text after the request completes. Providers process it under their own terms.
Services we rely on
We use the following third parties to run Matchum. They process data on servers in the United States and other countries, which may be outside the country you use the service from (including Korea).
| Service | Purpose | Policy |
|---|---|---|
| Vercel AI Gateway | AI routing, provider selection, and usage metadata | Privacy |
| AI model providers | Upstream processing, including Google, OpenAI, Anthropic, and separately attested direct-mode providers | Provider list |
| Supabase | Accounts, preferences, presets, custom prompts, glossaries, billing metadata | Privacy |
| Paddle | Checkout, payments, tax, subscriptions, billing portal | Privacy |
| Self-managed VPS hosting | Hosting and application delivery | Not applicable — self-managed infrastructure |
For signed-in customers with a linked billing account, we provide their Paddle customer ID to Paddle Retain for subscription recovery. We do not use your internal account ID or email as the Retain identifier, and we do not send your source text or generated output to Paddle.
Cookies & local storage
- Supabase session cookies — keep you signed in
matchum-ui-lang— remembers the UI languagematchum-theme(localStorage) — light or dark theme
Paddle checkout and its billing portal may use functional and fraud-prevention cookies under Paddle's privacy notice. Matchum does not use these settings for advertising.
Retention & deletion
Account data is kept while your account exists. Submitted source text is not stored by us after generation. Usage-metering metadata is retained while the related account exists and is removed with the account; guest daily records contain an HMAC identifier, UTC date, count, and update time; guest reservations retain a UUID, state, and lifecycle timestamps. Guest records are deleted manually when no longer needed for quota enforcement, abuse prevention, or service operations. Before deleting an account with a billable subscription, you must cancel it and wait for the paid period to end. Account deletion removes your profile, preferences, presets, custom options, glossary entries, and usage records. Limited billing records may be retained in unlinked form as needed for tax, accounting, fraud prevention, disputes, or refunds; Paddle keeps its own transaction records under its policies and legal obligations. If you cannot access your account, email [email protected] for help.
Your rights
Depending on where you live, you may have rights to access, correct, or delete personal data we hold, or to withdraw consent where it applies. You can update your display name and sign-in email, or delete your account, from Account settings. Email [email protected] for other access or correction requests.
Browser extension
The context menu copies only the text you select into a side-panel draft. Selection alone does not send it for AI processing. You can also type or paste text. Generate sends your input, instructions and selected settings through the Matchum API to AI providers; rewrite actions send the result being transformed. The extension does not scrape pages in the background or inject content scripts into arbitrary sites.
Preferences and guest presets, including custom instructions, use browser sync storage and may sync to other devices according to your browser settings. Sign-in tokens and an account bootstrap cache, including saved presets and custom options, use local extension storage. The account cache is removed on sign-out or account deletion. Delete guest presets in the preset menu; clearing extension data or uninstalling removes local extension storage according to browser behavior.
Selected text is staged in extension session storage until read by the panel. During social sign-in or account-deletion reauthentication, a temporary session-storage handoff may also contain the draft, instructions and writing settings so they can be restored. These drafts are not synced to other devices. Handoffs are logically invalid after 30 minutes and removed when an expired record is read or the flow clears it; the timeout does not schedule physical deletion. Browser session storage is cleared when the browser session ends. AI-provider retention remains subject to the policies described above.
Use of information received from Google APIs (if any) will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Children
Matchum is not intended for users under 14, or under the higher minimum age set by the law where you live. We do not knowingly collect personal information from children below that age. If you believe a child has created an account, contact us and we will delete it.
Changes
We may update this policy when the product or our practices change. The "Last updated" date at the top will change when we do. Continued use after an update means you accept the revised policy.
See also our Terms of Service.