Privacy and your results
Updated November 17, 2026
drawshapes.io is operated by IMMERSIBLE Business as part of IMMERSIBLE Games. This page describes the game’s local storage and daily score comparison. The IMMERSIBLE Games privacy policy provides the broader policy and contact information.
What stays in your browser
The game saves your daily progress, drawn lines, completed scores, streak history and sound preference in this browser’s storage. This allows a reload to restore the current round and deadline. It does not create an account or sync your history to another device.
A random browser identifier is also saved for the daily comparison. You can remove local game data through your browser’s site-data controls. Doing so removes your progress and statistics from that browser and creates a separate comparison identity on a later visit. It does not retract an already counted aggregate result.
What is submitted after a daily
During play, one request loads a signed snapshot of today’s aggregate one-point score bands, without other players’ identities or drawings. With at least five earlier results and a snapshot less than fifteen minutes old, your browser shows your percentile and histogram immediately when you finish. The score service verifies that snapshot and saves the same comparison in the background. If the snapshot is unavailable, too old or too small, the game waits for the ordinary server comparison. An unsuccessful save leaves the snapshot visible with a retry message; it is not cached as a confirmed result. Previously submitted scores always retain their server comparison.
Scoring happens entirely in your browser. When you complete all five rounds, the game sends your final numeric score, the UTC puzzle date, a random browser identifier, a format version and, when available, the signed aggregate snapshot loaded during play. Your drawing coordinates and individual round results are never sent to the score service.
The service adds one result per browser per daily to an aggregate of one-point score bands. At least six results are needed before a percentile is available. Until then, your score is counted once and the comparison stays pending. You can check again with the button or by refreshing the page. Once available, the comparison is saved against that snapshot of results, excluding your own score and treating tied bands separately. Later results do not change it. The response contains your percentile, sample counts and twenty grouped score-band counts for a histogram, without individual other players’ scores or identifiers. During play the snapshot contains aggregate counts for 101 one-point bands; no individual submissions are disclosed. The chart excludes your own result and shows the actual sample shape.
The available percentile and histogram are saved in this browser. An older saved percentile makes one check on refresh to add its histogram, keeping the original percentile unchanged; that histogram uses a later snapshot. Reloading a completed result with a saved percentile does not contact the score service. While a percentile is still pending, each reload checks once, and the Check again button makes one additional check; there is no automatic polling. If browser storage cannot retain it, a retry returns the existing server snapshot without adding another score or recalculating the comparison. Comparison records expire after 35 days. Clearing browser data creates a separate identity and does not retract an already counted aggregate result. There is no comparison polling or scheduled recalculation.
The first five submissions show an insufficient-data message instead of a percentile. Pending checks reuse the original submission without counting it or charging its abuse allowance again. Scores are reported by browsers, so this is an informal community comparison rather than an anti-cheat ranking.
Hosting and security
Hosting and score-service providers necessarily process connection information such as IP addresses to deliver and protect the service. Abuse controls store a daily keyed hash of the IP address, not the raw address, with a two-day expiry. Operational error logs have seven-day retention. Database expiry deletion is asynchronous, so an expired record may remain briefly while the provider removes it. These controls and provider processing are separate from the comparison. We do not display that connection information in the comparison.
The comparison is not proof of unique people or verified competitive play. It uses score bands to summarize submitted results, not to make decisions about people. No account, email address or payment information is required to play.
Advertising
Google AdSense review is being requested for this site. An application for review is not approval. Advertising remains disabled until the required approval and configuration are in place. If advertising is enabled in a later release, the site’s disclosures and consent controls must reflect the actual advertising setup before ad requests are made.
The current game does not require third-party advertising requests for gameplay or the comparison.
Contact
For privacy questions or other enquiries, use the contact information in the central privacy policy or the IMMERSIBLE Games contact page.