This manifest outlines the data processing logic for Bounce Back. Our architecture is designed for complete user anonymity. We do not maintain any persistent storage for user-specific identity markers.
Bounce Back operates as a stateless local application. We do not facilitate account-based authentication. This ensures:
To optimize execution and monitor system stability, we utilize specific external Software Development Kits (SDKs). These entities process diagnostic metrics as defined by their technical protocols:
We utilize Firebase for real-time crash reporting and performance monitoring. This subsystem collects anonymous hardware identifiers and OS version metrics to ensure compatibility across varied deployment environments.
The Facebook SDK is integrated for install attribution. This enables the calculation of marketing efficiency. Meta may process device-specific advertising tokens (IDFA) according to their global privacy standard.
Bounce Back includes integrated advertising modules to sustain project development. These modules are managed by external providers who may utilize device tokens to deliver context-specific content based on broad geographic regions or device behavior.
Users maintain the ability to reset these tokens via OS-level security settings. We do not permit external ad servers to access local game state variables.
Requests for local system access (e.g., storage I/O) are utilized strictly for the persistence of high scores and local preference files. No data accessed through these gates is exfiltrated to central servers.