No. Every upload happens through a single-use magic link — the sub opens it, uploads, done. You watch each request move sent → opened → uploaded on the Requests tab.

The nag engine queues escalating reminders to the sub (30-day, 7-day, expired) and automatically generates a self-serve renewal upload link. You never write the email.

On your machine. SubPacket is self-hosted by design — uploads stay on local disk and nothing phones home. W-9s from sole-prop subs contain SSNs; with a cloud SaaS those live on someone else’s servers.

Yes — paste a CSV of name, trade, email, phone. The header row is auto-detected, duplicate emails are skipped, and bad rows are reported instead of silently dropped.

Create a job, assign subs, add payment draws. Each draw gets a conditional / unconditional waiver checklist per sub. One click emails the sub a magic-link upload tied to that draw — and the checklist shows exactly who is blocking the payment release.

This build ships with a simulated sender so you can evaluate the exact email copy safely. Wire SES or SendGrid for production delivery — see the README.