Privacy Policy
What we collect, why, and how to ask us to delete it.
Trussmint is run as a sole proprietorship by Luke Austin. This page explains what is collected, who it is shared with, and how long it is kept. It is written in plain English for the homeowner submitting a quote form and the operator using the portal alike.
Last updated: August 24, 2026
Who runs this service.
Trussmint is operated by Luke Austin, a sole proprietor doing business as Trussmint, who is the operator of this service and the controller of the data it collects. The app you are using was built on Polsia, the development platform, but the service is operated and the data is controlled by Trussmint, not by Polsia. When you submit a quote form at a contractor's hosted quote page, the data is collected by Trussmint and delivered to that one contractor.
What we collect from a homeowner.
A quote form asks for the homeowner's name, phone number, email address, service address, and a set of qualification answers that vary by trade (for example, monthly utility bill, roof age, or lot size). We collect exactly what the contractor's question set asks for and nothing more — there is no cross-site tracking pixel and no advertising profile.
What operators provide to the portal.
When an operator signs up, the portal collects an operator contact name, the company's email, and — for SMS lead alerts — an optional phone number with a recorded consent timestamp. The portal stores the operator's notification preferences (fallback email, optional phone number, consent record) alongside the contractor's profile on Trussmint.
How the data is used.
The homeowner's submission is scored against the operator's question set and delivered to the contractor whose hosted page the lead came in on. The operator's portal settings are used only to route lead alerts (CRM webhook, fallback email, optional SMS) and to operate the account. Neither dataset is sold, brokered, or shared beyond the contractor whose quote page triggered the lead.
Who it is shared with.
A lead is shared with exactly one party: the contractor whose hosted quote page the homeowner submitted. Trussmint does not run cross-site advertising or match homeowner data against any external audience.
Subprocessors
To deliver the service, Trussmint relies on the following third parties. Each is given only the data needed to perform its role.
- Anthropic, PBC. Receives the homeowner's free-text intake answers alongside the question prompt and anchor labels, for AI scoring of free-text responses against the operator's qualification criteria.
- Twilio. Receives the operator's verified phone number and the SMS message body — a header line with the lead's tier label and score, up to three top reasons, and a deep link to the lead-detail page in the operator portal — for delivery of lead-alert SMS to operators who opt in.
- Stripe, Inc. Receives the operator's name, email, and the amount owed when an operator is sent an emailed checkout link to pay a setup fee or start a subscription. Stripe is the third-party payment processor used for these transactions; Trussmint does not see or store the operator's card details.
- Render. The application hosting platform where this service runs. Receives and stores all application data — lead submissions, operator records, authentication credentials, notification preferences, and audit logs — in a managed PostgreSQL database provisioned on Render.
Retention.
Lead submission records persist on the contractor's account until the operator archives them. Operator notification preferences — including the SMS phone and consent timestamp — persist for the life of the operator account. There is no automatic expiry; deletion happens by request or by operator archive.
Deletion requests.
A homeowner or operator can request deletion of any retained record by replying to a notification email or by emailing the address below. We confirm receipt within one business day and complete deletion within thirty days.
Email trussmint@polsia.appSMS program.
The SMS lead-alert program — what it sends, who receives it, how consent is collected — is documented on the SMS Terms page. The verbatim consent checkbox wording on the operator's settings page matches the language on that page.
Consent is required at the moment a phone number is saved on the operator settings page. SMS lead alerts are delivered through Twilio, a third-party messaging provider, to the operator's verified number. STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, and QUIT are processed automatically by Twilio; reply HELP for program information; clear the phone number in your notification settings to opt out at the app level.
Mobile information and SMS consent will not be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent are not shared with any third parties.
Privacy questions
Want this policy changed or clarified?
Open the SMS Terms or email us — and we will answer what is not on this page on the spot.