Privacy Policy

This Privacy Policy explains how the Quartenson website handles information when you browse our pages, follow external links, or contact us. It applies to the website only and does not apply to Quartenson mobile apps.

For questions about this website policy, contact quartenson.support@gmail.com.

1. Website Usage and Infrastructure

When you visit this website, your browser may automatically provide standard technical information such as your IP address, browser type, device information, referring page, and requested pages. This information may appear in hosting or delivery logs used to keep the site available and secure.

Quartenson uses hosting, database, delivery, security, monitoring, and infrastructure service providers to operate the website and the private API used by selected website features. These providers may process standard network metadata, such as IP addresses and request information, as needed to deliver pages, protect the service, monitor reliability, prevent abuse, and troubleshoot operational issues. We do not list exact infrastructure provider names in this policy, but we describe the categories of providers and the purposes for which they are used.

2. Analytics and Consent

The Quartenson website uses Google/Firebase Analytics to understand how visitors use the site in aggregate, such as which pages are viewed, approximate session activity, device categories, browser information, and general engagement patterns. This information helps us improve content, navigation, and product discovery across the website. The website may also use Google Ads measurement for conversion measurement and ad attribution when the relevant consent is granted.

Depending on the page and interaction, this can include page visits, article views, article engagement or read progress signals, navigation clicks, theme toggle interactions, card and button clicks, cookie notice acceptance, and clicks that open important destinations such as feedback forms or beta signup forms. Visits from shared Daily Challenge links may also record the broad device category and whether the visitor was directed to the app landing page or Google Play. The shared link does not send the player's result or training history to the website.

The website uses Google Consent Mode v2 in a consent-denied default state. Before you make a choice, Google tags may load in consent-denied mode and send limited cookieless signals designed to respect your consent choices. Analytics and advertising cookies are not set before consent.

Full Google/Firebase Analytics events are used only after you grant Analytics consent. Advertising storage and user data for ads are used only after you grant Ads measurement consent. Quartenson does not currently use personalized advertising or remarketing on this website, so personalized-ad consent remains denied unless that feature is explicitly introduced later.

You can accept all optional measurement, reject all optional measurement, customize categories, and later change or withdraw your choices from the Cookie settings link in the website footer.

Quartenson may also send a first-party anonymous request to its own API when consent preferences are saved. Consent preference requests store only a server-created timestamp and are skipped when the quartenson-analytics-disabled cookie is present.

We use consented interaction data in aggregated form to understand which pages are useful, which calls to action are being used, and how visitors move through the site. We do not use website analytics to read the contents of forms you submit on third-party sites or to build advertising profiles for personalized ads.

3. Anonymous Browser Tool Benchmarks

Some free browser tools can submit anonymized completion metrics after a finished session so the website can show community result benchmarks. These benchmark records are separate from Google/Firebase Analytics, Google Ads measurement, and local browser history.

Benchmark submissions are sent through a same-origin website route to the private Quartenson API. The browser request is made without cookies, credentials, referrer data, local history, local activity data, or local personal-best records. The website proxy also sanitizes each request before forwarding it to the API, so unsupported fields are dropped even if they are added manually.

The benchmark payload is limited to the tool name, schema version, allowed setup fields, and allowed result metrics. Depending on the tool, setup fields may include table size, mode, difficulty, sample size, or measurement count. Result metrics may include completion time, median response time, reaction-time statistics, accuracy, mistakes, clean trials, clean streaks, best level, longest sequence, total numbers, or round counts.

The benchmark payload and application database record do not include names, emails, accounts, payment data, cookie identifiers, advertising identifiers, browser fingerprints, local storage keys, local session IDs, locale, user agent strings, referrers, client timestamps, form contents, IP addresses, or full local history. Hosting and infrastructure providers may still process standard network metadata in service logs as described in the Website Usage and Infrastructure section.

