← MenuEN

THE FINE PRINT

Privacy Policy

Last updated: October 26, 2026

Welcome to Factually... — a trivia and deduction game about strange truths, misleading half-truths, and convincing falsehoods.

1. The short version

  • No accounts: You can play without registering or signing in.
  • No browser identifier: Factually... does not intentionally assign a persistent player ID to identify your browser across visits.
  • Local storage: Some game information may be saved in your browser so your game can work as intended.
  • Shared game records: When you submit a completed game, we store claim-level results in Supabase to calculate scores and shared statistics.
  • Public statistics: Daily Community Stats displays aggregated insights, not a public list of individual players and their answers.
  • Cloudflare Web Analytics: We use Cloudflare Web Analytics to measure aggregate traffic and page performance. It does not use cookies or create a persistent identifier.
  • Advertising: Google AdSense is planned, but it is not currently active. This policy will be updated if our advertising practices change.

2. Information stored in your browser

Factually... may use your browser's local storage to keep information needed for the game experience, such as local game progress or results.

This information is stored on your device rather than being automatically sent to our database just because it exists in your browser. Information may be transmitted when you submit a game or when a feature otherwise requires a server request.

We do not intentionally use local storage to create a persistent browser identifier.

You can generally clear local storage through your browser's site-data settings. Doing so may remove locally saved progress or other game information.

3. Information stored on our server

Factually... uses Supabase to store shared game information and calculate Daily Community Stats.

When a completed game is submitted, the records may include:

  • The daily challenge identifier or date.
  • The claims presented and the categories selected for those claims.
  • Claim-level outcomes, including whether each classification was correct.
  • The resulting game score.
  • Which wildcards were used and how they affected the game.
  • A submission timestamp.
  • Validation or technical information needed to process the submission and protect the integrity of the game.

This is claim-level data, rather than only a single aggregate score. We need individual claim outcomes to calculate which claims were hardest, which were easiest, and which categories were most frequently misunderstood.

Factually... does not require a name, email address, or account to submit a game. We do not intentionally attach submissions to a persistent browser identifier.

However, the absence of an account or browser identifier does not necessarily make a record completely anonymous. Depending on the technical information processed by our hosting or database providers, some information may still be associated with a request or submission.

We use stored game records to calculate scores and statistics, maintain the integrity of the daily challenge, and operate and improve the game.

4. Daily Community Stats

Factually... includes Daily Community Stats, which summarizes how people are doing on the current daily challenge.

The feature may display:

  • Today's Toughest Claim — the claim with the lowest observed classification accuracy when actual results are available.
  • Easiest Pick — the claim with the highest observed classification accuracy.
  • Biggest Brain Trap — a claim that most often leads to an incorrect classification.
  • Most Misunderstood Category — the category with the lowest observed classification accuracy.
  • Wildcard Dependency — an indication of how much players rely on wildcards.
  • Perfect Game Potential — an estimate of perfect-game likelihood or, when actual results are available, the observed frequency of perfect scores.

The game uses two modes for these statistics:

Before 100 valid completed submissions: Statistics are based on estimates from the game's claim metadata and scoring model. These are predictions, not measurements of actual player performance.

At 100 or more valid completed submissions: The feature switches to statistics calculated from actual valid submissions for that daily challenge.

The switch is immediate once the threshold is reached. The page will identify whether a statistic is estimated or based on actual results.

The public display presents aggregated insights rather than publishing individual submissions or a list of each person's answers. We use the underlying claim-level records to calculate these summaries.

Because Factually... does not require accounts or use a persistent browser identifier, a completed submission should not automatically be interpreted as one unique person. We cannot guarantee that every submission represents a different individual.

5. Hosting and service providers

Factually... relies on third-party services to operate.

Cloudflare

The live website is hosted through Cloudflare. When you visit the site, Cloudflare may process technical information associated with delivering website content, maintaining security, and handling requests. The exact information processed depends on the Cloudflare services and configuration used by the live site.

We also use Cloudflare Web Analytics. It processes technical information about page visits, such as pages viewed, referrer, browser, country and page-load performance, to produce aggregate statistics. It does not use cookies or create a persistent identifier.

Cloudflare's privacy information is available at Cloudflare Privacy Policy.

Supabase

Supabase provides the database used for shared game records and Daily Community Stats. Information submitted through the game is processed and stored according to the database configuration and the services enabled for the project.

Read more in the Supabase Privacy Policy.

GitHub

Our source code is maintained in GitHub. GitHub is not the live website host. We do not list it as a provider of live visitor data merely because the game's source code is stored there.

If the deployment process or any future feature begins sending visitor information to GitHub, this policy should be reviewed and updated accordingly.

Third-party providers may process information under their own privacy policies and applicable contractual terms.

6. Cookies and similar technologies

Factually... uses Cloudflare Web Analytics, which does not use cookies, to measure aggregate traffic and page performance. The site may use browser storage and technical mechanisms necessary to run the game.

Our planned Google AdSense integration is not currently active. If advertising is introduced, Google and its partners may use cookies or similar technologies to serve and measure ads, subject to the advertising configuration and applicable requirements.

Before enabling advertising, we will update this policy to explain the relevant advertising technologies, data practices, and available choices. Where required, we will also implement appropriate consent mechanisms.

For information about Google's advertising practices, see How Google uses information from sites or apps that use its services and Google's advertising settings.

7. How long we keep information

We retain shared game records for as long as they are needed to operate the daily challenge, calculate statistics, maintain historical results, and protect the integrity of the game, subject to applicable legal requirements.

Historical daily challenges and aggregated statistics may be retained longer so that the archive and historical community insights continue to work. Whether historical records contain claim-level data or only aggregates will depend on the retention and archival design.

8. Your choices and privacy requests

You can clear locally stored game data through your browser settings. This does not automatically delete records that have already been submitted to Supabase.

For questions about personal information, or to request review or deletion of information that may relate to you, email [email protected]. Please do not send passwords or other sensitive information.

Because Factually... does not use accounts or a persistent browser identifier, we may not be able to identify a particular submission from a person's name alone. We may need enough information to locate the relevant record and verify a request without collecting unnecessary additional information.

We will handle requests in accordance with applicable law. Some records may need to be retained where there is a valid operational or legal reason, or where a record cannot reasonably be linked to the person making the request.

9. International visitors

Factually... may be accessed from different countries. Depending on where you live, privacy laws may provide rights concerning access, correction, deletion, objection, or other processing of personal information.

The services used to operate the game may process information in locations outside your country. The applicable safeguards and arrangements depend on the providers and the services configured.

For privacy questions or requests, contact [email protected].

10. Children's privacy

Factually... is intended for a general audience and is not specifically designed to collect personal information from children under 13. The game does not require account registration.

If we learn that we have collected personal information from a child in circumstances where the law requires parental consent or deletion, we will take appropriate steps.

11. Changes to this policy

We may update this Privacy Policy when the game, its technology, or its data practices change. Examples include activating Google AdSense, adding accounts, introducing analytics, changing hosting or database services, or changing how long submissions are retained.

We will update the "Last updated" date when a revised policy is published. Material changes should be reflected in the policy before or when the relevant feature is introduced, as appropriate.

12. Contact

If you have questions about this policy or your data, contact us at [email protected].