Privacy Policy

Who this policy covers

Eaverow ("we", "us") is a product of Vantrow. Until an operating company is formed and named here, it is operated by Vantrow's founder, Andrew Brown. This policy covers eaverow.com, app.eaverow.com and the pages we serve to contractors' customers on their behalf.

It applies to four groups of people: roofing contractors and their teammates, who are our customers; homeowners whose details a contractor enters, or who submit a contractor's website estimate form; people who open a signing link, a dashboard link or an instant-estimate form; and visitors to our website.

For homeowner and job data, the contractor decides what is collected and why. We process it on the contractor's behalf, to run the service for them.

Accounts and roles

To open an account we ask for your name, your work email, your company name and a password. The signup form posts the password to our own server, which passes it straight to Supabase Auth, where it is hashed and kept. We do not store it ourselves.

Each person on an account has a role: owner, admin or rep. When an owner or admin invites a teammate we keep the invited address and name, the role offered, who sent the invitation and when; an invitation expires after seven days.

We set the cookies that keep you signed in, and two short-lived cookies used only while you reset a password. We set no advertising cookies and we do not track you across other sites. The network address a signup or sign-in comes from is counted to limit repeated attempts. It is not kept with your account, but the counter that holds it is kept for at least a day after that address's last attempt and then deleted by an occasional sweep.

Customer, homeowner and job data

A contractor's account holds the information their team enters or imports about their customers and jobs: contact names, addresses, phone numbers and email addresses; job details and notes; estimates and the options in them; photos and documents; roof measurements; insurance-claim details; invoices; and payment records.

When a homeowner submits a contractor's website estimate form, the name, email, phone and address they type are saved as a lead in that contractor's account and emailed to the contractor's office.

A homeowner sees their own information only through the links the contractor shares: the signing page shows that one estimate, and the dashboard link shows the job's progress, its estimate and latest invoice, the insurance-claim details a homeowner asks about (carrier, claim number, status, date of loss and deductible), and the photos the contractor has marked as shared.

The contractor is responsible for having the right to put their customers' information into the service, and for telling their customers how they use it.

Electronic signatures

When a homeowner signs an estimate, they first tick a box agreeing to sign electronically and to receive a copy by email. We then record the drawn signature image, the typed name, the option they chose, the date and time, the network address and browser identifier the signature came from, and a fingerprint of the estimate exactly as it was signed. That record is the audit trail, kept with the contractor's data so a later change to the estimate can be shown to post-date the signature.

At the same moment we draw a signed-estimate PDF carrying the signature image, the typed name, the date and time, the consent sentence they ticked, the fingerprint and the estimate itself. The PDF is filed under the job's Documents, for the contractor; it is emailed to the homeowner's email address on the job, when there is one; and it is emailed to the company's owners and admins. It can also be opened from the homeowner's signing link. It goes nowhere else. The network address and browser identifier stay in the audit trail and are not printed on the PDF.

Payments and card data

Card payments from homeowners run through the contractor's own Stripe account, connected to Eaverow from Settings. The homeowner enters their card on Stripe's checkout page. Card numbers never reach our servers and are never stored by us. For each payment we keep the amount, the date, the method, its status, Stripe's reference for it, and any refund or dispute Stripe reports back.

For a contractor's own subscription, any card given to us is held by Stripe. We keep Stripe's customer and subscription identifiers and a note that a card is on file, never the card.

Email

