Security and data

Where client data lives during an engagement, what leaves your systems, and who can see it.

Where the work runs

The workflow runs on your systems. Your documents, your data, and your Excel or Argus model stay in your environment, under access you grant and can revoke at any time.

What leaves, and when

Only the AI’s two jobs call out: reading a document and drafting words. Each request sends only the data that step requires, and nothing else leaves your systems.

The AI provider

Those calls run under commercial terms, on one of two routes, chosen with you at scoping.

Direct to Anthropic. Client data is never used to train models, and conversation content is not retained by default. Formal zero-data-retention arrangements are available where an engagement requires one.

Through AWS Bedrock. The model runs inside AWS, and Anthropic has no access to prompts or outputs. Retention is set by configuration and can be locked so that nothing is written to durable storage or shared with the model provider. Where Canadian residency is required, requests can run through AWS’s Canada (Central) region, with data at rest kept in Canada.

Neither route depends on the newest model. Where a requirement is strict, the workflow uses models that support it.

Ownership

Everything built during the engagement is yours: the workflow, the label-to-cell maps, the checks, and the calibration. Nothing built for your shop is reused in anyone else’s.

This website

provenancestudio.ca sets no cookies and runs no trackers. See the privacy policy.

Questions

Diligence questions are welcome, including security questionnaires. Send them to ethan@provenancestudio.ca and the answers come in writing.