Security

Trusted enough to sit on your homepage.

Mr C runs directly on your site, next to your brand. Here’s exactly what stops it from ever becoming a liability.

Hosted in Sydney, Australia Customer details encrypted Cites its sources, or says so

Encrypted, and kept in Australia

Conversations and enquiry details are encrypted with a key unique to your business, and everything is hosted in Sydney.

AES-256-GCM with per-business data keys managed in AWS KMS; AWS Sydney region.

Walled off at the database

Your data is separated from every other business by the database itself, not just by the app, so one business can never see another’s.

PostgreSQL row-level security on every business table, with tests that fail if it is ever switched off.

Only you decide where it runs

It only works on websites you’ve verified, so nobody can copy the snippet onto another site and use your assistant there.

Exact-origin allowlisting, verified by DNS record, meta tag or the installed snippet. No wildcards.

Can’t be hijacked, can’t be reused

Every visitor gets a one-time pass that only works on your exact website, for a short window, then it’s gone.

Origin-locked, signed session tokens with short expiry.

Fully walled off from your site

The chat lives in its own sealed bubble on the page. Your website can’t break it, and it can’t touch your website.

Renders in a Shadow DOM inside a sandboxed iframe.

It won’t make things up

Answers come only from your website, PDFs and FAQs, with the source shown. If it doesn’t know, it says so and offers to put the visitor in touch with your team.

Retrieval-grounded answers with validated citations and an explicit no-answer path.

Honest when something goes wrong

If an AI provider has a problem, a backup takes over. If none can answer, visitors are told plainly and can still leave an enquiry, never a blank reply.

Automatic failover, circuit breakers and an honest unavailable message.

Customer details stay private

Enquiry alerts tell your team something is waiting without including the customer’s details. Exports are recorded, and only owners and admins can make them.

Detail-free alerts, role-based access and an audit log.

Sign-in without passwords

Your team signs in with one-time email links, and each person gets only the access their role needs.

Single-use, expiring sign-in links; five roles from owner to viewer; append-only audit log.

It only reads what it’s allowed to

When Mr C learns your site, it stays inside your domain, respects your robots.txt, and never follows a redirect off your property.

Origin-bounded crawler, robots.txt compliant, validates every redirect, blocks private networks.

Uploads are checked

PDFs and logos are checked by what they actually contain, not their file names, and logos that could carry scripts are refused.

Content-type sniffing, size limits, no SVG; a PDF is only ever shown to visitors if you choose to share it.

Your keys never leave the building

AI provider keys and model details never touch a visitor’s browser. All they ever get is a temporary, limited-use pass.

Provider credentials stay server-side; the browser only receives a scoped session token.

Your data stays yours

Every business on Mr C is a separate, walled-off account. Your approved content, conversations, enquiries and settings are never visible to, or used for, any other business. Which services process data, and where, is listed on the Sub-processors page, and what we collect and how long we keep it is in the Privacy Policy.

Have a specific security or compliance question? Get in touch and we’ll answer directly.