Cannon Hit Privacy Policy

1. The short version

The audited Cannon Hit game does not require an account and does not send personal information or gameplay telemetry to polysign.lu. It stores one gameplay value locally on your device: your highest cleared sector.

The website does not use cookies, analytics, advertising pixels, browser storage, or third-party embeds. Like most websites, its hosting provider may process standard request and security logs. If you email support, we receive the information you choose to send.

2. Information handled by the game

Information stored locally

Cannon Hit stores your highest cleared sector in app-local storage under an internal versioned key. The current run, randomly generated run seed, remaining shots, and recovered upgrades are held only while the game is running and are not written as persistent progress.

The app and its framework may also create ordinary local files or caches needed to install and run bundled code, images, and audio.

Information not collected by the audited game code

The audited game code does not collect or transmit your name, email address, contacts, photos, microphone recordings, precise or approximate location, advertising identifier, payment details, gameplay events, crash reports, or device identifier to polysign.lu. It contains no advertising, analytics, authentication, cloud-save, leaderboard, purchase, subscription, or developer-operated backend integration.

Apple, Google, or your device manufacturer may separately process store, operating-system, backup, or diagnostic information under your settings and their own privacy policies. That processing is not performed by Cannon Hit’s gameplay code.

3. Device permissions and capabilities

Cannon Hit plays bundled audio and uses device haptics for gameplay feedback. These functions may use non-sensitive audio-control and vibration capabilities on supported devices.

The current app configuration disables microphone access, audio recording, and background audio playback. The game does not request camera, location, contacts, photos, Bluetooth, health, motion, notification, or tracking permission.

The current Android dependency set can declare Internet access and legacy shared-storage permissions through its framework modules even though the audited game source does not call a network endpoint or the file-system module. The legacy storage declarations are limited to Android API level 32 and below. A production release must be checked to confirm its final permission list.

Development builds may contain an overlay capability used by developer tooling. It is not a Cannon Hit feature and must not be present in the production store package.

4. Local storage, backups, and remote storage

polysign.lu does not operate a remote database or cloud-save service for Cannon Hit. Your best-run value remains in the app’s local storage. Clearing the app’s storage or uninstalling the app can delete it.

Your operating system may include app data in a device or cloud backup if you have enabled that feature. Backup creation, retention, and restoration are controlled by Apple, Google, your device manufacturer, and your settings, not by Cannon Hit.

5. Accounts and authentication

Cannon Hit has no account registration, sign-in, user profile, or authentication system. polysign.lu does not receive account credentials through the game.

6. Analytics, advertising, and tracking

Cannon Hit contains no analytics SDK, advertising SDK, tracking pixel, cross-app tracking code, or tracking-consent prompt. The current Apple privacy manifest declares tracking as false. The website also contains no analytics, advertising, fingerprinting, or non-essential cookies.

7. Purchases and stores

The audited app contains no in-app purchase or subscription flow. This policy makes no claim about whether obtaining Cannon Hit from a store is free or paid. If you obtain the app through Apple, Google, or another distributor, that distributor independently processes any acquisition, payment, store-account, refund, or tax information under its own terms and privacy policy. polysign.lu does not receive your full payment-card details through the game.

8. Third-party software and services

Cannon Hit is built with React Native, Expo SDK modules, React Three Fiber, Three.js, cannon-es, React Native AsyncStorage, and related local runtime libraries. In the audited app, these libraries render the game, run physics, play bundled audio, provide haptics, and store the local best-run value. No third-party advertising, analytics, authentication, purchase, or backend service SDK is integrated.

The website is delivered by Google Firebase Hosting. As part of standard delivery, security, and abuse prevention, the provider may process an IP address, request date and time, requested URL, referrer when supplied, browser user-agent, and technical error information in server logs. Those logs are retained for 30 days. polysign.lu does not add analytics or tracking to those requests.

Support email is handled by Google Workspace. When you contact us, that provider processes message headers, your email address, the message, and any attachments you choose to include.

9. Sharing and sale of information

polysign.lu does not sell or rent personal information. The game has no developer-operated server to which gameplay or personal information is sent.

Website-log information and support messages may be processed by the hosting and email providers described above, disclosed when required by law, or used when reasonably necessary to protect users, polysign.lu, or the service from fraud, abuse, or security threats. We do not share them for behavioural advertising.

10. Retention and deletion

The local best-run value remains on your device until app storage is cleared, the app is uninstalled, or the operating system removes or restores it. polysign.lu cannot view or remotely delete that local value because the game does not send it to us.

Hosting logs are retained for 30 days. Support messages are retained for as long as needed to handle the request, unless a longer period is required to establish, exercise, or defend legal claims or comply with law.

You may ask us to delete a support message or other support information we hold by emailing georges@polysign.lu. We may need enough information to locate the message and verify the request.

11. Your choices

You can reset the game’s locally stored best run by clearing the app’s storage or uninstalling the app. You can control device or cloud backups in your operating-system settings. You can choose not to contact support, omit optional attachments, and avoid sending sensitive information.

You may also contact us to ask about access to, correction of, or deletion of information you voluntarily supplied through support, subject to applicable law.

12. Children’s privacy

Cannon Hit does not require an account and does not knowingly seek personal information from children. Standard website hosting logs may still be generated for any visitor as described above. Children should not send support messages without a parent or guardian. A parent or guardian may ask us to delete a child’s support message by contacting georges@polysign.lu.

13. Changes to this policy

We may update this policy when the app, website, providers, or legal requirements change. We will post the revised policy on this page and change the effective date. If Cannon Hit’s data practices change materially, we will also update the relevant store disclosures and provide any notice required by law.

14. Contact

For privacy or support questions, contact: