You choose what leaves your systems.
Upshot reads only what a run needs and keeps only the run log. Here is exactly where data goes during a run, and who can stop what.
Where data goes during a run.
Your systems are read through their own APIs. The model provider sees only what a step needs, under zero retention. Nothing is written back without the sign-off you set.
The controls you hold.
Read-only until you say
Every connection starts with read access. Each write action is switched on separately, by a person on your team.
Sign-off thresholds
Set which actions need approval and above what amount. Anything over the line waits for a named person.
Never trained on your data
Your records are not used to train any model, ours or a provider's. Providers are contracted to zero retention.
Every action logged
Each run keeps what was read, what was decided, who approved it and what changed. Export all of it at any time.
Undo where the system allows
Actions that can be reversed come with an undo, and the undo is written to the log too.
Your cloud, if you need it
On Scale, Upshot runs inside your own cloud account, in the region you choose.
Audits and paperwork.
We are a small company and say so. Here is where each piece of paperwork stands today.
- SOC 2 Type IAudit under way
- Penetration testSummary on request
- Data processing agreementReady to sign
- Security questionnaireAnswered within a week
Sub-processors.
| Service | What for | Where |
|---|---|---|
| Cloud hosting | Runs the Upshot service and stores run logs | EU or US, your choice |
| Model provider | Single steps of a run, zero retention | EU or US |
| Email delivery | Approval requests and notifications | EU |
Security review before a pilot?
Say so on the pilot form. We send the pen test summary and our DPA within one working day.