Privacy Policy

Last updated 2 November 2026

Mortise is provided by Exception To Policy (Seattle, Washington). Contact us at support@mortiseapp.com.

Mortise is built so that your conversations never reach us. This page explains exactly what stays on your device, and the few cases where data leaves it.

What we collect

Nothing. The App has no account system, no analytics, no advertising, no crash-reporting SDK, and no server of ours to talk to. We do not track you across apps or websites, and we do not build a profile of you. We could not identify you if we wanted to.

What stays on your device

Your conversations, the documents you import, the summaries and notes the App derives from them, and the model weights themselves are all stored locally. Specifically:

  • Conversations, documents, and derived data live in a database on your device that is encrypted at rest, with the key held in the system keychain.
  • On iOS, stored files additionally use Apple's complete file protection, so they are unreadable while the device is locked.
  • Language models run entirely on your device's own processor. Prompts are never transmitted for processing — there is no cloud inference step.

Camera, photos, and the Share sheet

The App uses the camera for two things only: Scan document, on iPhone and iPad, which opens Apple's document camera, and scanning the pairing code shown by another of your own devices (see Device Sync, below). It asks for camera access the first time you use either one.

Photos and screenshots are chosen with the system photo picker, which gives the App only the pictures you pick. The App does not ask for access to your photo library.

A scanned page, photo, or screenshot is turned into a document on your device. Its location and other metadata are removed, and its text is read by Apple's on-device text recognition. Images are never sent to us or to any server.

On iPhone and iPad, Mortise appears in the Share sheet. Sharing a file to it only copies that file into the App's own storage, to be added to your library the next time the App is open. The Share extension makes no network request.

Deleting the App removes all of it. We hold no backup and cannot restore it.

When data does leave your device

There are exactly six cases, and you control all six.

1. Downloading a model

Models are hosted on Hugging Face. When you choose to download one, your device requests it directly from Hugging Face, which will see your IP address and which model you asked for, under their privacy policy. The App asks before the first download and never starts one on its own. No identifier of ours is attached to the request.

2. Online lookups — off unless you turn it on

The "Online lookups" setting is disabled by default. If you turn it on, capable models can look up a subject on English Wikipedia or Wikidata. Wikipedia and Wikidata requests go directly from your device to the Wikimedia Foundation. They will see the lookup text, your IP address, and a User-Agent that names Mortise, under their privacy policy. We do not proxy, log, or retain lookups — the App has no server of ours in that path. There is no API key.

The lookup text is derived from your conversation, so treat it as leaving your device. If that matters for a given question, leave the setting off — the App works fully without it. More detail is on our online lookups page.

Earlier versions offered an optional Brave Search API key. Updating the App deletes any key that was stored on this device, along with the old web-search setting. That consent is not carried forward: Online lookups starts off.

3. Open links — off unless you turn it on

The "Open links" setting is disabled by default, and it is separate from Online lookups. If you turn it on and send a web address, the App downloads that one page on your device and gives the text to the model. The site sees the address, your IP address, and a User-Agent that names Mortise. The conversation itself is not sent, and the App has no server of ours in that path. The App does not follow other links on the page, does not send cookies, and does not download audio or video.

The first time a message contains a link, the App explains this and asks before downloading. You can turn the setting off later in Settings. While it is off, a link is ordinary text.

4. Let the model open pages — off unless you turn it on

The "Let the model open pages" setting is disabled by default, and it is separate from Open links and Online lookups. The App asks before turning it on. When it is on and a question needs a website, a capable model may open a site it names, such as ford.com, and links shown on the pages it opens, up to three pages a reply. The App downloads each page on your device and gives excerpts to the model. Each site sees the address, your IP address, and a User-Agent that names Mortise.

The model can only name a site, open an address you wrote, or pick a link a page already showed. Which site it opens follows from your question, and that site learns that its page was opened. The model cannot write a path or a query, so nothing else from your conversation goes into an address, and the conversation itself is not sent. The App follows each site's robots.txt, does not send cookies, does not run scripts, and does not download audio or video. The App has no server of ours in that path. While the setting is off, the model cannot open pages.

5. Reports and feedback you choose to send

If you use "Report this response", "Report this error", or "Suggest improvements", the App composes an email and opens it in your own mail client. You see the full text before anything is sent, and you send it yourself. Nothing is transmitted in the background.

A report includes what you write. It includes recent error details, and your app version and device model, only if you tick those boxes — both are shown in the preview. We use reports to fix problems and improve the App, and we reply only to the address you send from.

6. Device Sync — off unless you turn it on

Device Sync (in Settings) is disabled by default. When you turn it on, the App asks for local network access and looks for your own devices running Mortise on the same network. A device can connect only after you pair it, by scanning a QR code or comparing six digits on both screens, and you confirm any device that another of your devices introduces.

Paired devices sync your chats, documents, and knowledge bases while they are open together. Everything travels directly between your devices over the local network, encrypted in transit. There is no server in between — ours, Apple's, or anyone else's, and nothing is sent to the internet. A knowledge base you keep on one device stays there. Turning Device Sync off stops it; removing a device stops that device syncing.

What the App deliberately does not do

  • No account, sign-in, or email address is required or requested.
  • No analytics, telemetry, or usage statistics of any kind.
  • No advertising identifiers and no tracking.
  • No fonts, assets, or configuration fetched from a content-delivery network at launch — everything the App needs to start is in the bundle.
  • No access to your microphone, contacts, or location.
  • No access to your photo library: the App sees only the photos you pick in the system picker.

Children

The App is not directed at children under 13, and we do not knowingly collect information from them. Since we collect nothing from anyone, there is nothing for us to delete — but note that language models can produce content unsuitable for children, and the App does not filter output.

Your rights

Privacy laws such as the GDPR and CCPA give you rights to access, correct, export, or delete the personal data a company holds about you. We hold none, so there is nothing for us to produce or erase. The data the App creates is under your control on your own device, and deleting the App destroys it.

Changes to this policy

If we change what the App sends over the network, we will update this page and its "last updated" date, and describe the change in the App's release notes.


Questions? Email support@mortiseapp.com.