← Back to Grave Shift

Pipapps · Grave Shift

Privacy Policy

Last updated: 24 October 2026

Lisa Petz, an individual trading as Pipapps in Austria, is responsible for the personal data described here. This policy covers Grave Shift and its landing website. For privacy questions or requests, email pipapetzolmos@gmail.com.

1. Age and local game information

The game is for people aged 16 or older. Before gameplay begins, it asks whether you are under 16 or 16 or older. The game stores only that choice locally, not your birth date or exact age. An under-16 answer blocks gameplay. We do not send this age choice as an analytics event.

Progress, preferences, and privacy choices are stored on your device. Local storage supports the game and remembers your choices. Settings → Data contains the account-deletion control. Deletion removes local progress and preferences after the backend confirms the account deletion; an internet connection is required.

If you allow notifications through your device’s permission prompt, the game schedules reminders locally for offline progress, daily rewards, new seasons, and Blood Moon availability. This feature does not register a remote push token or send your reminder schedule to a messaging backend. You can turn notifications off in your device settings without affecting gameplay.

2. Game services

Eligible players may be assigned a pseudonymous Firebase Authentication identifier without supplying an email address or password. Firebase processes technical information such as IP addresses and device/request information to provide and secure authentication. A pseudonymous identifier is not necessarily anonymous personal data. Your saved game remains on your device.

The online leaderboard stores your player display name, best night, seasonal progress, collector score, season identifiers, and submission times with your Firebase identifier. Your display name, scores, and ranking can be shown to other players. Please avoid using your real name or other personal information as your display name. Firebase also stores seasonal reward claims to prevent duplicate claims. These game services operate separately from optional analytics.

3. Optional gameplay analytics

Gameplay analytics is off unless you enable it. If enabled, Google Analytics for Firebase receives a limited set of journey events, such as cemetery milestones, event starts and completions, collection milestones, cremations, and offline rewards, alongside SDK information such as app version, device characteristics, app-instance identifiers, sessions, and approximate region. Our custom events do not include your name, email, exact age, free-text messages, saved-game contents, or Firebase account ID.

With analytics enabled, we also measure purchase and advertising revenue to understand how the game supports its running costs. Purchase measurement can include the purchased product, transaction information, price, and currency. Advertising measurement can include the ad network, ad format and placement, and the revenue reported for an impression. This does not give us your payment-card details. Revenue analytics follows the same analytics choice as gameplay analytics.

You can change the gameplay analytics choice in Settings → Data. The leaderboard works whether analytics is enabled or disabled. Withdrawal stops future collection by the game but does not automatically erase information previously collected. Account deletion submits the recorded app-instance identifiers for Google Analytics deletion; Google processes this asynchronously. If an earlier installation or withdrawn choice has made an old identifier unavailable, contact us for help locating those records. Apple tracking permission is a separate choice.

Our Google Analytics property is connected to Unity’s Developer Data framework through a Unity-managed BigQuery export. Unity receives exported analytics information to support the configured Unity services. Deletion of this separate copy requires a provider follow-up; we retain the available identifiers needed to process that request until it is completed. Google’s acceptance of a deletion request does not mean every provider copy has already been erased.

4. Install attribution and marketing measurement (Android)

In the Android version, if you enable optional analytics, we also use Tenjin, Inc. (USA) to attribute installs to our marketing campaigns and to measure how those campaigns perform, for example which ad brought players to the game and how much purchase and advertising revenue those players generate. For this, the Tenjin SDK processes your device’s Google advertising ID (GAID) where your device settings permit it, your IP address, device and app information (such as device model, operating system version, language, time zone, and app version), the Google Play install referrer, app opens, the gameplay milestone events described in section 3, and in-app purchase and ad-revenue events. Purchase events include the product, price, currency, and Google’s signed purchase receipt so that Tenjin can validate the purchase. We do not send your player name, saved-game contents, or Firebase account ID to Tenjin. Tenjin processes this information on our behalf as a service provider.

The legal basis is your consent (Art. 6(1)(a) GDPR, and § 165(3) of the Austrian Telecommunications Act 2021 for reading information from your device). Tenjin stays inactive until you agree in Privacy choices, and it also stays inactive if you refused storing or accessing information on your device in the advertising privacy message. Players who do not confirm they are 16 or older cannot start the game, so Tenjin is never activated for them. The iOS version does not currently use Tenjin.

To opt out, turn off usage analytics in Settings → Data → Privacy choices; the game then instructs the Tenjin SDK to stop collecting and sending data from your device. You can also reset or delete your advertising ID in your Android settings. Withdrawal does not affect processing that took place before it. For more information, including Tenjin’s GDPR information (its role as a processor, data-subject rights, and its EU representative and Data Protection Officer contacts), see Tenjin’s Privacy Policy.

