Privacy Policy
Last updated: October 4, 2026
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 support@quartenson.com.
Website Accounts
Creating an account is optional. We store your email address and unique nickname in readable form. The nickname is not encrypted. We store a salted password hash rather than your password and record when you accept the Terms of Use and the version accepted. Account information is used to provide your account and is not sent to website analytics.
Essential HttpOnly authentication cookies keep you signed in: an access token lasts up to 15 minutes and a refresh session lasts up to 30 days from login. Refresh tokens rotate when used and are stored as hashes on the server. Logging out revokes the current session. These functional cookies are separate from optional analytics consent. While signed in, supported completed-session summaries are saved to your account. Guest sessions remain in this browser until imported or cleared. You can review and import local summaries from your account page or a tool page. The account stores dates, selected settings, numeric results, and for reading practice only the passage identifier and version. It does not store passage text, answers, prompts, or other practice material.
After the server confirms each imported record was added or was already present, that record is removed from this browser. The first reviewed import enables automatic importing of future guest summaries for this account and browser. Earlier imported history also enables automatic import when the profile loads in a browser with no saved choice. A previously saved manual-only choice remains in effect, and a different account requires review. If a signed-in save cannot reach the server, its summary may be kept temporarily in this browser's IndexedDB retry queue. Each queued item is tied to the account that created it, is retried only for that account, and is removed after server acknowledgement. If the queue cannot store a failed save, the local history record remains for later review or import.
We verify account email addresses and use email for address confirmation and password recovery. Verification links expire after 24 hours, and password reset links expire after one hour. Each link contains a random single-use token; the website stores its hash rather than the token. Email requests for a known account are queued with the recipient and message content encrypted using a backend-only key, then sent through the Google Gmail API. Queued messages are retried for temporary delivery failures and their encrypted payload is removed after delivery, permanent failure, or expiry. Authentication email requests are limited to five per account per rolling hour. Public requests use the same confirmation response for known and unknown addresses. Emails are sent from a dedicated Quartenson address and replies go to support@quartenson.com.
A one-year quartenson-locale cookie remembers the language selected in the language menu or used on a Ukrainian or German route. When you later open the website home page, it uses this preference if it is valid. You can change it from the language menu. An unset or unsupported value uses English. This cookie stores only the language code.
The account profile may show experience points (XP) and a level. XP is awarded only for new account completions that pass server validation. Guest sessions, imported local history, duplicate submissions, and completions saved before XP was introduced do not earn XP. Validation uses a short-lived account, tool, and settings session, completion counters, and server-measured elapsed time. We use aggregate validated duration samples grouped by tool and selected settings to calibrate XP. These calibration samples omit account and completion identifiers and do not include custom practice content. The website stores the award, policy version, completion reference, and daily bonus in an account XP ledger so retries do not award the same completion twice. XP is a profile statistic and does not unlock features or provide other benefits.
Website account deletion is not currently available in profile settings. To request deletion of your Quartenson website account, email support@quartenson.com. We will verify that you control the account and respond within the timeframe required by applicable law. We will delete the account and its associated website records from active systems, including account history, XP records, credentials, and sessions. We may retain limited information when required by law or when needed to establish, exercise, or defend legal claims; any such information will be restricted to that purpose and deleted when no longer needed. Account deletion does not clear guest history, settings, or unsent account-bound records stored in browser storage on your devices. Clear Quartenson site data in each browser where you want to remove those local records. You can also contact us at this address to request access to your account information.
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. Browser Tool Completions and Benchmarks
Some free browser tools can submit 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. When you are signed in, your session cookie authenticates the request and new supported session summaries include your account ID. Guest records remain unlinked to an account, and older records are not reassigned when you sign in. These individual completion requests exclude local history, local activity data, and 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.
Benchmark payloads do not include names, emails, payment data, authentication tokens, advertising identifiers, browser fingerprints, local storage keys, local session IDs, locale, user agent strings, referrers, client timestamps, form contents, IP addresses, or full local histories.
Separately, an account holder may import supported local history after review. The import stores allowlisted dates, settings, numeric summaries, and for reading practice the passage identifier and version, with a one-way source hash. It excludes passage text, answers, prompts, and practice content. A submission UUID may be included only to prevent a duplicate in the same account. Confirmed imports are removed from this browser. After a reviewed import, automatic import can send later guest summaries from this browser to the same account. Earlier imported history also enables this behavior when the profile loads in a browser with no saved choice. The choice is stored in this browser; another account requires manual review. Imported history is not included in community benchmarks. 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 guest benchmark rows are not linked to an account, 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 and Embedded Media
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.
Some articles include lazy-loaded YouTube players using YouTube's privacy-enhanced embed domain. When an embedded player approaches the visible part of the page or you use its controls, your browser connects directly to YouTube or Google. That request may include standard network data such as your IP address, browser or device information, the requested player, and the Quartenson site origin as the referrer. YouTube may process playback interactions and use cookies or similar storage under its own policies. These embedded-player requests are separate from Quartenson's optional analytics and ads measurement controls.
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-locale cookie stores your selected site language for up to one year. It is used only to choose the language of the home page and does not track activity. 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 30 completed sessions per table size and mode, plus personal bests for those combinations. The Visual Search tool can store the last 30 completed sessions per mode and difficulty, plus personal bests for those combinations. The Visual Memory tool can store the last 30 completed sessions per mode and difficulty, plus best levels for those combinations. The Reaction Time tool can store the last 30 completed sessions per sample size, plus personal bests for those sample sizes. The Peripheral Awareness tool can store the last 30 completed sessions per difficulty and measurement count, plus best consistency records for those combinations. The Story Chain Memory Trainer can store the last 30 completed sessions, including the list source and length, recall scores, attempts, duration, and whether the word bank was used. The words in generated or custom lists and optional private story notes are not saved in Story Chain history. The Peg System Memory Trainer can store the last 30 aggregate session summaries, including list source and length, unaided recall, hints, attempts, recovery, and duration. It does not store targets, answers, associations, private notes, or prompt order. The Chunking Memory Trainer can store the last 30 aggregate session summaries, including material type, list length, exact-position recall, complete chunks, recovery, attempts, and duration. It does not store source items, answers, private chunk cues, group labels, or item order. The Keyword Method Memory Trainer can store the last 30 aggregate session summaries, including source, pair count, first and best mastered-pair counts, forward and reverse recall, recovered pairs, keyword-hint use, attempts, and duration. It does not store target terms, keywords, meanings, interaction notes, pronunciation data, answers, pair IDs, or prompt order. Guest history stays in this browser by default. When you are signed in, supported completed summaries are saved to your account. You can review and import existing guest history from the account or tool page. After each record is confirmed as added or already present, that local record is removed. A reviewed import opts this browser into future automatic imports for the same account unless you turn the option off. Reading summaries include only passage identifiers and versions, never passage text. Answers, prompts, private notes, and other practice material are excluded. You can clear local history 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, list or pair count, material source, 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 create an account or device identifier and is not sent to analytics or ads services. Daily activity is not part of the account import at this time. You can clear it by clearing site data in your browser.
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 support@quartenson.com.
