Your homeowners never sign up for LumeWay, so they never agreed to anything of ours. That puts a higher bar on this page, not a lower one. Here is every place their information goes.
Last updated August 5, 2026
LumeWay LLC is a Utah company. It builds and runs the customer portal that roofing contractors put their own name on.
When you use LumeWay, you are the controller of your customers' information and LumeWay is the processor. In practice that means you decide whose data goes in, what it is used for, and when it comes out. We hold and process it to run the service you asked us to run, and we act on your instructions. We do not sell it, we do not rent it, we do not share it with other contractors, and we do not use it to advertise anything to anyone.
This matters most when a homeowner asks a question about their own data. They have a relationship with you, not with us, so the answer normally has to come from you. We will help you answer it, and the section on access, correction and deletion explains how.
Split by whose information it is, because the two are not the same.
Server logs, which include IP addresses and browser type, and basic error reports. These are how a broken page gets diagnosed. There is no advertising network on the portal and no cross-site tracking.
A homeowner can choose to receive text updates about their own roofing project. The choice is theirs and it is off unless they tick the box in their portal. We record when they agreed, from what address, and the exact wording they were shown.
Texts are reminders about a project already underway, never marketing. Message frequency varies. Message and data rates may apply. Replying STOP stops them, and replying HELP asks for help. Stopping texts does not stop the emails a homeowner needs, such as an invoice.
Mobile phone numbers, text-message opt-in data and consent are never shared with, sold to, or distributed to third parties or affiliates for marketing purposes.Phone numbers reach our messaging carrier only to deliver the messages the homeowner asked for.
A contractor can also text a homeowner directly from their own phone or their own CRM, which is between the two of them and does not pass through us.
LumeWay never sees or stores a card number. Payment details are entered directly into Stripe, which is the payment processor for both homeowner deposits and your own subscription. What comes back to us is the part you actually need: the amount, the date, whether it succeeded, and which job it belongs to.
Stripe handles that information as its own controller under its own terms. If you want the detail of how, it is published at stripe.com/privacy.
Every company we rely on to run the service, and what each one actually receives. The first group is used on every account. The second only receives anything if you switch it on.
| Sub-processor | What it receives |
|---|---|
| Supabase | The database of record, plus stored photos and measurement PDFs. Hosted in the United States. |
| Bunny Stream | Inspection video only: hosting, encoding and playback. |
| Anthropic | Roof photos, inspection notes and measurement-report text, for the drafting features described below. |
| Stripe | Card and bank details for deposits and payments. These go straight to Stripe. |
| Vercel | Hosting and delivery of the portal, including the preview images that appear when a link is shared. |
| Resend | Transactional email, such as a portal link or a receipt. |
| Sub-processor | What it receives |
|---|---|
| Slack | Job and customer alerts, sent to a workspace you configure. Nothing is sent until you connect one. |
| JobNimbus | Job and milestone data, synced both ways. Only if you connect your JobNimbus account. |
| YouTube, Vimeo or Loom | If you embed education videos, the viewer's IP address and playback are visible to that provider. YouTube embeds use the nocookie host. |
Two details worth being precise about, because a vaguer sentence would be wrong. Photos and measurement PDFs are stored with Supabase, but inspection video is stored with Bunny Stream, which is a different company in a different place. And the education-library embeds are ordinary third-party video players: if you embed one, that provider can see who watched it, the same as on any website.
If this list changes, the change shows up here with a new date at the top of the page.
LumeWay drafts the written inspection summary, interprets measurement reports, and helps map pricing. Those features work by sending the underlying material to Anthropic, which is a third-party AI provider.
The photos of your customer's property are part of what gets sent. Not a description of them, the images themselves. There is no redaction or blurring step in front of that: if a photo shows a house number, a vehicle, or a person in the driveway, it is sent as it was taken.
We would rather you learn that here than find it out later. If it is a problem for a particular customer, tell us and we will talk through what can be turned off for you.
Anthropic's published policy for the API we use states: "We do not use API data for training (unless you have an agreement with us that states otherwise)." We have no such agreement. Their current statement is at privacy.claude.com. That article does not publish a retention period, so we are not going to invent one here; the link is the authority, not this page.
Everything drafted this way is a draft. A person at your company reads and approves the inspection summary before a homeowner ever sees it, which is deliberate, and it is why the product calls it drafted rather than sent.
Every contractor's data is separated at the database level, so one shop cannot read another's customers, pricing or jobs. This is enforced by row-level security in the database rather than by application code remembering to filter, because application code eventually forgets.
It is written up in docs/security/tenant-isolation.md in the application repository, and there is a re-runnable proof, scripts/verify-isolation.ts, that attempts cross-tenant reads and fails if any of them succeed. If you are evaluating LumeWay and want to see both, ask and we will walk you through them.
While your account is open, we keep your data because you need it. We do not run a background job that quietly deletes finished jobs, and that is a deliberate decision rather than an oversight.
In Utah, a claim for breach of contract or warranty on a construction project can generally be brought within six years of completion or abandonment, and the statute of repose runs nine years, stretching to eleven if the injury is discovered in year eight or nine.
If a homeowner raises something five years after an install, the signed contract, the inspection photos, the change orders and the payment history are what defend you. A policy that erased them after ninety days would be actively harmful. Keep your own copy as well. Your obligation to hold your records is yours, and it outlasts any subscription.
When your account ends:
Some records outlive that request whatever we both want: invoices and payment records we have to keep for tax and accounting, and anything we are legally required to retain.
If you are a homeowner and want to see, correct or remove what is held about your roofing project, contact the roofing company you hired. They control that record, and they can act on it directly in LumeWay. If you cannot reach them, write to us at forrest@lumeway.app and we will help you get to the right place. We will not change or delete a contractor's job record on a third party's say-so, because we have no way to know it is really their record to change.
If you are a contractor, write to forrest@lumeway.app. Export, correction and deletion requests are handled by the person who builds the product, and you will get a real answer rather than a ticket number.
Utah's Consumer Privacy Act applies to businesses well above the size LumeWay is today, so we are not going to claim we are bound by it when we are not. We follow the parts of it that are simply good practice because they are worth following, and we would rather say that plainly than imply a legal obligation that does not exist.
No system is perfect. If you find something that looks wrong, email forrest@lumeway.app and it will reach the person who can fix it, usually the same day.
If this policy changes in a way that affects what we do with your data, we will update the date at the top and tell account holders directly rather than relying on you to re-read the page.
Questions, requests or complaints: forrest@lumeway.app. LumeWay LLC, Utah, United States.
See LumeWay on a real roofing job: branded portal, in-portal payments, every payment tied to the job. Fifteen minutes.