Cookie Policy

A cookie is a small value a website asks your browser to keep and send with later requests. First-party cookies are associated with the site you visit; third-party cookies are associated with another service. Cookies may last for a browser session or until an expiry date.

Local storage keeps values for this website in your browser until they are cleared or replaced. Session storage generally lasts for a tab’s browsing session. These tools can remember settings or access tokens even though they are not cookies. Browser restoration and privacy settings can affect how long data remains.

IndexedDB is another form of browser storage that can hold larger data, such as a drawing reference image used for local practice.

• anonId — guest identity. Drawn to Battle sets a signed, first-party cookie when an action establishes guest play. It associates your browser with your drawings and activity and is configured to last up to one year. It is also used to attribute gameplay events and help enforce usage limits.
• Clerk authentication cookies. Clerk uses cookies and related storage to support optional accounts, session validation, and sign-in security. Names and lifetimes depend on the sign-in flow and Clerk configuration. Clerk’s privacy notice describes its processing.
• stats_key — restricted administration. A separate cookie, configured for up to 30 days, is set after successful administrator authorization. It supports protected statistics and moderation tools.

Blocking required cookies can prevent sign-in or stop the game from recognizing ownership. Clearing anonId can remove your ability to manage unclaimed guest drawings. Sign in and verify that your drawings belong to your account before clearing this cookie. The public drawings do not disappear merely because the cookie is gone.

The game stores small values locally so repeated visits and open tabs behave consistently. Examples include:

• Sound: dtb-sound-muted and dtb-sound-volume remember the sound settings you choose.
• Battle controls: dtb-replay-speed and dtb-battle-stance remember replay speed and a preferred stance.
• Navigation and notifications: dtb:last-fighter-id helps return you to a drawing; notification cache and coordination values reduce repeated requests across tabs.
• Temporary session state: reveal and achievement markers prevent repeated celebrations; live-duel session values help reconnect to a room.
• Pending recovery credit: session storage under dtb:rewarded-recovery-pending, followed by a fighter identifier, remembers an ad attempt while its earned recovery credit is being confirmed.
• Local drawing practice: IndexedDB’s drawn-to-battle-local database stores a practice reference image in practice-references. The app marks it to expire after 24 hours and checks that expiry when loading the reference. It may remain in browser storage until the next load or until you clear site data.

Persistent local preferences do not have a fixed automatic expiry in the application. You can change sound and battle settings through their controls, or remove stored values through your browser’s site-data settings. Clearing temporary session state can interrupt a duel or cause an animation to appear again.

Vercel Web Analytics uses request-derived visitor identifiers instead of tracking cookies, according to its privacy documentation. It collects traffic information such as page, referrer, browser category, and approximate region. Our separate server-side gameplay events can be linked to a guest identifier or account; clearing cookies does not erase those records.

If you visit Stripe-hosted checkout or its customer portal for Ink+, Stripe may use its own cookies and similar technologies to process payments, authenticate requests, and prevent fraud. Their duration and controls are described in Stripe’s cookie policy.

The site loads a Google AdSense verification script. An optional Google H5 rewarded-ad feature can also load and preload advertising when enabled. Google and participating advertising partners may place or read cookies and use web beacons, IP addresses, or other identifiers. These support ad delivery, fraud prevention, measurement, and, where allowed, personalization based on visits to this and other websites.

Advertising cookies are separate from the cookie that preserves guest ownership. Their names and lifetimes vary by vendor, ad, consent choice, and browser. An ad tag can contact an advertising service even when no visible ad has appeared or you have not chosen to watch a rewarded ad.

• Use an advertising consent message, when shown, to review participating vendors and choose whether to allow optional advertising processing. Use that message’s available privacy controls to revisit your choice.
• Manage Google personalized ads in My Ad Center.
• Review participating companies’ choices at AboutAds or Your Online Choices.
• Read Google’s partner-site data notice and Google’s cookie explanation.

Opting out of personalized advertising does not necessarily remove ads, prevent security-related processing, or block all cookies. Non-personalized ads can still use storage. Some choices are browser- or device-specific and may need to be renewed after clearing cookies.

This policy is an explanation, not a consent dialog. Where consent is legally required, the relevant advertising consent mechanism must collect it before the covered processing; continuing to browse or accepting the Terms of Use is not a substitute.

Open your browser’s privacy or site-data settings to inspect cookies, delete this site’s storage, or block third-party cookies. Browser help is available for Chrome, Firefox, and Safari.

Check your account ownership before deleting guest storage. Cookie deletion resets browser recognition, not your server-stored account, public content, subscription, or billing records. For a data-removal request, use the process in our Privacy Policy.

Browser signals such as Do Not Track or Global Privacy Control and advertising consent settings are different mechanisms. Do not assume a browser signal changes every provider’s settings; use the relevant controls and contact us about any applicable opt-out right.

We will revise this page when our use of browser storage changes. The examples describe the application’s current storage uses; third-party services may change their own cookie names and expiry periods.

For help understanding a stored value or exercising a privacy choice, contact hello@drawntobattle.com.