Three Corners Rising · Field notes

What we keep, and what we don’t.

Three Corners Rising has no accounts and no ads, and the browser alpha has nothing to buy. Your chronicle (seals, unlocked missions and any unfinished battle) stays on your device or in your browser. With Share analytics on, the game sends a small amount of anonymous gameplay information, described below.

This website

threecornersrising.com is a static website hosted on Amazon Web Services. To learn how many people visit and what they choose, it uses our own Umami analytics service at analytics.tinymachines.io. It counts page views, the website that sent you here, your browser, operating system, device type, screen size and language, your approximate location, and three named actions: choosing to play the game, previewing a battle image, and following the link to Circle Kingdom Tactics.

Website analytics sets no cookies, does not record your screen and uses no advertising identifiers. Query strings and URL fragments are left out, and the address that referred you is reduced to its website origin. If your browser sends Do Not Track, the tracker sends nothing. The fonts, artwork and video are served from this site itself. Our hosting provider processes the network information needed to deliver the pages. Website statistics are separate from the optional gameplay analytics described below.

The browser game

The game at play.threecornersrising.com is also hosted on Amazon Web Services. It needs a connection to load. Once it is running, it makes no advertising requests and never asks who you are. If Share analytics is on, it sends the gameplay analytics described below; nothing else leaves your browser.

Your progress (earned seals, unlocked missions, an unfinished battle and your sound setting) is saved in your browser’s storage for that address and stays on your device. Clearing the site’s data in your browser removes it. The game also reads your browser’s reduced-motion preference and window size on your device, to decide whether the opening vignette starts paused and how to lay out the page; neither leaves your browser.

Optional gameplay analytics

With Share analytics on, the game sends a small amount of gameplay information to Tiny Machines so we can tune the missions, the lesson and the expansions. The setting starts on. The first time you start the game, a notice tells you so, and nothing is sent until you continue past it. You can turn it off at any time under Privacy on the chronicle page, or under Privacy at the war table, the menu that opens when you pause a battle. Turning it off stops collection, cancels pending uploads, and deletes the analytics identifier and unsent events on your device. If you turn it back on, the game creates a new identifier. Events we have already received expire under the retention period below.

Events cover app sessions and time in the foreground; the screens you open (the chronicle, mission briefings, battles and the field guide); battles started, resumed, left without a result and finished, with the mission, whether it was the lesson, practice or a replay, and how long the visit lasted; wins and losses, and whether a loss came from a fallen banner or the round limit; the round reached, seals earned, villages rescued, whether your leader’s ability was used and whether a win was your first on that mission; and your progress through the lesson’s steps, including skipping its hints. On Android and iPhone/iPad, events also cover expansion pages opened, unlock and restore attempts and their results, and changes in which expansions you own. Each event carries the time it happened, and we receive the platform, app version and distribution store.

Analytics uses randomly generated installation and session identifiers, separate from any store account. We do not collect your name, email, precise location, advertising identifier, hardware identifier, receipt, purchase token, payment details or a recording of your play. We do not sell analytics, use it for advertising, or combine it with information from our other games; Three Corners Rising analytics is kept in its own database.

Storage and retention

Analytics is sent over HTTPS to infrastructure operated for Tiny Machines using Amazon Web Services and our PostgreSQL database. Our internal dashboard reads this data with a read-only account. Raw gameplay events and inactive sessions are removed after 180 days. Infrastructure providers necessarily process network addresses to deliver requests; the gameplay collector does not store them in the analytics database or log request bodies.

While you are offline, unsent analytics waits in a small, bounded queue on your device. Gameplay never depends on an upload succeeding. Clearing the site’s data in your browser, or uninstalling the game, removes your saved progress and settings as well as local analytics data. Your Share analytics choice is one of those settings, so once that data is cleared the setting starts on again.

Email

Messages sent to an address at threecornersrising.com are forwarded to the developer’s own inbox so that we can reply.

Mobile editions

The Android and iPhone/iPad editions save your progress on your device and include the same optional analytics. They also offer two optional expansions, bought through Google Play or the App Store, and report the expansion pages opened, unlock and restore outcomes and ownership changes described above, without store transaction identifiers or payment details. Apple or Google processes any in-app purchase under its own privacy policy. This page covers the website, the browser alpha and the mobile editions.

Questions

For any privacy question or request, write to hello@threecornersrising.com. Gameplay records carry no account name or email, so we cannot look them up by name or email. Turning off Share analytics deletes the identifier on your device; events already received expire after 180 days.

Return to Three Corners Rising