Service Description
Morai provides AI conversation features that can run on your phone, Mac, or an explicitly approved Browser compute node. On-device mode processes conversations on the device with the installed model. Optional Browser compute lets your phone use a model that is running locally in a Browser on a computer you choose.
User Content
In on-device mode, conversation content stays in the app's local storage unless you choose a feature that sends it elsewhere. In Browser compute mode, the current prompt, selected chat history, project or memory context, and required attached images are sent to the Browser node you approve so its local model can generate a response. Morai does not use this feature to perform cloud inference or to store that conversation content on Morai servers.
Data Processing and Storage
- Processing
- On-device conversations are processed locally. Browser compute requests are processed by the local model in the Browser node you approve. Browser compute is optional and is not the same as processing on the phone.
- Storage
- Conversation history is saved in the app's local storage by default. During Browser compute, selected request data is temporarily available to the approved browser runtime for generation. Morai does not store that request content on Morai servers.
- Storage Access
- Storage access may be used to download, save, and manage AI model files and local app data.
- Network Access
- Network access is used for model downloads and related app resources. When you select a remote compute node, it is also used for pairing, WebRTC signaling, and peer-to-peer inference. On-device conversation mode does not require network access after the required models are available.
Browser Compute and WebRTC Pairing
Browser compute starts only after you scan a QR code from the Browser node and approve the pairing in that Browser. The QR code contains a random one-time pairing capability, a six-digit safety code, and a two-minute expiry. After a complete disconnect, the capability cannot be reused and a new QR code is required. Keep QR codes private and approve only a phone you recognize.
After pairing, Morai sends the request data needed for the selected inference through an encrypted WebRTC DataChannel to the approved Browser node. The model remains in that Browser's local runtime. The Browser page must remain open while it is serving the node, and you can end access by disconnecting or unpairing the node in Morai, closing the Browser page, or clearing the site's local data.
Signaling Relay
Morai uses a short-lived signaling relay, currently deployed with Cloudflare Worker and Durable Object infrastructure, to establish the WebRTC connection. The relay forwards signaling envelopes such as SDP, ICE, and presence so the phone and Browser can find and negotiate with each other. It may handle connection metadata needed for routing and security, such as network addresses and signaling timing.
The signaling endpoint does not accept, store, or process prompts, images, model bytes, or generated text. After pairing, conversation data is sent through the WebRTC peer connection rather than through the signaling relay. Optional ICE/TURN services may also process connection metadata needed to establish the peer connection.
Model Use
The AI models provided by Morai are intended for personal use. You may not use Morai for illegal behavior or any activity that violates applicable laws, third-party rights, or platform policies.
Third-Party Services and Sharing
Morai does not send chat content, prompts, images, or generated text to advertising providers. The signaling relay and optional ICE/TURN services may process the connection metadata described above. These services are used to establish and protect the connection; the signaling relay is not used for cloud conversation processing.
Data Security
Morai uses transport security, short-lived pairing capabilities, explicit Browser approval, and access controls appropriate to this feature. You are also responsible for protecting your phone, Browser profile, QR codes, and the computer running the Browser node, including device passcodes, operating system updates, and physical access.
Disclaimer
AI replies may contain errors or inaccuracies. Please use your own judgment when evaluating the accuracy, suitability, and safety of information produced by AI. We are not responsible for losses caused by reliance on AI replies.
Contact
For privacy or support questions, contact us through LoomJ or the support information provided on the App Store listing.