Courtesy translation. The Spanish version prevails.

TEMPUS Privacy Policy

Last updated: October 22, 2026

TEMPUS ("the app") is an Android deduction game published by Nestor Gerardo Reyes Alanis ("the developer"), contact team@zetashift.app. This policy explains what data is processed when you play, who processes it, and what control you have over it.

1. The honest summary

TEMPUS has no servers of its own and no user accounts. The developer never receives your name, email address, location, contacts, photos, or the contents of your device.

What does happen: the app shows ads, sells in-app purchases, and — when the developer has configured the Firebase project — sends anonymous usage statistics and crash reports. Those three services belong to Google and process data on their own terms, under their own policies. The app needs an internet connection for any of them.

This policy does not claim that TEMPUS is "100% offline" or "ad-free", because that would not be true.

2. Data the app itself handles

Your save file is stored on your device, not on a developer server. It contains:

• Story progress, relics, daily streak, tutorial state, cosmetics, and gameplay stats.
• Eras unlocked with purchases that have already been consumed.
• Your balance of coins and decoder keys, plus the internal ledger that prevents the same purchase from being granted twice.
• A flag for whether you own the permanent upgrades (Lifetime Detective, Remove ads).
• If you choose to sign the dossier, the agent name and gender you type and choose. They are optional and you can change them at any time from the Dossier.

Except for the agent name you type, none of that identifies a person, and none of it is sent to the developer.

3. Google backup (Android Auto Backup)

Android can copy app data to your Google account and restore it when you reinstall or set up a new phone. In TEMPUS that copy is deliberately limited:

• Backed up: player progress (story, relics, streak, tutorial, cosmetics, stats, the eras you have already unlocked and, if you signed the dossier, the agent name and gender).
• Not backed up: your balance of coins and decoder keys, and the internal purchase ledger.
• Permanent purchases do not depend on the backup: Lifetime Detective and Remove ads are restored from your Google Play account, which is where the entitlement you bought actually lives.

That copy is handled by Google under your Google account and under Google's Privacy Policy. The developer cannot read it. You can turn it off in your device's backup settings.

4. Advertising (Google AdMob)

The app shows two formats: rewarded videos, which are always optional and which you choose to watch, and interstitial ads between scenes.

Ads are served by Google AdMob. To do that, Google may process your device's advertising identifier, your approximate IP-based location, device information, and ad interaction data, in order to serve and measure ads and to prevent fraud. The app declares the Android advertising ID permission because the ads SDK requires it.

If you are in the European Economic Area, the United Kingdom, or Switzerland, Google's consent form (User Messaging Platform) is shown when you open the app, before advertising is initialized. That is where you choose whether to allow personalized ads. You can change that choice later from the same form, and you can reset or delete your advertising identifier from your device's Google settings. Where the form is required in your region, Settings shows a "Privacy options" row that reopens it.

Buying Remove ads removes interstitial ads permanently; rewarded videos remain available and remain optional. Buying Lifetime Detective removes all ads: interstitial and rewarded videos alike.

Details on Google's processing: https://policies.google.com/privacy and https://support.google.com/admob/answer/7666366

5. In-app purchases (Google Play Billing)

Purchases are processed by Google Play. The app never sees or receives your card number, billing address, or payment details: it only receives Google's confirmation that a product was purchased, so it can grant what you paid for.

Prices are shown by Play; the product catalog includes permanent unlocks, coin packs, and decoder keys.

Google Play's data handling: https://policies.google.com/privacy

6. Usage statistics and crash reports (Firebase)

TEMPUS includes Firebase Analytics and Firebase Crashlytics, both from Google. These services are active only when the developer includes the Firebase configuration file (google-services.json) in the build. Without that file the calls are no-ops and nothing is sent. The version published on Google Play is built with that file, so they are available, subject to what follows.

Analytics and Crashlytics collection is off by default and is switched on only after Google's consent form (UMP): in the European Economic Area, the United Kingdom, and Switzerland, only if you give consent; where Google reports that consent is not required, it is on; if consent is unknown or you refuse, it stays off. You can change or withdraw your consent at any time from the "Privacy options" row in Settings, which appears only when the form is required.

• Analytics records three anonymous events: reaching the progress wall (the era you tapped), a board report, when you submit one (seed, world, difficulty, and the board of that scene), and clock_jump, sent when the phone's date or time changes abruptly against the device's internal clock (it carries only the direction, forward or back, and a size range such as "under an hour" or "one to seven days", never the date or time itself). The app does not attach its own user identifier to those events and does not send names, email addresses, or text you typed. Google, for its part, may process device and installation identifiers alongside those events. Besides those three, the Firebase Analytics SDK automatically records standard usage events (first open, session start and engagement time: first_open, session_start, user_engagement), not linked to the player's identity.
• Crashlytics sends crash reports: error type, technical stack trace, device model, and OS version. It exists to fix bugs, nothing else.

Details: https://firebase.google.com/support/privacy and https://policies.google.com/privacy

7. No other services

TEMPUS has no social networks, no sign-in, no chat, no third-party content beyond the ads described above, and sends no data to any server other than Google's.

8. Children

TEMPUS is not directed to children under 13, and the developer does not knowingly collect data from children under that age. If you believe a child in your care provided data through the Google services described here, write to team@zetashift.app and the request will be filed with Google.

9. Retention and your control

• On-device data: kept for as long as the app is installed. Uninstalling deletes it. You can also clear it from Android's app storage settings.
• Google backup: delete it from your Google account's backup settings.
• Advertising: withdraw or change your consent from the form described in section 4 (the "Privacy options" row in Settings), and reset your advertising identifier at any time from Android settings.
• Analytics and Crashlytics: TEMPUS has no accounts and the developer cannot identify the data of a specific installation, so it cannot delete it on request. To stop data being sent, withdraw your consent as described in section 6. Data already sent is removed automatically according to the retention configured in Firebase.
• Purchases: your purchase history lives in your Google Play account and is managed from there.

If you are in the European Union or the United Kingdom, you have the rights of access, rectification, erasure, restriction, portability, and objection regarding personal data concerning you. Since there are no accounts, what you can delete you delete yourself on your device and in your Google settings, as described above; for any question about this policy, write to team@zetashift.app.

10. International transfers

The Google services described here may process data on servers outside your country, including the United States, under the safeguards Google declares in its own privacy policy.

11. Changes to this policy

If the processing changes — for example, if a service is added or removed — this policy is updated and the date in the header changes. The current version is always the one published on the developer's site.

12. Contact

team@zetashift.app