One client email, four steps
What to check before you send to ChatGPT.
An agency owner following up on a proposal needs help with wording. The real email address and price may be unnecessary for that task. The same decision comes up in consulting, recruiting, accounting, and other client work.
Read the video transcript
- Review the fictional email address and proposal amount before approving their replacement.
- The saved composer excerpt shows placeholders replacing the selected email and amount before sending. The video adds line breaks for readability; it is not an independently verified network payload.
- In a separate test run, ChatGPT replies to a protected prompt. LegisComply restores
[email protected]and$12,500locally in the displayed answer. - Check the email, proposal amount, wording, and sender signature before using the draft. Restoring details does not verify the AI’s answer.
- Review the original details.
- In the fictional example below,
[email protected]and$12,500are the two details to consider replacing. Check the rest of the context too. - Inspect the composer before sending.
- The selected values should appear as placeholders, such as
[[LC_…_EMAIL_1]]. Your actual token IDs will differ. If an original value remains, stop and check the selected replacements. - Request a plain-text reply.
- Keep the task in the chat. Ask ChatGPT to preserve the placeholders exactly and avoid opening an email app or editable draft.
- Check the locally restored result.
- When recognized placeholders return, the extension can restore their original values in the displayed reply. Compare them with your source and review the wording before using it.
This guide describes the development build 0.5.12 workflow. The installed version’s interface may differ. For a completed video example, see the Claude walkthrough.
Using another platform? See the Claude · Gemini walkthroughs.
Start with fictional information
Try one small task.
If you use the Chrome extension, open its toolbar menu, read the disclosure, and enable protection. Refresh the ChatGPT tab after installing or updating it. Confirm that the LegisComply status is visible before pasting.
Start a new conversation with the example below. If you do not have the extension, use the separate browser workflow.
Write a short follow-up email to [email protected] about the $12,500 proposal. Ask whether they want to proceed. Include the email and amount in your answer. Preserve bracketed placeholders exactly. Reply as plain text in this chat only. Do not use an editable email block, Gmail, or any other app.
The extension workflow
Review, replace, send, restore.
- 01
Review what the task needs.
Check the email, price, client names, and any identifying context. With the local-model review enabled, you review the scan before pasting. Other settings can protect high-confidence matches automatically. A scan is a review aid: remove or rewrite anything sensitive it misses before sharing.
- 02
Inspect the protected composer.
Approve the selected replacements. The email and amount become placeholders such as
[[LC_…_EMAIL_1]]. The rest of the request stays readable. Check that the selected values have been replaced before sending. - 03
Ask for a plain-text reply with placeholders preserved.
Send the protected prompt and request a plain-text reply in the chat. Editable email blocks can retain placeholders in their body: the extension skips editable areas. In our first run, the email block’s body kept the amount placeholder, so the prompt below explicitly requests plain text. Consistent placeholders let ChatGPT refer to the same details without needing their original values for this writing task. Replacing numbers is unsuitable when the task requires calculations using those numbers.
- 04
Check the restored answer.
LegisComply restores recognized placeholders in the displayed conversation. Compare the email and amount with your source, then review the actual wording. If ChatGPT changes a placeholder or a mapping is unavailable, do not guess what it represents.
Use Protected before sending → View protected version to inspect the protected message. Seeing original values in the restored conversation does not, by itself, tell you what was in the outbound request.
What this changes
Less sensitive text in the prompt. Human review still matters.
- Processing is local; the extension still runs inside ChatGPT’s page.
- Detection, replacement, and restoration happen on your device. The website’s scripts may read original typed text and locally restored values. This workflow is not a guarantee that originals are inaccessible to the provider.
- Context can identify someone without their name.
- A distinctive project, exact date, unusual transaction, or combination of facts can reveal a client. Share only what the task needs and use tools approved for that work.
- Restoration depends on the mapping.
- Keep the tab open until you finish. Without saved recovery, mappings can be lost on refresh. Optional encrypted local recovery has separate setup and retention controls; it is not a cloud backup.
- A restored answer still needs checking.
- Putting an email or price back does not verify ChatGPT’s reasoning, promises, or factual claims. Read the result before sending it to a client.
Read how the extension handles information and why removing names is not anonymization.
A separate browser workflow
You can also review the text before opening ChatGPT.
In the LegisComply browser tool, paste the fictional example, review the suggestions, and add any missing confidential terms. Copy the protected text into ChatGPT. Bring the reply back to the same LegisComply tab to restore recognized placeholders.
This version does not require an extension or an account. Keep its tab open: its mappings are held in memory and disappear on refresh. The browser tool includes fictional samples for client emails, meeting notes, proposals, and contracts.