Patagonia privacy policy and data deletion

Who is responsible

Warweaver Studios, Tokyo, Japan, is responsible for Patagonia's data. Contact games@warweaverstudios.com. This notice supplements our studio privacy policy, including your rights, international processing, security and children's privacy.

Patagonia has no player accounts. This notice covers browser playtests and analytics-enabled native builds. Fields and controls depend on your version/platform; a collector upgrade does not update an installed game. Saves remain on your device.

Patagonia is intended for adults aged 18 and over. See the studio policy's Children section for age restrictions and requests concerning a minor's data.

See Delete your data to make a request without an account or password.

What the game sends

With gameplay sharing on, Patagonia can send:

Identifiers and consent: a random playtest ID, session/run identifiers, event times and sequence, build/version and source identity, build-assigned distribution/test-group labels, and your privacy choice, basis, version and time. These are pseudonymous records, not anonymous data.
Gameplay and interface: menus/screens, party and character choices, hub/progression, rooms and encounters, rounds, cards/upgrades, enemy actions, combat results, rewards, tutorials and interrupted runs.
Device and performance: platform, operating system or browser family/version where available, engine/renderer, rounded screen/window information, processor cores and supported graphics/memory context; loading, foreground/gameplay time, pauses, frame rate, slow frames, memory use, drawing load and dropped-event counters.
Diagnostics: bounded engine errors/freezes, browser or graphics failures, and unexpected-exit/restart reports on a later launch. Supported Android builds can attach Android's prior exit reason, process state and memory information. An unknown exit is not automatically a crash.

Older versions can send fewer fields. We do not request names, accounts, email, advertising IDs, contacts, precise location, typed text or save files as telemetry. Current diagnostic filtering removes personal paths, email-like strings, URLs and credentials. Collector IP addresses are used transiently for delivery and abuse control, without analytics database or collector access-log storage.

How we use it

We use telemetry to fix bugs/crashes, compare performance, understand onboarding/progression and improve design, including statistical and machine-learning models developed inside the studio for our games. We do not sell it, build advertising profiles or send raw gameplay/diagnostics to an external AI service.

Foundry, our private studio dashboard, receives aggregates rather than player IDs or raw diagnostics. Telemetry does not supply advertising spend or attributed installs.

For browser playtests, use Privacy choices on the studio/player page. Sharing is off until permission in the EU, EEA, UK, Switzerland or unknown regions; elsewhere it defaults on unless you opt out. A browser's Global Privacy Control signal keeps it off. The shared browser control is authoritative.

Analytics-enabled native versions offer Privacy → Share gameplay data from the title screen or pause menu. EU/EEA/UK/Swiss or unknown regions, and UTC−1 through UTC+3, require permission; other known regions default on. This uses device region/time-zone settings, not location services. No response means no. Play remains available with sharing off. For EU, EEA and UK analytics, our basis is consent as described in the studio policy.

Local storage and offline delivery

Saves/settings remain in browser/app storage. With sharing on, newer versions also store a random playtest ID, up to 2 MiB of unsent telemetry and a bounded diagnostic marker. Stored batches expire after 30 days or earlier under queue pressure, and retain their original build/session and time.

Turning sharing off stops recording, cancels sending, clears queued telemetry and diagnostic state, and removes the active ID. Newer versions retain a pending deletion token and retry when the game runs online, including across launches. It is necessary to complete deletion, not permission to resume analytics. Older browser versions make a best-effort request; use email if completion is uncertain.

Clearing storage or uninstalling can remove an undelivered request. Device/platform backups may restore local files according to your settings. Your choice and pending deletion tokens can remain while sharing is off.

Delete your data

Copy your playtest ID before switching sharing off or clearing storage. Look for Privacy, Privacy and playtest ID, or Copy playtest ID on the title screen or pause menu, depending on version.
In a browser, turn off Playtest analytics using Privacy choices. In a native build, turn off Share gameplay data in Privacy.
Keep the game running online to complete deletion. If offline, using an older build, or seeking confirmation, email the game name and copied ID to games@warweaverstudios.com.

Email is an alternative without an installed game. Include every installation/ID to remove. We cannot locate telemetry from a name or Google account alone. We may request information needed to verify the request; we respond within one month without a fee. Continued sharing can create new events, so switch it off when requesting deletion.

When processed, deletion removes linked gameplay, performance, device and diagnostic events from the active collector. To prevent delayed batches recreating them, the server keeps a one-way hash of the deleted ID and deletion time for up to 365 days. The suppression record contains no raw ID and is not used for analytics; its hash is still pseudonymous data.

We also review maintenance backups and remove or restrict corresponding records; later deletions must be reapplied before restore. Statistics already combined so they can no longer identify you may remain. Email correspondence can remain for two years after the last exchange, and a minimal rights-request record for three years after closure. Telemetry deletion does not erase local saves.

Storage, recipients and retention

Telemetry travels over HTTPS to our collector on Hetzner Online GmbH hosting in Finland, with studio access from Japan. Google Workspace handles email requests. We do not provide telemetry to advertising networks. Distribution platforms handle their own store/install diagnostics separately under their policies.

Active detailed telemetry is deleted after 365 days from receipt. The suppression hash expires within 365 days of deletion. Restricted maintenance backups are for recovery and included in deletion/retention handling. Statistics that can no longer identify anyone may remain longer. Saves/choices remain until cleared or removed; pending deletion tokens remain until acknowledged or local storage is removed.

Contact games@warweaverstudios.com for access, correction, deletion or other privacy requests. See the studio policy for your rights. Changes are dated above.