Alea Iacta Privacy Policy

SWITE Dev is responsible for processing personal data in connection with Alea Iacta. For questions or requests about your data, contact info@swite.dev.

Games and data on your device

Alea Iacta stores your game settings, selected theme and saved local game on your device. The local archive holds up to 500 completed games, including player names, moves and results. Statistics and replays are calculated from those records. We do not upload this archive to an online game archive.

You can delete games from the archive. Clearing app data removes local storage. Your device may include this data in system backups, depending on your Apple or Google settings. If you share a game code, its recipient can read the player names and game information included in that code.

Online multiplayer

We use Google Firebase Authentication, Cloud Firestore and Cloud Functions for online games. The app creates an account with a randomly generated user ID without requiring an email address or password. This ID can link your online activity across sessions; the data is not necessarily anonymous.

We process your chosen player name, user ID, room code, room membership, moves, results and timestamps to run and resume games. Other players in the same room can see names and game information. Share room codes only with people you want to join. Google may also process connection and technical data, including IP addresses and server logs, to operate and secure the service.

Notifications

If you allow notifications, we store a push notification token associated with your account. We send game notifications through Expo Push Service and Apple’s or Google’s notification services. This involves processing the token, message text and a reference to the game room. You can turn notifications off in your device settings. Doing so does not automatically delete the previously stored token from our database.

Purchases and subscriptions

Payments are handled by the App Store or Google Play. We do not receive your full payment card details. We use RevenueCat to verify purchases, unlock paid features and restore purchases.

RevenueCat processes information including a generated app user ID, product and transaction details, purchase and expiration dates, subscription status, and technical information about the app and device. The purchase service may also be contacted when the app starts to check existing access. The purchase identity is separate from your multiplayer account. Apple and Google process payment information under their own terms and privacy policies.

Advertising and privacy choices

When advertising is enabled, Alea Iacta uses Google AdMob to show a banner in Settings. The app requests non-personalized ads. These ads still involve data processing: Google may use IP addresses, device or app identifiers, ad interactions and diagnostic information to deliver and measure ads and prevent fraud. An approximate location may be inferred from your IP address.

Where required, we ask for consent using Google’s consent message. You can change your choices using the ad privacy option in Settings when it is available. Refusing consent does not block gameplay; whether an ad can be shown depends on your choices and the applicable rules. The app does not currently request access to Apple’s advertising identifier through a tracking permission prompt. Banners are not shown when paid access is recognized.

Crash reports

When the app crashes or hits an unexpected error, it sends a crash report to Sentry. A report contains the error and stack trace, app version and build, device model, operating system and language, and a randomly generated installation ID, plus technical events just before the crash, such as app start or going to the background. Reports do not include player names, game codes, account or purchase IDs, or button labels, and we do not store your IP address in them. Our Sentry project stores data in the European Union. Development builds do not send crash reports.

Usage statistics

To see how the app is used, it sends a small set of events to Aptabase: app opened, introduction finished, game started and finished (local or online, number of players and computer players), Themes opened, and purchase started and completed (which product). Each event also contains the app version and build, operating system and version, and language, plus a random session ID that is kept only in memory and renewed after an hour of inactivity. Events do not include player names, game codes, account, purchase or device IDs, or your advertising ID, and the app does not ask to track you. Aptabase derives a daily identifier from your IP address and user agent with a salt that it discards every 24 hours, so events cannot be linked across days or to you. Our Aptabase app stores data in the European Union. You can turn usage statistics off in Settings. The web version does not send usage statistics.

Why we process data

We process necessary game and purchase data to provide the features you use and fulfil purchases. We have a legitimate interest in operating a reliable service, including security, crash reports, usage statistics, troubleshooting and answering support requests. Where processing or access to your device requires consent, we ask for it. You can withdraw consent without affecting the lawfulness of earlier processing. Legal obligations may require us to retain certain records.

Data retention

Local data remains on your device until you delete it, clear app data or older games are replaced because of the archive limit. Online rooms are configured to expire 60 days after the last valid activity; completed games expire after 14 days. Expired room and room-code records are removed through Firebase cleanup. Deletion does not necessarily occur at the exact expiration time.

There is currently no automatic expiration period for accounts or stored push notification tokens. You can ask us to delete this data. Purchase records remain necessary for as long as they are used to verify access, restore purchases, handle disputes or meet legal obligations. Sentry deletes crash reports after 30 days. Aptabase keeps usage statistics for up to 5 years; because they cannot be linked to you, they cannot be deleted on request. Other technical logs are subject to the retention periods of the services involved. Contact us for information about records retained in your particular case.

Service providers and international processing

We use Google Firebase for online games, RevenueCat for purchase management, Expo and Apple/Google for notifications, Google AdMob for advertising, Sentry for crash reports and Aptabase for usage statistics. These providers receive data for the purposes described above. Apple and Google may also act independently for their own services. If you contact us, we and our email provider process your email address and message to respond.

Our game backend is configured in European Google Cloud regions. This does not mean all processing by every provider stays in Europe: support and other services may process data outside the European Economic Area. Such transfers require appropriate safeguards, such as an applicable adequacy decision or standard contractual clauses. You can contact us for information about the safeguards that apply.

For further information, see Google/Firebase, Google, RevenueCat, Expo, Sentry, Aptabase and Apple.

Your rights and how to contact us

You can ask us to access, correct or delete your personal data. Depending on the circumstances, you may also have rights to restrict processing, receive portable data and object to processing based on legitimate interests. Email info@swite.dev and mention Alea Iacta. We may need additional information to locate your records and verify that they belong to you. Do not send passwords or payment card details.

Uninstalling the app does not automatically delete online records or cancel a subscription. Manage subscriptions through your App Store or Google Play account. Some records may need to be retained after a deletion request because of legal obligations or other players’ rights; we will explain this where applicable.

We normally respond to privacy requests within one month. You can also complain to the Dutch Data Protection Authority or your local data protection authority.

Changes to this policy

We update this policy and the date above when our data processing changes. Where necessary, we also inform you about significant changes in the app.