5. Advertising and Apple tracking permission

On supported builds, ads are delivered through Unity LevelPlay (ironSource), Unity Ads, and Google AdMob. These providers may process IP addresses, device and app information, ad interactions, and identifiers to deliver ads, prevent fraud, and measure performance. Advertising identifiers and cross-app tracking depend on applicable permissions. Even non-personalized ads can involve processing technical data.

Google’s User Messaging Platform checks whether an advertising privacy message is required and presents the applicable purposes, partners, and choices before advertising starts. It processes technical request information and stores consent signals on your device. Where available, reopen Settings → Data → Advertising choices to review or withdraw your decision. Advertising choices are separate from optional gameplay analytics; accepting an advertising message does not enable gameplay analytics. You can reject optional processing and still play, although ads and ad-funded rewards may be unavailable.

On iOS, the game requests Apple’s native App Tracking Transparency permission at the first eligible ad opportunity, when applicable. You may decline tracking and still play. This system permission does not replace consent required by other privacy laws. You can manage Apple tracking permission in your device settings. Changes affect future requests; they do not undo previous processing.

Unity also describes its processing and privacy controls in its Game Player and App User Privacy Policy and privacy FAQ. Available ad providers may differ by platform and release.

6. Email, purchases, and the website

If you contact us, we receive your email address, message, and any attachments you choose to send. The feedback button opens your mail app; nothing is sent until you send the email. Please avoid sending passwords or unnecessary sensitive information.

Where purchases are available, the app store processes payment details under its own terms and privacy policy. Pipapps does not receive your full payment-card details. For Apple purchases, our Firebase backend verifies Apple-signed transaction information and records the transaction and product identifiers, purchase date, purchase environment, and grant verification record with your Firebase identifier. This helps deliver purchases, support restoration where available, and prevent duplicate grants or misuse. Purchase verification is necessary to deliver purchases and does not depend on optional analytics consent.

Vercel hosts this website and processes request information, including IP addresses and technical logs, to deliver and protect it. We have not added website advertising cookies or a website analytics tracker. External links, including app stores, operate under their own policies.

7. Purposes and legal grounds

Consent to analytics or tracking is not a condition of playing. We do not use gameplay data to make automated decisions with legal or similarly significant effects on you.

8. Recipients and international processing

Relevant recipients include Google/Firebase, Unity/ironSource, Tenjin, Inc. (install attribution, Android), Vercel, email service providers, and app stores for the functions described above. Data may be processed outside Austria and the European Economic Area, including in the United States. Applicable safeguards may include adequacy decisions and standard contractual clauses; you can ask us about the safeguards relevant to your data. Providers may also act as independent controllers for some purposes.

Further information: Firebase privacy and security, Google Privacy Policy, Tenjin Privacy Policy, and Vercel Privacy Policy.

9. How long information is kept

Local saves and preferences remain until removed through available controls or app/device storage. Authentication information remains until the associated account is deleted, subject to provider deletion and backup periods. Leaderboard and reward records remain while needed to operate rankings and resolve reward claims. Purchase records remain while needed to support entitlements, restoration, fraud prevention, and any legal recordkeeping requirements. Analytics, attribution, and advertising records follow the relevant service retention settings and provider policies. We keep support correspondence only as long as needed to resolve the request, handle follow-up, and meet legal obligations or establish or defend claims. We review whether retained information is still necessary; we do not promise that uninstalling the game deletes provider records.

10. Your rights and account deletion

Settings → Data → Delete Account removes the Firebase authentication account, leaderboard entries, reward-claim records, backend purchase records and local game progress. Purchase benefits on the device are cleared. This does not issue a refund, remove Apple’s purchase history, or prevent restoration of eligible store purchases. Pending analytics-deletion requests are retried until Google acknowledges them; completion is not instantaneous. Minimal hashed security records may remain to prevent deleted accounts or consumed purchase receipts from being replayed. Provider backups, security logs and legally required records follow their applicable retention periods. Advertising-provider requests can also be made using the Unity privacy controls linked above or by contacting us. Turning off usage analytics stops Tenjin attribution on your device; to have Tenjin attribution records erased, contact us and we will forward the request to Tenjin.

Depending on applicable law, you may request access, correction, deletion, restriction, or portability of personal data, object to processing based on legitimate interests, and withdraw consent without affecting prior lawful processing. Contact us at the email above. We may ask for proportionate information to locate your records and verify the request; do not send passwords. If we cannot identify a record, we will explain what additional information is needed.

You can complain to the Austrian Data Protection Authority (Datenschutzbehörde) or your local supervisory authority. You do not need to contact us first.

11. Updates

We update this policy when data practices change and show the revision date above. We will provide additional notice and seek fresh consent where required before introducing materially different optional processing.