How card numbers, ID numbers and other secrets go past the assistant, straight to your organization
When a job needs a secret, such as a card number, a social security number or a date of birth, the assistant does not ask for it in the chat. A secure form opens instead, and what you type goes from your device straight to your organization's system. The assistant never sees it. It is told only the outcome.
A secure form
A card appears in the chat with a lock and the form's name, for example Financing application · Mrs Alvarez, and an Open form button. The form is plain: labeled fields, the required ones marked, and a line at the bottom saying where it goes, such as Goes straight to Meridian.
Fill it in and choose Submit. The card then says Sent securely — not shared with the assistant, and shows the result your organization chooses to share, such as Financing approved. If you cancel, the card says Canceled — nothing was sent and the assistant is told you canceled.
A customer can fill a form in themselves on your iPad.
A payment page
For a card payment, an organization may send you to its payment processor's own page instead. The card shows the page's address first. It opens in a private browser view the app and the assistant can't see into. Neither the app nor the assistant ever holds the card number. The app warns you if the address is not secure or uses look-alike characters.
A secure view
Secure views go the other way: details the assistant must not see, shown to you briefly. Tap Show and the app fetches them straight from your organization. They stay on screen for a short time, cannot be copied, and blur in the app switcher. Then they hide; open them again to fetch them fresh.
On this device (free)
Your own MCP servers can ask you for information through a form of their own. It works the same way: Sent to the server only — not shared with the assistant.
The same manual ships inside the app. This section as Markdown