Your clients’ data, handled under rules you can explain.
Consulting and research firms carry their clients’ confidentiality into every tool they use. These are the rules Stratin is built around, in brief. The full detail is in the private briefing, or on request.
Every client gets its own workspace.
The separation is logical, on shared cloud infrastructure, not a separate database per client.
Stratin never pulls one client’s data into another client’s work. Access is granted client by client, so you decide who can open each account, including competing accounts inside your firm. Two things are shared across the firm by design: the method library your firm approves, and firm memory, but only if a firm admin turns it on. Disclose Stratin the way you disclose any third-party processor in your engagement terms.
Figures and coded quotes are checked in code.
A pass doesn’t prove a figure is right. What the checks don’t prove is in the private briefing →
Figures in a report are checked by code, not a model, against the analyses behind them, and any that can’t be verified are flagged for your team before anything goes to the client. Every quote the qualitative coding cites is checked word for word against its transcript, and one that doesn’t match is dropped.
Bring your data-handling questions to the demo.
We’ll walk through client workspaces and the figure and quote checks on a sample project.
Send a security questionnaire or data-processing terms to connect@stratin.ai, and we’ll answer by email, before the demo if you need that first.