Legal & Trust

Plain English. No corporate polish.

I'm a working commercial insurance agent. I know what it feels like to be asked to hand over client data to a black-box SaaS tool. These pages exist so you can tell — quickly — what happens to anything you send me. If a lawyer reads this and thinks I could have used more hedging language, good. That was the point.

Privacy Policy
What I collect, why I collect it, who sees it, and how to tell me to delete it.
Terms of Use
The rules of the road for using RiskWritr and the upload portal.
Data Processing Addendum
For agencies and carriers who need a DPA on file before they can share data.
Security
How your submissions are protected — encryption, access, vendors, incident response.
Data Retention
How long I keep submissions, uploads, and CRM records — and when I purge.

Who's behind this

UpFront Risk Solutions, LLC is a Pennsylvania-registered company. One human runs it — me, Scott Henman, a 22-year commercial insurance veteran. When you email scott@upfrontrisk.io, it lands in my inbox. That's the support queue. That's the DPO. That's the escalation path. Small by design.

A note on scope

Right now, RiskWritr is in limited private beta. These policies describe the platform as it stands today — a landing site, an upload portal, a CRM (Copper), and a secure file store (Supabase). As the product expands to the full Operating Cycle (intake → enrichment → narrative → appetite → proposal → bind), these pages get updated, and I'll note the changes at the top of each page.