MuraTalk / Privacy policy

Privacy policy

Version · 1 November 2026

MuraTalk is a free hobby app operated by Jonathan Regan-Beasley (JRB AI), for people aged 18 or older. This policy explains what stays on your iPhone and what can be sent elsewhere. There is no MuraTalk account, advertising or developer-added analytics in the app. When you accept the terms, MuraTalk asks iOS whether you are 18 or older, using Apple’s Declared Age Range. It receives only that answer, uses it once and does not store it.

How conversations are processed

The app’s default AI conversation processing runs on your iPhone. MuraTalk does not send your chats, remembered facts or to-do list to the developer. We do not collect this conversation content, sell it to advertisers or use it to train models.

You choose whether to send conversation context or spoken reply text to a custom server. Weather, maps and search make separate requests to external services; those requests can include personal details from your conversation. These connections, Apple services, website hosting and information you choose to email us are explained below.

Information on your iPhone

MuraTalk saves chat history, an optional profile, remembered facts, tasks and connection settings locally. Your acceptance of the terms is also saved locally, with the accepted version and date. You can skip the profile. Conversations can produce remembered facts, and concrete tasks from your messages can be saved automatically with a notice and Undo. Requested task completion or removal also has Undo. The local task list has no cloud sync or task notifications.

Chat history and saved facts are separate: deleting a chat does not delete facts already remembered from it. Reading your saved tasks or relevant past-chat excerpts can provide context for replies. The developer cannot remotely read this local information.

The app marks its Application Support folder, containing its saved chat and task files, for exclusion from iCloud and computer backups. Some preferences are stored separately in iOS preferences; this is not a promise that every setting is excluded from backups. Optional chat and voice API keys are held separately in the iPhone Keychain using device-only protection.

On-device conversation and speech

Apple’s on-device model generates replies by default when Apple Intelligence is available. Microphone speech is transcribed on your iPhone; MuraTalk does not save microphone recordings. Apple may download the required speech-recognition assets. Apple speech reads replies on-device, using an installed voice. Additional Apple voices are managed in iPhone Settings. MuraTalk does not download its own speech models.

On-device replies can still use the network tools below. A server you separately enable can receive text derived from speech, even though recognition itself happens on-device.

Optional servers you configure

Custom chat is off by default. MuraTalk does not provide public access to the developer’s private AI server. If you enable a compatible server, relevant conversation context, your profile, remembered facts and tool results are sent to the endpoint you enter. Results may include requested task or Calendar information, past-chat excerpts and location-related results.

While custom chat is enabled, the app also sends new portions of your conversation, including user and assistant messages, together with known facts, to extract useful memories. These requests can include more chat text than a normal reply request, potentially all the unprocessed conversation within the app’s size limit. They can run after quiet periods, when starting or opening another chat, or when the app moves to the background. Memory tidying can also send saved facts to that server.

Custom voice is a separate choice. If selected, the text being read aloud goes to your voice server and generated audio returns to your phone. This applies even to replies generated on-device. Voice requests do not automatically include the full conversation or saved profile, but spoken text can itself contain personal information.

When you use the optional combined gateway, reply text is passed to the voice service on your server. Your phone fetches matching prepared audio. The gateway temporarily holds reply text and prepared audio in memory; the server owner controls upstream logging and retention. The MuraTalk developer receives none of this data.

Server operators control their own processing, retention, use for training and onward sharing. A server you configure may be hosted overseas; MuraTalk does not guarantee where it processes or stores information. Use services you trust and check their policies. Turning a server option off stops new requests through that option; it does not erase information already sent.

Weather, maps and web services

Weather requests send a place name, possibly your saved home town, to Apple’s place lookup service and the resulting coordinates to Apple Weather through WeatherKit. Forecasts appear in a temporary card and are not saved in chat history, learned as memories or sent to your custom AI server. The requested place is saved with the conversation so you can choose Refresh weather to fetch current conditions. Place searches and routes use Apple Maps. Your current location can be used when needed and permitted.

If you configure SearXNG, search queries go to that service and its configured search engines. Page reading fetches public HTTPS pages. Relevant results can go to your custom chat server when enabled. Without integrated search, MuraTalk can display a browser-search query. Tapping to open it sends the query to Google or DuckDuckGo; MuraTalk’s assistant cannot read those browser results. External services receive normal connection information, such as IP addresses, and apply their own policies.

Your choices and deletion

You can edit or remove profile details, facts and tasks, delete saved chats, disable optional servers and change permissions in iPhone Settings. Calendar access requires permission; new events require confirmation. Those records may sync through your Apple settings. Timers use local notifications with permission.

Deleting the app removes its local app files. Unreadable files kept locally for recovery are also app files. Uninstalling does not explicitly clear Keychain entries: clear both server key fields before uninstalling if you want them removed. Local deletions do not erase copies already received by external services. Contact those operators about their copies.

This website and contact

The website consists of static pages with no signup or submission form. It is published as a ChatGPT Site. The host may process IP addresses and ordinary request logs to deliver and protect the site. MuraTalk does not receive those logs and does not set how long the host keeps them.

We use Cloudflare Web Analytics to understand website traffic and page performance. Its small browser script reports page views, visits, referring sites, country, browser and device categories, and loading times. Cloudflare states that this service does not use cookies, browser storage or visitor fingerprinting to identify people, and does not track individuals across websites. The developer sees website statistics, not your MuraTalk conversations, tasks or other app data. Cloudflare receives normal connection information when your browser loads the script and sends measurements; see Cloudflare’s privacy policy. Browser settings and content blockers may prevent these measurements.

If you email jrb@muratalk.com.au, Jonathan Regan-Beasley (JRB AI) receives your address and what you send to handle your enquiry. “Report this reply” opens a message in your mail app containing that reply and the app version; nothing is sent unless you send it. Avoid including sensitive chat content. Apple handles App Store and TestFlight information under its own policies. Contact the same address with privacy questions. Material changes to this policy will be dated and explained here.