Create a custom safety rule in SylphSpeak

Goal

Create a custom safety rule to replace, redact, or block matched text before SylphSpeak speaks a message. Custom safety rules are useful when you want extra protection for words, names, phrases, symbols, or sensitive patterns that are specific to you.

Before you start

Make sure you have:

• SylphSpeak open
• Config mode > Speech Rules open
• A paid SylphSpeak account linked to your active device

Add a custom safety rule

1. In Config mode, go to Speech Rules.
2. Under Safety & Blocking, select Add Rule.
3. Enter the text or pattern you want SylphSpeak to match.

Use the custom safety rule editor to match text before it is spoken.

Use wildcards when needed

Custom safety rules use whole-word matching by default. For example, bob matches “hi bob”, but not “bobby”. Use * for wildcards:

• *bob* matches text that contains bob
• bob* matches words that start with bob
• *bob matches words that end with bob

Choose what happens when text matches

After you enter the matched text, choose what SylphSpeak should do.

Replace

Use Replace when you want SylphSpeak to say different text instead of the matched text.

1. Select Replace.
2. Enter the replacement text.
3. Select Save.

Replace matched text with safer spoken text.

Use pronunciation for voice-specific replacement

Custom safety rules apply globally. If you want to replace a matched word only for a specific voice profile, use Config mode > Speech Rules > Pronunciation instead.

Redact

Use Redact when you want SylphSpeak to mask only the matched text and continue speaking the rest of the message.

Block

Use Block when you want SylphSpeak to cancel the entire message if the matched text appears.

Save and toggle the rule

After you choose the action, select Save. You can turn the rule on or off at any time.

Custom safety rules are global

Custom safety rules apply to all voices, regardless of which voice profile is active.

When to use a custom safety rule

Create a custom safety rule when you want to reduce the chance of saying something by mistake. Common examples:

• You often mistype a symbol or key. For example, replacing “ with [redacted] can stop SylphSpeak from saying “backslash”.
• You forget someone’s name or pronunciation.
• You stream under a persona and sometimes type your legal name.
• You use the wrong pronouns by accident.
• You use slang that you do not want certain groups to hear.
• You have a habit of swearing and do not want it spoken.
• You do not want to accidentally share your email address, home address, PIN, or password.

Matched text is not secure storage

Stored matched text is not secure. For highly sensitive content, use optimistic matching with * so the full sensitive text does not need to be stored in SylphSpeak.

Check that it worked

Send test messages in different combinations and voices to confirm the rule works the way you expect. You can also confirm the rule matched in message details:

1. Go to Config mode > Messages.
2. Select the message you tested.
3. Expand Technical details.
4. Check === Message === and === Speech Rules === to see whether the matching rule was applied.

Safety rules are not a guarantee

Safety rules are designed to reduce accidental disclosure of sensitive content. They do not guarantee that all sensitive information will be blocked in every situation.

If the result is not what you expected

If the rule does not match, try a broader wildcard pattern. If the rule matches too often, make the pattern more specific, or turn the rule off until you can adjust it.

Next step

Create one custom safety rule, send a short test message, then check message details to confirm the rule was applied.