Privacy Policy

Who we are

ParkVex is a mobile parking puzzle game published by Tangleon (contact: info@tangleon.net). This Privacy Policy explains what information the app handles on your device, what third-party services may process when ads or store purchases run, and the choices available to you.

Last updated: 12 October 2026.

No account required — data may still be processed

ParkVex does not create player accounts and does not offer cloud save sync in the current build. That does not mean that no data is processed. Gameplay progress is stored locally on your device. When advertising or in-app purchases are used, Google AdMob, Google Play, and/or Apple may process device, advertising, and transaction-related data under their own terms, as described below.

Information stored on your device

ParkVex stores stage progress, best scores, assist credits, preference toggles (language, sound, haptics, reduce motion), and related gameplay state locally using the app’s WebView storage (keys such as parking.save and parking.backup). The app may also store an interstitial pacing marker (parkvex.lastInterstitial), a local reward ledger (parking.rewards), and an on-device Remove Ads entitlement/catalog cache for offline use.

This gameplay and settings data stays on the device and is not uploaded by ParkVex to a Tangleon game server. Uninstalling the app typically removes local save data held in the app sandbox, subject to any OS backup features you enable. Resetting progress from Settings clears local save files but does not remove store purchase ownership.

Advertising — Google AdMob

The app integrates the Google Mobile Ads SDK through the Capacitor Community AdMob plugin (@capacitor-community/admob). Release builds use ParkVex production AdMob application and ad unit identifiers for Android and iOS.

ParkVex may show these ad formats when ads are enabled and the player has not purchased Remove Ads:

• Banner — adaptive banner above the play area when available
• Interstitial — full-screen ads between stages under the app’s ad cadence rules
• Rewarded — optional video ads for help such as a hint or extra undos after the free per-stage undo allowance

Declining or failing to complete a rewarded ad means the optional reward is not granted; core puzzles remain playable without watching a reward. Confirmed Remove Ads ownership disables banner, interstitial, and rewarded ads.

When ads are requested or shown, Google and its advertising partners may collect and process data typical of mobile advertising. This can include advertising identifiers (such as Google Advertising ID on Android or the Identifier for Advertisers on iOS where available), IP address, device and app identifiers, approximate location derived from IP, ad interaction and performance data, and diagnostic information needed to deliver, measure, and combat fraud related to ads. ParkVex does not operate a separate first-party analytics, crash-reporting, or account SDK in the current application codebase.

Personalized and non-personalized ads

In the current ParkVex application code, AdMob ad requests are made with the non-personalized ads (npa) flag enabled. Google may still process advertising identifiers and other data needed to serve and measure ads, including non-personalized ads.

Whether you see personalized or non-personalized ads can also depend on Google’s systems, your platform privacy settings, and applicable regional rules. Limiting ad personalization in device settings does not stop all ads; it may change how ads are selected.

Consent, privacy controls, and what is not implemented

ParkVex’s monetization layer can gate ad presentation behind an internal consent flag in code. The current application source does not implement Google’s User Messaging Platform (UMP) consent form UI, and it does not implement Apple’s App Tracking Transparency (ATT) prompt.

Where Google’s Mobile Ads SDK or the operating system present consent, privacy, or ad personalization controls, those controls are provided by Google or the OS — not by a separate ParkVex UMP/ATT interface. You can also limit ad tracking or reset advertising identifiers in your device settings (for example, Android ads/privacy settings, or iOS Tracking and Apple Advertising settings).

Publishers who show ads in regions that require a consent framework (such as the EEA/UK) should implement the applicable Google consent / UMP flow before relying on personalized advertising. ParkVex currently requests non-personalized ads in code and does not claim that a UMP or ATT flow is present.

In-app purchases — Remove Ads

ParkVex offers an optional one-time Remove Ads purchase processed by the platform store:

• Android: Google Play Billing
• iOS: Apple StoreKit

Store access is implemented through @capgo/native-purchases. Google Play or Apple processes payment, account, and receipt information under their store terms. ParkVex checks store ownership and keeps an on-device entitlement cache so Remove Ads can remain effective offline after confirmation. ParkVex does not receive your payment card details and does not send receipts to a Tangleon server. Use Restore Purchases with the same store account if you reinstall. Resetting game progress does not remove purchase ownership.

Offline play and network use

Stages and local progress are designed to work without an internet connection. Loading or showing ads, verifying store products, completing purchases, and restoring purchases require network connectivity and the relevant Google or Apple services. If the network or ad/store service is unavailable, gameplay can continue; ads or purchases may simply be unavailable until connectivity returns.

Permissions and identifiers

On Android the app declares INTERNET and BILLING-related store permission as needed for purchases. The AdMob / Google Play services stack may also introduce advertising-related permissions such as ACCESS_NETWORK_STATE and advertising ID / Ad Services permissions in the merged manifest. The app does not request camera, microphone, contacts, precise location, or photo-library access for gameplay.

Third parties that may receive data

Depending on how you use the app, the following categories of third parties may receive or process data:

• Google (AdMob / Google Mobile Ads) — to serve, measure, and secure ads
• Google Play — to process Android in-app purchases and ownership checks
• Apple — to process iOS in-app purchases and ownership checks via StoreKit / App Store
• Advertising partners of Google — as described in Google’s advertising and privacy documentation when ads are served

Tangleon does not operate a ParkVex player account database or game backend that receives your save file. Review Google’s and Apple’s privacy policies for processing they control.

Your choices and rights

You may:

• Reset locally saved progress from Settings
• Purchase Remove Ads to stop in-app advertising in ParkVex
• Limit ad tracking / reset advertising identifiers in device settings
• Uninstall the app to remove typical local sandbox data
• Contact us at info@tangleon.net for privacy questions or requests related to Tangleon’s role as publisher

Depending on where you live, you may have rights to access, correct, delete, or restrict certain personal data, or to object to certain processing. Because gameplay progress is stored on-device, the primary deletion control for that data is Reset saved progress or uninstall. For advertising-identifier controls, use your platform settings. We may need enough detail to understand and respond to a request; we do not operate a player account database for this app.

Children

ParkVex is a general-audience puzzle game. It is not directed to children under 13 (or the equivalent minimum age in your country). Do not use the app if you are below the age required by your platform’s terms.

International users

Ads and store services may involve processing by Google, Apple, and partners in other countries under their terms. Install and use the app only where it is lawful for you to do so.

Changes

We may update this policy when the app’s SDKs, permissions, purchases, or data practices change. The dated copy published at this URL is the store-facing Privacy Policy. The in-app Privacy Policy & Support page reflects the offline copy shipped with that build and may lag a web update until the next app release.