Ashen Swarm — Gameplay analytics privacy notice
Controller: Ashen Depths Studio
Contact: support@ashendepths.com
This notice covers optional gameplay analytics in Ashen Swarm and the Ashen Swarm demo. We use GameAnalytics to understand how people progress through the game and to improve the experience.
Your choice
Analytics is voluntary and based on your consent. You can play without enabling it. GameAnalytics does not start before you agree, and the game does not keep a backlog of gameplay events from before your consent. If you agree, your choice is remembered and analytics can start automatically on later launches.
You can withdraw consent in Settings → Gameplay analytics. This stops new gameplay events and disables the SDK's event submission. A request already in progress may finish; the SDK may still exchange configuration information until you exit. After restarting with analytics off, GameAnalytics does not start. If you switch it back on after withdrawing consent during the same launch, you need to restart the game.
Information collected
- Gameplay: reaching the menu; starting or resuming a run; the selected hero and Oath or Unbound path; survival milestones and elapsed time; the first upgrade; SALIGIA events and choices; and run outcomes. We also measure progress through the first run observed after consent and whether another run follows.
- Technical information: game, engine and analytics SDK versions; platform and operating system version; device model and manufacturer where available; event times; and session identifiers, counts and duration.
- A random analytics identifier that can persist between sessions. It is pseudonymous: it links activity without using your name. Our analytics integration does not attach your Steam ID, Steam name or email address. See GameAnalytics' identifier documentation.
GameAnalytics receives your IP address when your device connects. Its collection documentation says it uses the IP to determine your country and does not store the IP on its servers. GameAnalytics: country lookup.
The gameplay events do not contain your written messages or full game saves. Technical field categories are described in the GameAnalytics collection protocol.
Local storage and switching analytics off
The game stores your consent choice, its update time and version, and markers for the first observed run and the following run in local settings. These values have no automatic expiry and are not cleared when you switch analytics off.
While analytics is enabled, the SDK can store events locally to send later. Switching it off does not immediately delete that queue. If you later enable analytics again and restart, the game deletes the previous queue database and its journal files before restarting GameAnalytics. If cleanup fails, analytics stays off for that launch. If you never enable it again, those files can remain on your device without an automatic expiry.
This cleanup does not delete your game saves or other local settings. Switching analytics off does not automatically delete information already received by GameAnalytics. Contact us if you want to request deletion.
Service provider and storage periods
GameAnalytics processes analytics for us. Its published terms describe US processing and safeguards including EU standard contractual clauses and UK transfer arrangements. GameAnalytics DPA, §6 and Exhibit A.
Its published retention schedule lists raw/annotated data: 1 month; Player Warehouse: 1 year; Player Lookups: 18 months, with exceptions for legally required copies. These are the provider's separate categories, not one expiry date for every record. GameAnalytics DPA, §8.
Questions and your rights
Contact support@ashendepths.com for privacy questions or access and deletion requests. We may need additional information to locate records associated with your random analytics identifier.
Depending on applicable law, you may request access, correction, deletion, restriction or a portable copy of your data, object where applicable, withdraw consent, and complain to a data protection authority. European Commission: data protection rights.