What we do with your information
Takeoff is software for roofing contractors. It takes roof measurements, turns them into priced material orders, and keeps track of the job from the signed contract through to getting paid. Along the way a fair amount of information passes through it, and this page explains what happens to that information.
Takeoff is operated by Vero Tech LLC, a Nebraska company. When this page says "we," that's who it means.
There are two different people in this policy
This matters more than it sounds, so it's worth getting straight up front.
The contractor is our customer. A roofing company signs up, their staff get accounts, and they run their jobs in Takeoff. Everything below about accounts, billing, and connected services refers to them.
The homeowner is our customer's customer. They don't have a Takeoff account — there is no such thing as a homeowner login. The one thing they may receive is a private link to view their own estimate. Their name and address are in the system because the contractor is roofing their house. We hold that information on the contractor's behalf and at their direction. It's the contractor's customer relationship, not ours.
If you're a homeowner who found this page and wants to know what a particular roofing company has on file about you, ask them directly. We can't disclose or delete another company's records without their instruction, and we don't have your relationship with them in front of us.
What contractors give us
Account and company details — names, work email addresses, phone numbers, your company's address, and your logo and branding if you upload it. Login credentials, stored hashed. Whatever you configure: pricing, labor rates, material templates, supplier accounts.
We also collect the ordinary technical exhaust of running a web application: IP addresses, browser type, timestamps, and error reports when something breaks.
What ends up here about homeowners
- Name, property address, phone number, and email
- Roof measurements and aerial imagery of the property
- Photos of the property uploaded by the contractor or pulled from their photo tool
- Insurance claim documents, carrier estimates, and scope of work — for insurance jobs
- Contract amounts, payment schedules, and job costs
Insurance paperwork is the sensitive part of that list. Carrier estimates routinely include claim numbers, policy numbers, deductibles, and adjuster contact details. Takeoff reads those documents to pull out measurements and line items. We don't sell insurance, broker it, or share what we read with any carrier.
Where it goes
Takeoff only works because it talks to other systems. Here's every service that receives data, and why:
- EagleView — we send a property address to order an aerial measurement report
- Beacon/QXO, ABC Supply, and SRS Distribution — material orders, including the delivery address and contact for the job
- JobNimbus — two-way sync of job records, if the contractor uses it
- CompanyCam — property photos, if the contractor uses it
- Intuit QuickBooks — accounting data, covered in its own section below
- Anthropic — text from documents and chat messages, for the features that read insurance scopes and answer supplier questions
- Microsoft and Google — sending and receiving email on the contractor's behalf
- Render, Supabase, and Cloudflare — hosting, the database, file storage, and email routing
- Sentry — error reports when the application fails
Each of these gets only what it needs to do its job. The suppliers get a delivery address; they don't get your insurance paperwork.
QuickBooks
If you connect QuickBooks, you authorize it on Intuit's own page. We never see your Intuit password. What comes back to us is an access token tied to the single company file you chose.
We use it to read your job costs, invoices, and payments, so Takeoff can show you what a job actually made instead of what you hoped it would make. When you ask it to, we also write back — creating or updating an invoice, or recording a payment against one.
That token is encrypted where it's stored and scoped to your company alone. No other Takeoff customer can reach your books, and we don't pool your accounting data into anything shared. You can disconnect from Takeoff's settings or from inside QuickBooks itself; either way we delete the token and stop calling the API.
What we don't do
We don't sell your data, and we don't share it with anyone for their own advertising. We don't run ads. We don't build a cross-contractor database of homeowners and market to them. One contractor's jobs, pricing, and books are never visible to another.
Takeoff does learn from how a company works — which materials they order, how they price, what their crews charge — but that learning stays inside that company's own account.
How long we keep things
Job records stay for as long as the contractor's account is active, because a roof has a warranty and old jobs get looked up years later. If an account closes, we keep the data for 90 days so it can be exported or the account reopened, then delete it. Backups roll off on their own schedule after that. Error logs are kept 30 days.
Security
Traffic to and from Takeoff runs over TLS. Credentials for every connected service — supplier logins, QuickBooks tokens, email authorization — are encrypted at rest with authenticated encryption, and the keys live in the deployment environment, never in our source code. Account passwords are stored as salted hashes and are not recoverable, by us or anyone else.
Every query is scoped to the contractor who made it. That boundary is enforced on the server, not in the browser, so one company's jobs, pricing, and books cannot be reached from another company's session even by a modified request.
We request the narrowest access each integration will accept. With QuickBooks that means accounting data only — we do not request access to QuickBooks Payments, and we never handle card numbers. Operations that write into a connected system are gated behind an explicit server-side control rather than left on by default.
If a breach ever affects your data, we will tell you what happened and when we learned of it, promptly and without waiting until we have a tidy story to tell.
Your control over it
If you're a contractor, you can see and edit your data in the application, export it, disconnect any integration whenever you want, and ask us to delete the account. Email us and we'll handle it. We're not going to make you find a form.
If you're a homeowner, your request goes to your roofing company, not to us. They control the record and we act on their instruction. Send it to them and we'll carry out whatever they ask us to do — including deleting it. Depending on where you live you may have rights over your personal information under state law or Canadian privacy law, and those rights are ones your contractor is positioned to honor, with our help.
Children
Takeoff is business software sold to roofing companies. It isn't for children and we don't knowingly collect anything from them.
Changes
When this policy changes we'll update the date at the top. If a change actually matters — new categories of data, a new place it goes — we'll email account holders rather than quietly editing the page.