How we handle your plans and your bid.
This page describes current practice as implemented in the product. It is not a lawyer-reviewed security whitepaper.
What is collected and why
- Account data via Clerk, for sign-in.
- Billing data via Stripe. TakeoffSpeed does not store raw card numbers.
- Takeoff records in Postgres, so the bid workflow can be reopened.
- Uploaded plan PDFs in Vercel Blob, so a takeoff can be produced and previewed.
- Plan files are processed by Anthropic to produce the takeoff.
- Transactional and RFQ email via Resend.
Upload controls that already exist
Uploads require a signed-in account. The blob path is scoped to that user. Files must be PDFs. The upload screen accepts up to ten files and 150 MB; the server enforces a 200 MB limit. Your current page allowance is shown before upload. Large or dense sets may still exceed processing limits. Guest subcontractor quote links use an expiring token, not a new account.
What we are still tightening
New uploads use private storage, with authenticated access for the owner and scoped access through guest quote links. Saved takeoffs retain their source PDF so you can reopen the preview. Failed new uploads are scheduled for cleanup after checking that no saved record needs the file; a failed rerun does not delete its saved source. Older public uploads still require migration and verification. Treat TakeoffSpeed as a controlled paid beta, not as having passed an enterprise security review.
Deletion
Email support@takeoffspeed.io to request account or data deletion. More detail lives on the privacy page.