Security

Rennli answers calls and messages for businesses, so it handles information that matters to them and their customers. These are the safeguards it is built with.

How the service is built

• Each business is walled off. Every record belongs to one business, and access is checked on every request. Automated tests prove that one business cannot read another's data.
• Encrypted in transit and at rest. Connections use TLS. Call recordings and transcripts are encrypted where they are stored, and access keys for connected services are encrypted with a separate key.
• You decide what is kept. Call recording is off until a business turns it on, and each business sets how long recordings and transcripts are kept. Deleting an account deletes its data.
• Strong sign-in for staff. Staff accounts that can see more than one business must use two-factor authentication, and every administrative action is written to an audit log.
• Verified integrations. Messages from phone, messaging and payment providers are checked for a valid signature before they are processed.
• Private by default in logs. Personal details are removed from system logs, which refer to calls and conversations by ID instead.
• No guessing. Bookings are made by code that checks real availability, not by the AI, so a time is never invented or double-booked.

This website

The website is served over HTTPS and loads no third-party scripts, trackers or fonts.

Reporting a vulnerability

If you find a security issue, please tell us privatelyat support@redweyl.comwith enough detail to reproduce it. We will acknowledge your report within three business days and keep you updated while we fix it.

Please do not access or change data that is not yours, do not disrupt the service, and give us reasonable time to fix the issue before sharing it publicly.