We send email through Resend: signing links, invoices, the signed-estimate PDF (to the homeowner, and to the company's owners and admins with the PDF attached), team invitations, and a note to the contractor's office when a lead arrives from their website.

When Resend tells us an invoice email was delivered, opened or bounced, we record that on the invoice. For a signing link and the signed copy, we note on the job's record that it was sent and to which address.

Replies to an estimate or invoice email go to the teammate who sent it. The signed-estimate copy comes from our own address.

Hosting

Data is stored with Supabase: the database, a private file store for photos, documents and signed PDFs that browsers never reach directly, and Supabase Auth for passwords. The apps run on Vercel, which serves every request and so sees your network address, as any host does.

Google services

Roof measurements from Google are switched on for the service as a whole by us, not per account, and are off until we turn them on. While they are on, an address is sent to Google's Geocoding API to locate the building and then to Google's Solar API for the roof's measurements, in two cases: when a homeowner submits an address through a contractor's website estimate form, and when a rep asks for a Google ballpark on a job, which sends the job contact's address.

We keep only the totals Google returns (roof area, number of facets, pitch, the imagery's date and quality, and the building's location), never imagery, for at most 30 days. Expired measurements are deleted daily. A quantity a rep has copied onto an estimate stays on the estimate. Each lookup is counted against the contractor's account.

AI processing

Anthropic's models are used today only in our own internal growth desk, which only the founder can open: drafting articles from public content and the founder's own notes, sorting public posts, drafting replies to public forum threads that a person then posts by hand, and drafting outreach to roofing companies we may contact. The outreach drafts are built from business-directory facts about the company: its name, city and state, a contact name, certification, licence status and where it was listed, public review counts, a guess at the software it uses, and any other facts in the listing.

No customer, job or homeowner data from any account is sent to Anthropic. If we add a feature that uses these models for customers, it will send only the data that feature needs, and this policy will say so before it ships.

Website visits

eaverow.com sets no cookies and loads no third-party analytics. Our own endpoint logs each page view: the page path, the referring page, a utm_source tag when the link carried one, the country Vercel derives from the connection, and whether the visit came from a mobile device or a desktop. We also log visits by known AI crawlers: the crawler's name, its user-agent string and the path. The network address is never stored with a page view or a crawler visit. It is used only to limit how often those two endpoints and the early-access form can be called, and the counter that holds it is kept for at least a day after that address's last request and then deleted by an occasional sweep.

Your light or dark choice is kept in your own browser and never sent to us.

The early-access form stores your name, email, company, crew size, current software, whether you asked for a demo, the campaign tags on the link you arrived from, the time, and the first sixteen characters of a hash of your network address, not the address itself, which we use to spot abuse of the form.

Usage and feedback telemetry

Two things are reported to getvantrow.com, the console of Vantrow, our parent. First, what the app spends on AI models: for each call, the name of the surface that made it, the model, token counts, whether it succeeded, how long it took and when. No content and no customer data is included. Second, feedback submitted from Settings → Feedback: the sender's name and work email as signed in, the page they were on, the category and title they chose, and their words.

Nothing about customers or jobs is included in either, unless the sender types it into their feedback.

Retention

A company's data, including its signature audit trail and email delivery records, is kept for as long as the account is open and for 90 days after it closes, so it can still be exported. Then it is deleted.

Google measurements are kept for at most 30 days. Rate-limit counters, which hold the network address a request came from, are kept for at least a day after that address's last request and then deleted by an occasional sweep. Page-view and crawler rows hold no personal data and are kept for reporting. Early-access entries are kept until the program ends, or deleted on request.

Export and deletion

An owner or admin can download the company's data from Settings at any time, free, before or after cancelling. The export is a zip of plain CSV files (contacts, jobs, estimates and their line items, invoices, payments, activity, signatures, claims and measurements) plus the signature images, photos and documents. If the photos and documents are too large to bundle in one pass, the export still lists every file and we assemble the full archive on request, free.

The company's data is deleted after the 90-day window described under “Retention”, or sooner when the owner asks us by email.

Your choices

You can ask us to show you, correct or delete the personal information we hold about you by emailing the address under “Contact”. We do not sell personal information.

If you are a homeowner, your contractor holds your information in their account and decides how it is used, so please ask them first; we help the contractor respond.

The privacy law of your state may give you additional rights. We honor them.

Security

Data travels over TLS. In the database, each company's rows are isolated from every other company's by row-level security. Team-invitation links are stored only as a hash of their token, so a copy of the database does not contain a usable invitation. Signing links and homeowner-dashboard links are long random tokens that we store as they are, so treat them as private. A signing link stops accepting a signature 30 days after the estimate was sent; once the estimate is signed, the same link keeps opening its confirmation and the signed PDF. Passwords are held by Supabase Auth, and files sit in a private store that browsers never reach directly.

No system is perfectly secure. If a breach affects your data, we will notify you as the law requires.

Children

The service is for businesses and is not directed at children under 13. We do not knowingly collect information from them.

Changes to this policy

When we change this policy, we post the new version on this page with a new “Last updated” date.

Contact

Questions about this policy, or a request about your data:

andrew@eaverow.com