waivers.tattoo Privacy Policy
This waivers.tattoo Privacy Policy (the “Policy”) describes what Tattoo Waivers LLC, a Texas company (“we,” “us” or “our”), which operates waivers.tattoo (the “Service”), collects and what we do with it.
In this Policy, a “Client” is a client of a shop who signs that shop’s waiver form through the Service. A shop may also add to its client list people who have not signed its waiver form through the Service, as Section 3(e) describes. A Client’s “Record” is everything the Client gives on the shop’s waiver form, together with the waiver the Client signs. The “Signed Copy” of a waiver is the PDF file of the waiver as the Client signed it. “You” and “your” refer to the person reading this Policy: a shop’s owner or staff; a visitor to this website, including a person who starts the signup form without finishing it; a Client; a person whom a shop adds to its client list; a person who says yes to a shop’s texts on its page for them; a person who books a session with a shop, pays it a deposit or visits its link page or website; and a person who writes to us, by email, through the contact form or in a message or comment on Facebook or Instagram.
The Service includes this website, where a shop signs up, which in this Policy means www.waivers.tattoo and our websites at www.deposits.tattoo, www.L.tattoo, www.bookings.tattoo, www.websites.tattoo, www.texting.tattoo, www.emailing.tattoo and www.conventions.tattoo; each shop’s waiver form, which a Client signs on the Client’s own phone at the shop; each shop’s booking page and deposit page, on which a person books a session with the shop or pays it a deposit; each shop’s page for its texts, on which a person says yes to the shop’s texts without signing its waiver form; and each shop’s link page and website, on which a person finds the shop’s links or reads about the shop. They collect different information from different people. A shop’s use of the Service is governed by the waivers.tattoo Terms of Service. Questions about this Policy may be sent to hello@waivers.tattoo.
1. Information We Collect on This Website
(a) Information you give us. The signup form on the start page asks for your shop, an email address for the Signed Copies of your shop’s waivers and, if you choose to give them, your name, phone number, city and state. If you select your shop in the shop search, you give us the name, address, phone number and website that Google returned for it as your shop’s details, and we keep them, with Google’s identifier for the place. We use all of this information to set up your shop’s page and to email you about it: your link, your QR code and, while your first waivers are free, a few emails about getting set up. Each of these emails is sent once, and they stop once a Client has signed your waiver form and you have activated a subscription. You can also stop the reminders among them in your shop’s dashboard, under Settings, or from the link in a note we send to many shops at once or when your shop reaches a number of signed waivers, as Section 9(a) describes. To set up your shop’s link page and to follow your shop on Instagram, we also read the website that Google returned for your shop, or that you give us, for its links and its Instagram account, and ask Meta about that account by its name. We do not sell this information or rent it. The emails we send a shop are described in Section 9, and the lists of shop owners that we give Meta, in Section 2(a). If you write to us through the contact form, we keep what you write, your email address and, if you give them, your name and the name of your shop, together with the city and region in which your IP address places you, your browser and how you arrived, as Section 1(e) describes, so that we can answer you, and we keep it until you ask us to delete it. Our servers also tell Meta that you wrote, as Section 2(a) describes. If you ask us to tell you about tattoo conventions, we keep your email address, the state or province you choose and whether you are a collector, an artist or a promoter, together with the city and region in which your IP address places you, your browser and how you arrived, as Section 1(e) describes, so that we can tell you about tattoo conventions in that state or province, and we keep it until you ask us to delete it. If you ask us to email you about tattoo conventions, whether the shows near a city, the shows in a state, a province or a city, a particular show or the shows of an artist, we keep your email address, what you ask about, how far from that city you choose, if you choose a distance, and the page on which you ask, together with the city and region in which your IP address places you, your browser and how you arrived, as Section 1(e) describes. If you also give a mobile phone number and tick the box agreeing to get text messages from us about tattoo conventions, we keep the number and, as evidence of your consent, when you gave it, the words beside the box, the page and your IP address. A number given without the box ticked is not kept. We keep this information so that we can tell you about the tattoo conventions you ask about, by email and, if you ticked the box, by text message, and we keep it until you ask us to delete it. As of the date of this Policy, we do not send these emails or text messages.
(b) The shop search. When you search for your shop on the start page, what you type is sent to Google’s Places service to find it, under Google’s own privacy policy. Our servers send that search to Google with the approximate location that your IP address indicates, and not the IP address itself, so that the shops nearest you are listed first. We keep only the shop you select.
(c) A signup you do not finish. If you start the signup form and leave before finishing it, we keep what you had entered so far, including the shop you selected and any email address or name, with how you arrived, as Section 1(e) describes, and your browser. We use it to follow up about getting set up. If you selected your shop and gave an email address, we set up your shop’s page about an hour after you leave and, unless you have asked us to stop our emails, email you its link. If you gave an email address and named no shop, we email you once, a few days later, with a link back to the signup form with your email address, and your name if you gave one, filled in; this website takes them out of the page’s address before the advertising tags described in Section 2 can read it. We may also call your shop, email you about the Service as we email the shops that have signed up, and look up your shop’s Instagram account, as Section 1(a) describes, and we give Meta your email address, name, city and state, hashed, as Section 2(a) describes. We also use what you entered to learn where the signup form loses people. An email from us about the Service carries a link to stop such emails, which also stops our calls and leaves you off every list we give Meta after that, and we delete what we kept, and take it off the list we have given Meta, when you ask us to at hello@waivers.tattoo.
(d) Payment. When you activate a subscription, Stripe takes your card details on its own page, and your card number never reaches our servers. We keep Stripe’s reference to your subscription, and the receipts, for as long as tax law requires them.
(e) How you arrived. If an advertisement or a link brought you to this website, your browser remembers which one and attaches it to your signup, so that we know which advertisements bring shops. Your browser keeps your first arrival in its own storage for up to 7 days, and a list of up to 6 of your arrivals, the first and the 5 most recent, for up to 30 days. We keep those longer-lived copies because the browsers that Facebook and Instagram open a link in discard the shorter-lived kind between 2 pages, so that the advertisement that brought you is not lost on the way to the signup form. For the same reason, a link from one of our websites to another carries up to 3 of those arrivals in its address, and inside a browser that Facebook or Instagram opens, the page’s own address carries them, so that opening the page in your phone’s own browser keeps them; and a demonstration of one of our products keeps them in its own address, in any browser, and carries them on its links to its other pages and to our other websites and demonstrations. Each arrival holds the link’s tracking parameters, its other parameters except any that looks like a contact detail, a name or a key, the page you arrived on, the time and the website you came from, never who you are, and clearing your browser clears them.
(f) Testing the start page. The start page tests 2 versions of its wording. A cookie remembers which version you saw for the visit, so that the wording does not change while you are reading it, and the cookie carries nothing else.
(g) Logs and counts. Our servers keep ordinary access logs: the page requested, the time, your IP address and your browser. The logs are used to keep this website running and are not used for advertising. This website also counts its own use: each page you view and how long you stay on it, the buttons you tap, the steps of the signup form you take and any error a page meets, with the kind of device you use and the width of its screen, how you arrived, as Section 1(e) describes, and your browser and language. Each count carries a random key that your browser keeps in its own storage until you clear it, so that we can tell one browser’s visits from another’s, and a second key that your browser drops when you close the page, and no cookie and none of the contact details you type. The counts go to the company under the same ownership as ours that Section 8(a) names, and we use them to see how this website is used and which advertisements and links bring visitors.
(h) Access, correction and deletion. If you ask, we will tell you what we hold about you, correct it or delete it. Billing records are kept for as long as tax law requires; everything else is deleted when you ask.
2. Advertising on This Website
(a) Meta. We advertise on Facebook and Instagram, and this website carries Meta’s pixel. The pixel tells Meta which pages of this website you visited and sets 2 cookies in your browser: one that identifies the browser, and one that identifies the click on an advertisement that brought you. When you sign up, the pixel also sends Meta the email address, phone number, first name, city and state you gave us, hashed in your browser before they leave. When you sign up, our servers tell Meta what happened and send Meta the email address and phone number you gave us, hashed, so that Meta can match you to an account it already holds and count the advertisement that worked, and they tell Meta, with your email address, hashed, when you open the page on which you pay, first add your shop’s logo and activate a subscription. Each of these but the activation also carries your IP address, your browser and the identifiers of your browser and of the click on an advertisement that brought you, which the pixel’s cookies or the address of the page on which you arrived hold; each names your shop by its web address or, at a signup for which no page could be made, by the name you typed, and your signup also sends that web address hashed, with the source of the link that brought you and the product you signed up for; and the events for opening the page on which you pay and for the activation carry the plan and its amount. Those are the shop owner’s own details, given on a business signup. Once your shop’s first Client has signed, our servers tell Meta that too, with the shop owner’s email address, hashed, your shop’s web address and, where your signup kept them, the identifiers of your browser and of the click on an advertisement that brought you, and the browser from which you signed up, so that Meta can count the advertisement that brought the shop. When a shop starts taking deposits, and again when its first deposit is paid, our servers tell Meta that as well, with the shop owner’s email address, hashed, and the shop’s web address, which they also send hashed, and, for the first deposit, the amount of our fee on it and the address of the shop’s deposit page, so that Meta can count the advertisement that brought the shop. When you write to us through the contact form, our servers tell Meta that too, with the email address you gave, hashed, your IP address, your browser and the identifiers that the pixel’s cookies hold, and the name of the shop you gave, so that Meta can count the advertisement that brought you. We also give Meta 2 lists of the shops that have signed up, made from the details each shop’s owners gave us on a business signup: their email addresses, phone numbers and first and last names, the shop’s city, state and country, and the email address that pays for the shop where it differs, each put in the form Meta asks for and hashed before it leaves our hands. Meta uses the first to leave those shops out of our advertisements for signing up and to show them our advertisements for our other products, and the second, in which each shop also carries a number for the money it has brought us over the last year or, for a shop that has brought none, for how much it has used the Service, to find people like our shops to show our advertisements to. The second list also holds the people who start the signup form and do not finish it, as Section 1(c) describes. A shop with an owner who has stopped our notes, as Section 9(a) describes, or has asked us to leave them off these lists, is left off every list we give Meta after that. Meta uses what it receives under its own data policy. You can limit that use in your Facebook and Instagram advertising settings, or with a browser that blocks trackers. The pixel runs on this website only, and never on a shop’s signing pages.
(b) Google. We also advertise on Google Search, and this website carries Google’s tag (Google Ads). The tag tells Google which pages of this website you visited and sets cookies so that Google can count the advertisement that brought you. If an advertisement on Google brought you, Google’s identifier for your click on it arrives in the address of the page on which you land, and your signup keeps it with the rest of your arrival, as Section 1(e) describes. When you sign up, the tag also sends Google the email address you gave us, hashed in your browser before it leaves, so that Google can match you to an account it already holds and count the advertisement that worked; that is the shop owner’s own email address, given on a business signup. When you activate a subscription, the tag tells Google that a payment was made, with its amount and Stripe’s reference for your subscription, so that Google can count the advertisement that brought a paying shop; nothing about your card goes with it. Where your signup kept Google’s identifier for the click that brought you, our servers also report to Google Ads, against that identifier, the time of your signup, the time your shop first paid, with its amount, and the time your shop’s first Client signed, each with a reference of ours for your signup and nothing about the Client, so that Google can count the advertisement that brought the shop and we can see which advertisements bring shops. Our advertisements on Google are shown to people in the United States, and we send Google those reports on the basis of this notice and of your choice, described next, to limit Google’s use of what it receives. Google uses what it receives under its own privacy policy, and you can limit that use in your Google advertising settings or with a browser that blocks trackers. Like the pixel, the tag runs on this website only, and never on a shop’s signing pages.
3. Information Collected on the Waiver Form
(a) What the waiver form collects. Each shop that uses the Service has its own QR code. When a Client scans it and signs, the waiver form collects what the shop needs for the Client’s Record: the Client’s name, address, phone number, email address, age and date of birth; a photograph of the Client’s government identification, taken with the Client’s phone or, where the shop allows it, chosen from the Client’s saved photographs; the Client’s answers to the waiver form’s questions, about the Client’s health among them, which depend on the work and on the rules where the shop operates; the artist, the description of the work and its placement, and the jewelry for a piercing; the consent text and every box ticked on the waiver form, including the 2 optional boxes described in Section 10(a); the language in which the Client signs; and the Client’s signature, with the date and time. Where the shop or the rules where it operates ask for them, the waiver form also collects an emergency contact, the Client’s physician, the price of the work and how the Client is paying; for a minor, the parent’s or guardian’s name, relationship and signature, the other parent’s name and signature or a photograph of that parent’s written permission, a photograph of the minor’s identification, and photographs of the papers the rules ask for, such as a birth certificate or guardianship papers; photographs of a doctor’s prescription or written instructions; photographs of the needle and ink lot numbers; and the boxes the Client ticks for the shop’s own clauses and for its notice of a fee for paying by card. For a shop in HIPAA mode, the waiver form also records that the Client received the shop’s notice of privacy practices and, where the shop asks, the Client’s answer to its photograph release. After the signing, where the shop or the rules where it operates ask for them, the artist adds the artist’s own signature, drawn on a phone from a link we email to the artist or in the shop’s dashboard, and the lot numbers and expiration dates of the supplies used.
(b) Where the information goes. The waiver form runs on the shop’s own web address. It carries no advertising pixel and no third-party scripts. It counts its own page loads, the steps of a signing and its errors, so that we can tell a broken form from a quiet one, with no name and no cookie: each page load carries a random key made for that page load alone, which the browser does not keep once the page is closed. What a Client types goes to our servers and to the shop, and nowhere else. The one exception is the street address: as a Client types it, what the Client has typed so far goes from our servers to Google’s Places service to suggest the full address, under Google’s own privacy policy. Google sees the typed letters and the shop’s location, and never the Client’s device or anything else on the waiver form.
(c) The shop’s Record. The shop is asking for this information, and the Record is the shop’s. State regulations require shops to keep it, in most states for at least 2 years. We process the Record on the shop’s behalf: we produce the Signed Copy, email it to the shop, store a copy so that the shop can find it later, and keep the Client’s name and contact details in the shop’s client list.
(d) Health answers and identification. The health answers and the photograph of the Client’s identification are the most sensitive information on the waiver form. They are kept with the Client’s Record and in the Signed Copy, which the shop receives and which, where the rules of the shop’s state or the shop provide for it, the Client receives too, and a shop may include its Clients’ health answers in an export of its own records. They go nowhere else: not into the client list, not into the words of an email or a text, never into any marketing, and never to anyone but the shop, the Client, and those who keep the Service running, as Section 8(a) describes, when the shop needs help.
(e) The client list. The client list is the shop’s to keep in touch with. A shop can use its Clients’ names and contact details to reach them about their appointment, their aftercare, and the shop’s news and offers. We never sell a Client’s information. A Client who wants no more messages from a shop can reply STOP to a text, use the link in an email, tell the shop, or write to us, and we pass the request on. A shop can also add to its client list people who have not signed its waiver form through the Service: its owner can add the name of a person from the shop’s own records with their email address, their mobile phone number or both, and a shop that used another service for its waivers can send us that service’s export of them, which we keep on file for the shop and from which we add each person it names. We hold what a shop adds for that shop, as we hold the rest of its client list. Adding a person gives no consent to hear from the shop: a person added this way is sent no email and no text message from the shop until the person gives the consent that Section 10(a) describes, unless that other service’s export records the person’s own yes to the shop’s text messages, as Section 10(a) also describes.
(f) Minors. Where the rules where the shop operates allow a minor to be tattooed or pierced with the consent of a parent or guardian, and the shop allows it for that work, the parent or guardian gives that consent on the waiver form, which collects what Section 3(a) describes for a minor and keeps the consent with the Client’s Record. The waiver form takes no minor’s signing for a cosmetic tattoo. The shop is responsible for that consent, and, as the terms provide, for checking each Client’s identification and age in the way its state requires.
(g) Questions from a Client. If you are a Client and you have a question about your Record, ask the shop first, because the Record is the shop’s. If you want our help, write to hello@waivers.tattoo and we will work it out with the shop.
4. Information Collected on a Shop’s Other Pages
(a) The booking page. A shop can turn on a booking page, on which a person books a session with the shop. It collects the artist, the session and the time the person picks; the person’s name, phone number and email address; and, if the person writes one, a note about what the person wants. The booking goes to the shop, which is emailed about it and sees it in its dashboard, and onto a calendar the shop or the artist has linked, as Section 5 describes. We email the person about the booking, with a link to see or cancel it, and again if the shop confirms, declines or cancels it. Where a session asks for a deposit to hold it, the booking page takes the person to the shop’s deposit page with the booking’s details.
(b) The deposit page. A shop can take deposits on a deposit page, on which a person pays the shop a deposit. It collects the person’s name, phone number and email address, the state in which the person lives, the time of the appointment if there is one, and the person’s agreement to the shop’s deposit policy, with the time, the IP address and the browser from which it was given. The person pays on Stripe’s own page, which takes the payment details and the email address under Stripe’s own privacy policy, and the card number does not reach our servers; we keep Stripe’s reference to the payment and the card’s brand and last 4 digits, for the receipt. The deposit is paid into the shop’s own account with Stripe or, where the shop has chosen it for an artist, into the artist’s. Where the shop has appointed us to collect its deposits under the Deposits Terms of Service, the person pays us, on our Stripe account, and the deposit is transferred to the shop’s or the artist’s account at the time of payment; if the person disputes the payment, we answer the dispute through Stripe with the deposit’s record. We email the person a receipt, and a note if the deposit is refunded, and the shop a note of the payment, and the shop sees the deposit, and the policy the person agreed to, in its dashboard.
(c) Counting. Each page counts its own page views and the steps a person takes on it, in the way Section 3(b) describes for the waiver form.
(d) The link page and the shop’s website. A shop can also have a link page, which gathers the shop’s links in one place, and a website of its own. Each counts its own page views and the buttons a person taps on it, in the way Section 3(b) describes for the waiver form.
(e) The page for a shop’s texts. A shop can have a page of its own, at its address followed by /texts, on which a person says yes to the shop’s texts without signing its waiver form. It collects the person’s first and last name and mobile phone number, and the person’s yes, given in one box that is unticked until the person ticks it, with the time, the words of the box as the page showed them, the page, and which of the shop’s QR codes the person scanned to reach it, if any. We hold the person on the shop’s client list for the shop, as Section 3(e) describes for the people a shop adds, and the yes as the consent that Section 10(a) describes. The page counts its own page views and the steps a person takes on it, in the way Section 3(b) describes for the waiver form, and its server counts, for a minute and in its memory, how many sign-ups come from one IP address, to hold off a flood of them, and keeps no record of the address.
5. Linked Calendars
(a) When a shop’s owner, or an artist on the artist’s own sign-in, links a Google Calendar to the shop’s booking page, we ask Google which times on that calendar are busy, and never what the events are. We keep the busy times for 62 days at a time (from the day before through 61 days ahead), so that the booking page leaves those times out.
(b) We make one calendar of our own in that Google account, named for the shop, and put each booking on it with the name, phone number and note of the person who booked.
(c) We keep the Google account’s email address, unencrypted, and show it to the shop’s owner and to the person who linked the calendar.
(d) The keys that Google gives us to reach the calendar are kept encrypted. Unlinking the calendar deletes them and gives the access back to Google, unless the same Google account is still linked to another calendar on the Service, and the calendar we made stays in the Google account, which belongs to its holder.
(e) A private calendar address, made from the shop’s dashboard for use in any other calendar program, carries the same bookings, with the first name, phone number and note of each person who booked, to anyone who has the address.
(f) What is on a Google Calendar is held by Google under its own privacy policy.
6. Storage and Retention
(a) Storage. We keep information on Amazon Web Services, in the United States, encrypted in transit and at rest. Access to it is limited to the shop it belongs to, and to the people who keep the Service running and the artificial intelligence assistants they use to do so, as Section 8(a) describes; for a shop in HIPAA mode it is limited further, as Section 7(b) describes.
(b) Retention. The Signed Copies and the client list stay in the shop’s account while the account is open. If a shop closes its account while a subscription is running, the account stays open for 90 days after the period it paid for ends, so that it can export everything. When an account closes, we delete what we hold. Where the rule of a shop’s state sets a shorter period for client records, we follow it. Oklahoma’s rule provides that client records are “Destroyed by shredding or other appropriate destruction methods after three (3) years” (Okla. Admin. Code 310:233-3-8(5)(D)), so the Records of an Oklahoma shop older than 3 years are removed on that schedule, and the Client’s name and the date remain on the shop’s client list. The shop keeps its own copy for as long as its state requires, and the Signed Copy we email at every signature is that copy, except in HIPAA mode, in which the Signed Copy is not emailed, as Section 7(b) describes, and the shop’s export is its copy.
(c) Security. No system is perfectly secure. If a breach of security affects your information, we will notify you, or the shop for which we hold it, as the law requires.
7. HIPAA
(a) Coverage. The Health Insurance Portability and Accountability Act (HIPAA) covers health plans and the health care providers that bill them electronically, and a tattoo or piercing shop that does not bill a health plan is not one of those. Unless we have signed a business associate agreement with a shop, we do not act as its business associate under HIPAA, and the Service is not set up for protected health information.
(b) HIPAA mode. HIPAA mode is a plan of its own, for a shop that bills a health plan for its work. The shop’s owner reads and accepts our business associate agreement on the plan’s own page, and for that shop we act as its business associate under that agreement. The shop’s Signed Copies, its client list and the files behind them, identification photographs included, are kept in storage of their own, under an encryption key that only two can use: the Service itself, and the one person who runs waivers.tattoo, who opens a Record only when the shop asks for help with it or to look into a problem with its security. The artificial intelligence (AI) assistants we use to run the business cannot read those Records. A shop in HIPAA mode does not receive the Signed Copy by email; it opens in the shop’s dashboard, behind a sign-in.
8. Disclosure of Information
(a) Information collected through the Service is seen by the shop; by the people who run waivers.tattoo, and the AI assistants we run it with, to help a shop and to keep the Service working, except that the AI assistants cannot read the Records of a shop in HIPAA mode, as Section 7(b) describes; and by the services on which the Service runs: Amazon Web Services for hosting, storage and email; Stripe for payments; Google for the shop search, the waiver form’s address suggestions and the calendars a shop links, for signing in with a Google account and for the mailbox in which we read the email sent to us, and for the advertising described in Section 2, by its tag, which runs on this website, and by the reports our servers send Google Ads, which Section 2(b) describes; Meta for the advertising described in Section 2, by its pixel, which runs on this website only, and by the events our servers send it and the lists we give it, which Section 2(a) describes, and for our questions about a shop’s Instagram account, which Section 1(a) describes; Twilio, which registers a shop with the mobile carriers for texting and carries a shop’s text messages to its own Clients; Anthropic, which provides the AI assistants we run the Service with, and whose model reads the letter from the Internal Revenue Service that a shop gives us to register for texting; Square, for a shop that connects its Square account, in whose catalog we put the shop’s offers and from which we read the payments that use them; Lob, which prints and mails the cards we send to a shop’s mailing address; and a company under the same ownership as ours, whose servers, on Amazon Web Services, run part of the Service, including the systems behind the booking page and the deposit page, hold a copy of the client lists of the shops that are not in HIPAA mode, receive the Service’s own counts of how its pages are used, and run the tools with which we run the business, which read our records of the shops, their signups and their payments and show us the email and the Facebook and Instagram messages sent to us.
(b) Nobody else sees it, unless the law requires it, and then we tell the shop, unless the law forbids us to.
(c) A request from a public authority for a person’s information is checked for its legal basis before we answer it; we answer with the least the law requires, we challenge a request that we believe is unlawful, and we keep a record of each request and what we did with it.
(d) We never sell data, a Client’s or a shop’s.
9. Email
(a) Emails to shops. We email a shop the Signed Copy at every signature, except in HIPAA mode, as Section 7(b) describes; its sign-in, setup and billing emails; a few emails while its first waivers are free; a notice when its month’s allowance of emails to its Clients is used up; reminders, such as a reminder that it has no signed waiver yet; a note when it reaches a number of signed waivers; and notes about the Service from the person who runs waivers.tattoo, some of them sent to many shops at once. Each note sent to many shops at once, and each note at a number of signed waivers, carries a link to stop such notes, which stops the reminders and the notes at a number of signed waivers too, and a shop’s owner can stop them, and start them again, in the shop’s dashboard, under Settings; the emails an account needs, such as the Signed Copy, a sign-in link, a receipt and the notice that a month’s allowance is used up, still go.
(b) Emails to Clients. On a shop’s behalf, we email its Clients the thank-you the shop sends when a Client signs, unless the shop turns it off; the Client’s own copy of the Signed Copy, where the rule of the shop’s state hands the Client one or the shop sends it; the shop’s own emails, and the emails the shop sets to go by themselves, to Clients who ticked the boxes described in Section 10(a), each with a link to stop them; and the emails about a booking or a deposit described in Section 4.
(c) Emails to artists. Where the shop or the rules where it operates ask for the artist’s signature on a Record, we email the artist a link to sign it.
(d) Replies. A reply to any of the emails to a shop reaches a person at waivers.tattoo, and a reply to an email sent to a Client or an artist reaches a person at the shop or at waivers.tattoo.
10. Text Messages
(a) A shop can text its own Clients through waivers.tattoo. A Client gives a mobile number on the shop’s waiver form, and consent to hear from the shop after that day is given in 2 separate boxes, both optional and both unticked, under the box that accepts the terms. The first covers the Client’s own aftercare and how the Client’s healing is going; the second covers the shop’s news, offers and events. A Client ticks either, both or neither, and still signs, because saying yes is not a condition of getting tattooed or pierced. We keep the 2 consents apart when we send: a Client who agreed only to the first never receives a promotional message. A number that a shop adds to its client list from its own records, as Section 3(e) describes, is sent no text message until the person it belongs to gives that consent. A person can also say yes to the second of these, the shop’s news, offers and events by text, on the shop’s own page for its texts, which Section 4(e) describes, in one box that is unticked until the person ticks it; that box does not cover aftercare. A yes given there does not undo a STOP the person sent the shop, or a withdrawal of a consent by the shop or by the person. Where a shop that used another service for its waivers sends us that service’s export, and the export records a person’s own yes to text messages from the shop, we carry that yes over as a yes to the second of these by text alone, the shop’s news, offers and events, and keep with it which service recorded it and the date of its record; it does not cover aftercare or email.
(b) Every text names the shop it is from and is sent by waivers.tattoo on that shop’s behalf. How often a Client receives texts depends on the shop, and message and data rates may apply. Reply STOP to any message to stop, or HELP for help.
(c) Mobile phone numbers and text-message opt-in consent are never shared with third parties or affiliates for marketing or promotional purposes, and are excluded from every kind of sharing described elsewhere on this page. We do not sell them, and we do not hand them to anyone for their own marketing.
11. Changes to This Policy
We may change this Policy at any time. We post each change on this page, and the date at the top of the page is the date of the latest change. The Policy on this page applies from that date. Where a change is material, we may also mention it in an email we send to account holders.