What we collect, and who gets it.

The short version

• ✓This site uses Google Analytics and Google Ads. They set cookies in your browser and send Google information about your visit. The details, and how to turn them off, are in “Cookies and Google” below.
• ✓We also use Vercel Analytics and our own page count. Neither uses cookies, and neither is built to identify you.
• ✓When we email you, we can see whether it arrived and whether it was opened. We say so plainly below.
• ✓We do not sell, rent, or share what you type into our forms with anyone for their own marketing.
• ✓The personal information we ask for is what you type into the demo form or the chat: your name, your business, and a phone number and/or an email address. You can also tell us how you heard about us.

When you ask for a demo or a call

The form asks for your name, business name and a mobile number and/or an email address. Optionally you can tell us your trade, which plan interests you, your current website, how you heard about us, and a day and time that suits you for a call. That is everything you type.

The form also sends a few things you do not type: the page you sent it from, the page you first arrived on, and, if your link carried them, the campaign tags in the address (for example utm_source) and a Google ad click ID. If you change the figures in the savings calculator, we get those figures too. If your link pre-selected how you heard about us and you left it, we mark the answer as pre-filled.

It is used for one thing: so a person can contact you about the demo you asked for. It goes to our team's email, and into our own internal system so the request isn't lost. We do not add you to a marketing list you did not ask for, and we do not pass your number to anyone else.

The emails we send you, and what we can see

If you give us an email address, a person builds a demo home page for your business and emails it to you within 12 to 48 hours, and then whatever a person sends you afterwards. No automated sequence, no drip campaign.

Our email is delivered by Resend, and like every email provider it reports back on what happened to a message: whether it was delivered, whether it bounced, whether it was marked as spam, and whether it was opened. Opens are measured the way every email tool measures them — a small invisible image in the message — and it is tied to your record, because we sent that message to you by name.

We are telling you this because most companies bury it. It is used for one thing: so the person following up knows whether you have seen what he sent, instead of texting you about an email that never arrived. We do not build a profile from it, we do not sell it, and it does not feed any advertising.

Our marketing emails to businesses work the same way, and may also note which of our links in that email were clicked: the link carries a short tag naming the business we wrote to, so we can see that the shop looked at the demo we built for it. We record the business, the page, the time and the kind of mail app opened it. Our web pages carry the business tag in the address, so Google also receives which business we wrote to.

If you would rather we could not see that, most email apps have a setting to block remote images, which stops open tracking on our messages and everyone else's. Or reply and tell us to stop emailing you, and we will.

If you email us

Mail sent to bots@botsonstaff.com reaches a person, and we keep it — along with anything in it — so we can answer you and remember what was agreed. Please treat it as ordinary business email: it is not a secure channel for card numbers or passwords.

When you use the assistant on this site

The chat is powered by Anthropic's Claude. What you type is sent to Anthropic to generate a reply, and is subject to their handling of API data. The thread stays in your browser for the length of your visit so it makes sense as a conversation.

When you leave the page, if you typed anything to the assistant, a copy of the conversation is emailed to us and saved in our own system, so we can see what people need and where the assistant answered badly. It includes everything you typed, including a name, phone number or email if you gave them, and the page you were on. If you send your details through the chat, the conversation is kept with your request. If you would rather it was not sent, close the chat without typing anything, or use the phone number instead.

Please don't type anything into it you wouldn't put in an email to a stranger — no customer details, no card numbers, no passwords. It's a sales assistant, not a secure channel.

Cookies and Google

Every page on this site loads the Google tag, from Google LLC. We use it for two things. Google Analytics counts visits and shows us which pages and sources bring people here. Google Ads measurement tells Google when an ad click led to a visit or to a form. The Google Ads tag also reports the pages you open here to Google, even if you did not come from an ad. That is how Google Ads remarketing and view-through measurement work. We have not confirmed in our Google Ads account which of those are switched on. The tag loads after the page has finished loading, or when you first scroll, tap or press a key.

When the tag runs, your browser sends Google information about the visit: your IP address, the page you are on, the page you came from, your browser and device, and an identifier from the cookies below. What Google does with that is covered by Google’s own privacy policy.

These are the cookies we found on 16 October 2026, using a clean browser:

• •_ga and _ga_SGSRYHMG9P (Google Analytics, set on this site): recognize the same browser across visits. They last up to 400 days from your latest visit.
• •_gcl_au (Google Ads, set on this site): used to measure ads. It lasts 90 days.
• •_gcl_aw (Google Ads, set on this site): only if you arrive from a Google ad. It keeps the ad click ID and lasts 90 days. In that case Google also sets GCL_AW_P cookies on google.com, doubleclick.net and googleadservices.com, for 90 days.
• •test_cookie (set by Google on doubleclick.net): checks that your browser accepts cookies. It is short-lived: under a day when we measured.
• •_gcl_ls: Google also keeps this in your browser's local storage.

If you are signed in to Google, or have visited other sites with Google ads, your browser also sends Google’s own cookies on google.com and doubleclick.net with these requests, and Google may set others there.

The sample and preview websites we host (under /demo/, /sample/ and /preview/), and pages that show them in a frame, such as the home page and /website-examples, send their visits to the same Google Analytics property as the rest of this site. It loads as soon as the sample opens and uses the same cookie, _ga_SGSRYHMG9P, for up to 400 days. A few sample pages also load fonts from Google Fonts. Our emails can load a font from Google Fonts too.

When you send a form, the page tells Google Ads that a form was sent. On the free demo page it also tells Google Analytics where the visit came from: the source, medium and campaign in your link, and how you said you heard about us. Our code does not send your name, phone number or email to Google. The link to your personal demo page has your business name and first name in its address. The page removes the first name from the address the moment it opens, before the Google tag loads. The business name stays in the address and in the page title, so Google receives that.

