WorkflowPros · Website privacy
Your information.
Your choices.
This privacy notice applies to the public workflowpros.io website. It explains how we handle information from website inquiries, demo bookings, renewal reminders and earlier sign-ups, how we use website analytics and advertising tools, and how you can manage your privacy preferences.
Information we receive
When you contact us
When you request a demo, send us a message, or ask for a callback, including from under our booking calendar, we receive the information you enter in the form. Depending on the form, this may include your name, email address, phone number, company, trade, number of technicians, and message. We use this information to handle your request and contact you about it.
While we compare two versions of our homepage, one of them asks three questions — how many technicians you run, what you would fix first and what you use now — and then for your mobile phone number, to text you your price. When you send it, we receive your mobile phone number, your three answers, the time zone your browser reports and where on the page you started, and send them, with the consent statement shown under the field, to HighLevel / LeadConnector, which texts you your price, how it is made up and a link to book a demo, and the next day, if you have not booked one, a single follow-up with your price and that link. The page shows your price as well, and then the open times of our demo calendar, which our website reads from HighLevel / LeadConnector for the time zone shown. When you tap a time, our website books the demo in that calendar for the contact with your mobile phone number, and when you change the time, it cancels the time booked before: a number holds one demo booked this way at a time. Booking also marks that contact as having booked a demo, so that no follow-up text is sent. So that you can book without entering your number again, our website gives the page a signed note of your number and answers, which the page keeps only while it is open and which our website accepts for one day. If our spam check doubts a request, we show the price but text you nothing, and you book your demo in our booking calendar instead. To text a number its price once a day at most and book no more than three demos a day for it, however many requests come, our website keeps for two days a code made from the mobile phone number, which cannot be turned back into it, with when its price was texted or a demo booked.
Until October 15, 2026, this site had a sign-up form and email fields that showed our pricing. The first step of the sign-up, or an email address entered to see our pricing, sent your email address to HighLevel / LeadConnector even if you went no further; finishing the sign-up also sent your first and last name, mobile number and, if you provided it, company name. Since that day we name our price on a demo and the site no longer has these forms; until October 25, 2026, a page of ours still open from before could still send them, and since then our server no longer accepts them. We use this information to process the sign-up and contact you as described in Emails, calls and texts.
Until October 15, 2026, the site also saved your sign-up status in this browser. The saved record contains your email and, after a full sign-up, your first and last name, mobile number and optional company name. The site no longer writes it or uses it, and since October 25, 2026, it removes the record the next time you open any of our pages; you can also remove it by clearing this site’s browser data. If persistent storage was unavailable, the record was kept only for that tab. A button in our emails can bring your email address to our demo or pricing page: the address follows a # in the link, which browsers do not send to our server, and the page removes it from the address bar before our analytics and advertising tools load, without keeping it. Until October 15, 2026, our case study page asked for an email address to read the rest of it and kept a note in this browser, without the address, that it was open to you; the page no longer asks, and it removes that note the next time you open it.
Until October 17, 2026, you could ask us on our homepage to remind you of your notice deadline (until October 25, 2026, from a page still open from before). For such a request we received your email address, the renewal date and notice period you chose, and the reminder date shown. We use them to email you that reminder on the day shown and as described in Emails, calls and texts.
For forms that display a consent statement, we send the exact statement shown with the request. The message and callback forms on our contact page, and the callback request under our booking calendar, do not send a separate consent statement.
Our forms send this information through our website to HighLevel / LeadConnector, the service we use to receive these requests. Each request also includes the IP address it was sent from and the approximate country and network that Cloudflare associates with that address; we use them to detect and block spam. When we count your visits, as described under Browser storage periods, the request also includes your visitor ID, which links it to those visits, so we can see which visits led to it, and a list of the ways you arrived before it (the first, the last and how many), with the day, the kind of link, its service and the ad campaign number of each. While we compare two versions of our homepage, the request also says which version this browser was shown (see Browser storage periods). We also check the details you send for signs of spam, and a person reviews requests flagged this way; if a request is spam, we may stop the address it came from sending our forms and seeing our Google ads. Declining optional analytics and advertising does not prevent you from submitting a form.
We also count the requests our forms send from this site, in every region: which form it was and where on the page, whether it reached HighLevel / LeadConnector, how long that took and whether our spam check flagged it, the page it was sent from, the approximate country and whether the device is a phone, tablet or computer. When we count your visits, the count also records your visitor ID and how you first arrived (see Browser storage periods) and, while we compare two versions of our homepage, which version this browser was shown. Requests refused because too many came from one address are not counted. These counts hold none of the details you enter and no IP address; they are kept for three months, and we use them to notice when requests do not get through.
When Google Analytics is enabled, a Google Analytics browser identifier, campaign information from your visit, the first page of that visit and the domain of the website that referred you may be sent with your request. This helps us link your inquiry to the visit or campaign that led to it.
When Google Analytics is enabled and a sign-up step is accepted (until October 25, 2026, from a page still open from before October 15, 2026, as described above), we send an event stating that the email step or the full sign-up was completed and which of our forms it was sent from. These events contain no values entered in the form. These events are used for analytics only; until October 19, 2026, the full sign-up event was also reported to advertising partners.
When Advertising is enabled, we send with an inquiry request (and, until October 25, 2026, with a sign-up or reminder request) the newest advertising click identifier of each type that we have, such as Google’s gclid. A request may include more than one identifier. We use these identifiers to understand which ads led to requests and to support later conversion measurement.
Until October 19, 2026, when both Google Analytics and Advertising were enabled, we notified advertising partners that an accepted demo request, contact message, callback request or renewal reminder was submitted, or that a full sign-up was completed, and identified the page it came from. Since then these are no longer reported to advertising partners: of what you do on our forms and in our booking calendar, they are told only that our booking calendar was shown to you, when you first click into it and that you booked a demo in it, and Google Ads, Microsoft Advertising, Meta, LinkedIn, X and Reddit, only for their lists of people to show our ads to, until October 25, 2026, that the email step of our sign-up was accepted, as described below. Since October 26, 2026, when Advertising is enabled, Google Ads, Microsoft Advertising and Meta may also be told that you picked a time in our booking calendar and that its form for your details was opened — only that it happened, where on our site and at which step of the calendar, with no value, never the date or time you chose or anything you enter. Since November 19, 2026, when Advertising is enabled, Google Ads and Microsoft Advertising may also be told that you gave an email address for your demo invite — only that it happened, where on our site and a value we give it, never the address itself.
In the version of our homepage that offers your price by text, our advertising partners are also told when you answer its first question, when your request for a price is accepted and when you book a demo from it, as described below.
Our demo request page is an exception: when both Google Analytics and Advertising are enabled and a request you send from its form is accepted, the page tells Google Analytics, and may tell Meta, LinkedIn, Google Ads, Microsoft Advertising (ads on Bing), X, Reddit and OpenAI, that a demo request was sent from that page — only that it happened, never your name, email address, phone number or anything else you enter — to measure our ads and to show them to people more likely to request a demo. A request our spam check flags is not reported this way.
Some partners’ tags can also collect contact details you enter in a form, such as your email address or phone number. These details are converted into a hashed code in your browser before being sent to those partners. The code does not show your contact details in plain text, but partners can match it against codes generated from information they already hold. This may allow them to recognize you if you have an account with them and link your request to an ad. This happens only while Advertising is enabled.
When you browse
We use Cloudflare to deliver and protect this website. Loading a page involves processing connection information, including your IP address and the page you request. Cloudflare also keeps a log of the requests to our website for about a month, separate from our own server logs, and we may search it as described under Protecting our ads from fraud, including for visits that did not come from our ads. Our website also keeps its own record of each page of this site you open, for 90 days, as described under Our record of the pages you open. We also use your IP address to limit repeated form submissions and reduce abuse. On pages with our forms, Cloudflare Turnstile checks in the background that a person, not an automated script, is using the form, and when you arrive from one of our ads, it also checks the page you open, as described under Protecting our ads from fraud; Cloudflare receives information about your browser and device for this check (Turnstile Privacy Addendum).
We use Cloudflare Zaraz to manage the optional analytics and advertising tools on this site. Each tool runs only when its category is enabled. When a tool is running, its provider may receive information about your visit, including the page you visit and the page you came from, device and browser information, your IP address, identifiers stored in your browser, and identifiers included in an ad link you clicked.
Cloudflare Zaraz also sets a technical cookie named cf_zaraz_client whenever its script loads, even before you choose your privacy preferences. The cookie is empty: it holds no identifier and is not used to recognize you or to link your visits. It expires one year after your last visit, and you can delete it in your browser settings.
When both Google Analytics and Advertising are enabled, we also tell Google Analytics when your visit has been on screen for 15, 30 and 60 seconds, and when this browser comes back for its 2nd, 3rd, 5th or 10th visit or later; only visits with at least 15 seconds on screen are counted. These signals contain only those times, the visit number and a score we give each step, not the pages you read or anything you enter. The first time this browser reaches each of these steps, as far as the visit record described under Browser storage periods shows, the page also tells our website which step it was, even when the analytics and advertising tools did not load (a browser that cannot keep that record does not); your browser sends that request with this site’s cookies like any other, and when we count your visits, we count the step with them, as described under Browser storage periods, by visitor ID, approximate country, whether the device is a phone, tablet or computer and how you first arrived, without the page, the visit number or the score. With both settings on, these signals also go to Google Ads, Microsoft Advertising (ads on Bing), Meta, LinkedIn, X and Reddit, only to build the lists of people we show our ads to again and to find people with similar interests; our ads are not measured or optimized on them. Until October 19, 2026, they also went to OpenAI. A visit ends after 30 minutes without our site on screen.
When both Google Analytics and Advertising are enabled and your visit has been on screen for at least 15 seconds, we also tell Google Analytics, once per visit, that you changed something in one of our calculators or started a round of the missed-call test on our homepage. Until October 25, 2026, we also told it when the email step of our sign-up was accepted (once per browser). These signals contain only that it happened and a score we give it; they never contain your email address, the numbers or dates you enter or your results. These signals also go to Google Ads, Microsoft Advertising (ads on Bing), Meta, LinkedIn, X and Reddit, only to build the lists of people we show our ads to again and to find people with similar interests; our ads are not measured or optimized on them. Until October 19, 2026, they also went to OpenAI and were used to measure our ads. The first time this browser sends the calculator signal, the page also tells our website, and we count it as we count the visit steps above. From October 11 to October 15, 2026, with the same two settings on, a click on a button to our pricing was reported the same way, with where it was.
When Google Analytics is enabled and you click "Book a demo" anywhere on this site, or our booking calendar is shown to you — opened over the page, or on your screen where a page has it — the page tells Google Analytics and our website which button or calendar it was, once per page you open; your browser sends the request to our website with this site’s cookies like any other. It also tells our website, and Google Analytics, when you first click into that calendar, and tells our website when a booking you make in it goes through. When we count your visits, we count these as we count the visit steps above, with the page of this site they happened on, so that we see how many of the people who open the calendar book a demo, and from where on the site. These events contain only that it happened and where on the site, never anything you enter in the calendar. When Advertising is also enabled, our booking calendar shown to you is also reported to our advertising partners — Google Ads, Microsoft Advertising (ads on Bing), Meta, LinkedIn, X, Reddit and OpenAI — to measure our ads and to show them to people more likely to book a demo; this signal says only that a calendar was shown and a value we give it, not which calendar it was. They are also told when you first click into that calendar, with a value we give it, for the same purposes; this signal too says only that it happened, and until the evening of October 19, 2026 it went only to Google Ads and Microsoft Advertising. With both settings on, a click on "Book a demo" is also told to Google Analytics a second time, once per visit and only once your visit has been on screen for at least 30 seconds, the time on all pages of this site added up as for the visit signals above: a click made sooner waits until then and is not told if the visit ends first; this second signal does not say which button it was. Until October 19, 2026, the calendar shown went only to Google Ads and Microsoft Advertising, together with that click and your first click into the calendar; until October 17, 2026, only the click was reported, and only to Microsoft Advertising. The other events in this paragraph are not sent to our advertising partners.
Since October 26, 2026, when Google Analytics is enabled, the page also tells Google Analytics and our website, once per page you open, each step you take in our booking calendar: that you tapped a date, turned to another month, that it showed no open times, the time zone list you closed (which of the ten time zones of the United States and Canada you chose, another zone, or none changed — never the name of another zone), that you picked a time, went on to the form for your details or stepped back (from which step, and by the calendar’s own button or your browser), that the form to call you back was opened and why, that you pressed "Book my demo" or "Call me back" and what came of it, in a word, with how many milliseconds you waited, a field our page or our website did not accept (which field and what kind of error, never what you entered), the buttons after a booking ("Add to calendar", "Change the time"), that you pressed "Try again" when the open times did not load, that you gave an email address for your demo invite (since November 19, 2026; over a "Book a demo" button or as the first step of the booking window, and which of the two — never the address itself), and whether you are changing the time of a demo you booked. Each says the step of the calendar where it happened, the page of this site and where on it the calendar is; the calendar shown also says the step it opened on, and your first click into it what that click was. These events never contain the date or time you choose, your name, email address or phone number, or anything else you enter; when we count your visits, we count them as we count the visit steps above. When Advertising is also enabled, of these steps only the email address you gave for your invite (that you gave one, never the address), the time you picked and the form for your details opened may be told to our advertising partners, as described under When you contact us.
When Google Analytics is enabled, the page also tells Google Analytics and our website when our booking calendar is slow to load or could not load, with how long you waited for it on your screen; and when you leave it without booking — closing it, or leaving the page — with how many seconds it was open and whether you had clicked into it, and since October 26, 2026 at which step you left it, how you closed it (its close button, the dimmed page around it, the Escape key, a swipe down, your browser’s Back button, or leaving the page) and whether you had asked us to call you back. It tells our website alone when the calendar has loaded, with how long that took and how long you waited for it. The page also tells Google Analytics and our website when you tap our phone number, with where on the page the number was. These events say which calendar or number it was and the page of this site, once per page you open, and never contain anything you enter; they are not sent to our advertising partners. When you book a demo, our customer system (HighLevel) may later tell our website, with the visitor ID it holds from your request, whether the demo took place, was missed or was cancelled, whether you became a customer, and whether a call you made to our number was answered or missed. We count these with that visitor ID, as we count a booking, so that we see which ways to our site lead to demos held and to customers.
In the version of our homepage that offers your price by text, when Google Analytics is enabled, the page tells our website when you tap a "Get my price by text" button, with where on the page it was; when you answer each of the three questions, without your answer; when the field for your mobile phone number is shown; when the times of our demo calendar are shown; when you change the number of technicians for your price, without the number; and when sending your number, loading the times, booking a time or starting the questions does not work, with which of these it was; once per page you open. Your browser sends these requests with this site’s cookies like any other, and when we count your visits, we count them as we count the visit steps above, with the version of the homepage. Our website itself counts each request for a price it passes to HighLevel / LeadConnector and each demo booked from it, as it counts the requests of our forms and the bookings. With Google Analytics enabled, the page also tells Google Analytics when you answer the first question, when your request for a price is accepted, with the lowest monthly price for the number of technicians you chose as its value, and when you book a demo, with a value we give it; when Advertising is enabled too, these three also go to our advertising partners — Google Ads, Microsoft Advertising (ads on Bing), Meta, LinkedIn, X, Reddit and OpenAI — to measure our ads and to show them to people more likely to ask for a price or book a demo. None of these events contains your mobile phone number or your answers, beyond the value that follows from the number of technicians you chose, and a request our spam check flags is not reported as accepted.
Until October 16, 2026, our homepage had a 15-second test of how many calls your office would miss, and a page opened before then still has it. When Google Analytics is enabled, the page tells our website when you start a round of it, when you answer your first call in a round, when its result shows, with how many calls you answered and missed, and when you close a round before its result; your browser sends each of these requests with this site’s cookies like any other. When we count your visits, we count them as we count the visit steps above, by visitor ID, approximate country, whether the device is a phone, tablet or computer and, while we compare versions of the homepage, the version, so that we can see whether the test works on every kind of device. With Google Analytics enabled, we also tell Google Analytics about these events, with those numbers and, during a comparison, the version of the homepage, and when Advertising is enabled too, our advertising partners, who use them to show our ads to people who tried the test; they never contain anything you enter.
On our homepage opened before October 16, 2026, when Google Analytics is enabled, the page also tells our website when the missed-call test has been on your screen for a second, once per page you open; your browser sends this request with this site’s cookies like any other. When we count your visits, we count it as we count the visit steps above and, while we compare versions of the homepage, with the version, so that we judge each version by the people who saw it. We also tell Google Analytics; this event is not sent to our advertising partners.
On our case study page, when Google Analytics is enabled, the page also tells our website when its "Book a demo" in the story or the booking calendar at its end has been on your screen for a second, once per page you open; your browser sends this request with this site’s cookies like any other. When we count your visits, we count it as we count the visit steps above, so that we judge each place by the people who saw it. We also tell Google Analytics; this event is not sent to our advertising partners and never contains anything you enter.
On our case study page, when Google Analytics is enabled, the page also tells our website that you opened it and which page of this site you came from (nothing when you came from elsewhere), which of its parts have been on your screen for a second, when the page has been on your screen for 30 seconds, 1 minute and 2 minutes, and which of its screenshots you open full size, once per page you open; your browser sends these requests with this site’s cookies like any other. When we count your visits, we count them as we count the visit steps above, with that page, so that we see how far the case study is read. We also tell Google Analytics of the parts, the times and the screenshots; these events are not sent to our advertising partners and never contain anything you enter. When you arrived from one of our ads, our record of that arrival also keeps which of its parts were on your screen, when the page had been on your screen for 30 seconds, 1 minute and 2 minutes and which of its screenshots you opened, as described under Protecting our ads from fraud.
On our features page, when Google Analytics is enabled, the page also tells our website which of its parts have been on your screen for a second — its first screen, the card of each group of features, our numbers, the part about switching and the booking calendar at its end — and which of its cards you tap to open that group’s page, once per page you open; your browser sends these requests with this site’s cookies like any other. When we count your visits, we count them as we count the visit steps above, with that page, so that we see which features people read about. These events go only to our own counts, not to Google Analytics or our advertising partners, and never contain anything you enter.
On our pricing page, when Google Analytics is enabled, the page also tells our website when its price quiz has been on your screen for a second, which size of team and which trade you pick in it, and when you change the number of techs, go back a step, switch its price to yearly or open its rule on leaving a year paid ahead — never the number of techs itself —, once per page you open; your browser sends these requests with this site’s cookies like any other. When we count your visits, we count them as we count the visit steps above, with that page, so that we see how people use the quiz. These events go only to our own counts, not to Google Analytics or our advertising partners, and never contain anything you enter.
On our pages for each trade and on our industries page, when Google Analytics is enabled, the page also tells our website which of its parts have been on your screen for a second — its first screen, the steps of the job it shows, its questions, the booking calendar at its end and its other parts — and which of its links you tap, by where they lead, once per page you open; your browser sends these requests with this site’s cookies like any other. When we count your visits, we count them as we count the visit steps above, with that page, so that we see what owners of each trade read. These events go only to our own counts, not to Google Analytics or our advertising partners, and never contain anything you enter.
When you play one of our short films — the film on our homepage, or the demo of our app on our pages or from the menu on any page — and Google Analytics is enabled, the page also tells our website that it started, that you watched half of it and that you reached its end, and, whether or not you play it, that its picture was on your screen — on the page where it stands, or in the menu once you open it, with which film, where you played it and the page, once per page you open; your browser sends these requests with this site’s cookies like any other. When we count your visits, we count them as we count the visit steps above, so that we see whether the film is watched. These events go only to our own counts, not to Google Analytics or our advertising partners. The film itself loads from our website only when you play it, apart from its first two seconds, which your browser may load a moment before.
On our homepage, when Google Analytics is enabled, the page also tells our website which of its parts have been on your screen for a second — its first screen, our short film, our numbers, the part about our free trial and money-back guarantee, the steps of a job in our app, the part about switching, our answers to owners’ questions and the booking calendar at its end — once per page you open; your browser sends these requests with this site’s cookies like any other. When we count your visits, we count them as we count the visit steps above, with that page, so that we see how far down our homepage people read. These events go only to our own counts, not to Google Analytics or our advertising partners, and never contain anything you enter. When you arrived from one of our ads, our record of that arrival also keeps which of these parts were on your screen, as described under Protecting our ads from fraud.
On our pages that compare WorkflowPros with another company, when Google Analytics is enabled, the page also tells our website which of its parts have been on your screen for a second — its first screen, our report, our short film, the side-by-side table, the comparison feature by feature, what else WorkflowPros does, the questions to ask before you sign, the part about switching and what to do before you cancel, the booking calendar at its end and the sources — which of its folded parts you open, and which of its links you tap, by where they lead: one of our pages, a line of the sources on that page, or only that it leads to another website. It does so once per page you open; your browser sends these requests with this site’s cookies like any other. When we count your visits, we count them as we count the visit steps above, with that page, so that we see how far down each comparison people read and what they check. These events go only to our own counts, not to Google Analytics or our advertising partners, and never contain anything you enter. When you arrived from one of our ads, our record of that arrival also keeps which of these parts were on your screen, as described under Protecting our ads from fraud.
On every page, when Google Analytics is enabled, the page also tells our website when you tap a link in its header, in the menu that opens from the menu button on a phone or a narrow screen, or in its footer — which of the three, and which page of our site it leads to, or only that it leads to our email address or elsewhere — and when you open that menu, once per page you open; your browser sends these requests with this site’s cookies like any other. When we count your visits, we count them as we count the visit steps above, with the page you tapped on. These events go only to our own counts, not to Google Analytics or our advertising partners, and never contain anything you enter.
On every page with a form for a request or a reminder, the callback request under our booking calendar included, when Google Analytics is enabled, the page also tells our website when the form has been on your screen for a second and when you first type or choose something in it, once per form and page you open, with the name of that form — never what you type or choose. Your browser sends these requests with this site’s cookies like any other. When we count your visits, we count them as we count the visit steps above, so that we see, for each form, how many people saw it, started it and sent it. These events go only to our own counts, not to Google Analytics or our advertising partners.
Website performance monitoring
We also use Cloudflare Web Analytics to measure page views and monitor how quickly pages load. Cloudflare states that this service does not use cookies or browser storage to collect usage metrics and does not fingerprint visitors. Reports include page and referrer information, device and browser categories, and performance metrics. Learn more about Cloudflare Web Analytics.
Cloudflare Web Analytics operates separately from the Google Analytics and Advertising settings described below.
When Google Analytics is enabled, a script of this site also measures in your browser how quickly each page loads and responds to you and how much its layout moves, and sends these measurements to our website when you leave the page or switch away from it. We count them by page (its address without parameters), approximate country, whether the device is a phone, tablet or computer, the connection speed class your browser reports, whether you opened the page, reloaded it, came back to it or your browser loaded it ahead, how many times you tapped, clicked or typed on it and, when we count your visits, your visitor ID and how you first arrived. These counts hold no IP address, are kept for three months and help us keep the site fast. The same report also describes in more detail the screen, the device, the browser and how the page loaded, to find display problems; we do not count those details, and we keep them only while we investigate such a problem, in our server logs, for up to seven days.
Protecting our ads from fraud
When you arrive at our website from one of our ads, our website keeps a record of that arrival to detect invalid clicks, such as clicks made by automated programs or click farms, which our advertising partners charge us for; we also use this record to see how our ads perform, as described at the end of this section. The record holds the time, the page of this site you opened, the advertising partner, the ad click identifier in the link you clicked, the campaign number and the tags of that link (its source, medium, campaign, ad group, keyword and ad number), your approximate location (country, region and city), your network (the number and name of your internet provider’s network), your IP address shortened to its network (the first three parts of an IPv4 address or the first 48 bits of an IPv6 address) together with a code calculated from your full IP address that cannot be turned back into it, whether the device is a phone, tablet or computer, the name and major version of your browser and operating system, your browser’s preferred language, technical details of the connection provided by Cloudflare (its data center, the time zone of your IP address, the protocol and encryption version, a short fingerprint of the encryption handshake and the connection’s round-trip time), and whether your browser or Cloudflare identifies the visit as an automated program. When Google Analytics is enabled, we also record that the page was shown to you if this browser is new to us or the page was loaded in advance (see Browser storage periods), and, when the page reports them as described above, when your visit reaches 15, 30 or 60 seconds and when you click "Book a demo", open or first click into our booking calendar, pick a time in it, open its form for your details, book a demo, ask us from it to call you back, give an email address for your demo invite, start one of our forms, have a part of our homepage, of one of our comparisons or of our case study on your screen for a second, have our case study on your screen for 30 seconds, 1 minute or 2 minutes or open one of the case study’s screenshots full size on that page or, within 30 days of that arrival, on our other pages, with the name of the button, calendar, form, part of the page or screenshot where it happened and your visitor ID when we count your visits. The record never holds your full IP address, your browser’s full identifying text or anything you type.
A few seconds after a page you opened from one of our ads has loaded, Cloudflare Turnstile also checks in the background, without showing you anything, that a person’s browser, not an automated program, opened it; Cloudflare receives information about your browser and device for this check (Turnstile Privacy Addendum). Our record of that arrival keeps only the result: whether the check was passed or failed, or why it could not be completed, with Cloudflare’s error code when there is one. The check does not block or change anything on the page.
When that check could not confirm a person’s browser — Cloudflare could not complete it or asked for a click — and nobody taps, clicks, types or turns the scroll wheel on that page within 30 seconds or before leaving it, our record of that arrival also notes that the visit looks automated. When both Google Analytics and Advertising are enabled, the page then also tells Google Analytics, Google Ads, Microsoft Advertising (ads on Bing), Meta, LinkedIn, X and Reddit that the visit looks automated and why the check could not be completed, and nothing else, so that our ads are no longer shown to that browser or account.
We keep each entry of this record for 90 days from when it was made and then delete it, so a step recorded within 30 days of an arrival is deleted at the latest 120 days after that arrival. We use it to protect our advertising budget: to find invalid clicks, to exclude the networks and addresses they come from in our advertising accounts, and to ask our advertising partners to refund them, in which case we may share the click identifiers, the times and our reasons with that partner. We do this on the basis of our legitimate interest in preventing fraud, so it does not depend on your privacy preferences; it uses only the requests your browser sends to our website and sets no cookie. We also count each arrival in our own reports on our ads, by its advertising partner, campaign number and link tags, the page you arrived on and your device. We do this on the basis of our legitimate interest in knowing how our ads perform, so this count does not depend on your privacy preferences either. The steps described above, from 15 seconds on screen to a booking, reach this record only when Google Analytics is enabled (the 15, 30 and 60 seconds only when Advertising is enabled too), because we record them only when we count your visits. We also use them, with their times, the advertising partner, the ad click identifier, the campaign number and tags of the link you arrived by, the page you arrived on and the page where each step happened, your device and your visitor ID, to see which of our ads bring people who read our pages and book a demo; we leave out visits that your browser or Cloudflare identifies as automated and visits from networks that belong to our advertising partners themselves. When you book a demo or send us a request, or when we look into how you came to us and what you did on our site, we may also search this record and our record of the pages you open, described below, for earlier arrivals, pages and steps: by the ad click identifier or visitor ID, by the code calculated from your IP address, by your shortened IP address, by the short fingerprint of the encryption handshake together with your city, and by your city and region or those of your business; we may also search the request logs Cloudflare keeps for our website for about a month, by your network, your shortened IP address and your browser’s full identifying text. These logs record the requests to our website, whether or not they came from one of our ads, each with its time, the address requested (including any tags or ad click identifier in it), the full IP address it came from, its network and country, and the browser’s full identifying text. Such a search can find your other visits, including those from your other browsers and devices, on the same network or elsewhere in the same city or region; it can also find other people’s visits from that network or area, or from a browser like yours. We do this on the basis of our legitimate interest in knowing how our ads and pages bring people to us, so it does not depend on your privacy preferences. Turning Google Analytics off stops new steps from reaching this record; those already recorded stay in it until they are deleted as described above. The results of these uses stay in our own reports, which we do not share with our advertising partners or other third parties for their own purposes. You can object to any of these uses or ask us to delete your entries in this record, as described under Questions and requests.
Our record of the pages you open
Since October 28, 2026, our website also keeps a record of each page of this site you open, whether or not you came from one of our ads. It does not record pages your browser loads in advance, addresses that are not pages of our site, or visits that your browser or Cloudflare identifies as automated programs. For each page, the record holds the time, the page of this site, the tags in the page’s address (the source, medium, campaign, ad group, keyword and ad number of the link you arrived by) and any ad click identifier in it, where you came from (only the domain of the website that sent you, or the page of this site you came from), your visitor ID when we count your visits (see Browser storage periods), your approximate location (country, region and city), your network (the number and name of your internet provider’s network), your IP address shortened to its network (the first three parts of an IPv4 address or the first 48 bits of an IPv6 address) together with a code calculated from your full IP address that cannot be turned back into it, whether the device is a phone, tablet or computer, the name and major version of your browser and operating system, your browser’s preferred language, technical details of the connection provided by Cloudflare (its data center, the time zone of your IP address, the protocol and encryption version, a short fingerprint of the encryption handshake and the connection’s round-trip time). The record never holds your name, email address or phone number, anything you type, your full IP address, your browser’s full identifying text, the contents of your cookies other than the visitor ID described above, or the full address of the page that sent you. We keep each entry for 90 days from when it was made and then delete it. We use this record to protect our website and our ads from fraud and abuse, to see how people come to our website and which of our pages they open, and to see how a booking or a request came to us: when you book a demo or send us a request, or when we look into how you came to us and what you did on our site, we may search it as described under Protecting our ads from fraud. We do this on the basis of our legitimate interest in protecting our website and our ads and in knowing how people come to us, so it does not depend on your privacy preferences; it uses only the requests your browser sends to our website and sets no cookie. Turning Google Analytics off stops your visitor ID from being recorded with the pages you open, not the record itself. The results stay in our own reports, which we do not share with our advertising partners or other third parties for their own purposes. You can object to this use or ask us to delete your entries in this record, as described under Questions and requests.
When you refer a company
When you refer a company, you give us its owner’s name and contact details. We use them only to reach the owner about WorkflowPros, and we don’t send the owner text blasts.
When you book an appointment
Our booking calendar is our own: your booking is made in our calendar and stored in HighLevel / LeadConnector, the service we use to keep our contacts, and the meeting is held on Google Meet. It is on our demo page, our pricing page and our booking page, at the end of our other pages, and over any page when you click "Book a demo". It loads when you open it or come near it on the page, and that does not depend on your privacy preferences: it is how you book an appointment. Its open times also load from our website in the background soon after a page has loaded, before you open it, so that it opens at once; that request asks only for the open times. To book an appointment you enter your name, email address and mobile phone number and choose a time; the invitation and the Google Meet link for your demo are sent to the email address you enter. This browser tab keeps the time of your demo, its meeting link and a code that lets you change the time from this tab, until you close it; if instead we are to call you to confirm a time, it keeps that time until it has passed, so that our calendar shows your request when you open it again. From October 16, 2026 until we moved to our own calendar, our booking calendar was provided by Calendly, which received the details entered to book an appointment and sent the invitation and the meeting link, under its own terms. If a page of ours opened until we moved to our own calendar is still open, it can still tell our website of a booking made in Calendly: our website then reads your name, email address, mobile phone number, time zone and the time and meeting link of your demo from Calendly by the booking’s reference, passes them to HighLevel / LeadConnector with the same information as a booking in our own calendar, described below, and keeps that reference, with when it reached us, for 90 days, so that each booking is passed on and counted only once. Until October 16, 2026, our booking calendar was provided by HighLevel / LeadConnector and loaded only when a category called Optional features was enabled; that category has been removed from your privacy preferences. Under the calendar you can also ask us to call you back, as described under When you contact us, and you can contact us to schedule a demo.
If you enter your email address over “Book a demo” on one of our pages, or as the first step of booking a demo, we save it in HighLevel / LeadConnector when you press the button, even if you then book no time, as a request from our forms (see When you contact us), and we may email you about booking your demo and send you updates about WorkflowPros and our offers; you can stop these emails at any time, as described in Emails, calls and texts.
When you book, the page sends your name, email address, mobile phone number, time zone and the time you choose to our website, with where on our site you booked and, as for our forms, the campaign information and ad click identifiers your choices allow (see When you contact us). Our website books your demo in our calendar, which creates its Google Meet link, and sends the booking, with that information, the network details described under When you contact us and, when we count your visits, your visitor ID and how you came to our site, to HighLevel / LeadConnector, the service we use to keep our contacts and to tell our team about new bookings, including in Slack.
When Google Analytics is enabled and you book an appointment in our calendar, we tell Google Analytics that a demo was booked, and when Advertising is also enabled, our advertising partners too. This event contains only that a booking was made, a value we give it and where on our site the calendar was opened; it never contains the details you enter in the calendar or the time you choose. Partners use it to measure our ads and to show them to people similar to those who booked.
When you book in our own calendar, our website first looks up in HighLevel / LeadConnector whether you are already our contact and whether you have a demo booked, and makes you a contact there only if you are not one; it never changes the name or phone number of a contact we already have. To protect our calendar from automated bookings and repeated attempts, our website also keeps, in its own database at Cloudflare, codes that cannot be turned back into what you entered, never your name, email address or phone number themselves: for each booking request, a code calculated from a random number the page makes for it, your email address, your mobile phone number and the time you chose, with a code of the pass Cloudflare Turnstile gave that request and whether it booked an appointment, for 30 days, so that the same request sent again is never booked twice; codes calculated from your email address and from your mobile phone number with a secret key, with the time of each booking attempt and of each new demo, for 2 days, to limit how often one email address or phone number can book; a code calculated with a secret key from your network (your IP address shortened as described under Protecting our ads from fraud), with the time of each new demo booked from it, for 2 days, to limit how many demos one network can book; and, for each appointment, whether our team has been told of it and whether it has been counted, for 30 days. For each request sent from our booking or from one of our forms, it also keeps a code of the Cloudflare Turnstile pass the request carried with a code of that request, for 1 day, so that one pass counts for one request only, and, once a request from one of our forms has reached our team, the code of that request with whether our website accepted it, for 1 day, so that the same request sent again is not passed to our team twice. If Cloudflare Turnstile cannot confirm that a person is booking, or our limits on bookings are reached, depending on our settings we do not book the time and the page offers to call you back, we pass your name, mobile phone number, email address and the time you chose to our team as a callback request, as described under When you contact us, and a person on our team calls you or books that time for you, or we book it and mark it for our team to review. Currently we pass it to our team.
With such a callback request, whether it comes from our booking, from the callback form under our calendar or from the callback form on our contact page, we also give our team signs that a person sent it, so that they can call real people first: how long this page had been open, how long your visit had been on your screen and how many times you have visited (these two only when we count your visits), how long ago your visit began, whether you arrived from one of our ads in the last 30 minutes and whether the check on that page passed (from the record described under Protecting our ads from fraud), the name and number of your network as Cloudflare names it, and whether the domain of the email address you entered receives email, which our website asks Cloudflare’s public DNS resolver about with the domain alone. These signs never block a request. To limit how many such requests reach our team, our website keeps, for 2 days, a code calculated from your mobile phone number with a secret key and what became of each request.
When our booking calendar is shown to you, Cloudflare Turnstile checks in the background that a person is using it, so that the check is done by the time you book. Our website counts, once per page, whether that check gave a pass and how many milliseconds it took, or why it did not (an error with Cloudflare’s error code, its script blocked, no answer within 30 seconds, or the page left first), with the page, where on our site the calendar was shown, the device type, approximate country and, when we count your visits, your visitor ID and how you first arrived. This count holds no IP address or anything you enter, is kept for three months like our other counts of form requests, and does not depend on your privacy preferences, because it protects our booking.
We count each booking with the counts of form requests described under When you contact us, in every region, and with the visit counts described under Browser storage periods, under your visitor ID when we count your visits; we also count what became of passing it to HighLevel / LeadConnector. Until October 16, 2026, HighLevel / LeadConnector told our website of a booking in its calendar, with the visitor ID of a request you had sent us earlier, even if you had turned Google Analytics off since that request. These counts hold no name, contact details, appointment time or IP address and are kept for three months; under a visitor ID, the booking is also kept with that visitor’s arrivals for three years, as described under Browser storage periods. Since October 26, 2026, a change of the time of a demo you booked is counted as a change, once for each new time, not as a new booking.
In the version of our homepage that offers your price by text, you book a demo with one tap in our own booking calendar at HighLevel / LeadConnector, as described under When you contact us, with only the mobile phone number you entered for your price; HighLevel / LeadConnector sends you the meeting link and reminders by text message, and tells our team about the booking.
So that you don’t type your details twice, after you send our demo request form, or when you open the link to pick a time in the email we send after a request you made on LinkedIn, our website keeps your name, email address and mobile phone number for 30 minutes in an encrypted cookie named wp_dh, which only our website can read: the pages, their scripts and our analytics and advertising partners cannot. A second cookie, wp_dhs, holds only the fact that details are kept, and lasts as long. Our booking calendar then shows only your first name, on a button that books your demo with those details as described above, and, over it, where the invite and the reminder will go: the first letter and the domain of your email address and the last four digits of your mobile phone number; “Use different details” lets you type others instead. Both cookies are removed when you book or ask us to call you, and expire after 30 minutes. The link in that email carries a code of your contact in HighLevel / LeadConnector, signed by our website and valid for 7 days; when you open it, our website checks the code, reads your name, email address and mobile phone number from HighLevel / LeadConnector into that cookie and takes the code out of the address before the page loads, so no script on the page sees it.
Emails, calls and texts
If you entered your email address to get our offer or to see our pricing, we email you the offer and pricing you asked for, or an invitation to a demo where we name your price, and after that emails with updates about WorkflowPros and our offers. If you gave us your email address to read the rest of our case study, we may email you case studies and product updates. If the page said that your email reserved an offer, such as a monthly bonus, we use your email address and the date you left it to apply that offer.
If you asked for a renewal reminder (possible until October 25, 2026), we email you that reminder before your notice deadline and may also send you updates about WorkflowPros and our offers. If you completed sign-up (possible until October 25, 2026), we may contact you by phone, text message and email about WorkflowPros and our offers. If you book a demo, send us a message or ask for a callback, we contact you about that request. If you entered your email address over “Book a demo” or as the first step of booking a demo, we may email you about booking your demo if you have not booked one, and send you updates about WorkflowPros and our offers.
If you ask for your price by text on our homepage, we text your price, how it is made up and a link to book a demo to the mobile phone number you entered, once a day at most. If you have not booked a demo by the next day, we text you one follow-up with your price and that link, and none after it. If you reply to these texts, our team answers you by text. We do not call you unless you book a demo or ask us to call. If you book one, we text you the meeting link and reminders before it. Message and data rates may apply.
You can stop these messages at any time. Use the unsubscribe link in any of our emails, reply STOP to any text message, or contact us at info@workflowpros.io or (866) 521-5523. We act on your request within 10 business days. Unsubscribing from updates does not stop messages about a request you have made.
We do not share your mobile number or your consent to receive text messages with third parties for their own marketing. These messages come from WorkflowPros, 2240 Ringwood Ave #150, San Jose, CA 95131, USA, and we send them through HighLevel / LeadConnector. HighLevel / LeadConnector also records for us when you open one of our emails and when you click a link in it; the link first passes through its servers and then opens our page.
How long we keep what you send
We keep what you send through our forms, including sign-ups, reminder requests, messages and other requests, for ten years from the date you sent it. After that we erase your name, phone number, email address and the other details sent with your request, including its IP address and visitor ID, and keep only an anonymized record of the date, which form you used, the campaign parameters of your visit, the first page of that visit, the domain that referred you, and whether we responded.
You can ask us to delete your data sooner at any time — see Questions and requests below. When we delete it, we also delete it from the services that hold it for us, such as HighLevel / LeadConnector, unless the law requires us to keep it. Advertising partners that received information through their own tags handle it under their own terms; see Who receives your information.
Cookies and your choices
Cookies and browser storage can remember your settings and link activity across visits. The default settings depend on your location.
European Economic Area, United Kingdom and Crown Dependencies (Guernsey, Jersey and the Isle of Man), Switzerland and Quebec. All optional categories are disabled by default and stay disabled until you allow them. The Accept all and Reject all buttons appear side by side and have the same size and color. Selecting Reject all or closing the banner with × records a rejection and leaves all optional categories disabled.
Everywhere else, including the United States and the rest of Canada. All optional categories, including Advertising, are enabled by default from your first page view. The cookie banner links to this section and closes by itself after a few seconds; on phones, it appears after you first scroll. Dismissing the notice or letting it close automatically saves those settings so it does not keep appearing. This is not treated as consent where prior consent is required.
When you turn off an optional category, we update Cloudflare Zaraz and the Google consent signals so new optional events for that category are no longer sent. We also delete cookies and browser data set by that category that this site can access. Turning off Advertising deletes the ad click identifiers and ad markers this site stored in your browser. Turning off Google Analytics also stops our own visit counts and removes the visitor ID described under Browser storage periods. It does not stop our record of arrivals from our ads or our record of the pages you open, which we keep whatever your preferences, as described under Protecting our ads from fraud and Our record of the pages you open: from then on, your visitor ID is no longer recorded in them, and no new steps reach the record of arrivals from our ads. Cloudflare Zaraz keeps the Google Analytics browser identifier in its own cookie on this site, which our scripts cannot delete; we stop using it when you turn Google Analytics off, and clearing this site’s cookies removes it. In the same way, when Advertising is enabled and you arrive through an ad from Microsoft Advertising, Cloudflare Zaraz keeps that ad’s click identifier in its own cookie on this site for up to three months, so that Microsoft can link a later request or sign-up to the ad; we stop using it when you turn Advertising off, and clearing this site’s cookies removes it. We cannot delete cookies set on a provider’s own domain or undo requests a provider has already received.
We use the approximate country and region code that Cloudflare attaches to the request. The site does not make a separate location lookup. We store the returned country and region code in this browser for up to 24 hours and use them to select the default settings. A VPN, a company network, or a geolocation error may cause us to identify the wrong location. If we cannot determine your country or a region needed to choose the defaults, such as your Canadian province, we use the stricter defaults described above.
Your saved preferences take priority over the regional defaults and continue to apply if you travel between regions. There are two exceptions:
- A recognized browser opt-out signal keeps Advertising disabled for as long as the signal is sent, regardless of your saved preferences. When the signal stops, we do not automatically restore an earlier Advertising preference.
- Settings saved only by closing the banner do not count as consent. Where consent is required, we ask you to choose again instead of applying those settings.
Your preferences are saved in this browser for up to 180 days. You need to set them separately in other browsers or on other devices. Clearing browser storage removes your saved preferences.
- Necessary
- These functions deliver and protect the website, prevent abuse, remember your privacy preferences, including telling our server whether you allowed Google Analytics, remove from this device the sign-up status saved there until October 15, 2026, and load our booking calendar when you open it, as described under When you book an appointment. They work even when all optional categories are disabled.
- Google Analytics
- Google Analytics measures visits and activity on our site. Campaign information helps us understand where inquiries come from. Google Analytics can use browser identifiers to link activity across visits. We do not use this category to build advertising audiences. When Advertising is disabled, we also tell Google not to use this information for advertising. This category also enables Cloudflare Zaraz monitoring reports. Zaraz then sets its own cookie to group your page views into visits, so we can see aggregated reports such as which pages people view before contacting us. We use these reports only to improve the website. It also lets this site measure page speed in your browser, as described in Website performance monitoring, and count your visits with a random visitor ID, as described in Browser storage periods. When you arrive from one of our ads, it also lets us use the steps described under Protecting our ads from fraud in our own reports on our ads.
- Advertising
We use tools from Google Ads, Meta (Facebook and Instagram), LinkedIn, X, Reddit, OpenAI (ads in ChatGPT), and Microsoft Advertising (ads on Bing) to measure ad performance and support advertising based on website activity.
When their tags run, these partners may receive information about page visits, devices, browser identifiers, and ad clicks, and the signals described above about how long a visit lasted and whether you came back. They may also receive hashed contact details from forms, as described above. Some partners can use this information to show you ads on their own services. You can keep Advertising disabled while Google Analytics is enabled.
Until we moved to our own booking calendar, when Advertising was enabled, our Calendly booking calendar also loaded in the background soon after a page loaded, and Calendly's page could run its own tags then. Our own calendar loads no other company’s page or tags.
Change your privacy preferences
Open here, or Cookie preferences in the website footer, to change which optional categories are enabled, then save your preferences. Turning off a category stops further use of its tools on this site. It does not remove information already sent to a provider or cancel a request you have submitted.
If you visit a provider’s website, that website has its own settings.
If your browser sends a Global Privacy Control (GPC) signal, we keep Advertising disabled. This signal does not change your Google Analytics preference. When the signal stops, we do not automatically restore an earlier Advertising preference.
Browser storage periods
We store your privacy preferences in this browser for up to 180 days. When Google Analytics is enabled, this site stores campaign parameters, the first page of your visit and the domain of the website that referred you in your browser for up to 30 days. When Google Analytics is enabled, the Cloudflare Zaraz monitoring cookie treats a visit as ended after 30 minutes without activity. A new visit with campaign parameters, or from another website, may replace the previously saved campaign information. When Advertising is enabled, this site also keeps in your browser the ad click identifiers and other ad markers from the address of the page you landed on, each for up to 90 days after the site last saw it. A new ad click is kept alongside earlier ones. When both Google Analytics and Advertising are enabled, this site also keeps in your browser when you first and last visited, how many visits of at least 15 seconds you have made, how long the current visit has been on screen, which of the visit signals described above this browser has already sent and whether a click on "Book a demo" in the current visit is waiting for its 30 seconds or has already been reported, so that each visit signal, and that click, is sent once per visit. This record is deleted 180 days after your last visit, or as soon as you turn off Google Analytics or Advertising.
Separately, the country and region code used to select privacy defaults is stored for up to 24 hours. Sign-up state and the sign-up details described above, saved until October 15, 2026, are removed from this browser the next time you open any of our pages (since October 25, 2026), or when you clear this site’s browser data. These records support website functions and are not controlled by the optional analytics and advertising settings.
We also count visits to this site ourselves. When we do, a cookie named wp_vid keeps a random visitor ID, the day it was made and how you first arrived: the kind of link that brought you (an ad, a search engine, social media, an AI assistant, an email, another website, a link tagged for a campaign, a page of this site, or none) and, when we recognize it, its service, such as Google or Facebook — never the address of that link or any identifier in it. Outside the regions with stricter defaults listed above, we count your visits unless you turn Google Analytics off; in those regions, only once you allow Google Analytics. The visitor ID lasts three years from the day it was made. Browsers keep a cookie for at most 400 days, so each page you view renews it for up to 400 days, never past those three years; after that your browser gets a new ID. With it we count visitors, the pages they view, the visit steps described above, the requests they send us and the demos booked, by visitor ID and the day it was made, page, approximate country, whether the device is a phone, tablet or computer, how the visitor first arrived, whether the visitor is new and, for a request, the form, where on the page it was and whether our spam check flagged it. This lets us see the visits of one browser together, for example how many visits and which pages came before a request. These counts hold no IP address, name, contact details or anything you enter, and they are kept for three months. We also record each time you arrive: the first page you view after 30 minutes away from our pages, or, within those minutes, a new way in from outside, such as another ad, a search or our email. For each arrival we record the visitor ID, the time, the page, approximate country, the kind of device, the kind of link and its service as above and, for an ad of ours, the number of its ad campaign and the tags of its link (its source, medium, campaign, ad group, keyword and ad number, never an email address or a phone number) — never the address of the link or any identifier in it. We keep these arrivals, and the requests and bookings we count under the same visitor ID, for three years, as long as the visitor ID itself, because a decision to switch software can take that long; this lets us see which ways in came before a request. A fourth cookie, wp_vs, notes for 30 minutes after each page you view how the current visit arrived, so that a reload or a move between our pages is not recorded as a new arrival. We also send the visitor ID with your requests to HighLevel / LeadConnector, as described under When you contact us, and keep it with them. A second cookie, wp_vn, only notes, for up to 400 days, that we have not counted your visit yet. We count a browser new to us, and a page loaded in advance, only once one of our pages has been shown and has checked in your browser that Google Analytics is allowed, unless the cookie wp_an below already tells our server that you allowed it: the page then sends our server an empty request, which your browser sends with this site’s cookies like any other, and once we count your visit the cookie is removed. A third cookie, wp_an, tells our server, which cannot read the preferences saved in your browser, what you chose for Google Analytics: that you turned it off or your permission for it ran out, or that you allowed it after it was off — in the regions with stricter defaults it is off until you allow it. It is set only after such a choice, keeps it for up to 180 days and is renewed whenever you save your preferences again. It is the only one of these cookies that this site’s scripts can read; when you turn Google Analytics off, the page also writes it itself. When you turn Google Analytics off, we stop counting your visits and remove wp_vid, wp_vn and wp_vs from your browser. We do not use these cookies to choose which ads you see, and we do not share the visitor ID with advertising partners. Clearing this site’s cookies removes them. The cookies wp_abs and wp_abn, which we used from October 5 to 8, 2026 to compare two versions of our pages, are removed the next time you visit, and so is a wp_ab cookie of that comparison.
From October 11 to October 15, 2026 we compared two versions of our homepage: one showed a calculator of what missed calls could cost, the other the 15-second missed-call test, which every visitor saw from then until October 16, 2026. When we compare versions of our homepage, which version you see is chosen at random when you first open our homepage, and a cookie named wp_ab keeps the name of the comparison and your version, so that you see the same one on every visit. It lasts 90 days and is renewed on each page you view while the comparison runs; when a comparison ends, it is removed the next time you open a page of this site. Only our server reads it; this site’s scripts cannot. We do not set it, and you see the first version, in the regions with stricter defaults listed above or once you have turned Google Analytics off, which also removes it; the one exception is a link we use to check our own site, which marks the cookie as a check and which we never count. When we count your visits, we count them with your version, as described above, and we send your version with your requests to HighLevel / LeadConnector and with the analytics events described above, so Google Analytics and the advertising partners that receive those events receive it too. We use it only to compare the two versions, not to choose which ads you see. Clearing this site’s cookies removes it.
We are now comparing two versions of our homepage again: one invites you to book a demo, the other offers your price by text, as described under When you contact us. The cookie wp_ab keeps the name of this comparison and your version, as described above. Whenever the questions of the second version cannot work, everyone sees the first version. Our website also counts each time it gives a browser its version, at that moment, so we can check that the two versions are given out evenly: the count records only the name of this comparison and the version, the homepage, the approximate country, whether the device is a phone, tablet or computer and whether the page was loaded ahead of being opened — no visitor ID and no IP address — and is kept for three months.
These periods apply only to the privacy preferences, campaign data, visit information, ad click identifiers, ad markers, visitor ID, how you first arrived, whether your visit is counted yet, the version of our homepage and the details kept for booking in one tap (30 minutes, see When you book an appointment) that this site stores in your browser. They do not determine when submitted messages, bookings, or providers’ records are deleted. How long we keep messages and requests you send is described in How long we keep what you send. Contact us for information about a specific request or to request deletion of your data.
Notice to United States residents
In the United States, optional categories are enabled by default, as described above. We currently use advertising services from Google, Meta, LinkedIn, X, Reddit, OpenAI, and Microsoft, listed in the Advertising partners section below.
Under California law, allowing advertising providers to receive information about your website activity, including the hashed contact details described above, may be considered “selling” personal information or “sharing” it for cross-context behavioral advertising. Other states define these terms differently, and some treat targeted advertising separately from a sale. You can opt out of this sharing.
Opt out of advertising data sharing
Use here, or Do Not Sell or Share My Personal Information in the website footer. One click disables Advertising immediately in this browser, without opening a review screen. We then stop sending website activity for advertising and tell Google not to use advertising identifiers or personalize ads for you, including in Google Analytics. Your Google Analytics setting stays the same. You can change it in Privacy settings or Cookie preferences.
You do not need to identify yourself to make this choice. We do not change the prices, services, or level of service we offer you because you opt out.
Your choice applies to this browser. You need to make a separate choice in other browsers or on other devices.
Browser signals
If your browser sends a recognized opt-out preference signal, such as Global Privacy Control, we keep Advertising disabled. We honor these signals in every region and do not automatically restore an earlier Advertising preference when the signal stops. We do not respond to the older Do Not Track header, which does not have a consistent meaning across browsers.
Other rights
Depending on your state—including California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, and Virginia—you may also have the right to ask what personal information we hold about you, receive a copy, have it corrected or deleted, and appeal a denied request.
Email info@workflowpros.io or call (866) 521-5523 and tell us which right you want to exercise. We respond within 45 days. If we need more time, we will let you know before that deadline. We may need to verify your identity. You can also use an authorized agent; we may ask the agent for proof of your permission and ask you to confirm your identity with us. Information you provide solely for verification is used only for that purpose.
If we deny your request, we explain why. You can appeal by replying to our response with the word “appeal”. We respond to appeals within 45 days. If we deny your appeal, we explain how to file a complaint with your state authority.
Who receives your information
We use service providers to support the website functions described above. Advertising partners receive website activity data only when Advertising is enabled. They may also use this data for their own purposes, including advertising on their own services. The links below explain how each provider handles data. They do not replace the privacy choices available on this website.
Service providers
- Cloudflare: website hosting, delivery, security and Turnstile anti-abuse checks; Cloudflare Zaraz for managing optional analytics and advertising tools; Cloudflare Web Analytics for website performance monitoring; and Workers Analytics Engine for storing the counts described above. Cloudflare privacy information.
- Google: optional Google Analytics. How Google uses information from partner sites.
- Google Meet: the meeting for a demo you book in our calendar, its invitation and its link. Google privacy information.
- Calendly: from October 16, 2026 until we moved to our own calendar, our booking calendar, the invitation and the meeting link for your demo. Calendly privacy information.
- HighLevel / LeadConnector: receiving and storing sign-ups, website inquiries, demo bookings and renewal reminder requests, keeping the appointments of our booking calendar, and sending our emails and text messages; until October 16, 2026, also our booking calendar's widget. HighLevel privacy information.
- Slack: notifying our team about new sign-ups, website requests and demo bookings. Slack privacy information.
Advertising partners
- Google: advertising through Google Ads. How Google uses information from partner sites.
- Meta: advertising on Facebook and Instagram. Meta privacy information.
- LinkedIn: advertising on LinkedIn. LinkedIn privacy information.
- X: advertising on X. X privacy information.
- Reddit: advertising on Reddit. Reddit privacy information.
- OpenAI: advertising in ChatGPT. OpenAI privacy information.
- Microsoft: advertising on Bing and other Microsoft services through Microsoft Advertising. Microsoft privacy information.
Questions and requests
Email info@workflowpros.io or call (866) 521-5523 to ask how we use information collected through this website, request access, correction, or deletion, unsubscribe, or raise a privacy concern. Include enough detail to help us identify the request you’re referring to. Please do not send passwords or payment card details.
WorkflowPros2240 Ringwood Ave #150
San Jose, CA 95131, USA
We and our service providers store and process information in the United States and other countries, where courts and government authorities may be able to access it under local law. If you are in Canada and are not satisfied with our response, you can contact the Office of the Privacy Commissioner of Canada.
We may update this privacy notice as our website services or practices change. The date at the top shows when it was last updated.