Summary
- If you create an account, we store your email, optional display name, preferences, and saved presets (including custom contexts and tones).
- 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.
- Our primary provider is Google Gemini (free tier). Google may use submitted content to improve its products and models, including through human review. Do not paste confidential or sensitive content.
- 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 workplace text in many languages. 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)
- Subscription or plan records, including Paddle customer, subscription, product, and price identifiers; status; and billing-period dates
Guests. Without an account you cannot save presets. We keep these browser preferences and limited server-side usage records:
- 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 rows currently have no automatic retention job and remain until an operator deletes them. A bounded automatic retention policy is a required legal and operations decision before production.
Usage metering. For signed-in paid access, we retain an opaque HMAC request fingerprint, request ID, plan and monthly-unit state, timestamps, provider and model identifiers, token counts, latency, safe outcome codes, and an internal 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.
Google Gemini (primary). We use the Gemini API free tier. Under Google's Gemini API terms, free-tier content may be used to improve Google's products and machine-learning models, and may be reviewed by humans. Treat anything you submit as potentially visible to Google. Avoid confidential, proprietary, or personal sensitive text. See Google's Gemini API Additional Terms.
Groq (fallback). If Gemini is unavailable or rate-limited, we may send the same request to Groq. Groq states that it does not train on API data and does not retain API content by default (temporary logs may be kept for a short period, typically up to 30 days). See Groq's privacy documentation.
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 |
|---|---|---|
| Google (Gemini API) | Primary AI processing of your text | Terms · Privacy |
| Groq | Fallback AI processing | Privacy |
| Supabase | Accounts, preferences, presets, custom prompts, billing metadata | Privacy |
| Paddle | Checkout, payments, tax, subscriptions, billing portal | Privacy |
| Self-managed VPS hosting | Hosting and application delivery | Pending |
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. They have no automatic retention job and remain until operator deletion; a bounded retention policy is required before production. 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, 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
Our Chrome extension captures only text you select and send via the right-click context menu. That text is held briefly in session storage, then sent to the same Matchum API used by the website. It is not scraped from pages in the background.
Extension preferences use the browser's sync storage. Sign-in tokens and a temporary account bootstrap cache use local storage. The account cache is removed when you sign out or delete your account. The extension does not inject content scripts into arbitrary sites and does not request broad host permissions beyond what is needed to talk to our service.
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.