The fine print, in plain language
Privacy Policy
Effective Date: November 17, 2026
This policy explains how Biographle handles information when you play the daily biography game, sign in, or administer subjects. You can play and submit a biography without creating an account.
Information we use
- Account information. If you choose Google sign-in, we receive an account identifier and may receive your email address, display name, and profile picture URL. Your email address is stored in our authentication system to manage your sign-in, while your user identifier, display name, and profile picture URL are stored in your Biographle profile. Administrator accounts also have a role record.
- Your biography. When you submit an answer, we process the biography you wrote, the current subject, and an official Wikipedia summary to produce scores and the Judge’s verdict. Please do not include sensitive personal information in your answer.
- Gameplay signals. During a round, your browser tracks opened hints, attempted pastes, large text insertions, and whether you leave the tab after starting to write. These signals apply score penalties; they do not include the contents of your clipboard.
- Score history and streaks. When you finish a round, we process the puzzle date, the subject’s name, your final score, the Judge’s accuracy and convincingness scores, how many hints you opened, and whether an outside-assistance penalty applied. If you are signed in, these records are stored with your account. If you play without signing in, this detailed history is stored only in your browser’s local storage on that device. We use these records to show your history and calculate your streak. We do not save the biography text you wrote.
- Guest community scores. When you finish a round without signing in, our server separately stores your final score, the puzzle date, and a random browser-generated identifier so your browser contributes only its first saved score for that puzzle. This record does not include your biography, name, email address, Google account, accuracy and convincingness scores, or hint and penalty details. The identifier is not linked to your account, but it does distinguish that browser from others. We combine these records with signed-in scores to calculate the rounded Today’s average; players see only the combined average, not individual guest records.
- Guest score syncing. When you later sign in, guest results saved in that browser are sent to your account and matched by puzzle date. If your account already has a result for a date, the account result is kept and the guest copy does not replace or duplicate it. After a successful sync, the guest copies and random identifier are removed from the browser, and the matching guest community score records are removed from the server so the rounds are not counted twice.
- Preferences and session data. Your browser stores your light or dark theme choice, whether you have already seen the introductory “How to play” guide, guest score history and random guest identifier when you play without signing in, and, if you sign in, authentication session information.
- Subject curation. Administrator submissions may include names, Wikipedia links, public biographical details, emoji clues, and portrait attribution.
How we use information
We use information to operate and score the game, calculate community averages, authenticate accounts, restrict administration to approved users, prevent disruption, remember preferences, and understand and improve site performance. We do not sell your personal information or use it for targeted advertising.
Biographle’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Services that process information
- Lovable Cloud and hosting. Lovable provides our hosting, account system, database, and portrait storage. Account, role, subject, stored portrait information, signed-in score history, guest community score records, and guest results synced after sign-in are processed there. Lovable’s privacy policy explains its practices.
- Google sign-in. Google authenticates you and shares the account details described above. Google also receives information needed to process the sign-in. Google’s privacy policy applies to its services.
- Google Gemini. Your submitted biography, the subject’s public details, and the Wikipedia summary are sent to Google’s Gemini service for AI grading. Google returns accuracy and convincingness scores, a short verdict, and the fact-check breakdown shown under “See why?” — the biographical claims judged accurate and the claims flagged as inaccurate or unverified, each with a short explanation. Your biography text is not retained by us after grading.
- Wikipedia and Wikimedia. Our servers request public summaries, biographical facts, and portraits from Wikipedia, Wikidata, and Wikimedia Commons. If you follow a link to one of those sites, their own policies apply.
Visitor analytics
Lovable’s published-site analytics uses no cookies, stores nothing on your device, does not keep IP addresses, and does not identify visitors. Lovable collects this data for us. Lovable’s privacy policy explains how it handles it.
Button and link clicks are recorded for every visitor to the published site. Page visits, time on page, page speed, and errors are also recorded for every visitor, without cookies and without identifying anyone. The data includes pages visited, where visitors came from, their country, browser, operating system, and device type.
There is currently no analytics consent banner on Biographle. Detailed analytics data is kept for 90 days and daily summaries for one year. Activity in the editing preview is not counted.
Cookies and browser storage
Biographle does not use its own advertising cookies. Your theme preference, whether you have already seen the introductory “How to play” guide, and sign-in session are stored in your browser’s local storage so they remain available between visits. When you play without signing in, your detailed score history and random guest identifier are also stored in local storage on that device; the detailed history is not stored in your account unless you later sign in and sync it. You can remove locally stored information through your browser settings. Clearing guest history removes unsynced local scores and the identifier, clearing the guide preference makes the “How to play” guide appear again on your next visit, and clearing sign-in storage will sign you out. Clearing browser storage does not remove a guest community score already submitted to the server.
Google sign-in and external sites you choose to visit may use their own cookies or storage under their own policies. Lovable’s visitor analytics does not use cookies or store anything on your device.
Data retention
We do not save the biographies players write. For signed-in players, we keep the score history described above for as long as the account is active so streaks and history remain available; individual paste or tab-switch events are not stored, only whether a penalty applied. Detailed guest score history remains only in the browser until you clear it or sign in and successfully sync it. After syncing, the account retention period applies, the synced guest copies and random identifier are removed from the browser, and matching guest community score records are removed from the server. Unsynced guest community score records are retained as game statistics. Limited technical or error logs may still contain request details needed to operate and secure the service.
We keep account and profile information while your account remains active and administrator content while it is needed to run the game. Authentication sessions expire or can be ended by signing out. Browser preferences and unsynced guest score history remain until you clear them. Analytics retention is described above.
When you use the account panel to delete your account, your active authentication record, profile, roles, and score history are permanently removed. Unsynced guest community score records are not linked to your account and are not affected by account deletion. Curated subjects are retained because they are game content rather than your account record. Provider backups and limited operational or security logs may retain information for a limited period under their own retention schedules.
Your choices and requests
- You can play without signing in and can sign out at any time.
- You can choose a theme or clear locally stored preferences, unsynced guest score history, and session data through your browser.
- Signed-in users can open the account icon in the header to download a JSON copy of their stored account, profile, role, and score history information.
- You can permanently delete your own account from the same panel after typing DELETE to confirm. This signs you out and removes your account, profile, roles, and score history. To keep administration available, the only remaining administrator must add another administrator before deleting their account.
- You may also contact us to request access to, correction of, or deletion of your Biographle account information, subject to applicable law and records we must retain.
- Your browser or device may also offer privacy controls. Rights vary by location, so you may wish to seek advice about the rules where you live.
Security, children, and changes
We use access controls and other reasonable safeguards, but no online service can guarantee absolute security. Our providers may process information in countries other than yours.
Biographle is not directed to children under 13, and we do not knowingly collect their personal information. Parents or guardians who believe a child has provided information can contact us to request deletion.
We may update this policy as the game or its providers change. We will post the revised version here and update the effective date.
Contact us
The fastest way to download or delete your information is through the signed-in account panel. For privacy questions or help with account access, correction, or deletion, email [email protected]. To help protect your account, we may need to verify that a request relates to you.