Privacy

Using the visualizer

The build you design (films, tint and light films) is kept in the page’s address, in your browser. We don’t store it unless you send it to us with a quote request.

The visualizer sets no cookies. Your browser keeps one small setting in its local storage (cw-hint-seen), which records that you’ve seen the “drag to rotate” hint so it doesn’t show again, and, for the tab you’re in, whether it has offered you a quote or a share video, and, when you open a build someone shared, whether it asked you to remix it and whether you changed it. They aren’t sent to us. The only cookie on the site keeps shops signed in to their dashboards (below).

Share video makes its clip in your browser from the 3D view; it isn’t uploaded. The clip carries a link to your build, which you choose whether to share.

Some wrap shops show the visualizer on their own websites. It runs from wrapcolor.com inside their page and works the same way; the shop’s website has its own privacy practices.

Your car shows a film on a photo of your own car. The photo is read and recolored in your browser, by a model the page downloads to your device, and isn’t uploaded or stored: we never receive it. A quote request sent from it carries the color you chose, not the photo. Match a color works the same way: a picture you pick a color from is read in your browser and never sent, and neither is the code or paint name you type.

Cloudflare hosts this site. Like any web host, it processes your IP address and browser details to deliver the pages and protect the site from attacks.

To learn which parts of the site people use and to fix what breaks, the visualizer and the cost estimator send usage events to PostHog, our analytics service: the page address without your build, the tools you use (for example, trying a color, switching vehicles, opening the cost estimator), whether you shared a build and how (for example, by copying the link), whether a quote request went through, and errors the page runs into. Like any website visit, they also carry your browser and device type, the site that sent you here and your rough location (country and city). They never include your name, email, phone number, ZIP code, photo or the build in the page’s address. When a shop signs up, our server also records that one did, with the campaign tags in the link it came from when they’re plain names (for example, the shop whose “Powered by WrapColor” link it followed), and without the shop’s name or contact details. Campaign tags that look like anything else, such as an email address, a phone number or a ZIP code, are dropped before any event is sent.

The analytics sets no cookies and, for visitors, stores nothing in the browser. To count visitors without cookies, PostHog works out a one-way code from your IP address and browser details that changes every day, and we’ve set it not to keep your IP address. If your browser sends Do Not Track or Global Privacy Control, no events are sent. Content blockers usually stop them too. We keep our own visits out of the counts: a page opened with ?internal=1 keeps one setting in that browser (wrapcolor-internal), and no events are sent from it after that.

Quote requests

When you ask for a quote for your build, we collect only what an installer needs to contact you about your vehicle.

What we collect

• What you type: your first name, ZIP code, your email address or phone number (whichever you choose), the services you want quoted, your timeline, whether the truck already has PPF or a wrap, and any notes.
• Your build: its link, the film and code on each part, the window tint and light films, and the typical price range we showed you.
• Basic request details: the date and time, your browser’s user agent (which browser and device type it is), the address of the page that linked you here, without its query string, and any campaign tags in the link you followed (utm_ parameters).
• Your consent: the exact text you agreed to, and when.
• The shop you asked, if you sent the request from the visualizer on a shop’s website.

The form uses Cloudflare Turnstile to check that a person, not a spam bot, is sending it. To do that, Cloudflare processes your IP address and signals from your browser, as described in Cloudflare’s Turnstile privacy addendum. We don’t store your IP address with your request. To stop floods of spam, we count the requests from each IP address (an IPv6 address by its /64 network) for an hour, keeping a keyed one-way hash of the address rather than the address itself, and delete the counts within a day.

Why

To pass your request to one independent installer near your ZIP code, or to the shop you asked, so they can contact you about a quote, and to answer you if you write to us about it. We use your details only for that.

Who receives it

• The site owner. Every request sent from wrapcolor.com is emailed to the person who runs WrapColor, who reads it and chooses one independent installer near your ZIP.
• One installer. The owner passes your request to that one shop. We don’t sell your details, and we don’t send them to several shops.
• Or the shop you asked. A request sent from the visualizer on a shop’s own website is emailed straight to that shop and listed on its WrapColor dashboard, where the shop can download its requests. It isn’t sent to the owner or to any other shop.
• Services that handle it for us: Cloudflare (hosting, the database that stores requests, email delivery and the spam check) and Google (Gmail, where the owner receives requests).

How long we keep it

• Our request database deletes each request automatically 12 months after it arrives, or sooner if the shop it was sent to deletes its account. This 12-month limit is for quote requests. A request a shop receives also becomes a customer and a deal in its Peel records, which follow the shop’s own choices (below).
• The owner deletes the email copy by the same time, or sooner if you ask.
• The installer or shop keeps its own copy under its own privacy practices. If you ask us to delete your request, we’ll also tell you which shop received it, so you can ask them too.

Which one? polls