The API validates benchmark submissions and ignores unsupported, malformed, or out-of-range results without showing an error to the visitor. Accepted records are used to build aggregated benchmark distributions for matching tool settings. The public benchmark view shows aggregated comparison data, not individual visitor records, public profiles, or leaderboards.

Raw anonymous completion rows may be kept as long as they are useful for calculating and refreshing benchmark distributions. Aggregated benchmark statistics may be stored separately for performance. Because benchmark rows are not linked to an account or identifier, we cannot look up, export, or delete a specific visitor's benchmark row.

4. Contact and Feedback

This website may provide a first-party feedback form, including from the website footer or specific tool pages. If you submit it, we store the feedback text you enter, a short internal source label for where the form was opened, and, only if you provide it, your email address. This is used to review what felt useful, confusing, or unnecessary.

The website may also link to email contact methods, beta signup forms, or feedback forms hosted by third parties. If you contact us or submit information through those external services, we receive the information you choose to share with us. Please review third-party policies before submitting personal information outside Quartenson pages.

5. External Links

This website links to third-party services such as app stores, hosted forms, and other external resources. We are not responsible for the privacy practices or content of third-party websites. Please review their policies before submitting personal information.

6. Cookies and Local Storage

This website uses first-party cookies for a limited set of website functions. These include remembering your selected theme, remembering your consent preferences, and keeping optional measurement aligned with your selected choices.

The quartenson-consent-v2 cookie remembers your current consent choices. Older visits may still have a quartenson-cookie-notice cookie from the previous notice. The quartenson-analytics-disabled cookie, if you set it, disables website analytics requests including the anonymous first-party consent-preference checks. Anonymized benchmark completion metrics are separate from analytics cookies and are designed not to identify a visitor.

Google/Firebase Analytics cookies such as _ga and _ga_<measurement-id> may be set only after Analytics consent. Google Ads measurement cookies such as _gcl_au may be set only after Ads measurement consent. Exact names may vary as Google updates its measurement systems.

Before consent is granted for those categories, the site is designed to keep analytics and advertising storage denied and to avoid setting analytics or advertising cookies.

Some browser tools may use local storage to keep lightweight history on your device. The Schulte table tool can store the last 20 completed sessions per table size and mode, plus personal bests for those combinations. The Visual Search tool can store the last 20 completed sessions per mode and difficulty, plus personal bests for those combinations. The Visual Memory tool can store the last 20 completed sessions per mode and difficulty, plus best levels for those combinations. The Reaction Time tool can store the last 20 completed sessions per sample size, plus personal bests for those sample sizes. The Peripheral Awareness tool can store the last 20 completed sessions per difficulty and measurement count, plus best consistency records for those combinations. This local history is not an account, is not synced to cloud storage, and is not sent to Quartenson analytics, the Quartenson API, Google/Firebase Analytics, or Google Ads. You can clear it from each tool's History modal or by clearing site data in your browser.

Browser tools may also use local storage to remember tool settings such as table size, mode, difficulty, sample size, measurement count, number size, and display preferences. These settings are stored only for your comfort on the same device and are not sent to Quartenson analytics, the Quartenson API, Google/Firebase Analytics, or Google Ads.

Browser tools may also use quartenson-tool-activity-v1 local storage to show a lightweight daily practice summary across the free tools. This stores completion counts by tool and day, first and last completion times for that local day, and whether a local best improved. It does not store full result history, does not create an account or device identifier, is not synced to cloud storage, and is not sent to Quartenson analytics, the Quartenson API, Google/Firebase Analytics, or Google Ads. You can clear it by clearing site data in your browser.

If Quartenson adds website accounts or progress sync in the future, we may offer an optional way to import selected local browser history or activity into an account. That import would happen only if you explicitly choose it and consent to linking the selected local data to your account. Without that choice, local browser history and daily activity remain on your device only.

7. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date on this page.

8. Contact

Questions about this website privacy policy can be sent to quartenson.support@gmail.com.