Privacy Policy

1Scope and who is responsible

This policy applies to the Murmur apps on every platform and the Murmur website, provided by Wei Liu, an individual based in Melbourne, Australia. Wei Liu is responsible for the personal information described here. In this policy, “we”, “us” and “our” mean Wei Liu.

When you buy a subscription, Link, which is part of Stripe, is the legal seller of the purchase. The payment details you enter at checkout are handled by Link under its own privacy policy.

Where your data goes depends on the feature, so each one is covered separately below. Some of it depends on your settings; section 11 explains how to check this in the app.

2Data stored on your device

On your Mac, the following is stored in ~/Library/Application Support/Murmur/, in the macOS Keychain, or in macOS preferences. The sections below explain which features send part of it with a request.

3What each feature sends

3.1Offline recognition (done on your Mac)

With offline recognition, transcription happens on your Mac and the audio is not sent to us or to any recognition provider. There is one exception: if your macOS version can’t recognise the current language offline, the system may send the audio to the operating system provider, under its privacy policy.

3.2Cloud recognition

• On the free allowance, audio goes from your Mac to the speech recognition provider (United States). Each time you start recording, our server issues a single-use temporary credential, so we know when you start recording, but the audio does not pass through our servers.
• With your own service key, audio goes directly to that provider.
• Sent along with each recognition request: words from your dictionary, words learned by the input method, and, if screen context is on, up to 40 proper nouns taken from the text on screen. These help the recogniser get names and terms right.
• Long recordings are transcribed with speakers identified. On the free allowance (one free long recording, up to 3 minutes), they stream to the speech recognition provider in real time, like dictation. With your own key, the whole recording is uploaded to that provider as a file, and the app asks the provider to delete it once transcription is done. If the app quits during transcription, the file may be kept for the provider’s own retention period.

3.3Cleanup, translation, and voice commands

These features send the transcript to a language model once:

• Cleanup, which turns spoken text into written text;
• Translation;
• Ask, which treats what you say as an instruction and inserts the AI’s answer. Any text you have selected is sent too;
• Voice edit, which changes the text you have selected according to what you say, and sends that selection.

Where the text goes:

• On the free allowance, the text goes to our server and then to the text processing provider (China). Our server only forwards and meters it. It does not keep the text, and the text does not appear in our logs.
• With your own service key, the text goes to the provider you added the key for; some pass it on to the model provider you chose.
• If web search is on for Ask and you have added your own search service key, your search queries go to that service.

The same request may also include:

• your dictionary;
• if screen context is on, up to 1,500 characters of on-screen text;
• if Personal style is on (it is off by default), up to 3 examples of what you said and how it was cleaned up, taken from your recent history.

Prompt skills tidies up prompts you dictate into AI tools. When it is on, a longer sentence is sent once more to the same provider to work out what kind of request it is. Only the text is sent, with no audio and no window details.

Even with offline recognition (done on your Mac), cleanup still sends text to a language model. To keep everything you say on your Mac, choose offline recognition, set cleanup to Off, and don’t use translation, Ask, or Voice edit.

3.4Input method

• Words the input method learns are stored on this Mac only.
• When you press the shortcut to have AI clean up the current sentence, the related words from your dictionary and learned words (up to 500) go with the request, including when you use offline recognition (done on your Mac). Turning off “Let AI use my own words” in Settings › Input Method stops this entirely.
• Cloud candidates are off by default. When on, pinyin you have not yet confirmed goes through our server to the text processing provider (China). Only the pinyin is sent.

3.5Screen context

• Off by default on new installs. If you upgraded from an earlier version, your previous choice is kept. Turn it on or off in Settings › Recognition.
• When on, Murmur reads the visible text of the front window once, at the moment you start recording. It uses macOS accessibility features and takes no screenshot. If the front app is on your deny list, macOS secure input is active, or the cursor is in a password field, nothing in the window is read.
• With cloud recognition, proper nouns taken from that text go to the recognition provider with the audio.
• With cleanup on, or when you use translation or Ask, up to 1,500 characters of it go to the language model provider with the transcript. On the free allowance it goes through our server; with your own key it goes to the provider for that key.
• The text is not stored or logged on your Mac, and words from the screen are never added to your dictionary. With offline recognition (done on your Mac) and cleanup off, nothing is read.

4Records on our servers

Our servers keep:

• Account. Your email address, account status, and allowance.
• Sign-in sessions. Network address and device or browser information, used to keep your account secure.
• Usage records. For each sentence you dictate (including offline recognition done on your Mac, which doesn’t use allowance), the character count, how long you spoke, the feature, the path it took (offline recognition, your own key, or the free allowance), and the time. We use these to calculate allowance and prevent abuse. They don’t include anything you said.
• Language model forwarding records. For each request we forward, the tier, model, provider, estimated usage, and cost. No text.
• Seat requests. See section 6.
• Invite code attempts. Network address, email address, the first characters of the code, and the result, used to prevent invite code abuse. Kept for 30 days.
• Email delivery records. The delivery status of the email that tells you your seat is open.
• Request logs. Time, route, status, duration, and account ID. No email address, content, or keys.
• Subscription records. Subscription ID, plan, the price you chose, status, the start and end of the current period, whether it is set to cancel at the end of the period, and the plan before and after a switch. We use these to work out your plan.
• Payment event records. The notices Stripe sends us, as received, when you pay, renew, change your subscription, get a refund, or open a dispute. We use them to activate your plan, reconcile payments, and handle refunds and disputes. They may contain the email address, name, billing address, and tax ID you enter at checkout; the amount, tax, and currency; and Stripe’s customer, subscription, and invoice IDs. Refund and dispute notices may also contain your card brand, last four digits, and expiry date. They never contain your full card number or security code.
• Unclaimed orders. If you pay without signing in, we record the order under the email address you paid with (email address, order ID, plan, and period), so it can be matched to your account when you sign in with that address.