When you make a “Which one?” vote video, we store the poll: the looks you picked (each look’s build, as in the page’s address) and the pictures your browser made of them, so the vote page can show them. We don’t store anything that identifies you, and we keep a one-way hash of your private results link, not the link itself. Your browser keeps a list of the polls you made in its local storage (wc-polls), so their results stay findable.

Voting needs no sign-in. To allow one vote per browser, your browser keeps a random id in its local storage (wc-device) and sends it with your vote; we store only a keyed one-way hash of it with your choice. To stop vote stuffing we count votes per IP address for a day, hashed the same way as our other limits. Polls and their votes and pictures are deleted automatically after 90 days, or when the poll’s maker deletes it from the results page.

Shops

When a wrap shop signs up to show the visualizer on its own website, we keep what it gives us: the shop’s name, email address, website, phone number if given, city and state, its logo, accent color, film brands and starting vehicle, and the websites allowed to show it. We use the email address to send the shop sign-in links and its quote requests. We delete a signup after 7 days if none of its sign-in links was used, since its email address was never confirmed.

We also keep whether the shop asked for early access to Peel and which shop software it uses, if given.

Sign-in links work once, for 30 minutes. Signing in sets one cookie (__Host-wcshop) that keeps the shop signed in to its dashboard for 30 days, or until it signs out; we store only a one-way hash of it. The signup and sign-in forms use Cloudflare Turnstile and the same counts, which for sign-in links also count per email address, by the hour and by the day, hashed the same way.

A shop can also sign in with Google, when Google runs its address’s email (Gmail or Google Workspace). Google then tells us that account’s email address and nothing else; we use it only to find the shop, and keep nothing from Google. Signing in this way sets a second cookie (__Host-wcgoogle) for up to 10 minutes, which ties Google’s answer to the browser that asked for it.

A shop can change its details, or delete its account with its quote requests, from its dashboard at any time, or by emailing privacy@wrapcolor.com. After a shop is deleted we keep only its visualizer’s address, such as wrapcolor.com/embed/acme-wraps/, so that no other shop can take it over.

Peel shop data

Peel is the software a signed-in shop uses to run its leads and quotes. What a shop puts in Peel belongs to the shop’s own records. The shop decides why it holds its customers’ details; we store them so the shop can use Peel.

What Peel stores for a shop

• Customers: name, email, phone, ZIP, city and notes (an Instagram handle a shop adds is kept in the notes).
• Vehicles: year, make, model, trim, VIN and color, when the shop enters them.
• Jobs (deals): title, services, value, stage, follow-ups, and a timeline of notes and changes.
• Imports: the customers and deals a shop imports from a CSV file. The file’s rows are kept for checking and undo, then deleted 7 days after the upload; the customers and deals it created stay.
• Prices and quotes: the shop’s price list and tax setting, and each quote’s options, line items, prices, message and expiry date. Quote requests sent from the visualizer, described above, also arrive in Peel.
• Customer responses: when a customer opens a quote, when they approve it with the name they type, the option and total they chose, and the approval text they agreed to; or that they declined it, with the reason they gave.

Where it’s stored

In Cloudflare’s D1 database, which runs this site with Cloudflare Workers. Quote and approval emails go out through Cloudflare’s email service.

Who can see it

• The shop, when it’s signed in to its dashboard. No other shop can read it.
• A customer sees only their own quote, through its private link: the shop’s name and contact details, their first name, their vehicle (and their build’s picture, if they sent one from the visualizer), the options and prices, and the shop’s message. The shop can replace the link, and the old one stops working.
• The people who run WrapColor, who operate the database that holds it.

How long it’s kept

• Customers, vehicles, jobs, notes, prices and quotes are kept until the shop deletes them, or deletes its account. A job with a sent quote can be archived but not deleted on its own, so its quote history stays until the account is deleted.
• An unsent draft quote is deleted 30 days after its last change.
• An expired, declined or replaced quote loses its options, prices, message and decline reason 90 days after its last change. Its status stays in the job’s history. An approved quote is kept.
• The 12-month limit above applies to quote requests from the visualizer, not to a shop’s Peel records.

Export and delete

A shop can download its customers, its deals (with their notes), its quotes and its quote requests as CSV files from Settings in its dashboard. “Delete shop and all its data”, in the same place, deletes the account with all of its Peel records and quote requests at once. A shop can also email privacy@wrapcolor.com.

If we ever stop running Peel, we’ll email every shop at least 90 days ahead, so it has time to download its records.

Your choices

To see, correct or delete what we hold about you, email privacy@wrapcolor.com. Write from the email address you gave us, or include the phone number you gave, and your request reference if you have it. We’ll tell you when it’s done. You can also tell the installer directly that you don’t want to be contacted.

Children

WrapColor isn’t meant for children under 13, and we don’t knowingly collect their details. If a child sent us a request, email privacy@wrapcolor.com and we’ll delete it.

Changes

If we change how we handle your details, we’ll update this page and the date at the top.