Privacy Policy

Last updated: November 12, 2026

This Privacy Policy explains what information Fluent Thai collects, how it's used, and the choices you have.

TL;DR

  • No account is required. You can use all of Fluent Thai without giving us a name or an email address, and we never ask for one to let you in.
  • There is an optional email sign-in, in Settings > Account. If you choose it, we store the email address you give us, because that address is what lets your progress follow you to a second device, and so we can email you the sign-in link. If you also tick “you may reply” on a question in the app, we may send you a short note about it. Section 1D says what we keep and why, and how to stop the notes. If you don't use it, and you haven't left an address on a bug report, we hold no email for you.
  • We do collect usage and learning data to run the product (e.g., saving progress, generating your plan, fixing mistakes) and to improve it.
  • If you ask for help with a sentence, or with Thai you paste or type, and tap Ask, what you send goes to our provider, Anthropic, and we keep a copy of it for 180 days so we can read it and improve the help. (A report you send about an answer is kept separately, like other reports.) For Thai you paste or type, we send only the words we recognize in it, and we don't keep them or your question (unless you report the answer). Please don't send private messages you wouldn't want us to read. Sections 1G and 5 have the details.
  • We don't sell your data.
  • Your learning progress is automatically backed up to our server. If you clear localStorage only, your data will be restored on your next visit via a device ID cookie. Clearing all site data including cookies removes your device identity and progress cannot be automatically recovered. Use the in-app reset options instead.
  • You can selectively reset local data via Settings > Troubleshooting, and you can request deletion of server-stored data associated with your device.

1) What we collect

A. Device and basic request information

When you use the site, we receive standard information that your browser and network send to any website, including:

  • IP address (processed by Cloudflare for security and delivery)
  • User agent (browser/OS), and basic device/platform signals
  • Referrer URL (the page that linked you to Fluent Thai, if any)
  • Timestamps of activity
  • Timezone information (sent by the client to keep day-boundaries and “today” features consistent)

We use this for site operation, security, debugging, and analytics.

B. Product analytics (usage events)

We collect event-based analytics about how the product is used, such as:

  • Which pages/apps you open, and navigation events
  • Session start/end and approximate duration
  • App/round interactions (e.g., starting a round, submitting an answer, completing a round)
  • Performance signals (e.g., correct/incorrect, scores, counts, timing/latency)
  • Audio playback health (e.g., play errors, missing assets, autoplay blocked)
  • Feature interactions (e.g., tips, coach hints, onboarding steps)
  • Diagnostics events (e.g., data recovery, manifest health checks, troubleshooting resets)

These events may include identifiers for the exercise/item you interacted with (to understand what's working and what isn't).

C. Learning and progress data (to provide features)

