Application Name: Battle Rush
Package Name: com.hotel.savethecastle
Developer: 陈逸斐
Contact Email: markenligne@gmail.com
This privacy disclosure outlines localized runtime processing rules and ephemeral touch signal governance standards crafted exclusively for Battle Rush, a pixel side-scrolling platform adventure application built to operate on Android handheld hardware devices. The core interactive loop centers on touch-controlled horizontal character traversal, vertical platform vaulting and gathering scattered stage auxiliary supplies to bypass terrain hindrances and interact with roaming stage units across multi-layered mountain and woodland pixel backdrops. All internal computational workflows handling character coordinate rendering, terrain gap detection and play progress visualization run entirely on local device processing hardware, without any persistent bidirectional data transfer pathways connecting to off-site cloud server infrastructure during foreground software operation. This formal written document complies with Google Play developer distribution regulations, CCPA and GDPR cross-border data protection benchmarks to satisfy privacy compliance criteria for handheld device users across all global geographic zones.
This privacy statement only delivers valid legal coverage for unaltered installation packages officially released via authorized Google Play publishing pipelines. Any decompiled, restructured, modified or privately circulated altered variants of this mobile software fall outside the protective boundary defined by this policy, and developer 陈逸斐 shall not assume legal accountability for hardware breakdowns, system runtime crash faults or abnormal program performance defects stemming from unauthorized edited installation bundles. Instant tap and hold touch signals generated during user adventure gameplay solely trigger immediate pixel scene rendering adjustments within an isolated program sandbox; these short-lived touch measurement metrics will never be extracted from user mobile hardware for long-term classified sorting or permanent local storage archiving under any accessible device file format categories.
Users retain complete independent authority over program boot initiation timing, daily platform adventure play session length and full program termination operations throughout the entire usage lifecycle of Battle Rush. Repeated software downloading, opening and interactive stage exploration gameplay participation after installation counts as voluntary acknowledgment that participants have read, comprehended and fully consented to all regulatory clauses laid out within this privacy policy document. Users may suspend the software’s active runtime state at any instant if they hold contradictory opinions toward the listed policy provisions.
Brief touch coordinate recordings, sustained touch hold duration indicators and real-time playable character positional metrics are generated solely while users adjust adventurer travel bearing, complete vertical platform vaults or collect stage auxiliary supplies during active foreground gameplay cycles. These temporary runtime values occupy volatile memory partitions exclusively after the program obtains foreground running clearance authorized by the Android operating framework, and all such fleeting operational data gets fully erased instantly once users shrink the software display panel or finish a full stage exploration segment.
This pixel platform adventure program does not embed native functional subroutines engineered to duplicate, archive, export or back up these brief runtime parameters into permanent storage partitions on users’ mobile hardware devices. If users minimize program display windows, shift focus toward alternative mobile software applications or fully terminate all active program threads linked to Battle Rush, system automated cleanup routines eliminate all temporary runtime content entirely without generating cached document files, operation log archives, user behavior tracking records or hidden stored data files of any extension formats.
Android sandbox isolation partitions secure all internally computed values utilized for adventurer movement momentum calculation and terrain barrier bypass completion evaluation. Other applications installed on the identical mobile hardware cannot read, duplicate or retrieve these internal runtime datasets through shared memory folders or system-approved access channels supplied by Android operating frameworks. Once Battle Rush loses foreground running permissions, character movement calculation threads suspend instantaneously, and new touch input measurement metrics will not generate until users manually reopen the primary program visual interface panel. Background auxiliary modules fully pause touch signal recording tracking after users exit front-end stage exploration gameplay screens and refrain from activating hidden monitoring background scripts while mobile hardware devices remain in idle standby operational states.
All short-lived runtime generated content fulfills only instant mathematical computation and pixel backdrop rendering tasks within local program volatile memory space. These temporary parameter values will never be inscribed into permanent device storage folders, and no underlying program code architecture exists to sort, filter or analyze such runtime content after users finish successive platform adventure mission segments.
All internal program script modules constructed for internet connection initialization and remote server data transmission inside Battle Rush remain permanently disabled across every active runtime phase of the software. Background activated network-linked code segments will never initiate execution during program startup, woodland mountain scene rendering workflows and user touch-guided character locomotion adjustments. Preconfigured remote server domain address links, dedicated data transfer conduits and timed background synchronization scripts are not compiled into this pixel adventure-themed program’s official installation package submitted to the Google Play platform.
This software will never produce outbound data packets and transmit such file payloads toward public network server endpoints across the complete runtime lifespan of Battle Rush. Bidirectional online data exchange workflows never run within concealed background threads after this application exits foreground display mode. Undisclosed automatic network connection routines operating without user awareness do not exist within the program architecture, and internal code segments abstain from submitting internet access requests while this application operates under background suspended idle states.
Whether participants carry out extended uninterrupted platform adventure play 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. Full program operation depends entirely 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 states will never interfere with stable regular operation of in-program character movement momentum calculation functional modules under all practical daily usage scenarios. This application contains no network initialization code segments and will never launch network connection attempt actions when users lock device screens or switch over to separate independent mobile software applications.
The compiled core program architecture of Battle Rush 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 hardware, audio recording assemblies and image capture hardware components. Judgment logic for platform vault alignment precision, cross-mountain route travel coverage range and auxiliary supply collection completion outcomes fully relies on screen touch input data rather than signal data generated by device-embedded hardware sensors.
Internal functional modules of this software will not adjust character movement speed increment values or pixel scene rendering display parameters based on continuously generated sensor-derived signal data. This structural setup blocks all potential transmission pathways to gather hardware sensor generated information during full uninterrupted platform adventure gameplay cycles. Visual pixel asset resources utilized within Battle Rush only adopt pre-bundled asset files packaged inside the installation file instead of data information sourced from users’ mobile hardware components.
Even when mobile phone embedded sensors run under standard normal functional operating states, this program will never extract any sensor-produced signal data through its entire runtime lifespan. No background auxiliary threads begin scanning sensor signal data streams after users minimize program windows and shift the software into suspended idle running mode. All scene rendering and platform exploration progress calculation task modules stay 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 disregard all sensor-triggered runtime signal transmissions dispatched by the mobile operating system across the complete full user usage period.
Battle Rush builds an exclusive volatile temporary memory resource pool dedicated to its internal active pixel mountain platform exploration execution threads supported by the native Android sandbox system. This dedicated memory partition maintains full 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 duplicate temporary pixel scene rendering content and touch control related datasets belonging to Battle Rush via system-supplied shared memory directory pipelines. Cross-program code segments created to share runtime data information with background threads belonging to other mobile software programs are not embedded within this pixel adventure-themed program core functional architecture. This program firmly rejects all memory access request signals submitted by external separate applications whether the program runs under foreground active execution state or background suspended idle standby mode.
After users finish a full complete stage exploration route segment, the program releases all memory resources occupied by current woodland scene pixel asset files prior to loading resource data required for subsequent mountain zone route layouts to avoid excessive memory resource consumption and mobile device frame lag performance failure issues. Once users switch Battle Rush to background running mode, all scene calculation and touch tracking auxiliary threads terminate instantly, and unused idle memory resources get actively released to cut down overall system resource consumption burden on users’ mobile hardware devices. This software does not contain long-running resident background service threads, and all program startup and full complete shutdown operations fully rely on manual user-triggered touch input actions. When users fully close the whole program, the mobile operating system reclaims all previously allocated runtime memory space. This program will never hold idle memory resource allocations or continuously occupy system RAM storage space while operating under background idle standby conditions.
Battle Rush delivers full pixel mountain platform adventure oriented gameplay functionality solely through utilizing basic native rendering permission authority natively supplied by the Android mobile operating system. This software 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 woodland adventure gameplay sessions. Participants can complete platform vault tasks, gather scattered stage auxiliary supplies and navigate cross-mountain character travel routes without needing to accept extra permission request pop-up prompt windows displayed on mobile device screen surfaces.
Internal program logic within Battle Rush 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 complies with all native mobile system operating regulation rules and will never pursue deep-level device control administrative permission authority for mobile hardware equipment under any running circumstances.
Every permission-linked functional design integrated within this software 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 the program are strictly limited to pixel scene rendering and touch input processing operation tasks to deliver standard mountain platform exploration and terrain barrier bypass objective gameplay without accessing users’ sensitive mobile hardware component devices. This program only invokes core Android drawing related system functions necessary to render program screen pixel 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 陈逸斐 holds independent full revision authority to adjust all clause content contained within this privacy policy document to align with updated in-program mountain platform exploration route scene content and revised compliance standard rule sets released 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 Battle Rush official store listing page inside the Google Play global distribution service ecosystem network.
Users’ continuous program downloading, application opening and interactive mountain platform exploration gameplay participation behavioral 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 dispatch personalized individual notification messages to separate single users for policy revision update occurrence events; 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 confined 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 reasoning derived from Google Play platform policy update adjustments or formal regulatory adjustment documents issued by competent governing authority departments. Historical archived prior versions of this privacy policy file stay accessible on the program store listing page so users may review earlier historical policy term content at any self-selected personal time. 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 tweaks will be avoided to maintain consistent stable unified policy content standard rules for all global range participating users across all regional territories.
Should 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 20, 2026