Privacy Policy

Moosh · Last updated 25 September 2026

Workingcat ("the developer") explains below how the Moosh mini app inside Toss, the separately installed Android and iOS apps, and the website at moosh.workingcat.kr handle information.

1. Information used by the service

The current mini app does not require a developer account or separate sign-in.

Item selection, touch movement, and damage level are used during a session to render the screen, sound, and haptics.
The mini app uses a network connection to download its code, images, and sound files.
When you choose a language on the website, the browser stores that choice as wc-lang in localStorage.

The current mini app code does not send these interactions to a developer server or link them to an account.

2. Connection data and platforms

Toss and the content delivery service may process technical connection information, such as IP addresses, to open the mini app and deliver files. See Toss’s policy for its practices and retention periods. The website is served by Cloudflare Pages, which may process connection and traffic information when delivering page requests. See Cloudflare’s policy for its detailed practices and retention periods.

Toss Privacy Policy · Cloudflare Privacy Policy

3. Toss mini app permissions and external features

The current Toss mini app configuration requests no additional permissions.
On supported devices, the mini app may call the Toss haptic feature.
The current mini app code includes no separate advertising or analytics SDK.

Permissions and haptics of the Toss app itself are governed by Toss.

4. Separately installed Android and iOS apps

The separately installed apps process interactions in memory during a session and play audio and haptics. The current app code has no separate account, advertising or analytics SDK, feature to send interaction data to a developer server, or recording feature. Android app configuration declares FOREGROUND_SERVICE and FOREGROUND_SERVICE_MEDIA_PLAYBACK for audio playback and uses haptics. Operating system, app store, and framework communications and permissions cannot all be verified from developer code, so we do not claim that the installed apps have no network traffic.

5. Storage on your device

The current mini app code does not store interaction history in browser storage. You can remove the website language preference by clearing site data in your browser. Storage and cookie practices of the Toss app itself are governed by Toss.

6. Retention and deletion

Interaction state in the mini app and installed apps is used in memory during a session and is not kept after it ends. The developer does not separately retain interaction history to delete. Platform and hosting services retain connection information under their own policies.

7. Changes to this policy

We will update this page and its date if our processing changes.

8. Contact

Workingcat · support@workingcat.kr