Legal

This page covers the public website and the optional play data the game can send. The game Where the Arc Falls has a separate license in its release package.

Website analytics

The public site uses Google Analytics to count visits and the clicks that matter for the playtest funnel (trailer, demo, signup). Google may set cookies. This is separate from in-game play data, which is off until you choose to share it inside the game.

Play data in the game

Last updated: 2026-10-21. Disclosure version: 1.

Why this data is collected

Optional gameplay data is used to understand how players progress through Where the Arc Falls, where they encounter difficulty, and where they stop playing.

What may be collected

When you choose to share play data, the game can send:

play sessions, including the room where a session ends
rooms or areas visited, and how long a visit lasted
progression through the demo and through Chapter I story steps
puzzle opens, attempt counts, and puzzle completion
item pickups, removals, combinations, and item use
examine and interact actions
dialogue starts, skips, and choices, where those actions are instrumented
save activity as a session summary, and each load
places where play sits idle, the same spot is examined repeatedly, or the same item is tried on the wrong spot
end-of-demo answers, only while sharing is on (whether you want another chapter, a rating from 1 to 5, or a skipped rating) and whether the closing link or finish button was used. If sharing is off, those questions are not asked; the card points to itch.io for a rating or a reply

Frame-rate and load-time samples are sent only while a diagnostic toggle is on. They are off during normal play. The game also turns off the analytics service's built-in frame-rate and memory health events.

While a save is active, events can include a playthrough bucket (playthrough_0 through playthrough_18, or playthrough_other). That bucket is not a name.

What is not required

no player name
no account
no email address
no questionnaire responses sent through gameplay data

The share / decline choice itself is not sent as a gameplay event. The time of the choice and this disclosure version stay on the device.

Analytics service

The current analytics service is GameAnalytics. The game does not send play data to any other analytics service.

This service may change in the future. If the collection or processing materially changes, this disclosure should be updated and its version bumped.

With each session, that service also receives its usual session fields: platform, operating-system version, device, manufacturer, engine version, SDK version, build, and session number. Device and manufacturer can be reported as unknown.

Player identifier

The game does not set a custom player id. When sharing is enabled, the GameAnalytics SDK generates a random id, stores it on the device as default_user_id, and sends it as user_id. The game copies that same value into a player_id field on some end-of-demo events. The id groups events from one installation across sessions. It is not a name, email, or account. This page does not describe the id, or the play data, as legally anonymous.

When data is sent

No gameplay data is sent until you explicitly choose to share it. If you decline, gameplay data stays off. If you later turn sharing off in Settings, further submission stops. Turning it back on uses the same choice and starts sending again.

Changing the choice

You can turn Share optional gameplay data on or off from the game's Settings screen. The first-launch choice is Share play data or No thanks. Either choice continues into the game.

Copyright

LICENSE (full text)