Privacy Policy — Trust Issues

Effective date and last updated: 22 October 2026

Trust Issues is published by Shabbir Nuruddin ("we", "us", or "our"). Contact: nuruddinshabbir3@gmail.com.

1. WHAT THE GAME DOES NOT REQUIRE

The Game does not require an account, real name, email address, phone number, payment information, precise location, contacts, camera, microphone, or access to personal photos and files. Optional rewarded advertisements can provide a campaign floor skip or extra lives in Free Play. The Game does not currently offer in-app purchases. Ads are not required to keep playing or retry Castle floors.

2. INFORMATION STORED ON YOUR DEVICE

The Game stores progress, unlocked floors, deaths, checkpoints, achievements, best runs, Blood Shards, cosmetic ownership, equipped items, challenge codes, audio and visual preferences, a randomly generated safe nickname, and daily-play streaks using local app storage. This data normally remains until you clear the Game's storage or uninstall it, subject to Android backup settings.

3. INFORMATION SENT OFF YOUR DEVICE

Optional Android gameplay analytics: After you choose Allow analytics, Google Analytics for Firebase measures visits, active users, returning players, engagement and retention. We also send gameplay events such as mode and difficulty chosen, floor started or completed, checkpoints, death cause, time on a floor, run results, and optional ad and reward outcomes. Firebase processes a pseudonymous app-instance identifier and technical context such as app version, device model, operating system and language. IP addresses may be used to derive approximate location. We do not request precise location.

Firebase analytics is off until you make an affirmative choice. Declining has no effect on gameplay or available rewards. We disable Advertising ID collection and advertising personalization signals for Firebase analytics. We do not set a Firebase user ID or send nicknames, our studio gameplay identifier, session or run identifiers, map codes, or death coordinates to Firebase. Identifiers used by AdMob are governed by the separate advertising choices below.

Google processes Firebase analytics data to provide our analytics reports, including daily and weekly activity and retention. We use the reports to improve the Game's difficulty, usability and stability. We do not sell gameplay analytics. Firebase provider information: https://firebase.google.com/support/privacy and https://policies.google.com/privacy

Turning it off: open Settings > Data & legal > Gameplay analytics. Turning this off stops Firebase analytics collection, clears pending game events and local Firebase analytics data, and resets the Firebase app-instance identifier. This does not itself delete previously uploaded data. This switch does not control the separate ad provider; use Ad privacy choices when available.

Deletion: Settings > Data & legal > Copy gameplay data ID copies the studio gameplay ID and, when Firebase is enabled and ready, the Firebase app-instance ID. Copy these before turning analytics off if you want us to identify previously uploaded data. Email nuruddinshabbir3@gmail.com with the available IDs for an access or deletion request. Contact us if you need help locating them.

Earlier releases and other platforms: These may use our studio analytics service instead of Firebase. Their gameplay events can include a randomly generated studio identifier, screen size, a periodic heartbeat and death coordinates within the game. The studio identifier is not the Android Advertising ID and is not linked to an account, name or email. Data is sent over HTTPS to our access-controlled database. The analytics switch in older releases is labelled Anonymous stats.

Leaderboards and death echoes: When active, the Game uploads your score, the floor reached, your generated in-game nickname, and the location on the floor where you died, so other players can see ranked scores and tombstones. Nicknames are generated by the Game and cannot be freely typed, so they contain no personal information.

Live multiplayer: When you choose to host or join a race, the Game connects to Photon, operated by Exit Games GmbH. Photon processes the room code, the automatically generated nickname, network and connection information, and the real-time gameplay state needed for the match. The other player in the room receives relevant movement, score, and match actions. Photon may process IP addresses under its own privacy policy. If you never open multiplayer, the Game makes no connection of this kind.

Device services: Optional story narration uses the Android Text-to-Speech service. Depending on the installed provider, narration may be processed locally or by that provider. Sharing uses Android's share sheet and the app you select handles the shared material.

