Waystone (dev.nattle.waystone) is developed by Nattle. This policy applies to the Waystone Android and iPhone apps and explains what information they handle, why it is used, and the choices available to you.
Information stored on your device
Waystone stores certain information locally on your device so that the app can function, including:
- Imported tracker packages
- App preferences, including your leaderboard-contribution choice, and cached tracker state and progress
- Archipelago server addresses, slot names, and passwords that you enter
This information remains in the app’s private storage unless you choose to connect to an Archipelago server, as described below. Waystone does not send your Archipelago server address, port, slot name, password, player name, chat, tracker progress, or imported tracker-package contents to analytics, crash reporting, or the public leaderboard.
Leaderboard contributions
Waystone operates a popular-games leaderboard. Leaderboard contribution is enabled by default. When it is enabled, successfully connecting to an Archipelago game using a tracker package from Waystone’s curated catalog sends one contribution containing the catalog game identifier. Games using manually imported tracker packages are not included.
You can turn off leaderboard contribution at any time in Waystone’s settings. While it is off, Waystone does not record future contributions for your games, but you can still view the public leaderboard. Turning it off does not remove games already included in aggregate leaderboard totals.
The public leaderboard contains only a catalog game identifier, its aggregate play count, and an update time. It does not contain player names, accounts, installation identifiers, Archipelago connection details, or individual gameplay history.
Android and iPhone leaderboard processing
Android and iPhone use the same Waystone leaderboard service. An eligible contribution sends only the catalog game identifier. It does not include an account, advertising identifier, or stable device or installation identifier. Waystone does not send the Archipelago server, room, seed, slot, player, password, chat, tracker progress, or package contents with the contribution.
Like any internet service, the service receives temporary request information such as an IP address, request time, and HTTP metadata for delivery, abuse prevention, security, and troubleshooting. This request information is not published in the leaderboard or used for advertising or cross-app tracking. Data sent to the service is encrypted in transit.
Crash reporting and reliability
On Android, Waystone uses Firebase Crashlytics to identify and fix crashes, non-fatal errors, and application-not-responding events. Crash reporting is enabled when the app is installed.
Crashlytics reports may include technical crash context such as the app version, Android version, device and operating-system state, time of the event, stack traces, a random Crashlytics installation identifier, and a Firebase installation identifier. Waystone does not set a Firebase user ID or attach connection or gameplay details to crash reports.
Waystone does not intentionally send your Archipelago server address, port, slot name, password, player name, chat or other free text, tracker progress, or raw tracker-package contents to Crashlytics. Production logs are redacted so those values are not included as diagnostic breadcrumbs.
On iPhone, Waystone does not use Firebase Crashlytics. If you enable Apple’s option to share analytics and diagnostics with app developers, Apple may provide Nattle with crash and performance information under Apple’s privacy terms. Nattle uses any diagnostics it receives only to maintain and improve Waystone.
Archipelago connections
When you choose to connect to an Archipelago server, the app sends the connection information and gameplay messages required by the Archipelago protocol directly to that server. The server is operated by a third party or by the person hosting it. Its handling of that information is governed by the server operator’s practices, not this policy.
Secure connections are used when supported by the selected server. A custom server may permit an unencrypted connection, depending on the address and protocol you choose.
Service providers
For leaderboard requests on Android and iPhone, and crash reporting on Android, Google processes database, request, crash-reporting, and related technical information on Nattle’s behalf to provide and protect Firebase and Google Cloud services. This can include service and operational data such as IP addresses and request metadata; Android Crashlytics also processes the identifiers and crash context described above. For more information, see the Firebase Privacy and Security documentation and the Google Privacy Policy.
On iPhone, Apple processes App Store distribution information and any optional analytics or diagnostics you choose to share under the Apple Privacy Policy.
Data retention and deletion
Locally stored information remains on your device until you clear Waystone’s app data or uninstall the app. Leaderboard request information is retained only as long as reasonably needed for delivery, abuse prevention, security, and troubleshooting. Android crash reports and their associated identifiers are retained according to the configured Firebase Crashlytics controls and only as long as reasonably needed to maintain and troubleshoot the app. Aggregate leaderboard counts may be retained indefinitely because they do not contain user identifiers.
Waystone does not create user accounts. Nattle therefore may not be able to associate a contribution or diagnostic event with a particular person. Clearing the app’s data resets locally stored app data, and uninstalling the app stops future collection. You may contact Nattle with a data question or deletion request using the address below.
Children’s privacy
Waystone is not directed to children under 13, and Nattle does not knowingly collect personal information from children. If you believe a child has provided personal information through Waystone, contact Nattle so the issue can be investigated.
Changes to this policy
This policy may be updated when the app’s features or data practices change. The effective date above will be revised when an update is published.
Contact
Questions about this policy can be sent to: contact@nattle.dev