Privacy policy

This policy explains what data Prismloot (the iOS and Android game and this website) processes, why, who it is shared with, and how you can delete it. It describes what the game does today; the game is in development and internal testing, and we will update this policy when that changes.

Summary

• To play, we do not ask for your name, email or phone. The game creates an anonymous account when it opens.
• We store your progress on our server so you do not lose it and for the leaderboards.
• The only things other players see are your made-up display name, your tag, your depth record and your collection; and, if you join a clan, its members also see when you last played and whether you hit the boss that week.
• The game’s analytics and crash reporting only switch on if you say yes on the in-game card, and you can turn them off in Settings.
• If you buy Plus, Apple or Google take the payment (we never see your card) and RevenueCat tells us whether you have it.
• You can delete your account and data from inside the game.
• This website uses no cookies and does not track you across pages.

1. Who is responsible

Quique Tortosa, solo developer, Denia (Spain).

For any privacy matter, write to: softwareqts@gmail.com

2. Game data

Anonymous account

When you open the game, an anonymous account is created with Firebase Authentication (Google). It is a random identifier, with no name or email. It is used to recognise your progress every time you open the game.

Checking that the app is genuine

To prevent abuse, the server only answers the genuine app. We use Firebase App Check, which relies on App Attest (Apple) on iOS and Play Integrity (Google) on Android. Apple or Google exchange technical device and app data with Firebase to issue that check; we do not receive that data directly.

Your progress

We store on our server what is needed for your progress to exist and be verifiable: your items and gear, dust, medals, depth record, collection, number of runs, your automatic-salvage settings and your attempts against the weekly boss (best result and floor). It is stored against the identifier of your anonymous account. Each phone also carries its own random identifier, used so that the same action is not applied twice if a request is sent again. The game talks only to our server, never directly to the database.

Saving your progress with Apple or Google (optional)

You can link your account with Apple or Google to recover your progress on another phone. Linking only adds another way to sign in to the same progress: it never overwrites it or merges it with another. With Apple, we do not ask for your name or email. With Google, the game requests the basic identity and email permission, so Firebase Authentication stores the identifier of that Google account and its email address (and, on Android, Google may also include your name and profile photo in the sign-in token, which Firebase may keep). The game does not use or show that data to anyone: Firebase only needs it to recognise your account when you sign in again.

Public name and leaderboards

