Where your documents go. And where they don't.
Deckwire is built for confidential mandates. This page shows the path a document takes, who gets to see it and when it is gone again. Written to forward to your IT or compliance team.
Deckwire is still being built. This page describes how it is built. Before you trust us with a live mandate, you get the principles in writing.
The path of a document
Your computer
You upload the template and the sources: PDF, Excel, Word, PowerPoint.
Deckwire
Reading, matching and building slides run in an Azure data centre in Switzerland. Keys live in Azure Key Vault, not in the code.
Language model
Where text has to be written, an Azure OpenAI model in the same region does it. Your documents never train it.
Your file
What comes back is an ordinary .pptx in your template, checked so it opens without a repair prompt.
Deletion
Source documents are deleted when the mandate ends, or immediately on request.
A lock in the code
Only the model in Switzerland may receive client documents. Other models we test for comparison only ever get public sample files. Deckwire checks this before it opens any connection, and refuses any file whose origin it cannot determine for certain.
What happens to your numbers
- Values from Excel as the model shows them, with the cell's number format. Excel is never recalculated.
- If a format can't be rendered exactly, Deckwire stops and names the cell.
- Calculated values come with their calculation; conflicts between sources stay flagged until someone decides.
- Every number on a slide keeps where it was found: file, page, line or cell.
Short version for your IT
- Processing and storage: Microsoft Azure, Switzerland North.
- Language model: Azure OpenAI, Switzerland North. No training on client data.
- Other models technically receive public sample files only.
- Secrets in Azure Key Vault.
- Source documents deleted after the mandate, immediately on request.