What this reads, and what it never touches

What it reads

Configuration, and the smallest amount of personal data that a configuration contains.

• Routing configuration: queues, skills, teams, opening hours, holidays, wrap-up codes, prompts and flow structures.
• Agent records, because a queue is meaningless without the people in it. Name, sign-in name and skill assignments.
• The names and structure of the Dynamics environment being written to, so a plan can say what would change.
• Who used this tool, what they approved and when, because an approval that cannot be attributed is not an approval.

What it never reads

None of this is touched, on any platform, in any mode.

• Conversations. No transcripts, no recordings, no chat logs, no email bodies.
• Customer records. No contacts, no cases, no accounts, no order history.
• Interaction history. No call detail records, no handle times, no anything about a customer who rang.

What it refuses to do

These are enforced in the code and in the database schema, not written in a policy.

• Write to a client environment before an approval recorded against a named person and the exact plan they read. There is no flag that skips it.
• Store a credential in its own database. Anything marked secret goes to Key Vault; the connection row carries a reference and nothing else.
• Create a user. Dynamics users come from Entra and a licence, and an agent who cannot be matched is reported rather than invented.

What it produces

Three things leave the product, and each one says what it rests on.

• The inventory workbook Counts, gradings and effort ranges per entity. It contains the client's queue and skill names, because that is the inventory, and it should be handled as the client's configuration.
• The cutover runbook Steps and a write order. It names entities and what has to be rebuilt by hand.
• The apply ledger What was written, what was there before, and who approved it. It stays in the product's database and is what makes a rollback real rather than hopeful.

Deleting an engagement

Removing an engagement takes everything with it: staged records, canonical records, plans, the ledger and the credentials in the vault. That is what a data processing agreement requires rather than something to leave to a cleanup job, and it cannot be undone.

Where it runs

In a Capgemini Azure subscription, in the region chosen at deployment. Sign in is Microsoft Entra. Nothing is sent to a third party, and there is no analytics, advertising or tracking of any kind on this site or in the product.

Cookies

This public site sets none. The product itself sets a sign-in cookie, which is what keeps you signed in, and stores your language and theme against your account rather than in the browser.