To power features like spaced repetition, error review, assessments, daily plans, coaching tips, and data backup/recovery, we store:

  • Spaced repetition state (cards/items reviewed, scheduling info, review history)
  • Mistake/error tracking (what was missed, counts, and status for review workflows)
  • Assessments / calibration results (scores and answers where applicable)
  • Daily session / plan state (today's plan blocks, completion status, results)
  • Skill/progress summaries used for the dashboard
  • Activity history (streaks, minutes practiced, sessions completed)
  • User profile and preferences
  • Answers you give to questions inside the app, such as “What would you like to find easier in Thai?”, may be saved with your progress, whether or not you sign in. If a question offers to let us reply by email, it does so only if you have signed in with an email address, and we keep your answer to that too.

Learning data is stored both locally in your browser and server-side. The server copy acts as a backup so your progress can be restored if you clear localStorage. If you clear all browser data including cookies, your device identity is lost and automatic recovery is not possible.

D. Account details (only if you choose to sign in)

Fluent Thai works without an account. Nothing in this section exists for you unless you start the sign-in yourself from Settings > Account. Its main job is to let the same progress open on a second device, instead of being stranded in the browser that made it. It also lets us email you the sign-in link, and notes if you ask for them, as described below.

If you do sign in, we store:

  • The email address you enter — lowercased, with surrounding spaces removed — saved as the credential attached to your learner record.
  • Timestamps for that credential: when it was created, when it was verified, and when it was last used to sign in.
  • A record of which device was attached to which learner record, and why. This is what lets a “where did my progress go” question be answered rather than guessed at.
  • The sign-in link, stored only as a hash. The link that arrives in your inbox is never written down on our side. It expires 15 minutes after it is sent, and works once.

To deliver email we pass your address to Resend, a transactional email provider. We send you the sign-in link when you ask for it. If you tick “you may reply” on a question in the app, we may send you a short note about it. If you leave an email on a report, we may reply about that report (section 1E). There is no newsletter and no advertising.

You can ask us to stop at any time. Write to privacy@fluent-thai.com and we will stop sending you notes. You will still get a sign-in link whenever you ask for one.

Signing out detaches this browser from the account and returns it to an anonymous record. It does not delete the stored email address — to have that removed, use the deletion request in section 8C below.

E. Anything you type into a report

The issue reporting page has an optional email field. If you fill it in, it is stored with your report so we can reply about that report; leaving it blank still files the report. What you submit alongside it — what went wrong, which screen you were on, your answer and the expected one — is stored with it.

Now and then, after you finish a plan, the app may ask “What would you most like help with?” and offer a few quick picks and a box to type in. It is optional, and if you answer, it is filed like any other report: the picks, anything you type, which part of the app you were in, the time, whether you are on a phone or a computer and your browser's user agent are stored. Your device ID and user ID are not, and there is no email field.

F. A request to add a sentence to Look up

If you tap 'Ask us to add it', we keep what you typed along with your device ID, so we can add it and prevent abuse.

G. Help with a sentence, or with Thai you paste or type

Only if you use “Explain this sentence” and its “Ask about this sentence” button, which is growing into help with any Thai you paste or type. You type a question and tap Ask; nothing is sent or kept until you tap Ask. When you do, we keep a copy of what you sent, so that we can read it and improve the service:

  • For a sentence that is already in the app: the question you asked, and which sentence it was.
  • For Thai you pasted or typed: we send only the words we recognized in it, in order, with a marker where we hid something or didn't recognize it, but we don't keep them. We don't keep the question you typed (unless you report the answer, below), and we don't keep the text you pasted. If the text you pasted is exactly a sentence that is already in the app, it counts as that sentence, and your question is kept.
  • The answer you got, and whether it worked.
  • Your device ID, the random identifier your other progress data is saved under (section 2A), so that we can delete your copies if you ask (section 8C).
  • When you asked.

The copy has no email address and no IP address in it. Only our staff can see it, through our admin tools. If you send us text, we may read it. Please don't send private messages, or anything with personal details, that you wouldn't want us to read.

If you report an answer, we keep that question and answer with your report so we can look at it. The report is stored in the same place as the reports in section 1E, along with your device ID, your user ID (the record your progress is saved under), your browser's user agent, and any note you add. Separately, we keep a count of questions, which sentence they were about, whether the reply worked, and what it cost; those counts never hold the words you typed. They are not tied to your device, except through the temporary answer-verification value described below, in the copy described above, in a report you send, in the usage events described in section 1B (which carry your device ID like every other event), and in a short-lived counter, kept against your device ID and your IP address, that limits how often one device or connection can ask. That counter is deleted about a day after your last question.

When an answer is delivered, we keep a one-way verification value with its request record. It combines a random receipt for that answer with your device identifier so that only the device that received the answer can report it. The request record does not keep the receipt or your device identifier itself. This applies to answers about app sentences and Thai you paste or type, even when no copy of your question or answer is kept. The verification value stops authorizing reports 24 hours after the request. Scheduled cleanup removes expired values in batches; a delayed cleanup does not extend the reporting window. Aggregate counts remain. This is separate from the stored copy and its 180-day deletion. A report already sent is kept like other reports.

2) Identifiers we use (and why)

A. Device identifier

Fluent Thai generates a random device identifier stored in your browser's localStorage. This identifier is also persisted in a cookie (__ft_device_id, 2-year expiry, SameSite=Lax) as a durability fallback. If your localStorage is cleared, the cookie allows your device to be recognized so your backed-up data can be restored.

The device identifier is used to:

  • Keep your progress consistent on a single device
  • Associate analytics and learning state with your device
  • Enable data backup and recovery
  • Support pairing/sync when you opt in

This identifier is not your name and does not, by itself, tell us who you are.

B. Session identifier

We also use session-level identifiers to group activity into sessions (for example, when you return after being idle). Session identifiers may change more frequently than the device identifier.

3) Cookies and local storage

Fluent Thai uses:

  • A device ID cookie (__ft_device_id) to maintain your device identity if localStorage is cleared. This cookie contains only the random device identifier and expires after 2 years.
  • localStorage to store preferences, learning state, audio cache, and session data. This is the primary storage for your app experience.
  • sessionStorage for short-lived state like health-check throttles and recovery flags (cleared when you close the tab).

To manage your local data, use the Troubleshooting page in Settings. You can selectively reset specific parts of the app (audio cache, today's session, daily plan, coach notes, or SRS data) without losing everything. Server-backed data is restored on your next visit from the same browser. If you clear all site data for fluent-thai.com (including cookies and local storage), your anonymous device identity resets and automatic recovery may not be possible.

4) Server-side data backup

Your learning progress is automatically backed up to our server. This includes settings, skill progress, spaced repetition state, error bank, activity history, and profile data. Backup happens in the background when you use the app.

If your browser data is cleared but your device ID cookie is preserved, backed-up data is automatically restored on your next visit. If both localStorage and cookies are cleared, a new device identity is created and previously backed-up data remains on the server (it can be manually linked upon request).

5) Where data is stored and processed

Fluent Thai runs on Cloudflare infrastructure. Depending on feature flags and configuration, your analytics and learning data may be stored/processed in:

  • Cloudflare Workers / Pages (application runtime)
  • Cloudflare D1 (database for product state, backups, and analytics)
  • Cloudflare Analytics Engine (aggregated analytics storage)
  • Cloudflare R2 (audio files, event archival / logs)

