Privacy
Last updated 1 October 2026
Orchesta is software a company runs its own work in. Almost everything in it belongs to that company, not to us: the emails their customers send them, the cases their staff open, the notes they write. This page says what we hold, where it is kept, and who answers for it.
Who is responsible for what
For the data inside a customer's Orchesta — enquiries, cases, correspondence, the people named in them — the customer is the data controller and Orchesta is their processor. They decide what goes in, what it is used for and how long it is kept. We hold it and act on their instructions. If you are a member of the public whose details are in there because you contacted one of our customers, your request belongs with them, and we will point you to them.
For the handful of things we decide ourselves — who has an Orchesta login, our own billing records, the operational logs below — we are the controller.
Where it is kept
Each customer has their own database, in a region they choose when their account is made. Today that is the United Kingdom or the United States. Their data stays in that region. One customer's database is not readable from another customer's, and their credentials are encrypted with a key held only for them.
What we hold about people who sign in
- Name, work email address, and the desks they work on.
- A password that is stored only as a hash. Nobody at Orchesta can read it, and a reset replaces it rather than revealing it.
- Sign-in records: when, from which IP address, and which browser. Kept so an administrator can see who has been in their account, and so repeated failed attempts can lock it.
We do not resolve an IP address to a person or a place, and we do not track anybody across other websites.
Who else sees it
We use a small number of suppliers to run the service: Microsoft Azure for hosting and databases, and Resend to deliver account email such as invitations and password links. They act under contract and only to provide the service. Where a customer connects their own mailbox or their own mail server, that mail goes through their provider, not ours.
Artificial intelligence
Orchesta can read an incoming message and suggest what it is about and how to answer it. That reading is sent to the model provider configured for that customer and is used to answer that one question. It is not used to train anybody's model. A customer can turn it off, and what the engine proposed is always shown to a person before it reaches a case.
How long
Customer data stays as long as their account does, and the customer decides what to delete inside it. When an account is closed, its database is removed. Sign-in records are kept for twelve months.
Your rights
If you have an Orchesta login you can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it when your account ends. If your details are in a customer's Orchesta because you wrote to them, ask them — they decide, and we will help them answer.
Asking us
Write to privacy@getorchesta.com.
This page describes how the product actually works. It is not legal advice, and a customer with their own regulatory obligations should read it alongside the agreement they sign with us.
