Built for inboxes that hold more than client mail
Replyguard connects to some of your most sensitive systems. These are the safeguards built into the product.
Reading as little as possible
The safest data is data we never take. Email is checked envelope-first.
Envelope first
We look at who a message is from and to. Subject and body are only fetched when one of your registered clients is on it.
Never-capture list
Threads involving the people you list, such as lawyers, board or HR, are skipped, even when a client is copied in.
You choose the mailboxes
Monitor every mailbox or only the client-facing ones. Your own domain can never be registered as a client.
Text only
We record message text. Attachments are never downloaded.
Keeping customers apart
Isolation is enforced by the database itself, not only by application code.
Row-level isolation
Every customer's data is separated by row-level security in the database, in addition to checks in the application.
No automatic admin access
Platform administrators do not get automatic access to your message content.
Access and accounts
Who can see and change what is explicit, and recorded.
Multi-factor sign-in
Multi-factor authentication is required to sign in.
Role-based access
Roles control who can view messages, change configuration or resolve escalations.
Audit log
Sign-ins, configuration changes and resolutions are recorded.
Credentials and connections
Keys to your systems are stored and checked carefully.
Secrets kept apart
Connector credentials live in a dedicated secrets store, never in the main database or logs, and never reach the browser.
Checked on save
New Microsoft credentials are verified with Microsoft as soon as they are saved.
Verified events
Incoming Slack and WhatsApp events are verified as genuine before they are accepted.
Found a security issue?
Email [security@yourdomain.com] with the details. Please don’t access other customers’ data while testing. We’ll acknowledge your report and keep you updated while we fix it.