Privacy and data.

How data flows

During a conversation, the visitor’s message goes to your chosen AI provider so it can understand and respond. Before anything is stored, Fred’s redaction engine scrubs sensitive data, and only the redacted version is saved or sent to your CRM.

No raw sensitive data stored

Fred does not store raw credit card numbers, Social Security numbers, or bank details. Those are detected and redacted before any transcript is written. Contact details from the consent form are stored as a consent record and forwarded to your CRM, with retention you control.

What gets redacted

• Financial data: card, bank, and routing numbers
• Government IDs: SSNs, driver’s license, and passport numbers
• Health data: medical record and insurance numbers
• Contact info: optional, you can keep it for your CRM

You choose the level: full redaction, partial masking that shows the last four digits, or off (not recommended). Redaction applies to stored transcripts, webhook payloads, recordings, exports, and the admin viewer.

How reliable is it?

Redaction is pattern based. It is a strong automatic safeguard, not a guarantee that every phrasing is caught. It works alongside the bigger protection: sensitive financial and government data is never stored locally at all. For the most sensitive deployments, combine full redaction with tight retention.

Consent and compliance

Fred collects contact info through a configurable consent step, stores consent records with timestamps and the exact text shown, and includes export and deletion tools for GDPR and CCPA requests. Fred provides compliance tooling, not legal certification. Always consult qualified counsel for your situation.

What you control

• Retention periods, redaction categories, and webhook destinations
• Which AI provider processes your conversations
• Your knowledge base, which stays on your server with the plugin