You start with a made-up display name (and a tag like #4821). You can change it, for free every 30 days. Do not put personal data in your name: every player sees it on the leaderboards, together with your tag, depth record and collection. Other players see a public identifier derived from yours, not your account identifier. The server filters offensive words in names.

Clans

From level 20 you can create or join a clan (up to 20 players). Our server stores what the clan needs: its name, tag, language, whether anyone can join, who leads it and, for each member, their public identifier, name, when they joined, when they last played and how much they hit the weekly boss. Also each week’s bars and tier (the last 8) and requests to join (with the requester’s name, record and power).

• Clan members see your name and tag, when you last played (approximately: today, yesterday, a few days ago) and whether you hit the boss that week. If you ask to join a closed clan, its leader sees your name, record and power.
• There is no free-text chat in clans: members can only send 8 phrases written by us. We keep the clan’s last 30, with who sent each one and when.
• Every player can see the clan’s name and tag (in the clan search and leaderboard, and the tag next to its members’ names). Do not put personal data in them. The server filters them like names.

Before you set a name or create a clan, the game asks you to accept the community rules.

Reports

You can report a player’s name (from the leaderboard or your clan) and a clan (from the clan search or leaderboard). We store who reports, whom, and the reported name or tag, to prevent repeated reports and to review them by hand. If a name or a clan is reported by three players with some experience in the game, it reverts to a made-up name (and, for a clan, a made-up tag); reports from newly created accounts are stored and reviewed, but do not count towards that change. Whoever reports a name or clan stops seeing it on their phone.

Automated decisions

The offensive-word filter on names and tags, and the switch to a made-up name when three different players report it, are automatic, but they only affect the name and tag shown to other players. We also review reports by hand, and you can write to us so that we look at your case.

Technical server logs

When the game talks to our server (on Google Cloud), the service logs technical data about each request, such as date and time, IP address, path and result. We use them for security and to detect faults. With our configuration they are kept for about 30 days.

Purchases (Plus)

You can buy Plus from the in-game Shop, monthly or forever. The payment is taken by Apple (App Store) or Google (Google Play): we never see your card or payment details. To know whether you have Plus we use RevenueCat, which receives the purchase receipt from the store and links it to your anonymous account’s identifier (the same Firebase one, with no name or email). RevenueCat stores the product bought, the purchase, renewal or expiry dates, the store, the country and currency, the subscription status and technical data about the app and the device (system, app and library versions, and language). Our server asks RevenueCat whether you have Plus and until when, and stores that with your progress.

If you do not want to give us your data

To play with your progress saved on the server, the game needs the anonymous account and your progress data: without them it does not work. Linking with Apple or Google, choosing your own name, buying Plus and joining the waitlist are optional.

Analytics and crashes

After your first few runs, the game asks you once whether we may send data about how you play and about crashes. Unless you say yes, nothing is sent, and you can change your answer at any time in Profile › Settings › “Play and crash data”. Your answer is stored on your phone.

If you say yes:

• Firebase Analytics (Google) receives pseudonymous usage data: when you open the game and how long you play, the end of each run (which floor you started from, how many you cleared and whether it was a record) and which doors you pick. It is tied to an Analytics installation identifier, not to your account, name or email. Google infers a rough location (country or region) from your IP address and collects device data such as model, operating system and language.
• Firebase Crashlytics (Google) receives crash reports: what happened, where in the code, and on which device and version.

We use them to fix bugs and improve the game. They are not used for advertising or cross-app tracking. Google keeps Analytics data for the property’s retention period (currently the default: 2 months) and Crashlytics reports for 90 days.

What we do not do

We do not ask for your location, contacts, camera or microphone. We do no advertising tracking. We do not sell your data. Today the game shows no ads; if it ever does, this policy will be updated beforehand and will name the providers.

3. Why we may process your data

• Playing, saving your progress, your public name, clans and the leaderboards: this is the service you ask for by using the game (performance of a contract, GDPR art. 6.1.b). The same goes if you link your account with Apple or Google.
• Purchases (Plus): giving you what you bought (performance of a contract, art. 6.1.b).
• Checking the app is genuine, filtering names, handling reports and keeping the server’s technical logs: our legitimate interest in preventing fraud and abuse and keeping a safe environment (art. 6.1.f).
• The website waitlist: your consent (art. 6.1.a), which you can withdraw at any time by unsubscribing.
• Analytics and crash reports in the game: your consent (Art. 6(1)(a) GDPR), given on the in-game card and withdrawable in Settings.
• Technical hosting logs of the website: our legitimate interest in the security and proper working of the site.

4. Where it is stored and who processes it

• Google (Firebase and Google Cloud): the progress database is in the Europe multi-region (eur3) and the game server in Belgium (europe-west1). Google acts as a data processor and offers contractual safeguards for the case that any data leaves the European Economic Area. The website is also hosted on Firebase Hosting.
• Apple and Google (app checks and sign-in): they may process data in other countries as part of their own services (App Attest, Play Integrity, “Sign in with Apple” and with Google). They are governed by their own privacy policies.
• RevenueCat (purchases): a company based in the United States (RevenueCat, Inc.). It processes purchase data as our data processor, under a data processing agreement that is part of its terms and includes the European Commission’s standard contractual clauses (Decision 2021/914) for that transfer to the United States.
• Buttondown (the website waitlist): a company based in the United States (Richmond, Virginia). If you sign up, your email is stored and processed there. Buttondown provides the service as our data processor, under a data processing agreement (DPA) that includes the European Commission’s standard contractual clauses (Decision 2021/914, module 2) for that transfer to the United States.
• We do not share your data with anyone else and we do not sell it.

5. How long

We keep your progress for as long as your account exists. Today there is no automatic expiry of anonymous accounts: they are kept until you delete them. Reports are kept as long as the accounts involved exist. A clan’s data is kept while the clan exists: its weekly history, the last 8 weeks, and its phrases, the last 30. When the last member leaves, the clan is deleted; if it had hit the boss that week or has history, it is kept closed (no members, no tag and out of the search) with its weekly history, which says who counted for each reward, so that the reward can be paid; 8 weeks after its last week, it is deleted. Your purchase data at RevenueCat, also as long as your account exists; Apple and Google keep theirs under their own policies. If we ever add expiry for inactivity, we will say so here and in the game.

6. How to delete your account

In the game: Profile › Settings › Delete account, in two steps. This deletes:

• your progress on the server (items, dust, medals, name and leaderboard position);
• your clan data: you leave the clan, and your phrases and your request to join are deleted (if you were its last member, the clan is deleted or closed as described in section 5);
• the reports you made or received;
• your Firebase user;
• your purchase record at RevenueCat;
• the progress saved on your phone.

If you had linked Apple, the “Sign in with Apple” permission is revoked first. Deleting your account does not cancel a Plus subscription: cancel it in your App Store or Google Play account. Plus forever comes back on the new account with “Restore purchases” in the Shop. The game then starts again with a new, empty anonymous account. If you cannot access the game, write to the contact email and we will delete it for you.

7. Your rights

You can ask for access, rectification, erasure, restriction, objection and portability of your data, and withdraw your consent where we asked for it. Write to the contact email: we will answer within one month. If you think we have not handled your data properly, you can complain to the data protection authority of your country (in Spain, the Agencia Española de Protección de Datos, aepd.es).

8. Children

Prismloot is meant for people aged 13 and over. In Spain, giving your consent on your own (for example, to join this website’s waitlist) requires being 14: if you are younger, you need the permission of a parent or guardian. If you think a minor has given us their data without that permission, write to us and we will delete it.

9. This website

• No cookies. We use no tracking or advertising cookies. We store in your browser (local storage) only your light or dark theme choice, and only if you change it yourself.
• Optional analytics with Umami, cookie-free and without storing personal data or your IP address; it honours your browser’s “Do Not Track” signal. It only loads if it is enabled: the current status is shown at the top of this page. It counts visits per page, where they come from, language and device type, plus two clicks (on “Join the beta” and on the form submit) to know how many people reach the list. If we use Umami Cloud, Umami Software acts as data processor. The legal basis is our legitimate interest in knowing how the site is used and improving it.
• Beta waitlist (Buttondown). If you sign up, we process your email to tell you about the beta and important news. We use double opt-in and you can unsubscribe from any email. The legal basis is your consent. Buttondown is our data processor. We keep your data until you unsubscribe.
• Hosting. The site is served from Firebase Hosting (Google), which may log technical connection data, such as your IP address, in its server logs.
• Fonts are served from this site itself, with no calls to Google Fonts or other external services.

10. Changes

If we change this policy in a significant way, we will say so here and in the game. The date of the last update is shown above.