Back to Marble Maze
Policy page for mtl.vuba.one/privacy.php
Privacy Policy

Fast play, limited data.

This Privacy Policy describes how Marble Maze handles information when you use the app on Apple Watch and iPhone. The current app design focuses on fast local gameplay, on-device preferences, optional support purchases through Apple, and motion-based control.

Stored locally

Settings, progression, and onboarding state are kept on your device.

Motion for gameplay

Motion access is used so the maze can respond to tilt input.

Purchases via Apple

Optional support purchases and restoration are provided by Apple’s App Store systems.

What Marble Maze stores

Marble Maze stores gameplay preferences and progression on your device. This can include language choice, sound and vibration settings, onboarding state, saved round progress, current world and round position, and locally cached support-purchase status.

This local storage is used so the app can restore your settings and continue your game when you reopen it.

Motion data

The app uses motion sensors to control gameplay tilt on supported devices.

Motion access is used only for gameplay input and is not used to build advertising profiles or sold to third parties.

In-app purchases

Marble Maze offers an optional one-time support purchase. Purchase processing, restoration, and transaction handling are provided by Apple through StoreKit.

The app checks support-purchase status so it can reflect your support inside the app, but payment information is handled by Apple, not by Marble Maze directly.

Accounts, ads, and analytics

Marble Maze does not require account creation to play.

Based on the current app implementation, the app does not include third-party advertising SDKs or third-party analytics/tracking frameworks.

Data sharing

The app is not designed to sell your personal information.

If Apple provides purchase- or platform-related data as part of App Store operation, that handling is governed by Apple’s own policies and platform services.

Children and review notes

If you plan to position the app for children or family audiences, you should keep App Store metadata and privacy answers aligned with the final build and any future SDK additions.

If you later add analytics, crash reporting, cloud sync, external support forms, or marketing pixels, this policy should be updated before release.