FlareJab

FlareJab Privacy Policy

Last updated: September 26, 2026

This policy covers the current closed-test version of the FlareJab Android app (com.hyeonsang.flarejab) and its daily leaderboard, provided by Wingnut Polaris. For privacy questions, contact wingnutpolaris@gmail.com.

At a glance

1. Camera, face and hand input

Camera permission lets the app detect hand movements and facial expressions and display effects. CameraX and MediaPipe process frames and detection results on your device. Face analysis uses eye and mouth movements as game input; it is not an identity-recognition feature.

FlareJab's leaderboard server does not receive camera frames, photos, face or hand coordinates, or face-analysis values. If you choose to record, the camera preview can appear in the recorded screen video.

2. Screen recording and sharing

Recording uses Android screen capture. The recording can include notifications, other apps and other content visible on the display, not just FlareJab. Stay in the app while recording and take care to prevent sensitive notifications from appearing. The recording does not include microphone or device audio.

Finished videos are saved on your device. On Android 10 and later, the app uses the device's Movies/FlareJab media location. Older Android versions use app-specific storage. FlareJab does not automatically upload these videos to its own servers.

When you share a video or game result, it is passed to the app you choose. That app or service's rules then govern its upload, visibility, retention and deletion. Your device's photo or video backup service may also operate separately according to your settings.

3. Data stored on your device

The app stores settings such as language and effects, game records, scores, experience points, quest and badge progress, leaderboard caches and recording file locations on your device. Device information and runtime measurements support tracking, rendering, recording and the diagnostics display.

There is no FlareJab account service that synchronizes all of these local records to a server. Daily leaderboard information is transmitted separately as described below.

4. Daily leaderboard data

To run the Giggle Rush daily leaderboard and limit duplicate submissions and excessive requests, the app and service process the following information.

When a completed Giggle Rush result contains a valid same-day score, opening its result screen attempts a submission. Whether a request is sent depends on conditions such as a better score and submission limits. The current version has no separate switch to turn off automatic leaderboard submission. Looking up your own rank can also transmit your device identifier.

The server applies a secret-key HMAC to the received device identifier. The leaderboard database stores that derived value rather than the original identifier. This does not mean that the original identifier never reaches the server.

The public top 10 shows ranks, scores and public aliases beginning with FJ-. The public leaderboard response also includes rounds and update timestamps. The alias is not regenerated every day, so results across different days can be linked to the same alias. The app does not ask for a real name or email address to display on the leaderboard.

Leaderboard dates use Korea Standard Time (Asia/Seoul).

5. Service providers and security

The online leaderboard runs on Cloudflare Workers and D1. Communication between the device and leaderboard server uses HTTPS, and the leaderboard database does not store the original device identifier as-is.

Cloudflare may process network information such as IP addresses and request times when delivering, operating and protecting the service. The leaderboard service is configured with sampled operational observations and error logging. FlareJab error logs include the request method, path and error message. These records are separate from daily score data. See the Cloudflare Privacy Policy for information about the provider's processing.

The current app does not include advertising SDKs, advertising-ID-based ad tracking or in-app purchases.

6. Retention and deletion

Local data: You can remove locally stored app settings and records by clearing FlareJab's app data in Android settings or uninstalling the app. This can permanently erase your progress. The app has no separate in-app control to delete all records. Clearing app data does not necessarily remove videos in shared media storage or copies shared or backed up elsewhere. Manage those videos separately in your gallery, file manager or the relevant service.

Daily leaderboard: The database is configured to retain the most recent eight calendar dates, including today, in Korea Standard Time. A daily cleanup removes older scores and daily statistics. Older data may remain briefly depending on when cleanup runs. This is logical deletion from the database, not a promise that all Cloudflare operational logs, backups and recovery data are erased at the same time. Provider settings and retention practices apply separately to those materials.

FlareJab currently has no user accounts or account-deletion feature, and no self-service feature for deleting individual server-side leaderboard records. Uninstalling the app does not immediately delete scores already submitted. You can send questions about privacy and deletion to wingnutpolaris@gmail.com. This contact address is not an instant-deletion API or an automated deletion process.

Support messages: If you email support, your sender address, message and any attachments you choose to send are processed in the support mailbox to handle your inquiry. The leaderboard's eight-day cleanup rule does not apply to these messages. Do not send unnecessary sensitive information such as passwords, identity documents, raw device identifiers or other people's faces.

7. Choices and intended audience

You can change camera permission in Android settings. Turning it off may prevent camera-based games and effects from working. You can play without starting a recording, and sharing requires your action.

The current app is intended for people aged 13 and above. It does not ask for your date of birth or check identity documents to verify age. This audience setting does not mean that privacy requirements for minors are identical in every region.

8. Changes and contact

We will update this policy and its revision date when data-handling practices change. For app help, see FlareJab Support.

한국어 개인정보처리방침