Security and Data Privacy for the Virtual Front Desk Agent | IMCeleste
Security and trust

The AI suggests an action. Separate code decides if it's allowed.

Celeste can suggest an action, but a separate piece of code has the final say. That code gives the same answer every time. No customer can beg or trick their way past a rule that lives in code.

See every check an action passes →
Celeste proposes
Issue refund, $240.00
Your limits decide checked in code · same result every time
Outcome
Sent
Held for youover your $200 limit
Blocked
The guarantees

Nine things we don't leave to chance.

We don't train on your data

Your conversations, bookings and knowledge are here to serve your customers, and that's the only thing they're ever used for. They never train a model, ours or anyone else's.

You can see every decision

Open any reply and you'll see exactly what Celeste pulled from your knowledge, how sure the agent was, and why it acted.

Your passwords stay locked away

Your passwords and keys live in a locked vault. They're never handed to a tool, and they never show up in a log.

Nothing can be changed after the fact

Every action, override and change goes into a log that can only be added to. Nothing in the platform can rewrite or delete an entry once it's written.

Even our team can't just look

For anyone on our side to open your account, they need a time-limited grant, and every look is logged.

No making things up

If Celeste can't back up a claim with your own knowledge or a connected system, the reply waits for a person instead of going out. An action that was held or refused is never reported to the customer as done.

Double booking cannot happen

A slot is held while the customer confirms it, then written to one calendar, once. A saved record stops the same booking from running twice. Two customers cannot land in the same slot. No booking is written before the customer has confirmed it.

Opt-outs are honored

Every reminder and follow-up includes a way to opt out. A text reply of STOP ends the texts. Texts and review requests wait for your sending window. A booking confirmation or reminder email goes right away. Review requests and win-back notes have a per-customer cap.

Celeste never takes a card

When a customer is ready to pay, Celeste shares your payment link. It never collects card details in a conversation and never sets a price you did not list.

Privacy and compliance

Encryption in transit and at rest, in-app deletion tools, and a 30-day export window if you ever leave. IMCeleste runs on Microsoft Azure, and the data centers, storage, and servers behind it are SOC 2 and ISO 27001 certified. The certification covers the infrastructure, not the application.

No mystery vendors, either. Your data touches a short, named list. The cloud that hosts everything. The AI model services, which run inside our own cloud environment and never on a shared public endpoint. A payment processor. A text-messaging carrier for sign-in codes and the text channel. An email delivery service. Bot protection on the chat widget. Each one is named, with what it sees, in the privacy policy.

Encryption in transit and at rest In-app data deletion 30-day export window Named sub-processors Azure infrastructure, SOC 2 Azure infrastructure, ISO 27001
See it yourself

Test it yourself.

Start free, and Celeste runs on your own hours, services and answers, under limits you set. It drafts in private until you say otherwise. Prefer to look first? The demo workspace is read-only, but Test Celeste inside it is a live chat you can try. The Inbox shows which limit held each draft.