Privacy policy

Scope and controller

This policy covers the one-device version of Quasi at https://thequasi.app. The operator identified below is responsible for the personal data described here. The game has no account system or advertising integration.

If you email us, we receive your email address and message so that we can answer your request. Do not include sensitive information that is unnecessary for your enquiry.

Your game on your device

Player names, settings, recovery saves, completion statistics and question history stay in your browser for local play. These local records are not uploaded; selected settings and game-use measurements are described below. App resources and page content are also downloaded for offline play. The cookies page lists each storage item, its purpose, retention and clearing limits.

Anyone with access to the same browser may see locally saved information. Avoid sensitive information in player names. Browser site-data controls can remove preferences, saved games, statistics and downloaded content.

Analytics and measurements without cookies

We use Google Analytics to understand how the game is used and where it fails. On the production site the Google tag loads after interaction or idle time. Preview deployments do not use the live stream. Analytics and advertising storage start denied.

Accepting analytics permits Google Analytics cookies and browser/session identifiers. Rejecting or leaving the choice undecided denies those cookies, but online measurements without cookies can still be sent through Google Consent Mode. Rejecting cookies does not stop all analytics requests. Google receives network information, including your IP address and browser information, when a request reaches its service.

The app sends limited page categories, language and game-use measurements, such as counts, timings and outcomes. It strips query strings, fragments and room codes from reported page locations, uses fixed page titles and sends error categories instead of error messages or stacks. Player names, roster IDs, prompts, answers, guesses, emails and arbitrary text are excluded. Campaign labels and referrer origins are limited to an allowlist. Google may derive general location and device information from its requests.

Purposes and legal grounds

Local game storage is used to provide the game you request. We rely on providing that service for necessary game processing, and on our legitimate interests in security, reliability and answering enquiries for related technical records and correspondence. We retain correspondence only as needed to handle the request, resolve a dispute or meet a legal obligation.

Your consent is the basis for optional analytics cookies and the associated identifiable analytics. Limited measurements sent without analytics cookies are used for our legitimate interest in understanding use and maintaining the game. They are not treated as consented cookie analytics. You may object to processing based on legitimate interests by contacting us. Whether a request uses cookies does not by itself determine whether data-protection rules apply.

Your controls

Open Cookie settings in the footer or the lobby to accept analytics, reject it or save a selection. Rejecting after acceptance denies future analytics cookie storage, removes accessible analytics cookies, attempts to clear queued events and prevents events collected under the withdrawn choice from being replayed under a later choice. It cannot recall information already sent. Essential local storage supports the game and your privacy choice.

Advertising storage, advertising user data and advertising personalisation remain denied for every choice. Global Privacy Control is respected through this no-advertising setting; it does not automatically override an explicit analytics choice. Cookie settings are hidden during a full-screen game and available again when you leave it.

Recipients, transfers and retention

Google receives analytics requests. Vercel provides website hosting and processes request information, such as IP addresses, requested URLs, browser information and timestamps, to deliver and protect the service. Our email provider processes correspondence sent to the contact address. There is no advertising provider integrated into the game, and the app does not integrate Vercel Analytics or Speed Insights.

Google and Vercel may process data outside the European Economic Area, including in the United States. Their published data-processing and transfer terms describe safeguards such as standard contractual clauses and, where applicable, adequacy frameworks. These terms and provider privacy notices explain their own processing: https://policies.google.com/technologies/partner-sites, https://policies.google.com/privacy/frameworks and https://vercel.com/legal/dpa. Contact us for information about the arrangements applicable to your request.

The local offline analytics queue expires events after 24 hours and holds at most 500 events. Google Analytics is configured for 2 months of event data and 14 months of user data, with user retention reset on new activity. Those controls do not set retention for standard aggregated reports. Hosting providers retain operational records according to their service, security and legal needs; log availability varies with the hosting plan. Provider operational retention is separate from the analytics and local-storage periods described here.

Your rights and changes

Where the GDPR applies, you may request access, correction, deletion, restriction and, where applicable, portability of personal data. You may object to processing based on legitimate interests and withdraw consent at any time without affecting earlier processing based on consent. Contact the operator below. You may also complain to the Spanish Data Protection Agency at https://www.aepd.es or your competent supervisory authority.

We do not make automated decisions with legal or similarly significant effects about you. Local gameplay does not require optional analytics cookies. We will update this policy when our data practices change and request a new choice when required. Clearing browser data does not itself request deletion of data already received by a provider.