Use cases
Start with the task you want AI to help with.
Each page runs a fictional example through the real Hushbridge engine. You see what gets swapped, what stays, and what to check before you send.
Six worked examples
- Read the client emails example
Client emails
Get a clear follow-up email drafted from your notes on a client matter.
In the example: A fictional lease dispute with a client name, an email, a phone number, a case number and a company.
Watch for: Titles and the story around a name stay in the text.
- Read the document summaries example
Document summaries
Turn a long memo, letter or report into a few points you can act on.
In the example: A fictional memo with two people, a landlord company, a street address and contact details.
Watch for: Roles, rents and percentages stay in the text.
- Read the support replies example
Support replies
Draft a reply to a customer ticket that solves the problem on the first try.
In the example: A fictional ticket with a name, an email, a phone number and a shipping address.
Watch for: Order and ticket numbers are not detected.
- Read the financial notes example
Financial notes
Write a neutral case note on a disputed charge for the file.
In the example: A fictional dispute with a card number, a routing number, an account number and an IBAN.
Watch for: Amounts, dates and merchant names stay in the text.
- Read the code and secrets example
Code and secrets
Ask for help with a failing config without pasting live keys.
In the example: A fictional .env file and a JSON object with an API key, a connection string and customer data.
Watch for: A bare JSON number that gets swapped breaks the syntax.
- Read the ai applications example
AI applications
Protect user text inside your own app before your model call, and restore the streamed reply.
In the example: The SDK calls on a fictional prompt, with a fixed reply streamed through the restorer.
Watch for: The SDK is not on npm yet. The tarball is on the download page.
Choosing where to start
Pick the page that matches the text you paste most often. If you write to clients, start with client emails. If your text comes from tickets or account screens, the support and finance pages show which numbers are found and which are not. If you build software, read code and secrets first, then AI applications for the SDK. Every page lists its limits. Detection can miss a name with no cue, and context can still point to a person. The extension does not scan attachments, and a chat site's page can read what you type. Review the protected text before you send it, whichever task you start with.