Jumpulsa
Privacy Policy

Who is responsible?

This policy covers Jumpulsa, including its iOS TestFlight beta, and information you send us about the game. The controller is:

For information about visits to this website, see our website privacy notice.

Camera & movement

With your camera permission, Jumpulsa processes camera images on your device using a bundled pose-estimation model. The resulting body-movement estimates control the robot and help the game calibrate and recover tracking. They are used for gameplay, not to identify you.

The game’s camera feature does not record photos or videos, and does not upload camera images or a video feed to CAB Game Studio or the advertising providers. Live frames and movement estimates are processed in memory. Camera processing stops when the app is suspended.

Camera View changes whether the live image is visible behind the game graphics. Switching this visual setting off does not switch off the camera while movement-controlled play is active.

You can revoke camera permission in your device settings. Without camera access, movement-controlled gameplay cannot function. Camera permission is separate from advertising and tracking choices.

Local game data

The game saves your best and recent scores, sound and display preferences, safety-agreement and onboarding progress, and a previous-session flag used to space advertising between runs. This information is stored locally so the app can remember your progress and choices. Jumpulsa does not require a game account or operate its own cloud score-sync service.

The app also writes local technical diagnostic files for its camera and pose runtime. These can include timestamps, startup and error stages, camera configuration and orientation, frame dimensions, and processing or pose-detection status. They do not contain recorded images or video. The game does not automatically send these local files to CAB Game Studio.

Local preferences and diagnostic files remain in app storage until overwritten or the app’s local data is removed. The current diagnostic history has no automatic time-based deletion. On iOS, deleting the app removes its local app data; offloading it keeps that data. Device backups may retain copies according to your system and backup settings.

Multiplayer

Multiplayer is optional. When you create, join or quick-join a lobby, the game signs in to Unity Gaming Services (Unity Authentication and Unity Sessions) with an anonymous player ID. You do not create an account. The anonymous ID is stored on your device and reused for later multiplayer sessions.

While you are in a lobby or round, the following is shared through Unity with the other members of that session:

• a player name the game assigns at random from a fixed list for each lobby (you cannot type your own) and your selected robot;
• your ready status and round progress, such as score, pipes, Perfect Jumps, best streak, shield status and survival time;
• whether you left or dropped out of a round, for example after pausing or losing tracking.

Private lobbies are joined with a code that you share; Quick Join matches you with a public lobby. Because names come from a fixed list, other players never see a name you typed. Camera images and movement data are never sent: each player’s movement is processed only on their own device.

Unity processes connection data such as your IP address to provide the service. For Unity’s processing, retention and rights requests, see the Unity Game Player and App User Privacy Policy. Multiplayer wins are also counted locally on your device to unlock a robot.

Advertising & providers

Jumpulsa includes banner and interstitial advertising and an optional rewarded video for an extra life. It uses Unity LevelPlay for mediation with ironSource Ads, Google AdMob and Unity Ads integrations. Ad availability depends on consent eligibility, network access and advertising inventory.

Depending on the provider, device and privacy choices, advertising services may process:

• IP address and approximate location derived from it;
• device or advertising identifiers, where available and permitted;
• device model, operating-system and app information;
• ad requests, impressions, interactions and reward events;
• diagnostic, crash and performance information.

Providers use this information to deliver and measure advertising, prevent fraud and, where permitted, personalize ads. Receiving non-personalized ads does not necessarily mean that no data is processed. We do not send the camera feed to these services.

The providers explain their processing, retention criteria and rights-request procedures in their notices:

• Unity Game Player and App User Privacy Policy — including LevelPlay, ironSource Ads and Unity Ads.
• Google Privacy Policy and Google’s use of information from partner sites and apps — including AdMob.

Provider processing may take place outside your country, including in the United States. Where European data-protection rules apply, international transfers require an applicable legal mechanism, such as an adequacy decision or standard contractual clauses. The linked provider notices explain their applicable arrangements and how to obtain further information.

Your privacy choices

Google’s User Messaging Platform presents applicable advertising privacy messages and records your choices. Use Privacy in the game to reopen advertising privacy options when they are available; otherwise the button opens our studio website, where this policy is linked.

Apple’s App Tracking Transparency permission is a separate choice. On iOS you can change it under Settings → Privacy & Security → Tracking. Declining tracking permission does not prevent you from playing and does not necessarily remove all advertising. Device settings also let you change camera permission.

Withdrawing consent takes effect for future processing and does not change the lawfulness of processing already carried out. It does not automatically delete information already retained by an advertising provider; use that provider’s privacy controls or request process where appropriate.

Purposes & legal bases

Where the GDPR applies, we rely on the following bases for processing under our control:

• Providing the game you request: processing needed for movement controls and local game progress — Article 6(1)(b).
• Multiplayer you choose to join: anonymous sign-in and sharing your assigned player name, robot and round statistics with the players in your session — Article 6(1)(b).
• Technical reliability: local runtime diagnostics and necessary security measures — Article 6(1)(f), our legitimate interest in diagnosing failures and maintaining a working, secure game.
• Consent-based advertising or tracking: consent where required — Article 6(1)(a). Access to device information also follows applicable device-storage and consent rules.
• Support: responding to a request about the service — Article 6(1)(b) where it concerns the service relationship, or Article 6(1)(f) for our legitimate interest in answering other enquiries.
• Legal obligations: handling applicable legal duties — Article 6(1)(c).

Advertising providers may have their own responsibilities and legal bases, as explained in their notices and the applicable consent message. An operating-system permission alone is not a substitute for every required data-protection consent.

Camera access is necessary for this game’s movement controls. You do not have to allow advertising tracking to play. Jumpulsa does not use movement estimates to make decisions producing legal or similarly significant effects about you.

Support & TestFlight

If you contact us, we receive your email address and the information you choose to send. We use it to respond, troubleshoot and handle privacy requests. Avoid sending camera recordings, other people’s information or sensitive material unless needed for your request.

We retain correspondence, beta reports and feedback received by the studio for as long as needed to handle the enquiry, investigate the issue and complete relevant follow-up, or to meet applicable legal retention requirements or establish, exercise or defend claims. Please contact us if you want us to assess deletion of this information.

If you use Apple TestFlight, Apple automatically collects beta crash logs and usage information and shares them with us. Feedback and screenshots are shared when you submit them. If you join through an email invitation, your name and email address may also be visible to us; joining only through a public link does not share those details through the tester list. We use beta information to investigate issues and improve the game. Apple processes this information under its own terms. Read Apple’s TestFlight & Privacy information.

Your rights

Depending on the conditions in applicable law, you may request access, correction, deletion, restriction of processing, and a portable copy of personal data. You may withdraw consent and object to processing based on legitimate interests; the right to object to direct marketing applies at any time.

Contact egecabuk.it@gmail.com for requests concerning CAB Game Studio. We may need proportionate information to verify a request. For data controlled by advertising providers or Apple, their linked privacy notices describe their request channels. Deleting local app data does not delete data already held by those providers.

You may lodge a complaint with a data-protection supervisory authority, including one in the country where you live or work. Our local authority is Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW).

Children & updates

If you believe a child has provided personal information to us, please contact us so we can investigate and handle it appropriately. Parents and guardians can manage device permissions and should consider whether movement-based play is suitable for their child.

We update this policy when the game or its data practices change. The date at the top shows the latest update. Where a change requires a new choice or consent, we will provide the appropriate notice or request.