Last updated
QuickenBrain is made by Studio AM. You can browse without an account. We do not run ad-blocker detection.
Appearance and language. Choosing the dark or system theme saves that choice in the qb_theme cookie on this device for one year. Choosing the light theme removes the cookie. Larger text and Show the clock are kept the same way: turning on Larger text saves the qb_text cookie and turning off Show the clock saves qb_clock, each for one year, and going back to the default removes it. These cookies contain no identifier and are not used for advertising. If you save a preferred language in your account, we keep that choice with the account and a browser copy in qb:membership:v1:account, so it is available on your signed-in devices. You can change or remove it in Account; deleting the account also removes the preference stored on the server.
Your practice data
Mental rotation uses your browser’s local storage to remember your chosen level, up to 50 recent results with their level, accuracy and date, and daily attempt counts used to vary the questions. These records remain until you or your browser clear them; newer results replace older ones in the 50-result history.
Unfinished memory, math and word-search sessions stay in the current tab. Reloading or closing the page clears them. For these practices, individual answers and unfinished progress are not sent to our server, except for a round you have timed on Today's practice, whose answers go to our server to be checked. The weekly aptitude test is described below. When private usage logging is on, a start or error event may be sent even when you do not finish a round.
For the weekly aptitude test, we save your drafts, submitted answers, print confirmation and email request with your signed-in account on our server. These records remain until you delete your account. This browser also keeps an account-specific copy of draft answers and page settings; local copies may remain until you clear this site's browser data. Clearing browser data does not delete server records.
If you explicitly request the answer email for an edition, we temporarily keep an encrypted copy of your account's email address to send it through Resend. We clear that encrypted address after successful sending, cancellation or a final delivery failure. Request and delivery records remain until account deletion. This request does not subscribe you to a mailing list.
Progress saves summaries of fully completed practices in this browser: practice name, date, settings, accuracy, active time and answered-question or pattern counts. Memory summaries include found and extra tiles; math summaries note whether the scratchpad was used. Locale-sensitive practices also record their content version and language so unlike tasks are kept in separate comparisons. A completed reasoning practice records a short round reference that can reproduce the six questions you received; it does not contain your selections. Individual answers and drawings are not saved in this history. The latest 100 practice and lesson activity records are kept; newer records replace older ones. The rock pile keeps a list of the dates on which you finished a practice round in this browser, so older days stay in the pile after their rounds are replaced. If you are signed in, your account also keeps a copy of this history and of your rock pile, as described under Membership and your account. The training log keeps, for each level of a practice you have played, the date of its first round, how many rounds you played at it, the date you cleared it, and your best score and best tempo there, so they stay after their rounds are replaced. For a signed-in account, these kept level records also travel with the account; otherwise they stay in this browser. When you solve a grid or line puzzle, such as Nonograms or Kakuro, this browser keeps which puzzle it was and when you solved it, so that day counts toward “Days practiced this week”; this record is not synced to your other devices. Clear saved activity removes them with the history.
Saved test results. When you finish a subject or all-round test while signed in, we save its questions, your answers, scores, timings and explanations with your account so you can review them in Progress. These results are retained until your account is deleted. Clearing browser data or “Clear saved activity” does not delete these separate test records. Signing out removes access on that device until you sign in again.
The review notebook is separate from that history. When you get a question wrong in a supported language of a practice that can appear in Today’s set, this browser saves where to find that question again. It stores the practice, its language, level and content version, the round’s seed or the server’s reference to the round, and the question’s place in the round. It also stores the date you missed it, the date it is next due and its step in the 1, 3 and 7 day schedule. For reading skills it adds the passage and question ids. For word parts it adds the word and the kind of question. It does not store the question text or the answer you chose. It does record which questions you got wrong. It keeps up to 300 questions. The notebook itself is not uploaded, except that a signed-in account keeps a copy (see Membership and your account). Reviewing a reading skills or word parts question sends that round’s reference to our server, as described under Hosting. Clear saved activity in Account removes the notebook.
For generated practice tests, your account keeps up to 300 references to missed questions and their review schedules. Each reference points to the original saved test, preserving its question language. When you answer in the notebook, the server checks your answer and stores the latest review answer, review date and schedule. Active membership is needed to review these test questions. Clear saved activity removes these review entries when your account syncs, but keeps the original test records. Deleting your account removes both.
Favorites, recently opened activities, lesson steps, selected lesson answers, and whether you started a guide or a grammar rule or read it to its end also stay in local browser storage. Lesson completion markers remain separately so that reading a lesson again or replacing older activity records does not erase completion. None of this is uploaded or shared across devices, except that a signed-in account keeps a copy (see Membership and your account).
Days visited saves the local calendar dates when you view the site, starting when this feature becomes available. It does not reconstruct earlier visits, identify you or send visit dates to us. These dates stay in this browser until you clear saved activity or site data, separately from the 100-record activity limit. This Privacy page does not load our visit counter. Cloudflare's separate analytics and security features are described below.
The optional Pencil stores notes and drawings only in this browser. They are never uploaded. Lesson drawings are kept separately for each authored step; typed notes stay with their activity. On scored practices, Pencil is available before and after the round. You can clear these drafts in Account or by clearing this site's browser data. If browser storage is blocked or full, changes stay in the open tab.
Deep reading keeps your reflections only in this browser, under qb:deep-reading:v1. They are never uploaded; your saved history records only which passage you finished and how long you spent. You can delete one with Delete this reflection on its passage, or all of them with Clear saved activity in Account.
The optional math scratchpad keeps drawing strokes in the tab’s memory. Closing the scratchpad keeps your notes for the current question. Moving to a new question, ending the practice, reloading or closing the page clears the notes. Drawing marks the current session as “With scratchpad” so its results are compared separately. The drawing itself is never sent.
Guest profiles and community comparisons
Every completed round is also counted anonymously, whether or not you share results. Each count records the practice, its settings, the score, the number of answers, the time taken, whether hints or shown answers were used, and when the round was completed. Nothing that identifies a person, an account or a device is stored with it: no guest identifier, no network address and no account. These counts power the statistics pages. A round’s result does not show a percentile, so the page does not ask our server where the round falls among these counts. Each count is kept for 400 days. Because it is not linked to you, it cannot be looked up or removed on request. Detailed summaries for community comparisons follow the separate sharing setting described below.
A random guest identifier is created when you choose to save a nickname or when a future result is shared while community sharing is on. Opening Progress or Statistics does not create one. The identifier and optional nickname are kept in local storage, without signup or fingerprinting. Your nickname stays in this browser and is not sent with practice results. A guest profile is not an account, a verified person or a way to restore data on another device.
Community sharing is on by default when this browser has no saved preference. Saved choices, including opt-outs, are kept; invalid or unreadable preferences remain off. You can turn it off in Data sharing in Account without losing local history. The default and switching sharing on cover future rounds only, never earlier history. Choosing “Compare my result” also sends the round you have just finished and continues sharing later rounds until you turn it off. Only an explicit choice saves your choice, its date and the notice version in this browser; a default is not recorded as consent. The community switch does not change private usage logging or enable advertising.
When enabled, the round you shared and each new completed practice send Studio AM a summary: practice, settings, accuracy, active time and task counts. Math includes whether the scratchpad was used. Sequence, card and Go-board memory include correct positions or stones and perfect-round counts. Word search includes its mode, content version, language, words found and checked-selection count, not the words or selected letters. Locale-sensitive Stroop and Logic Grids summaries also include their content version and language. A reasoning summary includes its content version, language and reproducible round reference, but not your selections. The submission also includes the random guest identifier and a result identifier. The server stores keyed hashes of these identifiers, not their original values, alongside the summary and its receipt time in Cloudflare D1. We do not upload your nickname, individual answers, drawings or earlier local history.
Statistics pages compare matching settings only after at least 20 guest profiles have contributed. Each profile contributes its latest matching round within the last 90 days. Public responses contain combined counts and scores, not individual guest histories. A hashed identifier still links rounds from the same browser; it is not a guarantee of anonymity.
Statistics pages request public totals using the practice and settings, even when sharing is off. The request also carries the score of your latest round at those settings played without hints or shown answers, or its solving time for a puzzle ranked by time, so the page can show where that round falls among the anonymous round counts. Nothing from that request is stored. The community sharing described above is separate. Local history and charts work regardless of your sharing choice.
Mental rotation also sends accuracy, difficulty and median answer time to its original round-comparison service when contribution is enabled. Those older score records have no guest identifier and count attempts, not people. Replaying a shared round does not save or submit another result to that service. Incomplete rounds are not submitted as community-comparison results.
Private feedback and optional usage logging
Private usage logging is on by default when this browser has no saved preference. Saved choices are kept, including opt-outs; invalid or unreadable preferences remain off. It has a separate switch in Data sharing in Account. When on, we receive new practice start, completion and replay events, plus a short error category when something fails. It does not upload earlier history. A default is not saved as an explicit choice. Changing community sharing does not change this logging.
Each attempt uses a new random identifier. The server stores a hash of that identifier with the practice, content version, difficulty or settings group, page language, broad device category (phone, tablet or desktop), event type and receipt time in Cloudflare D1. For a generated reasoning practice, it also stores the reproducible round reference so feedback can be investigated against the questions that were shown. These event records do not include your guest identifier, nickname, individual answers, drawings, raw error messages or error stacks. The per-attempt identifier links events within one attempt, not a history of your visits.
When private usage logging is on, by default or by a saved choice, a visit from ChatGPT keeps the label “ChatGPT” and the first QuickenBrain page path in the current tab. It does not keep the referral URL, search or chat text, or URL query. When logging is off, nothing is stored or sent for this measurement. If you then start a practice while logging is on, that source label and page path can accompany its start and completion events. Cloudflare adds a two-letter edge country when available. This lets Studio AM compare which guides lead to completed practice among visits with logging enabled, not all visitors.
You can also choose to send a positive or negative rating, an optional reason and an optional comment through “Give feedback.” Sending feedback is a separate action that works whether private usage logging or community contribution is on or off. Please leave out names, contact details and other personal information; free-text comments are not automatically stripped of personal details.
Only Studio AM can read this feedback and these usage records through authenticated owner tools. They are not published as public ratings, counts or statistics. Private records expire from new owner reports 30 days after receipt. Expired database rows are removed in limited batches during later writes or through explicit owner cleanup, so physical deletion can take longer when activity stops or cleanup falls behind. Expiry does not automatically delete owner report files that were already generated.
Hosting and request protection
When you request a sign-in email, Cloudflare Turnstile checks for automated abuse. Cloudflare receives technical information such as your IP address and browser details. We verify the resulting short-lived token before sending an email. Your email address is not sent to Turnstile.
Cloudflare hosts and protects the site. It processes request information such as IP addresses and traffic and device details to deliver pages and manage security. Depending on the protection features used, it may set security cookies. See Cloudflare’s privacy policy and its security-cookie information.
Every page also loads Cloudflare Web Analytics, which counts page views and basic performance for us. It sets no cookie, stores nothing on your device and does not follow you between sites or visits; we see totals, not people. It is separate from the practice data described above and from any choice you make about community sharing. See Cloudflare Web Analytics.
Our server also uses your IP address to limit repeated requests. It converts the address into a salted code that changes daily and stores rate-limit information separately from scores. The application does not store the raw address in the score database. A hashed address still relates to a connection; it is not a guarantee of anonymity.
Starting a word-search puzzle requests six, eight or ten words and clues from our server, based on your chosen board size. The request also includes your Word list or Clues mode and the requested content language, but not your guest identifier or nickname. The response identifies its content version and language so results from unlike word sets remain separate. A daily salted connection code limits repeated puzzle requests; older counters are gradually removed during later requests. After loading, grid generation and word selection happen in your browser. The full clue collection is not downloaded.
Starting a reasoning practice requests six questions from our server, using the practice name, difficulty and requested content language. This applies to Missing pattern, Balance puzzles, Number sequences, Paper folding, Order logic, Shape analogies and Logical deduction. A shared daily salted connection code limits repeated reasoning requests. The generator stays on the server; the delivered round includes its answer explanations, content version, language and a short reference that can reproduce the question set. It then works locally, and no individual selections are uploaded. Completed reasoning summaries include that identity information, difficulty, timing mode, correct and answered counts, and foreground solving time. Timed-out challenges are saved with unanswered questions counted as incorrect. Unfinished reasoning rounds remain in the tab and are cleared when it closes or reloads.
Reading skills and word parts rounds also come from our server, with a short signed reference to the round. When the review notebook shows one of their questions again, the page asks our server for that round. The request sends the practice, the level and that reference. It does not send your answers, the rest of your notebook, your guest identifier or your nickname. The same daily salted connection code limits repeated review requests, in its own counter.
Newsletter
The newsletter is optional. The signup form on the home page is a plain form: it loads nothing from Buttondown and sends nothing until you press Subscribe. When you do, your email address goes straight to Buttondown, the service that sends the newsletter, not to our server. Studio AM keeps one mailing list for its sites, and the form marks your signup as coming from QuickenBrain.
Buttondown then sends one email asking you to confirm. You are not subscribed until you do. Every newsletter email has an unsubscribe link. To have your address removed, unsubscribe or email us at the address below. What Buttondown does with your address is covered by Buttondown’s privacy policy.
Membership payments and sign-in
Membership payments use service providers outside Studio AM. Timed sets on Today’s practice also use your sign-in account. A free account can start timed practice rounds without a daily limit.
Payment. Checkout, billing, receipts, renewals and cancellation are handled by Lemon Squeezy, our merchant of record. You provide your name, email address and payment details to them. When we prepare or open a checkout for you, Lemon Squeezy receives the email address you signed in with (when this device has it), a code that stands for your account (not your address), and the page to come back to after checkout. It also receives the selected plan and page language. We include the email address only after our server confirms that it belongs to the signed-in account. Our server keeps the account-code mapping so that a purchase reaches your account, along with the limited checkout diagnostics described below. The checkout email prefill stays only on this device, as described under What this browser stores. We process the email address and limited subscription information in verified payment notifications to connect a purchase with an account; the stored records are described below. We never receive or store a card number. Lemon Squeezy’s privacy policy covers its own processing. Membership renews automatically until you cancel through the link in your purchase email.
Preparing checkout. While you are signed in and not a member, the Membership page may prepare a checkout with Lemon Squeezy in the background to reduce the wait when you choose to join. This sends the details above even if you never press the checkout button. We do not prepare a checkout in the background while you are signed out. Preparing a checkout does not start a subscription or charge you.
Checkout diagnostics. When you choose a membership plan, this tab keeps a random attempt identifier, the plan, an account code when available, a broad entry category and its creation time. Repeated choices of the same plan in that tab reuse the identifier for up to 30 minutes. Our server records the plan, language, broad entry category, times of the choice and sign-in continuation, checkout handoffs and short error categories. When identified, these records use the keyed hash of your account email. Separate checkout references may be created during background preparation; preparation alone is not counted as a purchase attempt. Verified payment notifications link trials and first payments only where the checkout reference and account match. Internal testing is marked separately. These diagnostics do not include raw email addresses, IP addresses, card details, checkout URLs, page URLs or recordings of your screen. Only Studio AM can read aggregate reports through authenticated owner tools. Records are excluded from reports after 30 days and removed in limited batches during later writes, so physical deletion can take longer; existing report files do not expire automatically. Deleting an account removes diagnostics linked to that account. Checkout diagnostics are separate from optional practice usage logging and do not observe the fields you fill in on the payment provider's page.
Connecting early. When a membership offer is visible or you interact with a checkout button, your browser may connect to Lemon Squeezy’s checkout site in advance, including before you sign in or enter an email address. This connection exposes your network address to Lemon Squeezy. That connection alone does not send your email or account code, load payment scripts or embed a checkout.
Checkout on Lemon Squeezy. When you continue to checkout for a trial or membership, you go to Lemon Squeezy’s checkout page. The providers involved, which may include Stripe, Link and PayPal, process the details you submit in checkout and may use cookies and device or connection information under their own privacy policies: Lemon Squeezy, Stripe, Link and PayPal. QuickenBrain does not receive your card details.
Signing in. There is no password. You give an email address, we ask Resend, our email provider, to deliver a six-digit code to it, and that code signs you in. Resend receives the address and the message in order to send it.
What we keep. Our own database does not store your email address. It stores a salted SHA-256 hash of it, which lets us match a returning member without holding the address itself. Alongside that hash we keep the subscription identifier, which plan it is, its status, the date access runs to, and whether it is a live or test purchase. Sign-in codes are stored hashed, with an expiry and an attempt count, and are removed after use.
The cookie. Signing in sets one cookie, qb_supporter. It holds a random session token and nothing else: no email address, no name, no record of what you practice. It is HttpOnly, so scripts on the page cannot read it, SameSite=Lax, Secure over HTTPS, and it lasts thirty days from your last visit, up to a year after you sign in. It keeps you signed in so you can access your account and any active membership. Signing out clears it. It is not used for analytics or advertising, and it is not shared.
Removing it. Cancel through Lemon Squeezy to end the subscription. To have the membership records above deleted, email us at the address below from the address you paid with; we may need Lemon Squeezy to confirm the purchase before we can identify the record.
Membership through Google Play. In the QuickenBrain Android app, membership is bought through Google Play, which handles that payment, its renewals and its cancellation. When the app links such a purchase to your account, our server checks it with Google through the Google Play Developer API and keeps, with the keyed hash of your address: the purchase token Google gave the app, the product and plan, the state of the purchase, the date access runs to, whether it renews, whether we have confirmed the purchase to Google, the token of an earlier purchase it replaced, the code the app gave Google with the purchase (made from the code that stands for your account, not your address), whether it is a live or test purchase, and when the record last changed. Google also tells our server when the purchase changes, for example when it renews, is canceled or is refunded; we then read it from Google again and keep the type and time of Google’s latest notice. A notice can arrive before the app has linked the purchase; the record is then kept without the hash of your address until the app links it. Google’s answers also include details we do not keep, such as the price, the order number and the country of the purchase. We never receive your Google account or your card or other payment details. Deleting your account deletes these records, including one the app bought for your account and had not linked yet, but it does not end the subscription: cancel it in Google Play first, under Subscriptions. Google’s privacy policy covers its own processing.
For payment problems and refund reviews, we store limited provider identifiers, payment amounts, event types, reasons, review decisions and timestamps. We do not keep raw webhook payloads, payer addresses or card details in these records. Operational alerts sent through Resend contain provider identifiers and a reason, not payer addresses. Resolved refund reviews become eligible for removal after 400 days and sent alerts after 90 days; unresolved reviews and unsent alerts remain until handled. Alert quota records become eligible for removal after seven days. Scheduled cleanup removes eligible records in batches. When a reviewed full refund covers the current paid period, a small subscription record prevents that refunded period from reopening; it is removed when a later paid-through period is stored or the subscription record is removed. Refund handling does not delete your account or saved results.
Timed sets on Today's practice
Having your set timed is optional. The server times the rounds of Today's practice for you and names the day's fastest perfect set, so it needs to know which rounds are yours. A free account times its set too, with no daily limit.
Signing in. You give an email address and we ask Resend to deliver a six-digit code to it, as for members. There is no password. Our database does not store the address. It stores a keyed hash of it, which lets us find your account when you sign in again.
What we keep. With that hash we keep the nickname you choose and when the account was made and last changed. For each timed round you start, we keep the day, the practice and the seed the round was drawn from. We keep three times from our server's clock: when your start arrived, when the practice page showed the round, and when your answers arrived or the page said the round ended early. We also keep how many answers were right and whether the round counted. When all three rounds of a day are perfect, we also keep the set's total time. Your answers are checked when they arrive and are not stored. We also count how many sign-in codes each address hash was sent that day, to limit them. To space out repeated requests we also keep, with that hash, when its latest code was sent and how many were sent in a row; this counts for an hour at most and is removed when you sign in or as later requests arrive.
In your browser. Pressing Time my set saves qb:today-gold:v1 in this browser's local storage, so the sign-in stays open when you come back. It holds only that choice, and it is removed when you delete your account.
Why. To check every answer on the server, to measure each time on the server, to allow one try per practice a day, and to name the day's fastest perfect set and show you your own.
Who sees it. The page shows the nickname and total time of yesterday's fastest perfect set and of today's fastest so far. Your own place is shown only to you. Your email address is never shown to anyone.
The cookie. Signing in sets the qb_supporter cookie described above. Here it only keeps you signed in. It does not make you a member.
How long. Day results are removed 90 days after their day, a few at a time during later rounds. Sign-in code counts are removed after their day. Your account and nickname stay until you delete them.
Deleting it. Choose Delete my account on the account page, which says everything deleting removes. When Fastest perfect set shows on Today's practice, Your account there links to this same Delete my account. That removes the account, the nickname, every timed result, your signed-in sessions and any unused sign-in code at once. A membership with the same address is not affected. If you cannot sign in, email us at the address below.
One thing kept for the day. If you started a timed round on the day you delete your account, we keep the keyed hash of your address and that date until the day is over. It stops the same address from signing in again that day and starting the day's rounds a second time. It holds nothing else. It is removed after that day, during later rounds on the site.
Membership and your account
Added
What the account stores. Sign-in uses a keyed hash of your email address. Membership records hold that hash, the plan, status and paid-through date. Lemon Squeezy handles billing; we never see your card.
Optional Google, Apple or Facebook sign-in. When offered, you can choose Google, Apple or Facebook to sign in. The provider sends us an account identifier and, when available, an email address. We keep the provider's name and a keyed hash of its identifier linked to your QuickenBrain account. If Google verifies the same Gmail address, we connect Google sign-in to your existing account. Other connections may require an extra confirmation. Facebook requires a confirmed QuickenBrain account before it can be linked. We do not store provider passwords, access tokens, refresh tokens or identity tokens. Two temporary cookies, __Host-qb_oauth_browser and __Host-qb_oauth_pending, keep sign-in tied to the browser that started it. Each expires after ten minutes and is HttpOnly, Secure and SameSite=None. Temporary server records keep the sign-in checks, language and selected plan or return page needed to finish the process. A pending record may also hold an encrypted copy of the provider's email address. These records expire after ten minutes; completed records are removed, and expired records are removed in small batches during later sign-ins, so physical deletion can take longer. Deleting your QuickenBrain account removes its provider links.
Signed-in devices. Sign-in sessions keep a short device label, such as “Chrome on macOS”, and the time of last use, for the device list on the account page. They end after 30 days without use.
Approving new rounds. New practice rounds need server approval. Without an account, a browser gets 3 practice rounds a day; signed-in accounts have no daily limit. To count those rounds without an account, practice pages may set a signed qb_round_guest cookie with a random identifier. It lasts 30 days, is HttpOnly and SameSite=Lax, and is Secure over HTTPS. It is separate from the community guest profile. An approved start uses one of the day’s rounds even if the round is not finished. The server keeps a keyed hash of the identifier with the UTC date and the day’s count. Reading pages set no cookie.
Round-approval records. For each approved round, the server stores an approval token, the hashed guest identity and any signed-in account link, practice, random seed, request identifier, creation and expiry times, membership status and count after approval. When generated content is requested, the record also stores the endpoint and validated query, such as difficulty and language, so a retry returns the same round. A timed Today round also records its date and seed. These records do not contain your answers, drawings or score. The tab keeps a pending start's request identifier and settings so a failed request can be retried without reserving another start; timed-round handoffs also keep the approval in the tab.
Keeping and deleting approval data. An approval is valid for seven days. Its server record becomes eligible for deletion seven days after expiry. Daily count records for today and yesterday are kept; older daily counts become eligible for deletion. Later approval requests remove at most 100 eligible records from each table per request, so deletion can take longer if traffic stops or a backlog builds up. Deleting an account deletes its linked approvals and account daily counts. Guest daily counts and approvals made anonymously are not deleted with the account; they follow the same retention and cleanup rules.
Daily totals. We also keep daily totals with no identifier in them: rounds started by visitors without an account, free accounts and members; how often an offer was shown to a visitor without an account or a free account; how many sign-in codes were sent, requests for a code held back or refused, sign-ins completed, accounts created, checkouts prepared in the background and checkouts opened; and how many memberships started a free trial and how many paid their first charge. We also count Sam’s AI replies: how many were sent, how many failed at the AI provider and how many were held back by our checks. A total is a date, a name and a number. Totals are kept for 400 days. So that a trial or a first charge is counted only once, we keep a note of it beside our record of the payment notices we have handled: which total it counted, whether the purchase was a test or a live one, when, and the subscription it counted, named by Lemon Squeezy's subscription number or, for a Google Play purchase, by a SHA-256 hash of its purchase token. The note holds no address or name, and it is not removed.
Counting offers. When a page shows an offer to a visitor who is not a member (on a practice page, the free sign-in once the day's round is used), it asks our server, once each time the page is opened, to add one to that day's total. The server reads the sign-in cookie, when there is one, only to tell a visitor without an account from a free account; a member's page adds nothing. It also reads the address of the page that asks, for the visits from our ads described below. It keeps nothing about you or the page. To limit repeated requests, it counts them for each connection by the daily salted connection code described under Hosting and request protection, twenty a minute at most; those counters are removed during later requests after about an hour.
Visits from our ads. If you open the site from one of our own ads, the ad’s link says so in its address (for example utm_source=meta). The daily totals then count that visit, and count a second time the rounds started, the times an offer was shown, sign-in codes sent, sign-ins completed, accounts created and checkouts opened on pages whose address still carries that word. To keep it there, links you follow within the site carry the word on. These totals also hold no identifier and no campaign name. Nothing is stored on your device for this, and the site loads no advertiser’s code.
What this browser stores. Your free practice rounds are listed under qb:membership:v1:day with the practice name, completion and accuracy. This local list is separate from the server’s count of the day’s rounds. Once you sign in, qb:membership:v1:account holds a code that stands for your account (made from the keyed hash, not your address and not a number in our records), and the date your membership runs to. A cookie named qb_signed_in says only that this browser is signed in, so the page knows to ask our server; it holds the number 1 and nothing else, and goes with the sign-in. When the QuickenBrain Android app shows these pages, a cookie named qb_app holds the number 1 for that visit, so the pages leave out the website's prices and checkout; in the app, membership is sold only through Google Play. The address you sign in with is kept on this device, under qb:membership:v1:email, until you sign out, to fill in the checkout so the purchase reaches your account, to turn on the weekly summary without asking for it again, and so the account page can show it; if your sign-in ends another way, it goes when the site next checks your sign-in. To show it, the account page sends the address to our server, which only confirms whether it is the address of the account this browser is signed in to. The server sends no address back and does not store or log it. The page shows the address only when the server confirms it. While you are signed in, qb:member-sync:v1 keeps when this device last synced, which version of each copy it last saw, and when you last saved or removed a favorite, chose a practice setting or cleared saved activity here. When you sign out it keeps only the code that stands for your account, so that a different account that signs in on this browser does not take in your history; it goes when you delete the account. When Today's practice opens a timed round, the tab also keeps which round it opened, so that practice lets it start. When a checkout is prepared, as described under Payment, the tab keeps its link and a signed verification code, alongside the account code, selected plan, language and return page. The verification code lets our server check that the prepared checkout belongs to that account and offer. The tab can reuse these records for up to one hour, so a reload need not prepare another checkout. They last no longer than the tab stays open. We do not reuse a cached checkout for a different account, plan, language or return page; signing out clears it. Signing out or deleting the account removes the account entry and the qb_signed_in cookie. Clearing cookies can create a new guest identity on the next visit, but does not erase the old server records.
History and progress on every device. While you are signed in, your account also keeps a copy of what this browser saves for you, so every device you sign in on shows the same: your practice history (the latest 100 practice and lesson records, with the details listed above) and your Today's results from the last 366 days, your lesson, guide and grammar progress, completed lessons, favorites and recently opened pages, your review notebook, the dates in your rock pile, your kept training-level records (first date, round count, first clear, best score and best tempo), and the level and settings you chose on each practice, with when you chose each favorite and setting so the latest choice wins. It is stored against your account, which is a keyed hash of your address, never the address itself. Each signed-in device sends its copy a few seconds after a change and takes the others' when a page opens. It does not include Pencil notes and drawings, days visited, your guest profile or sharing choices, the original rotation history or today's local round list, which stay in each browser. This history copy is sent only while you are signed in; server round approvals and daily counts are separate. The copy is kept until you delete the account. Signing out keeps each device's own copy and stops syncing on it. If a different account then signs in on that browser, the copy there is cleared first, because it is yours and your account keeps it. Clear saved activity in Account, while you are signed in, also clears the account's copy and, when they next sync, your other devices. Deleting the account deletes its copy at once.
Programs. Program enrollment and progress are stored separately for each account in this browser and synced with that account while you are signed in. These records contain the program and content version, start time, completed practice targets, completion times and round references, and whether help was used. They do not contain individual answers. They follow the sign-out, retention, account-deletion and Clear saved activity rules above. A different account does not receive them. Program records remain under their original account on this device after sign-out or account switching; they are removed when you clear saved activity or site data.
Weekly summary by email. On the account page you can turn on a weekly summary of your practice. Turning it on stores your email address with Resend, our email provider, for that purpose only. Our own database keeps Resend’s reference to the address, never the address itself. It also counts your rounds against your account by week: for each practice, the number of rounds, your best score in rounds played without help, and the minutes played. To count them, a signed-in browser sends its sign-in cookie with each finished round. The anonymous round count described above still stores nothing about you. Each Monday we send one email with the previous week’s counts, if there are any, and then delete those counts. Turning the summary off, or using the unsubscribe link in any summary, deletes the counts and stops the emails. Resend then keeps the address marked as unsubscribed. Deleting your account also removes the address from Resend. Nothing else about you is linked.
Email about new practices and the weekly test. The sign-in window has a box for email about new practices and the weekly test. It is never ticked for you. If you tick it, a cookie named qb_news_choice carries that choice to the end of the sign-in, for ten minutes at most. It holds only the language and the version of the words beside the box. Once you are signed in, we keep with your account that you said yes, when, whether you said it while signing in or on the account page, the page’s language and the version of the words you agreed to. This record holds no email address. These emails tell you about new practices and each new weekly test, and nothing else. Every one of them has a link that stops them in one step, without signing in. You can also turn them off, or on again, on the account page. Turning them off, using that link or deleting your account deletes this record.
Why we use personal information
Where European or UK data protection law applies, we use the following legal bases for the purposes described on this page.
Contract: we process account, sign-in, membership, saved-result and sync information to provide the services you request and answer questions about them. Sam’s AI replies are part of membership, so we process the questions members send to Sam on this basis too.
Legitimate interests: we use necessary security logs, rate limits and abuse checks to protect the site, its visitors and email delivery. We consider the effect on your rights and avoid using these records for advertising.
Consent: optional newsletters and weekly summaries run only when you choose them. Sam’s visit memory works only if you turn it on. A Sam AI reply you report is kept with your consent, which you give by sending the report. Legal obligations: we retain transaction or request records when applicable accounting, tax or other laws require them. Optional Google Ads measurement also relies on your consent.
Your privacy rights
Depending on the law that applies, you may ask to access, correct, delete or restrict use of your personal information, receive a portable copy, or object to processing based on legitimate interests. To make a request, email contact@studioam.art. We may ask for information needed to verify your identity. We respond within the applicable legal deadline and do not penalize you for exercising your rights. Records that contain no identifier cannot be linked back to you.
You can withdraw consent through the relevant setting or unsubscribe link, or by contacting us. Withdrawal does not affect processing that was lawful before it, and does not end processing needed for your account, a contract or a legal obligation.
You can complain to the data protection authority where you live or work, or where an alleged infringement happened. The European Data Protection Board lists EEA authorities. You do not have to contact us before using a legal right to complain.
Providers and international processing
Cloudflare provides hosting and security, Resend delivers sign-in codes, weekly summaries and requested weekly test emails, Buttondown manages the newsletter, Lemon Squeezy handles payments as merchant of record, Fireworks AI generates Sam’s AI replies, and Google handles purchases made in the Android app through Google Play, answers our server’s questions about them through the Google Play Developer API and tells it when they change. These providers may process information in the United States and other countries, whose protections can differ from those where you live. With your permission, Google also processes advertising measurement information as described below.
Their published transfer terms describe the safeguards they offer, including standard contractual clauses or adequacy frameworks where applicable: Cloudflare, Resend, Buttondown, Lemon Squeezy, Fireworks AI, Google. Contact us for information about the arrangements that apply to your data.
Browser privacy signals
We do not sell personal information or use it for personalized ads. The site has no separate handler for Do Not Track (DNT) or Global Privacy Control (GPC) signals. Google Ads measurement is off for everyone, whether or not your browser sends a signal. Your settings separately control community sharing and private usage logging.
Keeping and removing information
Use “Clear saved activity” on Account to remove its history, days visited, favorites, lesson, guide and grammar progress, and review notebook. This leaves your guest profile, sharing choice, original rotation history and chosen levels unchanged. If you are signed in, it also clears the copy kept with your account, and your other devices when they next sync. Clear this site’s data in your browser settings to remove all local records, including the guest identifier and sharing choice. This also removes saved opt-outs. On a later visit with no saved preference, community sharing and private usage logging use their on defaults. If local storage is unavailable, a new choice lasts only on the current page; we show a message when it cannot be saved.
Turning private usage logging off stops new automatic usage events; it does not erase records already submitted. Clearing browser data also does not delete private records already received by the server. You can still choose to send manual feedback while logging is off.
Turning contribution off prevents new submissions; it does not remove previously received summaries. Clearing browser data also does not remove server records. Guest-based summaries older than 90 days are excluded from comparisons immediately. They and old rate-limit entries are gradually removed during later submissions, so physical deletion can take longer when activity stops. Original rotation score records currently have no automatic expiry. There is no self-service server-record lookup or deletion tool for these, and we may be unable to identify which submitted records are yours. Timed sets are the exception: you can delete that account yourself, as described above.
For a question or a request about information you have shared, email contact@studioam.art. If you contact us, we receive your email address, message and any attachments and use them to respond and investigate your request. Please avoid sending sensitive personal information.
Who may use QuickenBrain
QuickenBrain is for people aged 13 and over. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has sent us personal information, contact us using the address above. We will investigate and remove information we can identify as theirs, unless the law requires us to keep it. A person under 18 needs a parent’s or legal guardian’s permission to buy membership; local rules may also require parental consent for an account or optional data uses.
Advertising
Google Ads measurement is off. Since October 15, 2026 no page loads a Google advertising tag or sends a Google advertising measurement request, and the site asks no one for measurement permission. If we turn it on again, we will say so here first: it would be off by default, stay off until you allow it, and work as described below. The Privacy page does not load this tag.
After you allow measurement, Google’s tag can receive an ad-click identifier when available, a page address with sign-in tokens and other unrelated parameters removed, and technical information such as your IP address and browser. When a new account completes its first verified sign-in, we may send a conversion event with a random event reference. Signing in to an existing account does not create that event.
We do not send your email address, name, account identifier, practice answers or saved activity to Google for this measurement. We do not enable enhanced conversions, remarketing or advertising personalization.
Your choice is saved in the qb_ads_consent cookie on this browser for 30 days. We configure the measurement cookies set for this site with the qb_ads prefix to expire after 30 days, without renewing their lifetime on each visit. A conversion reference is valid for up to 10 minutes while waiting to be sent. A sent reference is used for up to 24 hours to prevent duplicates. Expired references are removed when they are next checked or when the tab closes.
A permission given before then sends nothing more, because no page loads the tag. The measurement cookies expire on their own, 30 days after they were set, and you can delete them in your browser at any time. This does not erase information already received by Google. Your choice never affected sign-in, saved activity or membership.
These reports do not count every new account or guarantee that Google can attribute a sign-in to an ad. Refusing consent, browser restrictions, blockers or connection failures can prevent measurement. See Google’s Privacy Policy for Google’s handling and retention of information it receives. Checkout providers’ own use of cookies is described under Payment above.
We will update this page when the site’s data practices change.