The short version
- This website (
warweaverstudios.com) and our browser player (play.warweaverstudios.com) use no advertising, tracking or social media cookies, and no third-party analytics or ad SDKs. - Analytics-enabled builds of Patagonia, Rootwardens and Wyrd Unbound can send first-party gameplay, performance and diagnostic data to help us improve them, linked to a random playtest ID rather than your name or email. These are pseudonymous records stored on our studio-controlled collector; no advertising or external analytics provider receives raw gameplay telemetry or replays.
- Starting with the Rootwardens Android 1.0.3 update, Share ad attribution lets AppsFlyer measure installs and early milestones and send limited reports to AppLovin for external ad campaigns. This includes organic installs when the setting is on. None of our games show in-app ads. Browser playtests, Patagonia and Wyrd Unbound use no third-party ad attribution.
- In the EU, EEA, UK, Switzerland, unknown regions, and European time zones (
UTC−1throughUTC+3for native apps) optional gameplay sharing and Rootwardens Android ad attribution are strictly off unless you allow them. Other known regions provide clear controls to switch either off at any time, and browser Global Privacy Control signals keep browser analytics off everywhere. - In supporting Rootwardens native builds (
1.0.3+), turning Share gameplay data off pauses new collection while keeping prior history, whereas Delete my data permanently erases your server records. Each game guide below explains its exact controls. - Game saves stay on your device, in your browser or in the app. We never receive them.
- We never sell personal data. We limit what we share to the data needed for the purposes below. If you email us or use our contact form, we use your message to reply.
- You can change website/browser choices at any time with Privacy choices at the bottom of every page, change native switches in-game, and contact us to access or delete your data at games@warweaverstudios.com.
Who we are
Warweaver Studios is a three-person independent game studio based in Tokyo, Japan. We are responsible for the personal data described here (the "controller" under the GDPR, and the personal information handling business operator under Japan's Act on the Protection of Personal Information, APPI).
- Operator: Warweaver Studios, Tokyo, Japan
- Address and representative: our business address and, where applicable, the name of our representative are available on request from the address below.
- Contact for anything in this policy: games@warweaverstudios.com
This policy covers warweaverstudios.com and analytics-enabled builds of Patagonia, Rootwardens and Wyrd Unbound, including browser playtests on play.warweaverstudios.com and native builds. It does not mean each game or platform is currently distributed. AskJev and the warweaver.io SDK site have their own notices.
Each game has its own privacy notice, deletion instructions and terms of service.
- Wyrd Unbound privacy and data deletion and terms of service
- Patagonia privacy and data deletion and terms of service
- Rootwardens privacy and data deletion and terms of service
What we collect, and why
When you visit this website
Our server briefly processes technical information that every browser sends, such as your IP address, browser type, the page requested and the time. We use it only to deliver the pages and to protect the site against abuse.
- Legal basis (GDPR): our legitimate interest in running a secure website (Article 6(1)(f)).
- Kept for: up to 14 days in server logs, then deleted.
The public studio pages set only the cookie that remembers your privacy choice. Authorized Foundry visitors also use the necessary sign-in cookie described below. See Storage on your device.
When you use Foundry
Our private workspace, Foundry, uses a shared team password. We store its password hash, a shared team identity and access role, workboard entries, campaign inputs, aggregate attribution summaries and dated reports. Changes are attributed to the shared team identity rather than an individual. Do not enter personal player information or confidential personnel details in workboard notes or reports. We use these records to manage studio work and reporting. There is no public signup or optional analytics in Foundry, and it requires no external identity or analytics provider.
Sign-in sessions use a necessary cookie and expire after seven days or 24 hours without use. We store hashed session tokens, short-lived hashed abuse-control keys, and a 90-day record of work changes. Rotating the shared password revokes existing shared sessions. We review workboard and report content when handling a removal request. We retain work records and reports while needed for studio operations.
Foundry receives closed aggregate game statistics and aggregate campaign summaries rather than player IDs, device advertising IDs, raw IP addresses or raw gameplay/error payloads. The game collectors and their privacy choices remain separate. Contact games@warweaverstudios.com about your workspace account or records.
When you contact us
If you write to games@warweaverstudios.com or use the contact form, for playtest feedback, press, partnerships or anything else, we receive your email address, your name if you include it, the topic you choose, and whatever you write.
The contact form delivers your message to that inbox as an email, and sends you a confirmation with a copy of what you wrote (at most one a day to the same address). Our server passes it on without keeping a copy, and does not log your IP address with it. To limit abuse, it keeps a scrambled (keyed hash) form of your IP address in memory for up to an hour, never on disk.
- Why: to read and answer your message, and to act on feedback about our games.
- Legal basis (GDPR): our legitimate interest in answering the people who contact us, or steps you ask us to take before an agreement (Article 6(1)(f) and (b)).
- Kept for: up to 2 years after our last exchange, unless we need it longer for an ongoing agreement.
Please do not send us sensitive personal information. If you mention your playtest ID or Google Advertising ID in a privacy-request email, we use it solely to locate and fulfill your request, for example to delete your data.
When you play a prototype
Our games save progress in browser or app storage on your device. We do not receive save files. Gameplay telemetry can include progression and match state described below. Clearing browser site data or app storage removes local files; device or platform backups may restore them according to your settings.
This storage is strictly necessary for the game you asked to play, so it does not need your consent.
Playtest analytics
Our prototypes and early releases use Playtest analytics (Share gameplay data in native builds) to send first-party data about how the game played and ran, so we can fix problems and improve the design.
- In the EU, EEA, UK, Switzerland, unknown regions, and
UTC−1throughUTC+3on native builds: off unless you allow it. - Other known regions: on by default. You can opt out or pause collection at any time. Gameplay analytics stops when you turn it off; necessary pending deletion requests may still be sent.
- If your browser sends a Global Privacy Control signal, browser analytics stays off wherever you are.
Browser playtests use your device's time-zone setting. Native telemetry-enabled builds use region and time-zone settings, treating unknown regions and UTC−1 through UTC+3 as opt-in. We do not look up your GPS location. An unknown browser time zone stays off until permission.
In Wyrd Unbound, where analytics is off unless you allow it, the game asks with a small question in town after your first venture, on at most three launches, and never interrupts play to do so. Not answering counts as no. Everywhere else it is on from the start. In both cases, Share gameplay data in the Pause menu turns it on or off at any time.
Games covered: Patagonia, Rootwardens and Wyrd Unbound. Ordinary Wyrd web/desktop builds do not send analytics. Available fields and controls depend on each build; the game-specific notices explain those differences, including Rootwardens Android's separate Share ad attribution control in the Rootwardens notice.
When first-party gameplay analytics is on, a game may send to our collector:
- Your device and browser: operating system, browser and its version, preferred languages and time zone, screen and window size, pixel density and orientation, graphics card model, number of processor cores, approximate device memory, connection type and approximate speed, whether touch is available, and which website linked to the game (the site name only).
- Native device context, where supported: model, operating system, language/region, time-zone offset, graphics chip, rounded screen information, processor cores and approximate memory.
- Performance and lifecycle: frame rate, slow frames, loading and download information, memory use, measured intervals, foreground/gameplay duration, pauses/resumes and delivery-quality counters. Frequency and available fields vary by game/build.
- Errors: error messages and technical traces when something goes wrong in the game.
- Errors, freezes and crashes, where supported: bounded error details and recent event/error context, freezes lasting at least two seconds, browser/graphics/startup failures, and later-launch reports of an unexpected exit. Supported Android builds can include the platform's prior exit reason, process state and memory information. Reports link the affected session/build; unknown exits and ordinary errors are not automatically confirmed crashes.
- Gameplay: how each run or match went, such as the party or heroes, cards and choices, each fight and card played, buildings, rewards and progress between runs, tutorial milestones, time spent in each area, and your character's position in the game world.
- Ventures and progress (Wyrd Unbound): each venture and how it ended, levels, items found and crafted, weapon and upgrade choices, bosses, quests, travel and deaths, and a detailed combat record of each venture (damage, enemies, abilities and timings).
- Interface: which buttons and menus you use in the game, where on the screen you pressed, and when you pause, switch tabs or leave (in Wyrd Unbound, when the app goes to the background or closes).
- Match replays (Rootwardens): compressed simulation commands, steering and match snapshots to reproduce bugs; not audio/video, physical location or save files. Replay accuracy depends on the matching build/platform.
- Identifiers and build context: random playtest, session and run/incident identifiers; game/build/source version, platform/engine, build-assigned distribution/test-group labels, event time/order, consent evidence and source-quality flags. Test-group labels do not supply names or advertising identities.
First-party game telemetry does not request your name, email, account details, device advertising ID, precise location, contacts or typed messages. Your IP address is necessary to deliver requests and is used transiently to prevent abuse; it is not stored in our analytics database or collector access logs. General website technical logs and Rootwardens Android's separate optional ad attribution are covered specifically in their own sections.
- Why: to find bugs and crashes, to see how the game performs on different devices, to understand how players experience the design so we can improve it, and to build statistical and machine-learning models of how our games are played. Those models are used only inside our studio, to design better games.
- Legal basis (GDPR, for people in the EU, EEA and UK): your consent (Article 6(1)(a)). Reading and storing information on your device for this purpose also requires your consent under EU and UK privacy rules for electronic communications.
- In Japan: the same purposes and sharing choices apply. We normally identify gameplay telemetry by a random ID; if you include that ID in an email, we can link the records to your request. Service providers and any consented Rootwardens Android attribution recipients are described below.
- Kept for: detailed first-party collector records up to 12 months (365 days), then deleted or reduced to statistics that cannot identify anyone.
- If you say no or opt out: nothing changes in the game. You can play every game without analytics or ad attribution.
We do not use first-party gameplay data to make automated decisions about you with legal or similarly significant effects. Raw gameplay, replay and diagnostic records are never sent to an external AI service. The private Foundry dashboard receives aggregates rather than player/session IDs or raw payloads; aggregating or removing an ID alone does not automatically make a record anonymous.
Optional mobile ad attribution (Rootwardens Android only)
Starting with Android 1.0.3, Share ad attribution in Rootwardens Options controls AppsFlyer independently of Share gameplay data. With attribution enabled, AppsFlyer can process the Google advertising ID, App Set ID, AppsFlyer installation ID, Play install referrer, IP address, install and event times and basic device and app information. AppsFlyer uses this information to measure acquisition and help detect install fraud. It can map the IP address to an approximate city, region or country. Basic SDK signals, such as app launch time or battery level, may be used to detect install fraud. It sends AppLovin limited install and early milestone reports for players with attribution enabled, including organic installs and installs from other sources.
AppLovin receives the organic or paid indication, attribution identifiers and the values for First Root tutorial completion and the first Tier 0 clears of Outer Yard and Moss Spring. This helps us see which campaigns reach players who continue playing and helps AppLovin optimize those campaigns. These reports contain no checkout or revenue. Warweaver keeps its first-party player ID, gameplay logs, bug reports, replays, crash logs and performance diagnostics outside this sharing. Optional bug reports go to the studio only when a player sends one.
Attribution defaults off until prior opt-in in the EU, EEA, UK, Switzerland, unknown regions and the additional European time-zone range used by the game. Turning it off stops new attribution reports. To remove prior records, follow the separate gameplay and attribution instructions. Rootwardens data deletion.
Storage on your device
These are all the cookies and similar storage our website and games use.
ww_consentcookie (necessary). Remembers your privacy choice on warweaverstudios.com and play.warweaverstudios.com. It is kept for 12 months, then we ask again. In the EU, EEA, UK and Switzerland, a refusal is kept for 6 months.ww_foundrycookie (necessary, authorized Foundry visitors only). A random sign-in token, restricted to the studio host and Foundry path, inaccessible to page scripts, with a seven-day maximum lifetime. The server also expires an idle session after 24 hours. Signing out removes it.- Game saves (necessary). Stored in your browser's IndexedDB storage by each game on play.warweaverstudios.com, or in private app storage on native builds. Kept until you delete them, clear site/app data, or uninstall.
- Motion setting (necessary). Remembers whether you turned site animations on or off, in session storage. Deleted when you close the tab.
- Game files (necessary). Your browser may keep the downloaded game files in its normal cache so the next visit loads faster.
- Active playtest ID (only while gameplay analytics is on). A random ID in browser/app storage. In Patagonia, Wyrd Unbound and browser playtests, turning sharing off removes the active ID (with Patagonia/earlier Rootwardens retaining a pending-deletion copy only until acknowledged). In Rootwardens
1.0.3+native builds, turning Share gameplay data off pauses new collection, while Delete my data removes the active ID and queues confirmed server erasure. - Wyrd Unbound app storage (necessary). Your saves, settings and privacy choice, in the app's private storage on your phone. Deleted when you uninstall the app.
- Unsent analytics (Wyrd Unbound, only while analytics is on). If you play offline, the app keeps up to 2 MB of analytics it could not send yet and sends it later. Deleted when you turn analytics off.
- Crash record (Wyrd Unbound, only while analytics is on). A small file next to your save noting the game version, its recent game events and errors, and whether it is frozen, so that if it closes unexpectedly, the next launch can tell us. Replaced each time you start the game and deleted when you turn analytics off.
- Newer Patagonia/Rootwardens builds: bounded offline telemetry queues (native 2 MiB) and run/restart markers while gameplay sharing is on. Turning gameplay sharing off discards unsent local queues and markers. Necessary sharing-choice records (
consent_version = 2on supporting Rootwardens Android builds) and pending deletion tokens may remain while sharing is off. - Rootwardens Android ad attribution storage (only while
Share ad attributionis on): the AppsFlyer SDK stores an installation UID and attribution state in app-private storage, and reads Android'sAD_ID(GAID) and Play Install Referrer only when Share ad attribution is permitted. Before opt-in in opt-in regions or whenever Share ad attribution is off, SDK collection is stopped andAD_IDreads are suppressed.
Our website and browser prototypes use no advertising, social media or third-party analytics cookies. Supporting Rootwardens Android builds also read Google Play's install referrer for private first-party campaign measurement while Share gameplay data is on (with no Meta SDK or Conversions API). Only Rootwardens Android's separate, consent-gated Share ad attribution control uses AppsFlyer and AppLovin UA postbacks, as detailed in the Rootwardens notice.
Who we share data with
We do not sell or rent personal data, and we show no third-party advertisements in our website or games. Depending on what you use and allow, data is handled only by:
- Hosting (website, browser prototypes and first-party game collectors): Hetzner Online GmbH (Germany), which runs our servers in Finland on our instructions.
- Email: Google LLC (Google Workspace), which hosts our
games@warweaverstudios.cominbox on our instructions. - AppsFlyer Ltd., based in Israel, processes optional Rootwardens Android install and milestone data to attribute installs, measure campaigns and help detect fraud. AppsFlyer customer data processing.
- AppLovin Corporation, based in the United States, receives the limited install and milestone reports described above for external Rootwardens campaigns. AppLovin privacy policy.
For versions distributed through Google Play, Google separately handles store distribution, installs, ratings and platform diagnostics under its own privacy policy, and advertising platforms separately process ad impressions and clicks on their own services under their own policies. This notice does not mean every game is currently released on Google Play.
We may also disclose information if Japanese or other applicable law requires it, or to protect our rights, our players or the public.
Where your data is processed
Warweaver Studios accesses its systems from Japan. Website hosting and first-party game collectors are in Finland. Google Workspace handles email. If Rootwardens Android attribution is enabled, AppsFlyer Ltd. in Israel and AppLovin Corporation in the United States also process attribution data. Service providers and their subprocessors may process information in other countries.
Where the law requires transfer safeguards, they can include adequacy decisions or contractual safeguards applicable to the recipient. For information about a particular transfer, its destination or a copy of the applicable safeguards, contact games@warweaverstudios.com.
How long we keep it
- Server logs: up to 14 days.
- Emails: up to 2 years after our last exchange.
- Active detailed playtest analytics: up to 365 days from receipt on our Finland collector, then deleted or reduced to statistics that can no longer identify anyone. This includes replay chunks and first-party
install_sourcereports. - Rootwardens Android attribution records. AppsFlyer retention depends on the integration and partner requirements. AppLovin reports that it typically retains service data for up to two years, subject to deletion and legal exceptions. The six-month milestone-reporting window controls which events are forwarded. AppsFlyer retention and AppLovin privacy policy.
- Maintenance backups: restricted to recovery and included in deletion/retention handling. Later deletions must be reapplied before a restore; they are not a separate source for routine analytics.
- Patagonia deletion suppression: a one-way hash of a deleted playtest ID and deletion time, up to 365 days after the request, to reject delayed old batches. It contains no raw ID and is not used for analytics; it remains pseudonymous data.
- Privacy request records: a minimal record for three years after closure; request emails follow the email period above.
- Your privacy choice: 12 months (6 months for a refusal in the EU, EEA, UK and Switzerland) in browser cookies; stored locally in app settings on native builds until cleared or uninstalled.
- Game saves: in your browser or the app, until you delete them or uninstall.
- Playtest ID: active while gameplay sharing is on (or retained while paused in Rootwardens
1.0.3+until you resume or select Delete my data). Necessary pending deletion copies in newer Patagonia/Rootwardens versions remain only until acknowledged or local storage is removed.
Your rights
Depending on where you live, you can ask us to:
- tell you what data we have about you and give you a copy;
- correct it;
- delete it;
- stop or restrict using it, or object to how we use it;
- give it to you in a portable format;
- withdraw consent or opt out of playtest analytics or Rootwardens Android ad attribution. Withdrawing consent or opting out does not affect lawful processing before withdrawal, and you can request deletion of prior records as described below.
In Japan, you can request disclosure, correction, addition or deletion, suspension of use or third-party provision, and disclosure of third-party provision records of your retained personal data, as APPI provides.
To make a request, email games@warweaverstudios.com. Because first-party playtest data is linked only to a random ID, include your playtest ID: each game shows it with a Copy button (in Patagonia under Privacy or Privacy and playtest ID, in Rootwardens in menu Privacy or native Options, and in Wyrd Unbound under Copy ID in Pause). For Rootwardens Android ad-attribution erasure (OpenGDPR), include your Google Advertising ID (GAID) as explained in Rootwardens deletion. We may ask for minimal confirmation that the request is yours, and we answer within one month without a fee.
You can also complain to a data protection authority, for example the authority in the EU country where you live, the Information Commissioner's Office in the UK, or the Personal Information Protection Commission in Japan. We would appreciate the chance to fix a problem first.
Opting out or withdrawing consent
- Website and browser prototypes: open Privacy choices at the bottom of any page on warweaverstudios.com or play.warweaverstudios.com and turn off Playtest analytics. The game stops sending data straight away and deletes its playtest ID from your browser. If you also want server records deleted, copy your playtest ID first, then email it to us.
- Wyrd Unbound: turn off Share gameplay data in the Pause menu. The game stops sending straight away, discards unsent queues, deletes its local playtest ID and sends a best-effort deletion request (if offline, copy your ID first and email us).
- Patagonia: turning Share gameplay data off clears analytics and retries pending deletion when the game runs online.
- Rootwardens (
1.0.3+native builds): turning Share gameplay data off pauses new gameplay collection while keeping prior server history; selecting Delete my data (with confirmation) erases your server gameplay history and retries online until acknowledged. Turning Share ad attribution off stops the AppsFlyer SDK (AppsFlyerLib.stop(true)) and suppressesAD_IDreads; use Android Settings → Ads → Delete advertising ID and see Rootwardens deletion for OpenGDPR attribution erasure.
Clearing storage or uninstalling before an online deletion request completes does not delete records already on a server; use the game-specific deletion guides above whenever completion is uncertain.
Children
Patagonia, Rootwardens and Wyrd Unbound are intended for adults aged 18 and over. They are not designed for children, and we do not offer a parental-consent route for optional game analytics or mobile attribution.
Our games do not independently verify age. Google Play's restrictions depend on the age information available to Google and do not identify every minor. We do not knowingly collect optional game analytics or advertising identifiers from people under 18. If you believe a minor has sent us data, contact games@warweaverstudios.com with the game name and playtest ID or GAID if available. We will investigate and delete linked records we can identify.
How we protect data
We keep what we collect to a minimum and limit who can see it.
- Organisation: one team member is responsible for privacy and for handling requests and incidents. Everyone who can access studio data must keep it confidential.
- Access: only our team can reach our collector and Foundry servers, through key-based SSH and authenticated access.
- Technical safeguards. Data travels over HTTPS. The gameplay collectors validate submissions, enforce rate limits, keep raw databases off the public internet and do not retain IP addresses or advertising IDs. The Rootwardens Android game controls access to the advertising ID with its attribution setting.
- Devices: team computers must use disk encryption, screen locks and up-to-date software.
- Foreign providers: we review the data protection frameworks and contractual safeguards of the countries where processors and consented attribution partners operate.
If a data breach puts you at risk, we will tell you and the relevant authorities as the law requires.
Changes to this policy
We will update this page when our games or services change, and show the new version and date at the top. When a change expands optional collection or adds new attribution recipients (such as Rootwardens Android's consent_version = 2 controls), supporting builds ask for or apply the updated versioned choice before new collection starts.
Questions about this policy: games@warweaverstudios.com.