Your data never leaves your control.
That isn't a concession. It's the design. Crestwise works from program-level status: milestones, schedule variance, and the decisions leadership needs to make. We never need access to your systems or the sensitive records inside them. That distinction is why we can start next week instead of after a six-month security review.
Pick the model that fits your compliance posture.
Most engagements run on Option 1 or 2. If your compliance posture rules one out, we adapt to it. We won't ask you to make an exception for us.
Governed facilitation
We never receive your material at all. We define the model, set the shared definitions, and run the cadence review while your team holds the screen.
Requires: a mutual NDA. Nothing else.
Your environment
We work in your tenant, on your platform, under your access controls and audit log: Foundry-class environments, Power BI, and similar.
Requires: your standard onboarding and access review.
Program metadata
Status artifacts with names and identifiers already removed: counts, dates, variances, risk descriptions. Commercial terms, zero retention, never consumer tooling.
Requires: NDA, data processing agreement, written subprocessor disclosure.
Four commitments we hold under pressure.
- Request access to operational or record-level data
- Process your material on consumer tools or personal accounts
- Engage a subprocessor without disclosing it in writing first
- Retain anything after the engagement ends
What the free sandbox stores, and where
- Your account (email, name) is held by our hosting provider's identity service so you can log in. Every account also requires two-step verification with an authenticator app.
- Everything you type or paste into the sandbox is saved in your own browser's local storage on that device. It isn't sent to Crestwise.
- Clearing your browser data or using “Reset sandbox” removes it.
- Use general program information only. Never paste restricted or classified records, personal information, proprietary data, or customer records.
Program metadata is not the sensitive data.
Milestone counts, schedule variance, and “two workstreams behind schedule” are not personal data, not restricted or classified information, and usually not proprietary. The records inside your system of record are sensitive. Crestwise operates a layer above them.
We'd rather answer your security questions up front
Than find a blocker in week three. Tell us your compliance posture and we'll tell you which option fits before you sign anything.
Talk through your requirements