Every model we use runs on commercial API terms with retention and training disabled wherever the provider allows it. Firm data never enters a training set. Period.
Where possible, agents read from your existing systems (SharePoint, Egnyte, email, CRM) and write back to the same. We avoid creating new copies of sensitive data unless an engagement explicitly calls for it.
Every integration is scoped to the minimum read and write scopes required by the workflow. Credentials rotate on a fixed schedule. Access logs are on by default and shared with your security team.
Nothing about one client ever touches another. Separate credentials, separate compute, separate prompts, separate logs. No shared vector indexes.
Engagements land in one of three deployment models. We recommend based on the sensitivity of the data and the tempo of the work. Every path is reviewed with your security team before the first line of code runs against real data.
We run everything. Fastest to stand up. Appropriate for public-market research, non-sensitive commercial real estate comps, and pre-production pilots.
Pipeline code runs inside your cloud tenant, your Entra, your subscription. Data never leaves your perimeter. Appropriate for LP, bid-sensitive, and regulated data.
Execution in your environment, orchestration in ours. Balances speed of iteration with information-security constraints on raw data.
ARC is an emerging firm. Formal certifications (SOC 2 Type I, then Type II) are on the roadmap as the client list grows. In the meantime, every engagement comes with a security addendum customized to your firm's requirements, a named point of contact, and a written data handling plan reviewed with your team before kickoff.
Need specifics for your security review? Contact us and we will walk your team through the architecture in detail.