Privacy Policy
Lucidwords ("we", "us"), a sole proprietorship registered in the Republic of Korea, runs LucidHoldem. This policy explains what personal information we process, why, and what rights you have. We are the controller of your personal information.
Effective date: 11 November 2026
Notice of changes
This policy takes effect on 11 November 2026. Until the day before, the previous policy (effective 5 November 2026) applies. Read the previous policy
What changes from the previous policy:
- Ads: the Service now shows Google ads (Google AdMob in the apps, Google AdSense on the web). We list what the ad company collects (advertising ID and other device identifiers, IP address and the approximate location estimated from it, ad interactions, device and browser information, diagnostics) in section 1 and section 4. The sentence "the Service does not show ads" is removed.
- Personalised ads and your choices: new section 8 explains personalised ads and how to say no (consent tool, the US state right to opt out of sale or sharing, the advertising ID setting on your device, and iOS tracking permission). Section 7 (US state residents) is rewritten: personalised ads count as "sharing" for cross-context behavioural advertising.
- Rewarded ads and daily limits: we added rewarded ad confirmation records and daily usage records (kept for 35 days) to sections 1 and 3.
- Sign-in required: there is no longer a way to use the Service without signing in (guest use). Every feature needs an account. We added Sign in with Apple in the iOS app.
- Preflop range tables from our server: signed-in users receive range table spots from our server one spot at a time, and we record the spots you receive each day to apply the daily limit (kept for 35 days).
- International transfers: Google LLC (ads, United States) and Apple Inc. (Sign in with Apple, United States) are added to sections 4 and 5, and what happens if you object to transfers now reflects that sign-in is required.
Contact: support@lucidholdem.com
1. What we collect
| Category | Information | When |
|---|---|---|
| Account | Google account email address or Apple account email address (if you choose "Hide My Email" with Sign in with Apple, the relay address Apple creates), account ID | When you sign in with Google (web, Android, iOS) or with Apple (iOS app) |
| Study history | Quiz results and statistics, range builder settings, practice statistics, practice hand records (hand text, replays, simulated profit figures) | Saved automatically as you use the Service |
| Range table access records | Your account ID, the preflop range table spots you received for the first time that day (table name and spot number), where you opened them (range screen, practice, hand record scoring), and the date | When you receive a range table spot from our server |
| Daily usage records | Your account ID, the date, how many times you used each feature type (range tables, practice, server solves) and how many rewarded ads were confirmed that day | Saved automatically as you use the Service |
| Rewarded ad confirmation records | Your account ID, a one-time confirmation code, the feature type, the platform (Android, iOS or web), the ad unit, the transaction number sent by the ad company, and the request and confirmation times. We do not store advertising IDs, device identifiers or IP addresses | When you choose to watch a rewarded ad and the ad company tells our server that you finished it |
| Uploaded hand records | Hand record text as is (including the nicknames of you and other players in the hand record, table names, tournament numbers and play times), a hand summary (seat, hand, result, pot, whether it went to showdown, month), the site (PokerStars or GGPoker), play time, an identifier made from the hand number, file details (an identifier made from the file contents, hand count, size, play period) and your account ID. We do not receive the file name. Up to 20,000 hands per account | Only when you press "Keep on server" on the hand review screen and agree in the confirmation window |
| Custom flop solve requests | Your account ID, the identifier of the solve you asked for, whether it counted as a new solve towards the daily limit, and the time of the request | When you request a custom flop server solve |
| Custom flop solve settings | Board, pot, stack, bet size settings, per-hand range weights, node-lock and node-edit settings. Kept per solve job, not in the same table as your account. Users who ask for the same settings share one result. | When you request a custom flop server solve |
| Study history (postflop solve requests) | Postflop solve request details (board, pot, stack, bet size settings, ICM stage settings, solver settings and engine version, node-lock settings and the seat you chose, the source of the default range or the per-hand weights of a range you edited, and how many times it was requested). Collected anonymously and not linked to your account, email address or device identifiers. | Sent automatically when you solve on the device a spot that is not yet in the result store |
| Error reports | The question you reported and the answer you chose, the reason, your optional note (up to 200 characters), app version, time, stored with your account ID | When you press the report button |
| Collected by the ad company | Advertising ID (the Android advertising ID; on iOS, the advertising identifier IDFA only if you allow tracking), app set ID and other app- or device-level identifiers, IP address and the approximate location estimated from it, ad interactions (ad views, taps, video views), device, operating system and browser information, performance and diagnostic information about the app and the ad software, and ad cookies on the web. To confirm rewarded ads, we add your account ID and a one-time confirmation code to the ad request | Collected directly by the ad company (Google) when the Service requests and shows ads |
| Stored on your device | Sign-in token, email address, error reports not yet sent, copies of range table spots you received (7 days), and your ad consent choices (kept only in your browser or app storage) | When you sign in and as you use the Service |
| Connection data | IP address, access time and similar logs kept by our infrastructure provider | When you use the Service |
- We do not sell any paid products, so we do not process payment, order or subscription data. If we introduce a paid product, we will update this policy in advance.
- We do not store advertising IDs, device identifiers or IP addresses on our own servers. The ad company collects them directly when it serves ads, as described in sections 4 and 8.
- Practice hand "profit" figures are simulated study numbers with no monetary value.
File-based hand review
Completed-session PokerStars and GGPoker text files are parsed in browser or app memory. Acknowledgement of the GGPoker policy warning is not stored and is requested each time. This is separate from existing quiz and practice study history.
- Files you do not keep: hand records are processed only on your device. Raw records, filenames, nicknames and review aggregates are not sent to a server or synced to your account. Leaving the screen, clearing results, selecting another file or reloading releases the review state; it is not saved in device storage. The range table spots needed for scoring are received from our server, so those spots appear in your "Range table access records" (the hand records themselves are not sent).
- Files you keep: only files you choose to keep by pressing "Keep on server" and agreeing in the confirmation window (which lists what we keep, how to delete it and the limit) are stored in your account as "Uploaded hand records" in the table above. We keep the hand record text as is, without changing it, including the nicknames of you and other players in the hand record. The file name is not sent. Only you can see your kept records, and you can delete hands, files or everything at any time on the hand review screen. Signing out does not delete kept records from your account.
Rewarded ads and daily limits
- Range table access, practice and custom flop server solves have a daily limit per account. The free daily amount, how much one rewarded ad adds and the daily maximum are shown in the Service. Hand record scoring has its own daily limit that has nothing to do with ads. Where rewarded ads are not offered (for example, on the web), only the free daily amount is available.
- A rewarded ad plays only when you choose to watch it. When the ad company tells our server directly that you finished the ad (server-side verification), we use the "Rewarded ad confirmation record" above to add that day's extra uses. For custom flop server solves, the solve starts while the ad plays and the result opens once the ad is confirmed.
- You get the same rewarded ads and rewards even if you refuse personalised ads or do not allow tracking on iOS.
2. Why we use it and our legal basis
If you live in the United Kingdom, UK data protection law requires us to tell you the legal basis for each use.
| Purpose | Legal basis (UK GDPR Article 6) |
|---|---|
| Creating your account, signing you in, syncing across devices | Contract — needed to provide the Service you signed up for |
| Saving your study history and showing weak-spot analysis | Contract |
| Providing range table spots and applying the daily limit to stop bulk collection by automated tools | Contract; legitimate interests (protecting our content from scraping) |
| Keeping your uploaded hand records and showing their review | Contract |
| Providing custom flop server solves and applying the daily request limit | Contract |
| Confirming rewarded ads and adding the extra daily uses | Contract |
| Showing ads that are not personalised, measuring them and preventing ad fraud | Legitimate interests (keeping the Service free) |
| Showing personalised ads | Consent — asked through the consent tool before personalised ads are shown; you can withdraw it at any time (section 8) |
| Counting anonymous solve requests to fill the postflop solve result store in advance | Legitimate interests (giving everyone faster results without solving the same spot twice) |
| Answering your questions and handling disputes | Legitimate interests (supporting our users and defending our rights) |
| Using error reports to fix mistakes in questions | Legitimate interests (keeping the content accurate) |
| Keeping the Service secure and working | Legitimate interests (security and reliability) |
Where we rely on legitimate interests, you have the right to object (section 6).
3. How long we keep it
- Account, study history, error reports and custom flop solve request records: deleted without delay when you delete your account.
- Range table access records, daily usage records and rewarded ad confirmation records: deleted 35 days after the day they were recorded, or without delay if you delete your account first.
- Uploaded hand records: kept until you delete them (hands, files or everything) or delete your account, and then deleted without delay. Up to 20,000 hands per account.
- Custom flop solve settings and results: kept for 30 days after the solve finishes and then deleted. If anyone asks for the same settings again in that time, the 30 days start again. Results are stored in a public store that can only be found by the identifier of the settings.
- Anonymous solve requests are not linked to an account, so we cannot single out yours when you delete your account. Once a request is reflected in the result store, we keep only its identifier (key) and request count and delete the rest. Requests that are not reflected are deleted one year after collection.
- Information collected by the ad company: we do not keep it. Google keeps and deletes it under its own privacy policy.
- We do not sell anything at the moment, so no records on contracts, payment or withdrawal of orders are created under the Korean Enforcement Decree of the Act on Consumer Protection in Electronic Commerce, Article 6. If such records exist from before, we keep them for the periods in that article (contracts and withdrawals 5 years, payment and supply 5 years, complaints and disputes 3 years).
- Connection logs: we do not keep our own copy. Logs kept by our infrastructure provider (Supabase) are deleted after up to 7 days under its retention settings.
- Information stored on your device stays until you sign out or clear your browser storage. Copies of range table spots are removed when you sign out.
4. Who we share it with
We do not sell your personal information for money. We do not give it to others except the providers below, where the law requires it, or where you have agreed. Ads in the Service are served by Google, which collects information directly as described in the table.
| Provider | What they do | Location |
|---|---|---|
| Supabase, Inc. | Sign-in, database hosting (including uploaded hand records, range table access records, daily usage records and rewarded ad confirmation records) and the solve result store — on our behalf | Republic of Korea (Seoul region) |
| Google LLC | Google sign-in — on our behalf | United States and other countries |
| Google LLC (Google AdMob, Google AdSense) | Serving and measuring ads, personalised ads (if you agree or do not opt out), preventing ad fraud and confirming rewarded ads. Google is an independent controller for this information and may also use it for its own purposes | United States and other countries |
| Apple Inc. | Sign in with Apple (iOS app) — on our behalf | United States and other countries |
| Cloudflare, Inc. | Hosting and delivering this website, and routing emails sent to support@lucidholdem.com — on our behalf | United States and other countries |
| Vercel Inc. | Hosting and delivering this website until it moves to Cloudflare — on our behalf | United States and other countries |
- Learn how Google uses this information in How Google uses information from sites or apps that use our services and the Google Privacy Policy.
- You can refuse personalised ads in the ways listed in section 8. Ads that are not personalised are still shown, and the ad request still sends technical information such as your IP address.
5. International transfers
We are based in Korea, so your information is processed in Korea and, through the providers above, in the United States and other countries.
- For users in the United Kingdom: the UK has recognised the Republic of Korea as providing an adequate level of protection (The Data Protection (Adequacy) (Republic of Korea) Regulations 2022). Transfers to Google, Apple, Cloudflare and Vercel in the United States rely on the safeguards those providers offer under UK law, such as the UK Extension to the EU–US Data Privacy Framework or standard contractual clauses.
- Information is sent over the network when you sign in, when the Service requests ads, and when you visit the website.
- The Service requires an account, so if you object to the transfers needed for sign-in you cannot use the Service. The transfers needed to request ads are also part of providing the Service and cannot be switched off separately. You can refuse personalised ads in the ways listed in section 8 and still use every feature on the same terms.
6. Your rights
Depending on where you live, you can ask us to:
- Access — give you a copy of your personal information
- Correct — fix information that is wrong
- Delete — erase your information (you can also delete your account in the app; see Delete your account for the steps and what we keep)
- Portability — give you your information in a machine-readable format
- Object — stop using your information where we rely on legitimate interests
- Restrict — pause the use of your information while a request is checked
- Withdraw consent — withdraw your consent to personalised ads at any time (section 8)
Email support@lucidholdem.com. We will reply within one month. We will not treat you differently for using your rights.
Complaints in the United Kingdom: you have the right to complain to the Information Commissioner's Office (ICO), the UK data protection regulator, at https:/
7. California and other US state residents
- Sale and sharing: we do not sell personal information for money. When personalised ads are on, Google's collection of advertising IDs, IP addresses and ad interactions through our apps and website may count as "sharing" personal information for cross-context behavioural advertising (and, in some states, as a "sale" or "targeted advertising"). In the last 12 months before this revision we did not show ads; we start doing so when this policy takes effect.
- Your right to opt out: if you live in California or another US state that gives you the right to opt out of the sale or sharing of personal information or targeted advertising, you can opt out using "Privacy settings" (Do Not Sell or Share My Personal Information) in the app or on the website. You can also turn off personalised ads with the device and browser settings in section 8. After you opt out, ads that are not personalised are still shown and every feature, including rewarded ads, works the same.
- You have the right to know, delete and correct your information, and to limit the use of sensitive personal information. We do not collect sensitive personal information as defined by California law. We will not discriminate against you for using these rights.
- Categories we collect for the purposes in section 2, from you, from your device and through the ad company: identifiers (account ID, email address, advertising ID and other device identifiers), internet or other electronic network activity (study history, range table access, ad interactions), approximate location estimated from IP address, and study records. The categories disclosed for cross-context behavioural advertising are identifiers, internet activity and approximate location, disclosed to Google. We do not knowingly sell or share the personal information of consumers under 16.
8. Cookies, device storage and personalised ads
- Sign-in and app storage: we use your browser or app storage (local storage and IndexedDB) to keep you signed in and to keep copies of range table spots you received. Clearing it signs you out. This is strictly necessary and does not need consent. Copies of range table spots are removed when you sign out.
- Ads: to serve ads, Google uses advertising IDs and other device identifiers in the apps and ad cookies on the web. If you allow personalised ads, information such as your ad interactions in the Service may be combined with information from other apps and websites to show ads based on your interests.
- How to refuse personalised ads: you can use every feature and receive the same rewards whichever you choose.
- Consent tool: if you are in the European Economic Area, the United Kingdom or Switzerland, we ask for your consent before personalised ads are shown. If you live in a US state with an opt-out right, you can opt out of the sale or sharing of your information for personalised ads. You can change or withdraw your choice at any time in "Privacy settings" in the app or on the website.
- Android: delete or reset your advertising ID in your device settings ("Privacy → Ads").
- iOS: before the app first requests ads, iOS asks whether you allow tracking. If you do not, neither we nor the ad company can use the advertising identifier (IDFA). You can change this later in your device settings ("Privacy & Security → Tracking"). Your tracking choice has no effect on rewards.
- Web: block or delete cookies in your browser settings, or turn off personalised ads in Google My Ad Center.
9. Children
The Service is not directed at children under 13, and you must be at or above the minimum age set by the law of your country, and at least 14, to create an account. We do not knowingly collect personal information from children under 13. If you believe we have, contact us and we will delete it. Ads are not directed at children, and we request only ads suitable for the Service's age rating.
10. Security
- Row-level access controls in our database mean each user can read and write only their own data. Range tables, daily usage records and rewarded ad confirmation records cannot be read or changed directly by users; only our server functions handle them.
- Rewarded ad confirmations are applied only after we check the ad company's signed server notice.
- Information is encrypted in transit (HTTPS).
- Administrator keys are kept on the server only, never inside the app.
11. Changes to this policy
We will post changes in the Service at least 7 days before they take effect. For significant changes we will also email you.
12. Contact
Lucidwords, Republic of Korea. The person responsible for data protection can be reached at support@lucidholdem.com. Our full business details are at the bottom of this page.
↑ Contents