Privacy

Your game and browser storage

Daily play uses two first-party cookies, mi_identity and mi_active, to recognize this browser and keep your active daily puzzle selected. They are set for up to one year, renewed during use, and cannot be read by page scripts. The server uses a hash of the random identity token to associate your saved play with this browser.

Submitted daily guesses, including chosen or drawn outlines, placements, sizes, scores and submission times, are stored in Cloudflare D1 alongside that browser-linked identifier and game summaries. The server remains the authority for official daily results. Each daily has a numbered URL; returning to it resumes unfinished rounds or shows completed results.

Completed daily, practice and prototype-demo attempts, including every retry, are also kept in this browser’s remapit-history IndexedDB database. Records include the challenge or game identifier, round, chosen or drawn outline, placement, size, score and submission time. Shared game definitions retain original island information and target geometry, round modes and seeds, offered coastlines and version identifiers; each attempt also retains its resolved geographic guess geometry, enough to redraw the original island and guess without today’s island catalog. Transient camera gestures and the surrounding world-map background are not archived. Practice and demo scores stay local and are not submitted to the daily API; analytics may still observe practice interactions. Returning to a practice link restores its last completed result.

Older remapit:history:v1: localStorage records are copied into IndexedDB without deleting or rewriting their originals. Older attempts remain readable, but cannot provide full replay geometry that was never captured.

Your island trophy case is derived from these locally saved daily and practice attempts, including retries and readable older history. Demos, unsubmitted edits and pending daily saves do not collect trophies. The collection is browser/device-local, not an account or a new server record; clearing site data removes it.

Opening a trophy shows its artwork and, when available, the actual first-earning attempt’s stored island and guess overlap. Later retries do not replace that first receipt. Saved-attempt links read only this browser’s history; older or missing geometry is explicitly unavailable rather than recreated from the current puzzle catalog.

When you submit a daily guess, its unchanged request and original full game definition are saved locally while awaiting server confirmation, so you can retry it after reloading without losing the geometry you saw. A server-derived, game-specific recovery token keeps these pending requests separate between daily players; it is not sent to analytics. Pending guesses are not official results until the server confirms them. Unsubmitted sketches and map adjustments are not durable saves.

Local history has no automatic expiry or history-size eviction. If storage is blocked, full or unreadable, or required replay map data is unavailable, the game shows a warning and leaves existing records untouched. New unsaved attempts can only be retried while the page remains open. Browser storage limits, private browsing and clearing site data can remove local history; browser storage is not a backup or cross-device recovery service.

Your theme and sound preferences are stored locally in your browser. Clearing cookies or switching browsers creates a different daily player and does not delete records already saved on the server. There is no account-based or cross-device recovery.

Feedback and shared scores

If you send feedback, we store your optional thumbs-up or thumbs-down rating, optional message, the validated game-page path and a submission time in Cloudflare D1. You can send a thumb, a message, or both. The feedback table does not attach your player identifier, IP address or browser cookies. Please do not include personal or sensitive information in your message. The app does not send your message or rating to GA4, and both the inline end-of-game feedback and menu dialog are explicitly masked for Clarity.

If you create a daily score share, the app stores a spoiler-free score card in Cloudflare R2. The public page and image show the puzzle number and round scores, not your island answers or outlines. Anyone with the share link can view or pass it on, and others may keep copies.

Post-round Wikipedia summaries

After a scored round, your browser requests that island’s article summary directly from Wikipedia. No summary requests run while you are guessing, and exploring other islands on the map does not request new summaries. Requests omit browser credentials and referrers; we do not send daily identifiers, scores, placements or drawings to Wikipedia. Wikimedia still receives the requested article title and network information such as your IP address when your browser connects.

If Wikipedia is unavailable, some islands have saved source text; others show a load error with retry. Text is by Wikipedia contributors under CC BY-SA 4.0, and each summary links to its source article. Article links open Wikipedia in a new tab, where its own privacy policy applies.

Google Analytics 4 (GA4)

We use GA4 to understand visits and game actions, such as starting and completing rounds, scores, opening help and using sharing. Google also processes technical information such as browser and device details and network information when your browser connects to its services. Analytics identifiers are not the same as your daily-game identifier.

The app sends only allowlisted game-event fields, not feedback text or ratings, drawings, precise guess coordinates or the daily identity cookie. Google signals and advertising storage, advertising user data and ad personalization are disabled in our tag configuration. Analytics storage is enabled, so GA4 may use analytics cookies. This is not a claim that analytics data is anonymous.

Read Google’s Privacy Policy and how Google uses information from sites that use its services.

Microsoft Clarity: heatmaps and session replay

We use Microsoft Clarity to see how people interact with the app and find confusing or broken parts of the experience. It can collect page content and usage information such as clicks, taps, pointer movements, scrolling, navigation, browser and device details, and network information including IP addresses. Heatmaps summarize interactions; session replay reconstructs a visit from recorded page and interaction data.

The inline feedback and feedback dialog are marked for masking, in addition to Clarity’s own masking of sensitive input. Masking is a safeguard, not a reason to enter personal information into the game. We do not pass your daily-game identifier to Clarity’s identification API.

We send Clarity a denied signal for both analytics and advertising cookie storage; we do not grant cookie consent on your behalf. Clarity can still operate in limited, no-consent mode without persistent tracking cookies. Cookie-free collection is still data collection.

Read the Microsoft Privacy Statement, Clarity privacy information and Clarity’s consent documentation.

Analytics, cookies and your choices

Analytics loads automatically on clean daily and practice game URLs. It is not initialized on this privacy page, demos, share pages or URLs with a query string or fragment. If a tracked page navigates to an excluded URL, the app disables GA4 collection and stops Clarity for that document.

The site does not currently have an on-site analytics consent selector. A privacy notice is not consent, and Clarity’s no-consent mode is not a substitute for any consent required by local law. GA4’s current analytics-cookie setting is described above.

You can block analytics scripts with browser privacy tools, manage or clear cookies and local storage in your browser, or use Google’s Analytics opt-out browser add-on where supported. Blocking analytics does not prevent gameplay or feedback; blocking the game’s first-party cookies prevents daily progress from being saved. Clearing browser data does not delete information already received by us, Microsoft or Google.

Hosting and data handling

Cloudflare hosts the app, its database and shared score images. It processes requests and technical information needed to deliver and protect the service, which can include IP addresses and operational logs. The feedback table’s limited fields do not mean the hosting or analytics services never process network information.

We use saved game data to restore progress and calculate game results, feedback to improve the app, and analytics to understand usage. The app does not currently offer a self-service data deletion tool or a fixed automatic deletion schedule for saved games, feedback or score shares. Provider handling, retention and international processing are explained in their privacy information, including Cloudflare’s Privacy Policy.