Even when you are not signed in, the app reads public configuration from time to time and checks for a new version once a day. These requests carry no identity and none of your content.

How long we keep it. When you delete your account, we delete your account, sign-in sessions, usage records, email delivery records, application, and invite code attempts from our live systems within 30 days. Request logs are deleted automatically under our hosting provider’s retention period. Copies in backups are overwritten when the backup cycle ends. Payment and subscription records (subscription records, payment event records, and unclaimed orders) are not deleted with your account. We use them to reconcile payments and handle refunds and disputes. To meet Australian tax record-keeping requirements, we keep them for 5 years from the date each record is created, and then delete them.

5Providers and locations

• Where requests are handled. The database is in Singapore. Requests from the app and the website may also pass through the country of the server nearest you.
• International transfers. Your data may be transferred to the United States, China, Singapore, Australia, and the countries of the servers mentioned above. Data protection laws there may differ from those where you live. China does not have an adequacy decision from the European Union. We give each provider only the data it needs for the feature you use. If you are in the European Economic Area or the UK, we make these transfers because they are necessary to provide the features you use under our contract with you.
• Model training. We don’t train models on your content. The speech recognition provider states that it does not train on customer content and does not store real-time audio by default. The text processing provider’s API terms do not rule out training on submitted content, and we have not found a published retention period. If you don’t want your content to reach the text processing provider, use Murmur signed out; or, once signed in, set cleanup to Off, don’t use translation, Ask, Voice edit or the website trial, and skip the three career questions. To find out exactly which providers we use, write to us and we will tell you.
• No selling. We don’t sell your personal information or share it for advertising. Data goes only to the providers above, as needed to run the service, and to any provider you have added your own key for.

6Information the website collects

• Seat requests. Your email address, the message you write, the interface language, and your browser type, plus a one-way hash of your network address used only to limit repeat submissions. Submitting sets up an account for that email in advance, and the form is forwarded to our inbox through our email provider.
• Trying cleanup on the website. The text you paste goes through our server to the text processing provider (China). Our server does not keep it. We also keep a daily one-way hash of your network address to limit the number of tries.
• Membership page. When you are signed in and choose a payment button, we put your account ID and sign-in email in the address of Stripe’s checkout page, so the payment can be matched to your account. The upgrade button in the app does the same. The checkout page is hosted by Stripe and is subject to Link’s terms and privacy policy.
• Scripts. Scripts on the sign-in, try, and skills pages are hosted on this site. When bot protection is on, those three pages also load a script from our bot protection provider.
• Cookies and local storage. The website uses no advertising or analytics cookies. Once you sign in, your sign-in state is stored in your browser. The bot protection provider may set the cookies it needs to work.
• Do Not Track. We don’t track you across websites, so we don’t respond differently to a browser’s Do Not Track signal.
• Hosting. The website is hosted by our website hosting provider, which receives standard access information such as your network address when you visit.

7Legal bases

If you are in the European Economic Area or the UK, we rely on these legal bases:

• Providing the features you use (recognition, cleanup, your account, allowance): performance of our contract with you.
• Usage metering, abuse prevention, sign-in sessions, and request logs: our legitimate interest in keeping the service secure and fair.
• Seat requests: steps taken at your request, when you submit one, before entering into a contract.
• Subscription records and payment event records: performance of our contract with you. Reconciling payments and handling refunds and disputes: our legitimate interest.
• Responding to legal requirements: compliance with a legal obligation.

8Your rights

• Data on your device is yours to manage directly; see section 2.
• For data on our servers, you can ask for a copy, ask us to correct it, or ask us to delete your account. Email support@day1aifitness.com from your registered address so we can confirm it is you. We reply within 30 days.
• Section 4 explains what happens to payment and subscription records when you delete your account.
• For purchase information that Link holds, ask Link to see or delete it under Link’s privacy policy. When Link deletes your data, it also cancels any subscription bought through it.
• If you are in the European Economic Area or the UK, you can also object to certain processing or ask us to restrict it, and ask for your data in a commonly used format.
• If you have a complaint, please email us first. We will reply within 30 days. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au) or to the data protection authority where you live.

9Children

We don’t knowingly collect personal information from anyone under 16. If we learn that we have, we will delete it.

10Data breaches and changes to this policy

• If a data breach is likely to affect you, we will notify you promptly and report it to regulators as applicable law requires.
• Each update to this policy is dated at the top of the page. For significant changes to how existing features handle your data that are to your disadvantage, we will email registered users at least 30 days before they take effect and show a notice in the app.
• Information about how a new feature handles data takes effect when that feature launches and applies to people who start using it.

11Checking these claims yourself

• Files on your Mac. Everything stored locally is in ~/Library/Application Support/Murmur/, and you can open it at any time. Deleting that folder deletes the copy on your Mac; records on our servers and with providers are handled as described in sections 4 and 5.
• Network connections. A network monitor such as LuLu shows the addresses Murmur connects to. To check which kind of provider each address belongs to, email us.
• Where your data went. In the app’s History, “Where your data goes” uses your current settings to show what a dictation sends and where.

12Contact

For questions about this policy or your data, email support@day1aifitness.com.