PRIVACY / PROXIMA WARS

Your flight.
Your choices.

Privacy Policy for the Proxima Wars app and this support website.

Effective and last updated: September 9, 2026 · Operator: Yeachan Hwang

What we use, and why

• On your device: language, music/effect settings, local scores, blocked-record choices, and any record awaiting submission. After you choose to submit, an anonymous account ID and authentication credential are stored in the app's private storage so it can update or delete your record. Active gameplay is not restored after the app terminates.
• Public world records: your chosen nickname, fastest submitted active clear time, craft, revive use, completed-stage count, run/ruleset identifiers, update time, and the anonymous account identifier associated with the record. The app shows the Top 100; submitted leaderboard records are public data. We use these fields to display rankings and keep one best record per anonymous account. There is no email/password sign-in for this feature.
• Support and reports: if you email us, we receive your email address, message and any attachments or record details you choose to send. We use them to respond, investigate issues, and handle reports. The app opens a draft for you to review; it does not send a report without your action.

Firebase Authentication and Cloud Firestore provide account and record services. Google may process network/security information, including IP addresses and user-agent information, to operate and protect them. The app does not include Firebase Analytics, Crashlytics, or a native Firebase SDK; these account and database features use network APIs. Firebase privacy information.

Advertising and privacy choices

The app uses Google Mobile Ads and Google’s User Messaging Platform for a banner and an optional rewarded-ad revive. It requests non-personalized ads and disables the publisher first-party ID feature, whether you allow or decline tracking permission. After the applicable privacy choices, iOS may ask for App Tracking Transparency permission. If you allow it, Google’s advertising SDK may use your device’s advertising identifier (IDFA) for advertising measurement. This permission does not switch the app to personalized ads.

If you decline tracking permission or iOS restricts it, the app can request non-personalized ads without IDFA when your other privacy choices permit ads. You can keep playing if you decline. GDPR consent and Apple’s tracking permission are separate choices. You can manage tracking permission in your iPhone’s Settings.

Google's SDK may process IP-derived approximate location, device/app identifiers, ad interactions, and diagnostic or performance information for ad delivery, measurement and service improvement. Non-personalized ads may still use identifiers for frequency limits, reporting and fraud prevention. Open Settings → Privacy Options for available consent controls. Ad availability can vary with those choices. Google's SDK disclosure and non-personalized ads explanation.

We do not sell your leaderboard or support data. Google processes advertising data under its own applicable policies; see Google's Privacy Policy. A non-personalized request alone is not a promise that every form of data sharing or measurement is disabled.

Control, retention and deletion

To delete your account and public record: open Settings, select Delete Account and Records, confirm, and keep the app open and connected until success is shown. This requests deletion of the live leaderboard document and its anonymous authentication account. If a request fails, retry or contact support. Hidden records are only hidden on your device and remain on the server.

Uninstalling the app does not delete server data. It can remove the credential used to manage your anonymous account. If you can no longer use the in-app deletion control, email us with the nickname and record details. Ownership verification may be necessary; never send an authentication token.

We keep the best public record until you delete it, it is removed after a report, or the service is retired; it has no scheduled automatic expiry. Pending submissions and preferences remain locally until replaced or removed. Support messages are retained as needed to resolve the request and meet legitimate security or legal recordkeeping needs; you can ask us to delete them.

Provider backups and service logs may outlast live deletion. Firebase states that Authentication IP logs are kept for a few weeks and that deleted authentication information is removed from live and backup systems within 180 days. Hosting IP logs may remain for a few months. Firestore backup retention depends on the project's backup settings, so deletion is not a guarantee of immediate erasure from all backups. Public screenshots or copies held by other users are outside our direct control. Firebase retention details · Firestore backup retention.

This website and international processing

This site adds no analytics, advertising scripts or cookies. Its small language switch reads your browser language or the page's language parameter without saving a preference. Firebase Hosting still processes request data such as IP addresses to deliver and protect the site.

Google's services may process data outside your country. Firebase Authentication operates in the United States; Firestore and Hosting use Google's infrastructure according to their configured services and locations. We do not claim an independent privacy/security audit or independent anti-cheat verification.

Questions and privacy requests

Contact Yeachan Hwang at proxima1527@gmail.com to request access, correction or deletion, or to raise a privacy concern. Tell us which record or message your request concerns without sending unnecessary personal information. Available rights and exceptions may depend on your location. Parents or guardians may contact us if a child has published personal information.

We will update this page if the app's data practices change. The revision date above identifies the current policy.