This policy says what we collect through waivers.construction, why, where we keep it and who sees it. Tattoo Waivers LLC, a Texas limited liability company ("we") runs waivers.construction. The policy covers the website at waivers.construction, the web app a company's people sign in to, each company's own page at its waivers.construction address, and the pages a sub or a supplier signs on. You may send questions to hello@waivers.construction.
1. Whose information it is
(a) A company's jobs and lien waivers are the company's records. We keep them for the company. A person who signed a waiver and wants to see it or correct a fact on it asks the company that sent it; if that person asks us, we pass the request to the company. A signed waiver is not changed after it is signed.
(b) Information about a company, its people and a visitor to the website is ours to keep for running waivers.construction, as the rest of this policy describes.
2. What we keep about a waiver and the person who signs it
(a) The job: its name, its location, the property's owner, the state it is in, who hired the sub or supplier, its description and number when the company gives them, and, for a job in Texas, whether its original contract was signed before January 1, 2022.
(b) The waiver before it is signed: which form it is; who at the company made it; the facts the company fills in, such as the sub's or supplier's name, the through date, the check's maker, amount, payee and number, and any exceptions; and the email address the company gives us to send the link to.
(c) What we record when a person signs: the name, the title and the company that person types; the address and the telephone number that person types, where a form prints lines for them; the word that person circles, where a form asks for one; the signature that person draws; the time, and the time zone that person's browser reports; the IP address and the browser's description of the device that person signed from; and the words of the form as that person was shown them, with every blank as filled. We keep a fingerprint (SHA-256) of that record.
(d) The email addresses a signer gives us to send copies to, and the signer's own.
(e) A waiver a company records as signed on paper, with the date the company gives.
(f) A waiver a sub or a supplier makes without a company. A person may fill in and sign a form at waivers.construction and send it to a contractor. We keep that waiver as paragraph (c) describes, with the email address of the person who signed, the addresses that person asked us to send copies to, and the contractor's address that person sent it to.
(g) While a person is signing, what that person has drawn and typed is kept in that person's own browser, so that a page that reloads does not lose it. It reaches us when that person signs.
3. What we keep about a company and its people
(a) The company's name, address, telephone number and time zone; its contractor's license number and the state that issued it, when the company chooses itself from a state's public list of licensed contractors or gives them; the word in its waivers.construction address; and which forms it uses.
(b) Each person's email address and first name, the company they belong to, their role there and who added them. When a company's owner adds a colleague who has not signed in yet, we keep that colleague's email address until they do.
(c) The sign-in codes we send, kept in a form that cannot be read back, and the sign-ins they start.
(d) How the company found us. When a visitor arrives from an advertisement or a link that carries campaign labels (the "utm" values in the link's address), we keep those labels with the company that visitor sets up, with the 2 random numbers section 4(e) describes.
(e) What a person writes to us: a message sent from the website's contact form, with the name, the email address and the company that person gives; email sent to hello@waivers.construction; and a state a company asks us for.
(f) Payment. When a company pays, Stripe, Inc. takes the card on its own page, and we do not receive or keep a card number. We send Stripe the owner's email address and our identifier for the company. We keep Stripe's identifiers for the customer and the subscription, whether the plan is by the year or the month, and whether it is active.
(g) A company's own page. Anyone who has the page's address or its printed QR code can open it. It shows the company's name, and the name and the location of each of the company's open jobs, so that a sub can choose the job a waiver is for. It shows no waiver, no amount and no person's name.
(h) The demo. The company in the demo is invented, and its screens say that it is a demo. We delete a demo waiver, and what a visitor typed on it, a day after it is made.
(i) A set-up a visitor started. While a visitor fills in the page where a company is set up, we keep what the visitor has given so far: the company chosen, and the email address and the name as typed, with the campaign labels. When a visitor leaves that page with a company chosen and an email address typed, we set that company up an hour later and send that address one email with the company's page and its QR code.
4. On the website and in the web app
(a) Cookies of ours. The web app sets a session cookie named _construction_waivers_key, which protects its forms and keeps a person signed in, and a second cookie named _construction_waivers_web_user_remember_me, lasting 14 days, which keeps a person signed in on the same device. A third cookie, named cw_company, lasting 365 days, holds the word in a company's address and the company's name, so that the website knows which company a returning owner set up. A fourth, named cw_internal, marks a browser as one of our own, and no visitor receives it.
(b) For 7 days a person's own browser remembers the campaign labels of the link that first brought that person to the website, so that the labels travel with a person who sets up a company. Until it is closed, the browser also keeps a number that names the set-up that person started.
(c) Where a visitor's connection comes from. The network that serves the website tells us the city and the state a visitor's connection appears to come from, and a point near that city. The website uses the state to show that state's lien waiver first, and the search for a company uses all three to put nearby companies first. They are kept in the visitor's own browser until it is closed. We do not keep the visitor's IP address for this, and we do not keep the city, the state or the point in our records.
(d) The search for a company. The page where a visitor finds their company searches a state's public list of licensed contractors, a copy of which we keep, and asks Google's Places service. The search sends what the visitor types to our server, and we send Google those words and the point paragraph (c) describes, so that Google answers with companies near the visitor. We keep nothing of a search. When an owner sets a company up from a result, we keep that company's name, address and telephone number as section 3(a) describes.
(e) What we count. We count the pages of the website a visitor opens, how long each page stays on the screen, and the buttons a visitor presses there. With each count we keep the page's address without anything typed into it, the site that linked to the page, the campaign labels, the width of the window and whether the screen is touched, the browser's description of itself and its language, and 2 random numbers kept in the visitor's own browser: one for the browser, so that two visits count as one visitor, and one for the visit. In the web app we count the screens a company's people open and how long each takes. With these counts we keep no IP address, no email address and no signer's name.
(f) Our servers keep a log of each request: its time, its address and how long it took. A request to a waiver's link is left out of that log, because the link is what opens the waiver.
5. How we use it
(a) We use a company's jobs and waivers, and a signer's information, to provide waivers.construction to the company and to the person who signs: to show the waiver, to record the signature, and to send the signed waiver to the company and a copy to the signer. We do not use them for advertising.
(b) We use a company's and its people's information to run waivers.construction: to sign people in, to show each company its own records, to send the emails section 7 describes, to finish a set-up a visitor started as section 3(i) describes, to answer a person who writes to us, and to learn which of our advertisements bring companies to us.
(c) We do not sell anyone's information.
6. Where we keep it, and who sees it
(a) We keep waivers.construction's information in a database in the United States. It is encrypted on its way between our servers and a person's browser.
(b) These companies handle information for us:
- Amazon Web Services, Inc., which runs the servers and the database waivers.construction is kept on, and sends its email.
- Stripe, Inc., which takes a company's payment.
- Google LLC, which answers the search for a company, from the words a visitor types and a point near where that visitor's connection comes from.
(c) These people see a waiver: the people of the company it belongs to; the person who has its link, which opens that one waiver; and whoever that person or the company sends the signed waiver to. The one person who runs waivers.construction, and the artificial intelligence (AI) assistants we run it with, see a company's records to help the company and to keep waivers.construction working.
(d) Each company sees its own records. One company's people do not see another company's records.
(e) Beyond that, we disclose information as the law requires.
7. Email
(a) To a company's people, we email a sign-in code when they ask for one, a welcome when their company is set up, one email when the company's owner adds them, an email with each signed waiver, and notes from our founder: a few in a company's first weeks, and one each as the company reaches the counts of signed waivers at which its plan asks for payment and pauses. A visitor who started a set-up and left gets that welcome once, as section 3(i) describes.
(b) To a sub or a supplier, we email the link to a waiver when a company asks us to, naming the company, and a copy of the signed waiver when the signer asks for one.
(c) To a contractor, we email a signed waiver when the sub or supplier who signed it asks us to send it to that contractor's address, as section 2(f) describes.
8. How long we keep it
(a) We keep a company's records while its account is open. When a company asks us to close its account, we send the company its signed waivers and delete its records.
(b) We delete a demo waiver, and what a visitor typed on it, a day after it is made.
(c) We keep what a visitor gave the page where a company is set up, as section 3(i) lists, until the visitor asks us to delete it.
(d) We keep a waiver a person made without a company, as section 2(f) describes, until that person asks us to delete it.
9. Your choices
A person may ask us what we keep about them, and ask us to correct it or delete it, by writing to hello@waivers.construction. For a fact on a waiver, section 1(a) says whom to ask.
10. Children
We built waivers.construction for construction businesses and the businesses they pay. It is not for children, and we do not knowingly collect a child's information.
11. Changes to this policy
We may change this policy. We post each change on this page, and we date the version at the top of the page with the latest change. The policy on this page applies from that date.
Version 2026-11-14. SHA-256 of this text: 191671850675bce60150d49d5fe4bf35e82c57cf9acb7467604902e48309d4c4