Tirri JamPrivacy contact

PRIVACY / TIRRI JAM

Your play. Your privacy choices.

This policy explains what information Tirri Jam uses, why it is used and the choices available to you.

Effective 4 October 2026

1. Who is responsible

Tirri Jam is operated by MAHADEV LIFESTYLE PRIVATE LIMITED, publishing as Mahadev Dgtly ("we", "us" or "our"). For privacy questions or requests, email mujahid@dgtly.co. This policy covers the game and this support website, not other websites linked from it.

2. Offline play and local information

The offline game stores progress, puzzle attempts, earned rewards, owned cosmetics, restoration progress, language, accessibility settings and other preferences on your device. An offline build does not send this game progress to our backend. Device or operating-system backups may retain their own copies under your device settings.

You can use the game's Settings → Account & privacy → Delete local progress action, clear the app's storage where supported or uninstall the app to remove local information. Local deletion is irreversible. It does not by itself delete an account, records held by a service provider or copies in an operating-system backup.

3. Advertising and Google services

Ad-enabled builds use Google Mobile Ads (AdMob) and Google's User Messaging Platform (UMP). Test ads are not a no-data mode. Depending on the device, permissions and configuration, Google may process your IP address and IP-derived approximate location, device or account identifiers, advertising information, app or ad interactions and diagnostics such as crash and performance information. These are used for advertising, measurement, security and fraud prevention.

We do not promise that an advertising identifier is always available or collected. Device permissions and settings affect what can be used. Our ad integration checks UMP's advertising eligibility before initializing or requesting ads. When required by UMP, the app offers Advertising privacy choices in settings so you can revisit your decision. Your device may also provide advertising-personalization or tracking controls.

The separate gameplay-analytics preference does not switch off all processing by Google. Google handles its own data under the Google Privacy Policy. See Google's Android/Unity SDK disclosure and iOS SDK disclosure for additional details. No rewarded-ad grant is currently enabled.

4. Connected features, when activated

Connected features are not currently live in the default app configuration. If introduced, they may process a pseudonymous player or account identifier, sign-in/link status, cloud-save data, consent records, referral and reward records, operational messages and account-support requests. Sign-in providers may process information under their own policies. We use operational records to provide the feature you request, protect accounts, restore progress, prevent repeated grants and process privacy requests.

Optional gameplay analytics requires a separate choice. It can include session, puzzle, progression, feature-use and ad-observation events, app version, platform and pseudonymous scope/owner information. Analytics uses consent-scoped records; withdrawing that choice stops new optional collection and starts removal of affected records. Operational service records are separate from optional behavior analytics.

Remote notifications, if activated, also need device permission. Notification delivery may require a device destination token, platform and account/device association. Promotional permission is separate from device permission and operational notifications. Tokens are not included in gameplay analytics. You can change notification permission in your device settings and promotional choices in the app when those features are available.

5. Sharing and service providers

Local-only progress is not sent to our backend. In builds with enabled online or advertising features, relevant information may be processed by the providers that deliver those features, including Google for ads and consent, the selected sign-in provider, backend/cloud hosting and notification-delivery providers. Information may be processed outside your country under the provider's arrangements. We may also disclose information when necessary to meet applicable legal obligations, protect users or investigate abuse.

We do not treat a client ad callback as proof of revenue or a verified reward. We do not include raw advertising errors, device notification tokens or email addresses in the ad-observation analytics contract.

6. Retention and deletion

Local progress remains until you delete it or the device removes it. Online records, if enabled, are retained according to their purpose and the applicable service's retention rules. Some consent, security, suppression and transaction/idempotency records may need to remain to prevent deleted data from being restored, fraudulent activity or duplicate rewards. Google and other providers control retention for records they hold.

Account deletion is different from local progress deletion. Where available, use the account/privacy controls in the app or contact us. Removal across connected systems can take time; an offline device or service failure may leave a request pending. We do not promise immediate erasure of every backup or provider-held record. We will explain any applicable retention requirement when responding to your request.

7. Your choices and privacy requests

Depending on applicable law, you may request access, correction or deletion of personal information, object to certain processing or withdraw consent. Email mujahid@dgtly.co and identify the app, requested action and the minimum account information needed to locate the relevant record. Do not send passwords, payment details or unnecessary identity documents. We may ask for proportionate verification before acting on an account request. You may also contact your local data-protection authority where applicable.

Withdrawing optional analytics or advertising consent does not automatically delete all operational records or information already held independently by a provider.

8. General audience and children's privacy

Tirri Jam is intended for a general audience and is not child-directed. This does not mean we verify every player's age or guarantee that no child uses the game. We do not knowingly seek personal information from children below the applicable minimum age. If you believe a child has provided personal information through the app, contact us so we can investigate and take appropriate action. Age and regional consent requirements must be respected when online features are introduced.

9. Website and support requests

This website does not add marketing analytics, advertising scripts, sign-in or forms. Its hosting provider may process request metadata such as IP address, browser information and request time to deliver pages and protect the service. If you email us, we use the information you provide to respond and manage your request. Please share only what is necessary.

10. Security and policy updates

We use controls appropriate to the enabled feature, including scoped access, transport protection and owner/consent checks in prepared connected systems. No device or online service is completely secure. Keep your device and account credentials protected.

We will update this policy and the relevant store disclosures before enabling material new data uses. The effective date above identifies this version. For questions, contact mujahid@dgtly.co.