Purplelink
← Outbound Veil

Outbound Veil compatibility

Where Outbound Veil works: apps and fields tested

Outbound Veil can only check text that an app hands to macOS. This page lists each app and field it has been tried in, what happened, and which ones have not been tried at all.

Outbound Veil has been tested and works in TextEdit, Notes, Messages, Microsoft Word, and in Chrome text areas, including the ChatGPT and claude.ai prompt boxes. It cannot read the body of a new message in Apple Mail, and it is switched off in Terminal by default. Safari, Slack, VS Code, Pages, Google Docs and most other apps have not been tested.

What the three statuses mean

Every status is written out in words. The same test text was used each time: Maria Gonzalez, SSN 472-81-0094, born on March 3, 1990. All of it is invented.

The only recorded test run was on one Mac running macOS 26 on October 3, 2026, with builds made before release 1.0.0. Releases 1.0.1, 1.0.2 and 1.1.0 changed power use, the update key and licensing. The tests have not been recorded again since.

Checking and Redact all

Apps and fields tried with the badge and Redact all. Highlighting is the marking drawn on the text itself.
App and fieldStatusWhat was recorded
TextEdit, documentTested and worksBadge appeared. Redact all rewrote the field in place. Highlighted word by word.
Notes, note bodyTested and worksBadge appeared. Redact all rewrote the field in place. macOS reports where each word sits, so findings are highlighted word by word.
Messages, message boxTested and worksTried in a new message with no recipient, so nothing was sent. Badge appeared and Redact all rewrote the field. How highlighting looks in Messages was not measured.
Microsoft Word, document bodyTested and worksBadge appeared. Redact all rewrote the field in place. macOS reports where each word sits, so findings are highlighted word by word.
Chrome, plain text area on a web formTested and worksFour findings. Redact all replaced them with placeholders. macOS reports where each word sits, so findings are highlighted word by word.
Chrome, ChatGPT prompt boxTested and worksFour findings. Redact all replaced them with placeholders. macOS does not report where each word sits in this box, so the whole box is outlined instead of each word being highlighted.
Chrome, claude.ai prompt boxTested and worksFour findings. Redact all replaced them with placeholders. The whole box is outlined, as in ChatGPT.
Apple Mail, body of a new messageTested and does not workMail hands macOS a web view with no text in it, so there is nothing to check. The menu says Cannot read this field in Mail instead of showing an empty badge. No fix is currently planned.
Terminal, promptTested and does not workTerminal exposes its whole screen history as one block of text, not the line you are typing, and the text cannot be edited. Outbound Veil is switched off in Terminal by default. iTerm2, Warp and Ghostty start switched off too, and were not tested one by one.
Safari, plain text area, ChatGPT prompt box and claude.ai prompt boxNot testedThe tool used for testing cannot type into Safari, so the three Safari rows were never run.
Firefox, Edge, Brave, Arc and other browsersNot testedNo result recorded for any field.
Google Docs and other web editors in a browserNot testedNo result recorded. Web editors draw their own text areas, so a result in a plain text area says nothing about them.
Claude desktop app, prompt boxNot testedOnly probed. macOS reported the box as readable and editable, but no note was checked and Redact all was not tried.
ChatGPT desktop app, prompt boxNot testedNo result recorded.
Slack, message boxNot testedSlack was not installed on the test Mac.
Microsoft Teams, message boxNot testedNo result recorded.
VS Code, editorNot testedVS Code was not installed on the test Mac.
Other apps built on Electron, such as Discord, Notion or ObsidianNot testedOutbound Veil asks apps built on Chromium or Electron to expose their fields to macOS. No result is recorded for any of them.
Pages, documentNot testedNo result recorded.
Password fieldsNot testedOutbound Veil is built to skip them, and an automated test covers that skip with a simulated password field. It has not been confirmed on a real macOS password field. 1Password, Bitwarden, Keychain Access and the Passwords app start switched off.

Send hold

Send hold is optional and is turned on one app at a time in Settings, on the Apps tab. It holds the send key while a field still has findings. It needs Input Monitoring, which macOS asks for only when you turn a hold on.

Apps tried with send hold. In browsers the hold applies only on AI chat pages.
AppStatusWhat was recorded
MessagesTested and worksIn a new message with no recipient, a made-up number followed by Return was held. A panel offered Redact all, Send anyway and Cancel.
TextEditNot testedOne trial, on a Mac under extreme load, did not hold Return. Outbound Veil is designed to let the key through when a check runs late. The trial has not been repeated on an idle Mac.
Apple MailNot testedThe body of a new message cannot be read, so there is nothing to hold. The welcome guide does not offer Mail for send hold.
SlackNot testedSlack was not installed on the test Mac.
ChatGPT and claude.ai in ChromeNot testedThe prompt boxes can be read and rewritten, but holding the send key on those pages has not been recorded.
ChatGPT and claude.ai in SafariNot testedNo result recorded.

What decides whether a field can be read

Outbound Veil reads a field only when macOS describes it as a text field, text area, combo box or search field and hands over its text. Three things follow.

Check your own app in the 7-day trial

The trial is the complete app for seven days, with no account. That is enough time to try the apps you use. Use made-up details only.

  1. Download the trial from the Outbound Veil page, open it and allow Accessibility. The setup guide shows where.
  2. Click into a text field in the app you want to test and type or paste Maria Gonzalez, SSN 472-81-0094, born on March 3, 1990. Values such as 555 phone numbers or example.com addresses may not be flagged, so use this line.
  3. Wait a second. A badge with a number of findings near the field means the field can be read. If the menu bar menu says Cannot read this field followed by the app’s name, it cannot. If nothing shows, check that checking is not paused and that Accessibility is still on.
  4. Click the badge and choose Redact all. The field should now hold placeholders such as [SSN_1]. If the app refuses the edit, the redacted text is put on your clipboard with a notice.
  5. Choose Copy details of the focused field in the menu bar menu. It copies the app, the kind of field and whether it is readable and editable, and never what you typed. Email it to ben@purplelink.llc if you want a row added here.
  6. For send hold, open Settings, choose the Apps tab and set the app to Check and hold send. Test it only where a stray send does no harm, such as a document, or a new message with no recipient.

If your app cannot be read, the free trial is how to find out. If you buy and change your mind, email ben@purplelink.llc within 14 days of buying for a refund (terms).

Limits

Latin-script names only. It also flags public figures’ names. It will miss some things. It lowers the chance of a mistake and is not a compliance product.

More about Outbound Veil