Privacy Policy — Casus Foederis

Version of 19 October 2026 · This policy is also available in Polish.

This policy covers the game “Casus Foederis” for Android (pl.casusfoederis.gra), its browser version, and this website, casusfoederis.com.

Controller: Artur Kwapisz, a private individual publishing as Casus Foederis Studio (“the developer”). Contact: contact@casusfoederis.com.

1. In short

The game has no ads, no user accounts and no analytics or tracking by the developer; it sends the developer no data and sells nothing. You do not need the internet to play; it is needed only to buy and restore the full version. In the Android app the only connections come from the Google Play Billing library, through which the game asks the Play Store about the full version: when you buy or restore it and, in the demo, also when the game starts and when you return to it (point 8). Google handles the payment (point 8) and may receive technical data about how that library performs (point 9); the developer has no access to it. If you buy the full version, the developer sees the order data in Google Play Console (point 8).

This website sets no cookies, uses no analytics or trackers, loads nothing from other servers and has no forms.

2. This website

The website consists of static files. It stores nothing on your device and asks for no data. The website is hosted by Netlify, Inc.. As with any web server, the hosting provider may record technical data of each visit (such as the IP address, time and the page requested) in server logs, for security and to operate the service; the developer has no access to these logs and does not combine them with any other data. If you write to us by e-mail, point 6 applies.

3. Data on your device

Saved games, settings (e.g. language, volume), the chronicle of past games, the log of the game’s technical errors and the record that the full version is unlocked (product name, date and method of unlocking, the last price shown) are stored only in the game’s storage on your device. The developer has no access to them. You can delete them by uninstalling the game or clearing its data in Android settings; a purchased full version comes back after reinstalling, because the purchase is recorded in your Google Play account.

4. Permissions

The Android app declares: internet access and network state (used by the Google Play Billing library to buy, restore and check the purchase and to send technical data to Google, points 8 and 9), the Google Play purchase permission (com.android.vending.BILLING, which lets the game open the Play Store purchase window) and vibration (short in-game signals). The game does not ask for location, contacts, camera or microphone.

5. Android backup

If backup is enabled in your Android settings, the system may store the game’s data (including the record that the full version is unlocked) in your Google account. This is done by Google under its own terms; the developer has no access to that backup.

6. “Report a bug (game save)” and e-mail

At your request the game creates a file containing the current game, game settings, a browser description (which may include the device model and system version), the screen size and the log of the game’s technical errors (the latest program errors: message, place in the code, game version, turn; nothing about you). The file is never sent automatically — you decide whether and to whom to pass it on.

If you send the file or any message to the developer (e.g. by e-mail), the developer uses it and your e-mail address only to investigate your report and reply (legal basis: legitimate interest, Art. 6(1)(f) GDPR), shares them with no one, and deletes them when the matter is closed, no later than 90 days after receipt. Messages are kept in the developer’s mailbox, protected by a password.

7. Google Play and testing

Downloading the game from Google Play is subject to Google’s privacy policy. In Google Play Console the developer sees aggregate statistics (e.g. number of installs) and technical crash reports collected by Google; these do not identify players. During closed testing the developer knows the e-mail addresses of enrolled testers and uses them only to provide the test version and to contact testers about the test; they are removed from the list after testing ends.

8. Full-version purchase

You buy the full version on Google Play. Payment, card details, billing address and purchase confirmation are handled by Google under its own terms (Google Play Terms of Service, Google Privacy Policy); neither the game nor the developer receives this data. The game asks the Play Store only for the price of the full version and whether it is owned on your account; it stores the result on your device, and the game itself sends it to no one (for the Google library’s technical data, see point 9).

In the demo the game asks this on its own, without you tapping anything: when it starts and when you return to it, so that a purchase is unlocked after a reinstall, after redeeming a promo code or after a payment approved later. Once the full version is unlocked these checks stop; only the “Restore purchase” button runs one again.

In Google Play Console the developer sees orders (order number, product, price, date, country, status) and can look up an order by e-mail address if you provide it, e.g. when asking for a refund. The developer uses this only for accounting, refunds and replying to you (legal basis: Art. 6(1)(c) and (f) GDPR) and keeps order data as long as tax law requires (up to 5 years after the end of the tax year).

9. Technical data from the Google Play Billing library

The library the game uses for purchases belongs to Google and runs inside the game. According to Google it records information about its own operation — such as the results of its calls (success or error) and problems connecting to the Play Store — to improve the library and its error handling. It sends this to Google’s servers together with technical data that the transport mechanism attaches to every such upload: device model and manufacturer, Android version, language and country, network type, game version; the server also sees the IP address. The game adds nothing of its own to it, and the developer neither receives this data nor can delete it. Google processes it under its own terms (Google Privacy Policy).

You cannot switch this off inside the game. In the demo the game also connects to the library when it starts and when you return to it (point 8), so an upload can happen without you tapping “buy”.

10. Your rights

For data you have sent to the developer, you have the right of access, rectification, erasure, restriction and objection, and the right to lodge a complaint with a supervisory authority (in Poland: the President of the Personal Data Protection Office, uodo.gov.pl). Write to: contact@casusfoederis.com.

11. Children

The game is not directed at children under 13, and the developer does not collect children’s data. If a child has sent the developer a file or message, a parent or guardian may request its deletion.

12. Changes

Changes are published at this address with a new version date. If a future version of the game were to collect or transmit data in a way not described above, this policy will be updated before that release.