Short version
Last updated: October 22, 2026.
This policy applies to Manatan websites, apps, and account services, including manatan.com, account settings, membership checkout, tracker account linking, Discord member perks, and Google Drive token brokering for app sync.
Who we are
Manatan is a language immersion app and account service. The account service lets you manage sign-in methods, memberships, tracker connections, supporter profile settings, and sync-related account links.
If you use a self-hosted or development deployment, the person operating that deployment may control its database, logs, environment variables, and connected service credentials. This policy describes the official Manatan deployment and the software defaults.
What we collect
Account and sign-in data
- Manatan login email address when you sign up with email, add it to your account, or a sign-in provider verifies it for account reconciliation.
- Email verification status, account status, account creation time, and account deletion state.
- Password hashes for email login. Manatan does not store plaintext passwords.
- Session cookies, CSRF tokens, passkey records if you add passkeys, and login security events.
- OAuth provider IDs, provider email addresses, and provider email verification status for Google or Discord when you link those sign-in methods.
- An account-matching form of your email address. For personal Gmail addresses, dots, plus tags, and the googlemail.com alias are treated as the same mailbox to prevent accidental duplicate accounts and signup abuse. The address you entered is still kept for display and delivery.
- A risk flag when the email domain appears on Manatan's limited list of known temporary-email services. Temporary-email accounts are not automatically banned solely because of this flag.
When Google or Discord confirms that you control an email address, Manatan may use that verified address to recognize an existing account and keep your sign-in methods together. Unverified provider emails are never used for automatic account linking. Adding an email-and-password login still requires a secure email confirmation or password-setup link.
Optional extension feedback
If you submit the browser extension’s uninstall feedback form, Manatan stores your selected reason, optional comments, extension version, submission time, and any email address you choose to provide for follow-up. Feedback is private to the Manatan team and can be submitted without an account. An IP-derived, hashed rate-limit key helps prevent spam; the feedback record does not include your browsing history or account identity.
Profile and built-in tracker data
If you use Manatan profiles or built-in tracking, Manatan stores your username, public profile settings, avatar or banner image URLs, video, manga, novel, and game list entries, reading, watching, or playing progress, scores, notes, and immersion time totals or progress events you add.
Public shared decks
If you publish a deck, its package, description, author attribution, selected license, and release history become public. For new and updated releases, we record the publishing account, release, selected license, accepted publishing-terms version, and server acceptance time. These acceptance records remain associated with the publication and are removed when that publication is unpublished. Private flashcard collections are not made public merely by syncing or studying.
Connected tracker data
If you connect tracker accounts, Manatan stores enough tracker connection data to let your signed-in app instances reuse that tracker session. Depending on the tracker, this may include provider user IDs, usernames, OAuth access tokens, refresh tokens, token expiration times, or session tokens.
For trackers that use username/password login rather than OAuth, Manatan sends the credentials to that tracker during the connection attempt and stores the resulting session information. It is not intended to store the tracker password itself.
Google Drive sync data
If you connect Google Drive for Manatan sync, Manatan stores OAuth token data needed to issue short-lived access to your app. The app then talks directly to Google Drive for backup sync.
Membership, billing, and supporter data
- Membership plan, tier, entitlement state, billing provider, billing status, and renewal-related metadata.
- Service-credit grants, purchases, balances, rollover, expiration, and usage records, including the service category, billed units, and limited request metadata such as a job identifier.
- Stripe customer/subscription identifiers and limited transaction metadata, such as amount and currency.
- Apple transaction and original-transaction identifiers, product, price, currency, expiration, renewal, cancellation, and refund status. Manatan uses an account UUID as Apple's app account token to link the purchase to the correct Manatan account.
- Google Play purchase-token and order identifiers, product, price, currency, expiration, renewal, cancellation, acknowledgement, test-purchase, and refund status. Manatan sends Google a one-way hash of the account UUID to bind the purchase to the correct Manatan account.
- Supporter profile display name and whether you opted into a public supporter listing.
- Discord IDs, Discord usernames, guild membership, and mapped roles when Discord perks are enabled.
- Legacy supporter records, such as supporter email, Discord username, tier, amount, and active status.
Technical and security data
Manatan may process IP addresses, request metadata, user-agent strings, rate-limit records, audit events, error logs, webhook delivery results, and account-operation records to operate and secure the service. These records help detect abuse, diagnose failures, and protect accounts.
Manatan loads Cloudflare Turnstile during email signup and may also require it when other authentication activity appears unusual. Cloudflare may process security signals such as the IP address, TLS fingerprint, user-agent header, site key, and originating hostname to distinguish people from bots. See the Cloudflare Turnstile Privacy Addendum.
Network-backed OCR, translation, and other AI tools
When you choose a network-backed tool, the images, audio, subtitles, text excerpts, prompts, or files needed for that request are transmitted to Manatan and/or the configured processing provider. We also process the resulting output and job, usage, and service-credit metadata needed to deliver and account for the requested service. This is different from local OCR, local dictionaries, and local media playback, where processing on your device alone is not collection by Manatan.
Do not assume that a network-backed request is processed only in memory or that its inputs and outputs are immediately deleted. Processing and retention depend on the selected service and the work needed to deliver the result, resolve failures, and maintain security and billing records.
Crash and performance diagnostics
Official Manatan app releases use Sentry to process automatic crash reports, application hangs, Android application-not-responding reports, and unexpected process exits. When configured in the release, automatic diagnostics are enabled by default. We also collect a sample of performance traces and profiles to investigate reliability, startup, and responsiveness problems, not to target advertising.
Reports can contain the app version and build, operating system and device details, stack traces, error codes, timing and resource information, and the feature or operation that failed. At a failing media, dictionary, or network boundary, reproduction context can also include an exact source-request URL, a public media title or identifier, a search or dictionary term, a relevant text excerpt, or a local path when needed to diagnose that failure. This is not a general upload of your media library or browsing history.
Our reporting configuration filters account identity, passwords, authorization headers, cookies, and credentials, and does not attach screenshots or enable session replay. Filtering differs between Flutter, native, and embedded-server reports; it does not mean every report removes all URLs, paths, terms, or media identities. Do not include secrets in a diagnostic attachment you choose to send to support.
You can disable automatic app reporting using the Anonymous crash diagnostics control in Manatan settings. Reports already received may remain available for investigating and fixing failures; disabling reporting does not erase existing reports. Contact privacy@manatan.com to request access or deletion where applicable. Operational server security logs and diagnostic files you explicitly share with support are separate from this automatic-reporting control.
How we use information
- To create and secure Manatan accounts.
- To verify email addresses, reset passwords, manage sessions, and prevent abuse.
- To provide Manatan profile pages, built-in media tracking, and immersion statistics.
- To let you connect optional sign-in methods, tracker accounts, Discord perks, and Google Drive sync.
- To process memberships, grant paid or legacy supporter perks, and handle billing webhooks.
- To show public supporter names only when you opt into the public listing.
- To investigate support requests and keep the service reliable.
- To comply with legal, tax, accounting, security, and fraud-prevention obligations.
YouTube terms and privacy policy
Some Manatan services use the YouTube API. The YouTube Terms of Service apply to the use of YouTube content through those services. The Google Privacy Policy also applies.
When you open a video through Manatan, its public YouTube video ID can contribute to our shared discovery catalog. The website verifies public availability, embedding eligibility, audio language, title, channel, thumbnail, and duration before recommending it to other users. An account is required for submission and rate limiting, but the discovery record does not identify who watched the video or include their watch time, searches, cookies, or private playlist links. Personal saved, followed, and watched state remains separate and scoped to your account and profile.
The in-app YouTube website browser observes only top-level video URLs and skips these automatic discovery submissions while Incognito applies. Navigation after you choose to open the system browser is outside Manatan's observation. Unknown-language, private, unlisted, and non-embeddable videos are not included in shared recommendations. YouTube-provided metadata is refreshed or removed separately from retained public IDs.
Google Drive sync
Manatan's Google Drive sync is designed around least practical access. The server may store OAuth tokens so your signed-in Manatan apps can obtain short-lived access without asking you to sign into Google on every device. The actual .manatanbk backup payload is intended to move directly between the app and Google Drive.
This means Manatan may know that Drive sync is connected and may broker access tokens, but it should not proxy or inspect your backup file contents during normal sync.
Billing and legacy support
Memberships can be processed through Apple, Google Play, Stripe, Ko-fi, Discord role matching, or manual support review. Manatan validates Apple StoreKit transactions, Google Play purchase tokens, and provider renewal notifications so a store membership can work on the same Manatan account across platforms. Manatan stores the minimum billing state needed to decide whether an account has member perks, show billing diagnostics, handle webhook retries, and avoid accidentally removing perks when a provider has a temporary outage.
Legacy supporter matching may compare account emails, verified emails, Discord usernames, Discord IDs, and uploaded supporter CSV records. Public supporter profile information is only shown publicly if you opt in.
Referral and creator partner operations
Manatan operates member referrals and creator attribution directly. When you intentionally follow a Manatan referral link, Manatan stores an opaque first-party click token, the partner or member code, click time, landing path, referring page when supplied by your browser, and a 60-day expiration time.
If you start an eligible website checkout in that window, Manatan attaches its internal partner and click identifiers to the Stripe Checkout record. Member referrals can produce Premium rewards; approved creator referrals can produce revenue-share commissions. Apple and Google Play purchases are excluded. Referrers and creators see aggregate referral, reward, and earnings information, not your payment details or account credentials.
If you apply as a creator partner, Manatan processes your application answers, identity and contact information, publishing channels, referral activity, commission history, payout details, invoices, and applicable tax documentation. Manatan retains transaction, attribution, risk-hold, reward, commission, payout, and post-payout offset records needed to prevent duplicate adjustments and reconcile reversals.
You can clear the Manatan referral cookie through your browser controls. Blocking or deleting it can prevent referral attribution.
Retention and deletion
Manatan keeps information while your account is active and as long as needed to provide the service, secure accounts, resolve disputes, and meet legal or accounting obligations.
- Account deletion requests schedule the account for deletion after a 30-day waiting period.
- Email-only accounts that are never verified may be deleted after 30 days if they have no sign-in-provider link, session, membership, billing record, credits, entitlement, or administrative account grant.
- Session records, verification tokens, reset tokens, rate-limit rows, and temporary OAuth states expire or are cleaned up over time.
- Billing and transaction records may be kept longer where required for tax, accounting, fraud prevention, or dispute handling.
- Backups stored in your Google Drive are controlled through your Google account and Drive settings.
Some information may remain in backups for a limited time after deletion, but it will not be restored into active systems unless needed for disaster recovery, security, or legal reasons.
Your choices and rights
- You can log out from the account page and revoke active sessions.
- You can add, change, verify, or remove your Manatan login email when your account has another recovery method.
- You can disconnect linked sign-in methods, tracker accounts, Discord, and Google Drive where the account page provides controls.
- You can opt in or out of the public supporter listing.
- You can disable automatic app crash and performance diagnostics in Manatan settings. This does not remove reports already received or stop separate operational security logging.
- You can request access, correction, export, deletion, or restriction of personal information where applicable law gives you those rights.
- You can also revoke OAuth access directly from Google, Discord, or tracker provider account settings.
If you are in a region with privacy laws such as the GDPR, UK GDPR, CCPA/CPRA, or similar laws, you may have additional rights. Contact us and we will handle the request according to the law that applies to you and to Manatan.
Security
Manatan uses security measures such as hashed passwords, CSRF protection, session cookies, rate limiting, conditional bot challenges, OAuth state checks, token expiration, restricted access controls, and audit logs. No internet service can promise perfect security, but the goal is to keep sensitive data narrow, encrypted in transit, access-controlled, and removable when it is no longer needed.
Do not paste passwords, OAuth secrets, API tokens, or billing secrets into public issues, screenshots, or chat logs. If you accidentally expose a secret, rotate it with the provider.
Children
Manatan is not intended for children under 13. If you believe a child provided personal information without appropriate consent, contact us so we can delete it.
Changes to this policy
We may update this policy when Manatan changes, when new account or billing features are added, or when legal requirements change. The "Last updated" date will change when the policy changes. For material changes, we will make reasonable efforts to provide a more visible notice.
Contact
For privacy requests, account deletion questions, or data-access requests, contact privacy@manatan.com.
If that mailbox is not yet active on a new deployment, use the Manatan GitHub or Discord links from the homepage and include "Privacy request" in the subject or first line.
This policy is meant to be understandable and accurate for Manatan's current implementation. It is not a substitute for legal advice if you operate your own deployment or process data for other people.