What This Notice Covers
This Notice applies to the Munex mobile application. It describes categories of data that may appear on your device during ordinary use, why those categories exist, which system permissions may be requested, how long hunt materials typically remain, and choices you can make. It does not claim that Munex processes zero data of any kind; creative capture tools necessarily handle the media you choose to create or import.
Categories Tied to a Dual Constraint Mission
- Mission and spin state. Active and historical missions may store identifiers for the selected color chip and scene rule, status values such as active or completed, and timestamps so the Spin Arena can show what you are hunting.
- Hunt relics. When you save a find, Munex stores the image and thumbnail files you confirm, optional note text, optional links to scene audio, and related metadata needed to show Color Wall tiles and detail views.
- Scene audio drafts and finals. If you record or import street sound for a find, audio files are written to app storage and associated with that find for Sound Lane playback.
- Rule Deck selections. Enablement and unlock state for scene-rule packs you manage locally so the inner spin ring draws from your chosen pool.
- Theme and sound mood settings. Preferences such as neon glow intensity, spin-reveal presentation, haptic pulse, ambient loop style, and interaction-sound toggles.
- Coin balance ledger on device. A local balance used by optional digital features inside Munex. Transaction processing, when it occurs through Apple platform services, is handled under Apple's own policies; Munex does not operate a separate cloud identity for that ledger.
Munex does not request precise location, contact lists, or calendar access for the hunt loop described above.
Why Those Materials Exist
Data listed above is processed to deliver the dual-spin challenge, keep your mission visible while you shoot, display Color Wall and Sound Lane, remember Rule Deck and mood choices, and restore your local balance after app restarts. We do not use your finds to train remote models or to build advertising profiles inside Munex.
Permissions You May Be Asked to Grant
- Camera. Requested when you choose to photograph a find for an active mission. If camera hardware is unavailable, Munex hides camera entry points and leaves import as the path for images.
- Photo library. Requested when you import an existing image into Capture Booth.
- Microphone. Requested for scene audio recording and for voice input that becomes note text.
- Speech recognition. Requested when you use voice-to-text for find notes; recognition follows the platform speech service behavior on your device.
You may deny or later revoke permissions in system Settings. Features that depend on a denied permission will not operate until access is restored. Denying a permission does not block the rest of Munex where alternatives exist (for example, typing a note instead of speaking).
Local Storage Before Anything Leaves the Device
Core hunt content is written under the app's sandboxed document area using relative file paths for images, thumbnails, and audio, together with structured local files for missions, relics, rule state, and preferences. Munex is designed so Color Wall and Sound Lane can function without creating a Munex user account or uploading finds to a Munex-operated server.
Network Paths and Platform Services
Opening Terms or Privacy links from Profile may load external pages in a system browser. Those destinations apply their own notices. Optional digital features distributed through the Apple App Store may cause Apple frameworks to exchange limited technical or commercial signals with Apple under Apple's terms. Diagnostic or crash mechanisms provided by the operating system, if enabled on your device, are controlled by platform settings rather than by a Munex account.
Munex does not presently operate a proprietary analytics dashboard that ingests your Color Wall images or scene recordings.
Practical Safeguards We Apply
We rely on the operating system sandbox, relative-path file isolation inside the app container, and permission prompts that appear at the moment of need. These measures reduce exposure but cannot eliminate every risk of device theft, malware on a compromised handset, or platform vulnerabilities. Treat your device lock screen and OS updates as part of protecting hunt media.
How Long Finds Typically Remain
Mission history, relics, and scene audio remain until you delete a find in-app, clear related drafts, or remove the application data. Preference flags remain until you change them or reset the app. Draft audio that is never saved with a find may be discarded when you leave Capture Booth or clear the draft control.
Choices Available Without an Account Console
Because Munex has no mandatory account portal, your primary controls are on-device: delete individual finds, clear scene audio drafts, adjust Sound Mood and Visual Mood, and revoke system permissions. You may also stop using Munex and uninstall it. For questions about this Notice, write to ember.hue@munexlane.co.
Younger Hunters
Munex is not directed at children as a primary audience. If you believe a child has saved content in a way that raises concern under relevant regulatory requirements, contact ember.hue@munexlane.co and use device parental controls where available. We will review requests consistent with applicable laws.
Updates to This Notice
When Munex changes how permissions, local storage, or platform services interact with the hunt loop, we may revise this Notice. The revised text will appear with the app or at the same distribution channel used for these documents. Material shifts will be presented in a manner consistent with applicable laws.
Governing interpretation of privacy-related obligations follows applicable laws and relevant regulatory requirements, without naming a single national court in this Notice. Complaints may be directed to competent dispute resolution bodies where those laws allow.
Closing Line
If you continue the dual-spin hunt after reading, you do so with this Notice in view. For correspondence, use ember.hue@munexlane.co only; that address is the consistent channel named throughout Munex legal pages.
Effective as of September 20, 2026. This date marks when the present Privacy Notice began to apply to Munex builds distributed with it.