OPTIONAL REWARDED ADVERTISING

If you choose Watch ad, Google AdMob and Google's User Messaging Platform provide the advertising and applicable consent messages. No ad reward is granted unless the SDK reports that the reward was earned. Ranked runs and practice do not offer ad-based extra lives.

Google's advertising SDK may collect and share IP addresses (which can imply approximate location), ad interactions, diagnostics, and device or advertising identifiers for advertising, measurement and fraud prevention. Relevant choices depend on your region, consent status, device and Google's configuration. You can decline an ad and keep playing without its reward. Where required, Settings > Data & legal > Ad privacy choices reopens Google's privacy choices.

AdMob provider information: https://policies.google.com/privacy and https://developers.google.com/admob/unity/privacy/play-data-disclosure

4. PURPOSES AND PROVIDERS

We use information to operate gameplay and multiplayer, save progress, improve difficulty and stability, and provide optional advertising and its rewards. Google provides Firebase analytics and AdMob advertising, which have separate collection choices. Photon provides multiplayer networking. These providers may process information in other countries under their own policies and applicable privacy protections. We do not sell gameplay analytics.

5. RETENTION

Firebase event- and user-level data follows the retention setting in our Google Analytics property. Aggregated reporting may be retained longer under Google's policies. The retention limit for raw gameplay events held by our studio service is 24 months; older records are deleted through server maintenance. Leaderboard and death-echo records persist while the feature is live and are deleted on request. To identify your records, use Copy gameplay data ID and include the available IDs in your email to us.

Photon holds match and connection information under its own retention schedule; we do not keep a copy. Local progress remains on your device until you clear storage, reset progress, or uninstall. Advertising-provider retention is described in Google's policies.

6. YOUR CHOICES AND RIGHTS

You can decline analytics on first launch or turn it off in Settings > Data & legal > Gameplay analytics, avoid multiplayer entirely and play the Game offline, mute narration in Settings, clear local data through Android Settings, or uninstall the Game. Older versions label the analytics switch Anonymous stats.

To access or delete analytics data, email nuruddinshabbir3@gmail.com with the available studio gameplay and Firebase app-instance IDs; contact us if you need help locating them. Depending on where you live, you may have additional access, correction, deletion, restriction, portability, objection, consent-withdrawal, or complaint rights.

7. CHILDREN

Trust Issues is not directed to children under 13 and should not be used below the minimum digital-consent age that applies where the player lives without permission from a parent or guardian. If you believe a child submitted information in violation of law, contact us so we can investigate and delete it where appropriate.

8. SECURITY AND CHANGES

Analytics events are sent over HTTPS and processed by Firebase or our access-controlled studio service, as described above. Multiplayer traffic uses Photon's secure transport where supported. No method is completely secure. We may update this policy when the Game, providers, or legal requirements change, and the date above identifies the latest version. If a future version begins collecting additional information, we will update this policy and the store listing before release.

9. WEBSITE COOKIES AND LOCAL STORAGE

Our public developer and privacy-policy pages do not embed advertising or analytics scripts, and we do not set non-essential tracking cookies on those pages. The pages are hosted by GitHub Pages and Vercel. Hosting providers may process normal request information, such as IP addresses, browser information and security logs, to deliver and protect their services under their own policies and retention schedules. Provider information: https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement and https://vercel.com/legal/privacy-policy

The Android Game uses app storage for progress, preferences, consent choices and SDK identifiers, as described above. These are app-storage mechanisms rather than cookies set by our public web pages. Google's advertising and consent SDKs may read or store identifiers and consent signals according to the applicable choices and Google's policies. Links to Google Play or other external websites take you to services governed by their own privacy and cookie policies. Browser cookie controls do not replace the Game's analytics or advertising privacy controls.

CONTACT

Shabbir Nuruddin
nuruddinshabbir3@gmail.com