Privacy

Privacy

This page describes what TakeoffSpeed actually does, as implemented in the product. It is not a substitute for a lawyer-reviewed privacy policy.

What is collected, and why

  • Account data (via Clerk) — for authentication and account management.
  • Billing data (via Stripe) — for subscription billing. TakeoffSpeed does not store your raw card number.
  • Takeoff data (in a Postgres database) — the takeoffs, line items, and related records the product needs to function.
  • Uploaded plan PDFs (via Vercel Blob storage) — the plan sets you upload, so a takeoff can be produced from them.
  • Cached data (via Upstash Redis) — short-lived caching to speed up the app.
  • Transactional and RFQ email (via Resend) — account emails and the subcontractor RFQ emails you send through the product.
  • Uploaded plans are processed by a third-party AI model provider (Anthropic) to produce the takeoff.
  • Material pricing lookups — when you price a takeoff, the descriptions of those line items are sent to third-party web-search providers so current prices can be found. Your plan PDFs are not sent to those providers.

Sharing

Data is shared only with the service providers listed above, each processing data as needed to provide their part of the service — authentication, billing, storage, caching, and email.

Retention

We do not publish a specific retention period here because we cannot verify one for every system listed above. If you need to know how long a specific category of data is kept, contact support@takeoffspeed.io.

Deletion

To request deletion of your account or data, email support@takeoffspeed.io.

Note

This page describes current practice as implemented in the code. It makes no certification claims and is not a substitute for a lawyer-reviewed privacy policy.

Product overview · About · Contact