How your data is handled

Plainly stated, for the person who has to take this to their security team. The short version: your data stays yours, I take the least I need, and everything is logged, encrypted, and deletable.

Principles

Compute-to-data

The approach is to bring code to your data rather than the reverse. In a typical engagement your data stays inside your boundary (a read-only mount or your own database) and results come back — copying data out isn't part of how I work.

Least-data-necessary

I aim to work from a scoped, representative sample rather than the whole warehouse, and only the fields the question needs.

No PII in the analysis

Analytical tables are designed to use surrogate IDs, keeping personal information out of the modeling layer wherever the work allows.

Single-tenant

Your work runs in your environment or a dedicated space — not pooled with anyone else's.

Auditable & deletable

Access and transformations are logged so the work is auditable, and the working sample is deleted when the engagement closes — the aim is that every number traces back to a row and a timestamp.

Practical controls

Encryption

In transit (TLS), and at rest on any surface I control. Where data lives in your own environment, encryption is governed by your infrastructure.

Access & MFA

Least-privilege access; multi-factor on accounts that touch the work; secrets kept out of code.

Version-controlled & tested

Pipelines and models live in version control with a test suite — reproducible, reviewable, and survivable if I'm hit by a bus.

Identity

SSO + role-based access against your own directory for any hosted surface.

Honest scope

I'm a boutique studio, not a 500-person firm — and I'd rather be straight than oversell. I'm not SOC 2-certified today; for regulated or enterprise needs I work within your framework— your DPA, your access reviews, your pen-test requirement — and I scope exactly what's required before any data moves. If your security team has a questionnaire, send it.

The practices above describe how I aim to work; they aren't a warranty. The binding, specific commitments for any engagement — controls, retention, and liability — are set in the written agreement (MSA / DPA), which governs. See also our Terms.

Security questions? hello@backporch.studio