Camera and shared rooms
Stash uses your camera and motion tracking to place Momo in your room. Two-phone AR play uses Google Cloud Anchors on Android and Apple devices. After you agree in the app, visual and spatial data from the camera is sent to Google to match a shared starting point on both phones. This includes camera imagery and the position and orientation of the phone and starting point.
Google requires this notice: “To power this session, Google will process sensor data (e.g., camera and location).” Learn how Google handles AR data. Stash does not request GPS or microphone permission and does not use the Geospatial API.
Google says hosting imagery is marked for automatic deletion after hosting finishes. Resolving imagery is processed in memory and not retained afterward. Stash sets the shared reference to expire after 24 hours. Google may retain service identifiers, usage information and diagnostics separately. Google’s ARCore data guidance explains these practices.
The shared starting point is separate from Momo’s hiding spot. Choose a clear area without private documents or people who do not want to appear in the camera view. Practice works without camera access or room sharing.
Connecting two phones
OMIGA’s connection service at signal.omiga.com.au exchanges temporary room and connection identifiers and network setup information, including IP addresses, so the two phones can connect. Google’s STUN service also receives connection requests and network addressing information. Your partner receives connection information needed for this direct link.
The phones exchange the shared-reference identifier, Momo’s position relative to that reference, roles, readiness, tracking status, hints, timing and round results over an encrypted WebRTC data channel. The game does not send camera video, audio or room images to your partner or OMIGA’s connection service. Google’s separate Cloud Anchors processing is described above.
Room codes are for a person physically beside you. They are not an account or proof of identity. Confirm your partner is present before continuing and leave the room if someone unexpected joins. There is no public matchmaking, chat or public profile.
Storage and your choices
Stash saves sound, vibration, reduced-motion and difficulty preferences on your phone. Live room and round state stays in memory and is cleared when you leave. OMIGA does not maintain player accounts, profiles, saved round histories, leaderboards, advertising identifiers or an app analytics database. Stash is free and currently has no ads or in-app purchases.
Local diagnostic logs can include technical errors, tracking state, screen size and round status. The app does not automatically upload these logs to OMIGA. Connection and platform services can process operational or security logs under their own data practices.
You can decline room sharing and use Practice. Leaving a room stops its camera session and disconnects the game. It does not immediately delete data already processed by Google. Change camera permission in your phone’s settings. Uninstalling removes app-local preferences, subject to the platform’s backup and restore settings.
Platform services
On Android, Stash runs on Google Play Services for AR (ARCore), governed by the Google Privacy Policy. Google documents collection of account or device identifiers, performance diagnostics and API usage information. These service practices apply even though Stash has no app analytics SDK.
On Apple devices, ARKit handles camera and motion tracking. Google Cloud Anchors also runs when you choose shared AR. Apple services and device diagnostics you enable are governed by Apple’s privacy policy. App-store purchases, installation and TestFlight feedback are handled by the relevant platform.
Contact and changes
Contact OMIGA at support@omiga.com.au for privacy questions or help. We use the information you choose to send to respond to your request. Keep passwords and private room imagery out of your message unless necessary and agreed.
This policy describes the two-phone version being prepared for private testing. Earlier preview builds use a single phone and do not provide Cloud Anchors. Material changes will be reflected on this page and in the app and store disclosures.