Tiletrace Privacy Policy

This Privacy Policy explains what information Tiletrace collects, how the app uses it, when it is shared, how long it may be kept, and what controls users have. This document is intended to describe the current app build and should be reviewed again before future releases that add new features, partners, or integrations.

Effective Date May 6, 2026

App Name Tiletrace

Publisher Harsh Patel

Contact terwa.tech@gmail.com

1. Scope

This Privacy Policy applies to the Tiletrace mobile application, including Journey mode, Decipher mode, Challenge mode, Endless mode, Daily Challenge features, leaderboards, profile features, in-app feedback, analytics, crash reporting, remote configuration, advertising, and notification reminders.

2. Summary of What the App Does With Data

Tiletrace stores a large amount of gameplay and preference data locally on the user's device so that the game can work smoothly across sessions. Some optional or connected features use third-party services, including Firebase and Google advertising tools. Depending on the feature being used, the app may:

store gameplay progress, settings, tutorial state, review-prompt state, reminder preferences, and similar app data locally on the device;
create an anonymous Firebase account for app-backed features;
sync selected profile and leaderboard information to Firebase Firestore;
send feedback submissions to Firebase Firestore;
send analytics events and crash reports to Firebase;
fetch configuration values from Firebase Remote Config to control gameplay flags, banners, and ad behavior;
request advertising consent and show Google AdMob ads when ad features are enabled; and
request notification permission and schedule local daily reminder notifications.

3. Information We Collect

3.1 Information stored locally on the device

The app stores data locally so that progress and preferences can be preserved between sessions. Local storage may include:

classic level progress and best local level results;
daily retry counters, rewarded hint counters, and similar game state;
tutorial progress and first-run completion state;
review-prompt state and engagement counters;
settings such as sound, music, haptics, notification preference, reminder time, and color scheme;
dismissed banner state and other interface preferences; and
notification scheduling preferences.

3.2 Anonymous backend account data

Tiletrace uses Firebase Authentication and may sign a user in anonymously. This creates a Firebase UID that is not the same as a traditional email-and-password account. The UID can be used to support profile, sync, leaderboard, feedback, and related app-backed features.

3.3 Profile and leaderboard data

Tiletrace uses Firebase Firestore for profile and leaderboard-related features. Information written to backend profile or score records may include:

anonymous Firebase UID;
a display name generated by the app or later chosen by the user;
experience points, player level, and streak values;
completed classic-level records and related progress data;
settings data synced to the backend profile;
Daily Challenge score, time, and date records;
Daily Deduce completion markers; and
server timestamps and related sync metadata.

Some leaderboard information is intended to be visible to other users of the app. Users should therefore avoid choosing a display name that reveals personal information they do not want displayed publicly.

3.4 Feedback submissions

Tiletrace includes an in-app feedback form. If a user submits feedback, the app may send the following information to Firebase Firestore:

feedback type selected in the form;
the message entered by the user;
the optional contact text entered by the user;
anonymous UID and display name, if available;
platform, app version, and build number; and
server-side creation timestamp.

3.5 Analytics and diagnostic data

Tiletrace uses Firebase Analytics and Firebase Crashlytics. These services may receive analytics events, screen-view data, app version data, device and OS information, crash logs, error details, and related diagnostic data needed to analyze usage, stability, and app quality.

3.6 Remote configuration data

Tiletrace uses Firebase Remote Config to fetch app configuration values. These values may control advertising behavior, rewarded gameplay settings, top-banner content, and certain feature-visibility flags.

3.7 Advertising and consent-related data

Tiletrace uses Google Mobile Ads / AdMob and Google's User Messaging Platform for consent management. Depending on the app configuration, device region, user consent choices, and ad availability, Google and its advertising partners may process device information, advertising identifiers, app interaction data, approximate network information, and consent-related information for ad delivery, measurement, fraud prevention, and related ad operations.

Tiletrace also stores ad-related session state in memory or local app storage, such as ad cooldowns, reward counters, offer eligibility, or reminder flags, so that ad frequency and rewarded gameplay can be managed consistently.

3.8 Notification information

The app may request notification permission so it can send daily reminder notifications. If permission is granted, the app may schedule a local daily reminder. Reminder preference and reminder time are stored by the app.

3.9 Information we do not intentionally request in the current version

