Use case · Support teams
Send support tickets to AI without the customer’s data.
Your team uses an AI model to draft replies and summarize tickets. Every ticket carries email addresses, and some carry card numbers and keys. The Vrymdor™ AI Node masks them before the model reads the ticket.
The problem
A ticket is written by a customer, so anything can be in it.
- Customers paste card numbers into tickets when a payment fails.
- Ticket headers and signatures carry email addresses, and forwarded threads carry several.
- A developer asking for help pastes an API key into the ticket to show what broke.
With the AI Node
Put the AI Node between your help desk and the model, in the automation tool you already use. The model drafts a reply that keeps each [REDACTED:TYPE] label, and your help desk sends it to the customer’s real address, which never left your side.
- Create your free account and add an agent for this automation, for example "Support drafts".
- Copy the three values from the Connect your AI Node card: Node Host URL, Agent ID and Agent Secret.
- In n8n, Make or Zapier, add the AI Node step right after the new ticket trigger, and send it the text the model will read.
- Map the masked output into your AI step, and keep the customer’s real address in your help desk, where the reply is sent from.
Try it on a support ticket
The AI Node hides email addresses, phone numbers, card numbers, US Social Security numbers, private keys, and the API keys and tokens for OpenAI, Anthropic, Stripe, GitHub, AWS, Google and Slack, plus bearer tokens and JWTs. Each one becomes a label like [REDACTED:EMAIL], so the model still knows something was there.
The name stays: names are not masked by default. Masked here: EMAIL 1, CREDIT_CARD 1, STRIPE_KEY 1, PHONE 1.
This demo uses the Playground's Local engine: public, well known detectors set to the types the AI Node masks by default, in the AI Node's [REDACTED:TYPE] format. In your workflows, the Vrymdor™ AI Node does the masking.
What it does not cover
Plainly, so you know where you still need care.
- Names and street addresses are not masked by default. On Pro and Business you can add your own masking patterns for details with a fixed shape.
- It works by pattern matching on known formats, with the Luhn test for card numbers. A detail written in an unusual way, such as a card number spelled out in words, can get through.
- It hides private details before the model reads the text. It does not check what the model answers, and it does not make an AI model safe in general.
Start free, upgrade when you grow.
Community is free for up to 2 agents and 10,000 requests a month, with a hard cap so nothing is ever billed. Pro is $29 a month for up to 15 agents and 100,000 requests, and Business is $99 a month for up to 50 agents and 500,000 requests, each with 14 days free. Enterprise is sized to your contract.