How long Google keeps this data is set in our Google account and by Google. We have not confirmed that period, so we do not state one here. The cookie lifetimes above are what we measured.

To turn it off: block or delete cookies for this site in your browser settings. The site works without them. Blocking cookies does not stop the tag loading. To stop it sending anything to Google, use a tracker blocker in your browser. Google’s Analytics opt-out add-on covers Google Analytics only. You can change how Google uses ads data about you at adssettings.google.com. Or write to bots@botsonstaff.com and a person will help. There is no cookie banner on this site today.

Our other analytics

We use Vercel Web Analytics and Vercel Speed Insights. Both are cookieless and are designed not to collect or store personal data or identify individual visitors. They tell us which pages get read and how quickly the site loads.

We also keep our own count of how many times each page was opened. That is all it is: a page, a day, a count, the name of the website that linked here, and whether the visit came from an ad. There is no column anywhere for a person — no cookie, no IP address, no device fingerprint, nothing that could be traced back to you or joined up with anything else. This count is separate from the Google tag above.

Your browser tab also holds a few things for the length of your visit, and drops them when you close it: the chat thread, the page you first arrived on, the campaign tags in your link, and a Google ad click ID if you came from an ad. They are not cookies. If you send a form, the page you arrived on, the tags and the click ID are sent with it. If you close the tab without writing to us, they are gone.

The click ID is a code Google puts in the address. It says a click happened, not who you are. We keep it with your inquiry so we can tell Google that that particular ad led to a real conversation. It is how we know which ads are worth paying for.

We also use Google Search Console, which reports how our pages appear in search results. It reports on our pages, not on you.

Hosting and the technical bits

The site is hosted by Vercel, and email we send is delivered through Resend. Like any web host, Vercel processes the requests your browser makes in order to serve the page. Lead requests, chat transcripts, our page count and our email events are stored in a database hosted by Supabase. Some pages can show another website in a frame when you open it. That site loads from its own address, and its own privacy policy and cookies apply. We do not maintain our own logs of visitor IP addresses for marketing or profiling.

Your shop's data, if you become a customer

The paragraphs above are about this website. This one is about the thing shop owners actually ask us: can another shop see my numbers? No — and not because we promise it, because of how it is built.

• ✓Every shop's data is walled off from every other shop's, and the wall is enforced by the database itself on the tables that hold your work — not by application code that could forget.
• ✓The rule is refusal by default. A request that cannot prove which shop it belongs to gets nothing back — not an empty list by accident, nothing, by design.
• ✓We attack it on purpose. Before a release we run an automated suite that signs in as one shop and tries every route we know of to reach another shop's rows. It has to come back clean.
• ✓Your data is yours. We do not sell it, we do not train a public model on it, and we do not show one shop's numbers to another — including in anything we publish.

And the part most companies leave out: we do not have SOC 2, and we have not had a third-party penetration test. We are a small team, and we would rather you hear that from us than discover it in a questionnaire. The attack suite above is ours, it runs at release, and putting it on an automatic schedule is on the list — it is not done yet. If your insurer or a fleet customer needs something formal, tell us and we will say plainly what we can and cannot sign today.

Text messages and your mobile number

We send text messages in one situation, and only ever to somebody who asked for them: some demo forms on this site (on the trade pages and the hire page) have a box — unticked by default, and never required — to have us text you about it. Leave it clear and we will email you instead. The demo form on our home page has no such box, and we do not text you from it: we reach you by email, or by phone if you ask us to call. We do not text your customers, and the platform cannot do it today; if a shop's own messaging is enabled in future it will be separately registered, and that shop will be the sender, not us.

Mobile information and messaging consent are not shared with third parties or affiliates for marketing or promotional purposes. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent are not shared with any third party. We do not sell your mobile number, and we do not sell or rent your consent to anybody.

Your number is handled for us by the companies that run this service: Twilio and your mobile network deliver texts, Resend delivers our email, and our own system stores your request in a database hosted by Supabase. We do not give it to any of them for their own marketing.

Message and data rates may apply. How often we message you depends on which of the two above applies: if you asked us for a demo, message frequency varies and is typically one to four messages, and a repair customer typically gets between two and six messages over the life of their repair. Reply STOP to any message and they end — you get one confirmation and then nothing further. Reply HELP for help, or email us at the address at the bottom of this page.

Your choices

You can ask us what we hold about you, ask us to correct it, or ask us to delete it — write to bots@botsonstaff.com and a person will action it. If you asked for a demo and changed your mind, say so and we will delete the request.

If you live in California, you can ask us what we hold about you and ask us to delete it, using the email above. We do not sell what you type into our forms. The Google Ads tag lets Google use your visits for advertising, which California law may treat as “sharing”. To stop it, follow the steps to turn it off. This site does not change what it does when your browser sends a Do Not Track or Global Privacy Control signal.

Children

This site sells websites and website chat to businesses. It is not directed at children and we do not knowingly collect information from anyone under 18.

Changes

When what we collect changes, we update this page and the date at the top. The date is the last time it moved.

Contact

Bots On Staff — bots@botsonstaff.com. A real person reads it.

Bots On Staff is a trading name of Cut Above Web Media LLC, a Florida limited liability company. 7901 4th St N, Ste. 300, St. Petersburg, FL 33702 · bots@botsonstaff.com

Plain-English summary, not legal advice, and not a substitute for your own counsel's view of your obligations. See also our terms and our accessibility statement.