The current version of Tiletrace is not designed to collect precise location data, contacts, photos, microphone recordings, or a traditional login identity such as email address or phone number for normal use.

4. How We Use Information

We use information for the following purposes:

to provide gameplay, save progress, and restore state between sessions;
to operate Journey, Daily Challenge, Daily Deduce, and profile features;
to remember settings and tutorial progress;
to provide optional leaderboard, score, and profile sync;
to process feedback submissions and improve the app;
to measure usage and feature engagement;
to detect, investigate, and fix crashes and bugs;
to configure app behavior through remote configuration;
to manage ads, ad consent, and rewarded gameplay flows; and
to schedule and deliver reminder notifications.

5. Legal Bases (EEA, UK, and Similar Jurisdictions)

If privacy law in a user's jurisdiction requires a legal basis for processing, the app generally relies on one or more of the following:

Performance of a contract: to provide requested app features, save progress, and operate profile or sync features;
Legitimate interests: to maintain app security, product quality, fraud prevention, diagnostics, and operational analytics; and
Consent: where required, including certain notification and advertising-related permissions or consent choices.

6. When We Share Information

We do not share user information more broadly than necessary to run, secure, analyze, monetize, and improve the app. Information may be shared with:

Firebase services used for anonymous authentication, Firestore, analytics, crash reporting, and remote config;
Google Mobile Ads / AdMob and related consent and advertising partners;
platform providers such as Apple and Google when the app uses system services such as notifications or store services; and
other users of the app, but only for leaderboard or profile information intended to be public.

We may also disclose information if required by law, lawful request, legal process, or to protect rights, safety, property, users, or the public.

7. Third-Party Services Used by the App

The current app build uses or may use services from the following providers:

Google Firebase Authentication (anonymous authentication)
Google Firebase Firestore
Google Firebase Analytics
Google Firebase Crashlytics
Google Firebase Remote Config
Google Mobile Ads / AdMob
Google User Messaging Platform (consent management)
Expo Notifications and related platform notification services

If users tap external links, including store links, banner links, or other third-party destinations, those services operate under their own privacy policies and terms.

8. Data Retention

On-device data generally stays on the user's device until the user clears app data, deletes the app, or removes specific data through app-provided controls where available.

Backend data such as profile records, leaderboard records, analytics events, crash reports, remote-config related state, and feedback submissions may be retained for as long as reasonably necessary for the purposes described in this Privacy Policy, including operational, security, analytics, recordkeeping, and legal purposes.

9. User Choices and Controls

Users may have the following choices:

disable notifications in app settings or device settings;
change reminder time inside the app;
choose a non-identifying display name for public leaderboard use;
avoid submitting feedback if they do not want to send that information;
use platform privacy settings for advertising permissions and controls where available;
avoid using connected leaderboard/profile features if they do not want backend sync; and
delete the app to remove locally stored data from the device.

If a user wants us to review, correct, or delete backend data we control, they should contact us and provide enough detail for us to identify the record, such as a display name, anonymous UID, approximate date, feedback type, screenshot, or similar context.

10. International Data Transfers

Third-party service providers used by the app may process data in countries other than the user's own country. By using the app, users understand that their information may be transferred to and processed in jurisdictions with different data protection laws.

11. Security

We take reasonable steps to reduce privacy and security risk, but no app, database, network transmission, or storage system can be guaranteed 100% secure. Users should avoid submitting sensitive personal information in feedback messages or public display names.

12. Children's Privacy

Tiletrace is not intended to knowingly collect personal information from children in violation of applicable law. If a parent or guardian believes a child has provided personal information through the app, they should contact us so we can review the issue and, where appropriate, delete relevant data.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will update the Effective Date at the top of this document. Material changes should be reviewed carefully before continued use of the app.

14. Contact Us

If you have privacy questions, access requests, correction requests, deletion requests, or complaints, contact:

Name: Harsh Patel
Email: terwa.tech@gmail.com
Website: https://www.buildingdev.fun/tiletrace

Important note: Tiletrace includes optional online services, ads, leaderboards, and feedback features in addition to local offline gameplay. Users who prefer minimal data sharing should review notification settings, avoid submitting public or identifying profile information, and use privacy controls provided by their device and platform.

This Privacy Policy is provided for general transparency regarding the current Tiletrace app build. It is not legal advice, and it may need to be updated if the app's features, partners, or data flows change.