Official Game Name: Path Sprint
Package ID: com.zulu.mergemonster
Google Play Registered Developer: 陈逸斐
Developer Email: markenligne@gmail.com
This formal privacy disclosure defines native local device operating specifications and touch-triggered interactive frameworks uniquely built for Path Sprint, a casual Android mobile leisure experience centered around urban rooftop parkour challenge cycles spanning stacked residential high-rise and industrial warehouse building map layouts. Participants tap on-screen virtual directional touch buttons to manipulate stickman avatars, execute vertical wall climbing, spring-assisted long aerial glides and cross-building sprint leaps, activate score multiplier boost tiles and touch checkpoint flag markers to lock stage progress through continuous play sessions. All internal computational pipelines responsible for avatar movement trajectory calculation, stage progress tracking and score multiplier value rendering run entirely on the user’s local mobile hardware without creating persistent two-way data transmission links to remote cloud server infrastructure or external online computing platforms during any active foreground runtime state of the application. This document fully complies with the Google Play Developer Distribution Agreement, GDPR, CCPA and cross-border regional data safety regulatory standards applicable to all Android platform participants across global territories.
This privacy statement exclusively applies to authentic installation builds officially circulated through authorized Google Play publishing pipelines. Decompiled, restructured, altered or privately distributed modified variants of this mobile program fall outside the valid coverage boundary of this policy, and developer 陈逸斐 shall not bear legal accountability for hardware breakdowns, system runtime faults and abnormal program running outcomes triggered by unauthorized modified installation files. Real-time tap-driven touch operation signals only generate instant visual scene rendering adjustments within an isolated program sandbox and will never be extracted from users’ mobile hardware for long-term category sorting or permanent local storage archiving under any accessible device file format categories.
Users hold complete independent control over program startup timing, daily parkour challenge session length and full application shutdown operations across the complete usage lifecycle of Path Sprint. Continuous program downloading, opening and interactive gameplay participation after installation counts as voluntary confirmation that participants have read, understood and fully accepted all clauses laid out within this privacy policy document, and users may terminate program running status at any moment if they hold disagreement with the listed policy provisions.
Short-lived touch coordinate readings, directional button trigger markers and screen hold duration metrics only generate while participants adjust stickman movement direction, trigger vertical wall climbs or launch spring-powered aerial jumps during foreground active gameplay cycles. These transient runtime values occupy temporary volatile memory space solely after the program receives foreground running clearance granted by the Android operating framework, and all such ephemeral data gets fully erased instantly once users minimize the application or finish a full batch of rooftop parkour stage assignments.
This mobile program does not integrate built-in functional modules engineered to copy, archive, export or back up these brief runtime parameters into permanent storage partitions on users’ mobile devices. If users shrink program windows, switch over to alternative mobile software applications or fully terminate all active program threads connected to Path Sprint, system-level automatic cleanup routines eliminate all temporary runtime content entirely without generating cached document files, operation log records, behavior tracking archives or hidden stored files of any extension formats.
Android sandbox isolation safeguards secure all internally computed values used for stickman movement momentum calculation and stage checkpoint completion assessment. Other applications installed on the identical mobile hardware cannot read, duplicate or retrieve these internal runtime datasets via shared memory folders or system-approved access channels supplied by Android operating frameworks. Once Path Sprint loses foreground running permissions, avatar trajectory calculation threads suspend immediately, and new touch input measurement metrics will not generate until users manually reopen the primary program interface screen. Background auxiliary modules fully halt touch record monitoring after users exit front-end parkour gameplay screens and avoid launching hidden monitoring scripts while mobile devices remain in idle standby operating states.
All brief runtime generated content exclusively serves instant mathematical computation and scene rendering functions inside local program space; these temporary parameters will never be written into permanent device storage folders, and no underlying program code framework exists to sort, filter or analyse such runtime content after users finish successive rooftop parkour mission rounds.
All internal program scripts constructed for internet connection activation and remote server data transmission within Path Sprint stay fully disabled throughout every running phase of the program. Background activated network-associated code segments will never initiate execution during program startup, directional boost tile activation workflows and user touch-guided stickman movement adjustments. Preconfigured remote server domain address links, dedicated data transfer pipelines and timed background synchronization scripts are not compiled into this rooftop parkour themed program’s official installation package submitted to the Google Play platform.
This software will never generate outbound data packets and transmit such file payloads toward public network server endpoints across the full runtime lifecycle of Path Sprint. Two-way online data exchange workflows never operate within hidden background threads after this application exits foreground display mode. Undisclosed automatic network connection routines running without user awareness do not exist within the program framework, and internal code segments refrain from submitting internet access requests while this application operates under background suspended idle states.
Whether participants carry out extended continuous rooftop parkour mission sessions or leave the program inactive for lengthy time spans, no runtime-associated content will be uploaded to external servers through cellular data or Wi‑Fi connection channels. The full application operates purely based on local device computing logic and fully excludes network request code segments for content uploading, external resource retrieval and cross-server information exchange with remote-side server infrastructure. Mobile device network connection conditions will never interfere with stable normal operation of in-program stickman movement momentum calculation functional modules under all practical daily usage scenarios. This application contains no network initialization code segments and will never launch network access attempt actions when users lock mobile device screens or switch to separate independent mobile software applications.
The compiled core program framework of Path Sprint will never execute scanning or data capture command functions targeting built-in mobile device hardware sensors including motion detection modules, ambient light readers, short-range distance measurement equipment, audio recording assemblies and image capture hardware components. Judgment logic for vertical wall climbing traction precision, cross-building jump coverage range and stage checkpoint completion outcomes relies entirely on screen touch input data rather than signal data produced by device embedded hardware sensors.
Internal functional modules of this program will not adjust stickman movement speed increment values or scene rendering display parameters based on continuously generated sensor-derived signal data, which blocks all potential transmission pathways to collect hardware sensor generated information during full complete gameplay cycles. Visual asset resources used within Path Sprint only utilise preconfigured bundled asset files packaged inside the installation file instead of data information sourced from users’ mobile hardware components.
Even when mobile phone embedded sensors operate under standard normal functional states, this program will never retrieve any sensor-produced signal data across its entire full runtime cycle. No background auxiliary threads start scanning sensor signal data streams after users minimize program windows and shift the program into suspended idle running status. All scene rendering and progress calculation task modules remain fully separated from hardware sensor-associated data within the application core code architecture. This program never subscribes to sensor data listening background service functions and will ignore all sensor-triggered runtime signal transmissions sent out by the mobile operating system through the complete full user usage period.
Path Sprint constructs an exclusive volatile temporary memory resource pool dedicated to its internal active execution threads with support from the native Android sandbox system. This dedicated memory partition maintains complete isolation separation from memory space occupied by other applications installed on the same single mobile hardware unit, and built-in sandbox rule sets consistently block unauthorized data reading request signals originating from external separate independent program sources.
Other simultaneously running mobile applications cannot copy temporary scene rendering content and touch control related data sets belonging to Path Sprint through system supplied shared memory directory channels. Cross-program code segments built to share runtime data information with background threads belonging to other mobile software programs are not embedded within this rooftop parkour themed program’s core functional framework. This program firmly rejects all memory access request signals submitted by external third-party applications whether the program runs under foreground active execution state or background suspended idle standby mode.
After users finish a full complete batch of rooftop parkour mission rounds, the program releases all memory resources occupied by current scene asset files before loading resource data required for subsequent regional stage checkpoint layouts to prevent excessive memory resource consumption and mobile device lagging performance failure issues. Once users switch Path Sprint to background running mode, all scene calculation and touch tracking auxiliary threads terminate instantly, and unused idle memory resources get actively released to lower overall system resource consumption burden on users’ mobile hardware devices. This application does not contain long-term resident background service threads, and all program startup and full complete shutdown operations rely entirely on manual user triggered input actions. When users fully close the entire program, the mobile operating system reclaims all previously occupied runtime memory space; this program will never retain idle memory resource allocations or continuously occupy system RAM storage space while operating under background idle standby conditions.
Path Sprint delivers complete rooftop parkour oriented gameplay functionality solely by utilizing basic native rendering permission authority natively supplied by the Android mobile operating system. This application will not launch authorization request pop-up window prompts for sensitive or standard system privilege groups during installation, repeated program startup cycles and extended daily parkour challenge gameplay sessions. Participants can finish vertical wall climbing tasks, activate directional boost tiles and reach stage checkpoint markers without needing to accept extra permission request pop-up prompt windows displayed on mobile device screen surfaces.
Internal program logic within Path Sprint will never submit access authorization application request signals targeting local device storage folders, image capture hardware assemblies, audio recording module components, location sensing hardware devices, contact directory archive files and native Android user account framework systems. No extra privilege access record entry items are generated within device permission management menu panels after full installation process completes successfully. This application fully abides by all native mobile system operating regulation rules and will never seek deep-level device control administrative permission authority for mobile hardware equipment under any running circumstances.
Every permission-related functional design integrated within this program complies with core safety standard rules defined by official Android development teams and will never attempt to bypass native system permission verification mechanism functions to gain unauthorized device access authority rights. All system-level function call signals triggered by this program are strictly limited to scene rendering and touch input processing operation tasks to deliver standard rooftop parkour and checkpoint objective gameplay without accessing users’ sensitive mobile hardware component devices. This program only invokes core Android drawing related system function calls necessary to render program screen visual display content; it will never submit permission application request signals while running under background states or request system authority permissions without displaying corresponding visual prompt windows within users’ sight ranges.
Registered developer identified as 陈逸斐 holds independent full revision authority to adjust all clause content contained within this privacy policy document to match updated in-program parkour mission content and revised compliance standard rule sets issued by official Google Play platform administration management teams. Every newly revised updated version of this privacy policy text file will be uploaded and permanently displayed on Path Sprint’s official store listing page within the Google Play global distribution service ecosystem network.
Users’ continuous program downloading, application opening and interactive gameplay participation behavior actions after revised policy content formally takes legal effective status will be treated as voluntary full acceptance of all updated revised policy clause content. The developer will not send personalized individual notification messages to separate single users for policy revision update occurrence events, and users can view the latest full complete text policy content directly on the Google Play store listing page without mandatory account login operation requirement steps.
All policy modification adjustment actions are strictly limited to platform rule adaptation matching purposes and will never alter the core privacy protection foundational principle rules defined inside this document text content. The developer will not rewrite core document provision clauses arbitrarily without valid official supporting reasons derived from Google Play platform policy update adjustments or formal regulatory adjustment documents issued by competent governing authority departments. Historical archived previous versions of this privacy policy file remain accessible on the program store listing page so users may review prior historical policy term content at any time of personal choosing. The developer will only carry out policy revision adjustment operations when Google Play updates its official developer distribution agreement document and matching platform data safety policy document sets; trivial minor wording modification adjustments will be avoided to sustain consistent stable unified policy content standard rules for all global range participating users across all regions.
If you hold inquiries or reasonable feedback regarding this privacy policy content you may reach out via the developer provided email address listed below.
markenligne@gmail.com
Effective Date
July 17, 2026