Our hosting provider, Cloudflare, keeps request logs (including your device ID, IP address and approximate location) for up to 7 days for security and troubleshooting.

Two things can leave Cloudflare, and only when you use them.

Email sign-in. If you use the optional email sign-in, your email address and the sign-in link are passed to Resend, which delivers the emails we send you. Resend receives those emails and nothing else — no analytics, and no learning data beyond what an email itself says.

Help with a sentence, or with Thai you paste or type. When this option is available and you type a question and tap Ask, we send that question to Anthropic, who write the reply for us. If you are asking about a sentence that is in the app, we also send that sentence's ID, its words and our notes on it. If you are asking about Thai you pasted or typed, we don't send the text itself. We send only the words we recognize in it, with a marker where we don't recognize something. Before the words from your text are sent, we hide email addresses, links, phone numbers, long numbers and numbers spelled out in four or more words. A name that is also an ordinary Thai word, like a nickname that means “fish,” can go out as that word. We and Anthropic process what we send, and we may read what we keep to improve help (section 1G). Anthropic receives only that: not your device ID, your email, your progress, your IP address or anything else about you. We shorten the question to 300 characters and hide email addresses, links that start with http or www, phone numbers and long numbers in the question before it is sent, but please don't type personal details into the box, and please don't send private messages you don't want read. Nothing is sent until you tap Ask. Anthropic doesn't use what it receives from us to train its models, and deletes it within 30 days, unless it has to keep it longer to enforce its usage policy or because the law requires it.

We don't sell your data and we don't share it with third-party advertisers.

6) How we use information

We use collected information to:

  • Provide core functionality (sessions, progress, review, plans, tips/coaching)
  • Back up and restore your learning data
  • Maintain and secure the service
  • Diagnose bugs and improve quality (including audio/content correctness)
  • Read what you send when you ask for help with a sentence or with Thai you paste or type, to improve that help (section 1G)
  • Measure product performance and improve recommendations over time

7) Data retention

Retention varies by data type:

  • Analytics may be retained for trend analysis and product improvement.
  • Learning state is retained as long as needed to provide features (and as long as your device remains active or paired), unless you request deletion.
  • Server-side backups are retained to enable data recovery. They are deleted upon request.
  • If you use the optional email sign-in, the credential and its sign-in history are kept for as long as the account exists, so that signing in again lands you on the same progress. Spent and expired sign-in links are kept as records rather than pruned; each one holds a hash, never the link itself.
  • A request from Look up (section 1F) and the device ID kept with it are both deleted once we have dealt with it, or 180 days after the first request.
  • Help with a sentence, or with Thai you paste or type: the copy we keep of what you send (the sentence you asked about; your question, except when you ask about Thai you paste or type, which we don't keep; the answer, whether it worked, your device ID and the time) is deleted 180 days after you sent it, or sooner if you ask us to delete your data (section 8C). Only staff can see it. If you report an answer, we keep that question and answer with your report so we can look at it. A report is kept like other reports (section 1E). Anthropic doesn't use what it receives from us to train its models, and deletes it within 30 days, unless it has to keep it longer to enforce its usage policy or because the law requires it. The counts described in section 1 are kept as ordinary analytics. Their temporary answer-verification values expire for reporting after 24 hours and are removed by scheduled cleanup, separately from the stored copy's 180-day deletion.

We aim to retain only what is necessary for product operation and improvement.

8) Your choices and rights

A. Manage local data

Use the Troubleshooting page in Settings to selectively reset specific parts of the app. Each option shows exactly what will be cleared and what will be preserved. Server-backed data is restored automatically on your next visit from the same browser. If you clear all site data for fluent-thai.com (including cookies and local storage), your anonymous device identity resets and automatic recovery may not be possible.

B. Don't sign in, or sign out again

The email sign-in is optional and stays optional. Skip it and Fluent Thai works exactly as it does now on this device, with your data still backed up for recovery. If you have signed in and change your mind, signing out from Settings > Account detaches this browser from the account. That is a detach, not a deletion — the stored email address goes only when you ask for it to, below.

C. Request deletion

Because we store learning and analytics data server-side keyed to your device (and/or paired user record), you can request deletion of the data associated with your device(s). Contact us at privacy@fluent-thai.com and include:

  • The fact you want data deletion, and
  • The device you used, or the email address you signed in with

(We may ask for a simple verification step to ensure you control the device(s) in question.)

9) Backup and recovery limits

Backup and recovery are best-effort:

  • Data backup and recovery are best-effort. We work to ensure reliability but cannot guarantee zero data loss.
  • If both your cookies and localStorage are cleared simultaneously, and you have not signed in with an email address, your device identity is lost and backed-up data cannot be automatically restored (manual recovery may be possible upon request).

10) Changes to this policy

We may update this policy as the product evolves. We will update the “Last updated” date at the top of this page.

11) Contact

Questions or requests: privacy@fluent-thai.com