Privacy Policy
Last updated: August 27, 2026
This policy explains what this site collects, why, who else sees it, and what you can ask us to do about it. It's written in plain language because that's how we'd want it explained to us—but it's meant to be complete, not just friendly. If something here is unclear, ask and we'll answer directly.
Who we are
With Regard, LLC is a founder-led digital consulting practice run by Bill Barker, based in the Kansas City area and working with clients across the United States. We decide what information this site collects and why, which makes us the business responsible for it.
Reach us any time at bill@withregardco.com.
The short version
- The contact form sends what you write to our inbox. We don't keep a copy here unless it fails to send.
- Analytics cookies are off until you turn them on, and you can change your mind below.
- We don't sell your information, and we don't share it for advertising.
- If you want your information deleted, email us and we'll do it.
What we collect, and why
When you use the contact form
We receive what you send us: your name, your email address, your business or organization if you provide one, any service interests you check, and your message. We also record which page on this site you came from, so we know what prompted your inquiry. If you arrived from a tagged campaign link—like an ad or a newsletter—we record which one, for the same reason. That describes the link you clicked, not you.
We use it to reply to you and, if we end up working together, to carry out that conversation. Sending the form does not add you to a mailing list—you'll get one automatic note confirming we received your message, and after that you'll only hear from a person. Two services touch this data on the way: Cloudflare Turnstile checks that you're not a bot, and Resend delivers the message as email. You can read Cloudflare's privacy policy and Resend's privacy policy for what they do on their end.
To stop the form being used to send the same pitch over and over, we count recent submissions against a one-way hash of your network address—we don't store the address itself, and the count deletes itself within the hour. We also label obvious sales solicitations so they can be filed separately. Nothing is blocked or discarded on the strength of that label: every message still reaches us, and a real one still gets a reply.
When you use the free tools
The Google Business Profile checklist, the Proposal Red-Flag Checker, and the Missed-Lead Calculator all work entirely on what you type in. Those answers never leave your browser—there's no server behind any of them, nothing is stored, and we never see your results unless you choose to tell us about them. That includes the figures you enter in the calculator, which we would have no way of seeing even if we wanted to.
The three tools that take a web address work differently, and it's worth knowing how. The AI Answer Visibility Check, the Tracking Health Check, and the website speed test send the address you enter to our server, which then goes and looks.
- The visibility check requests three public files from the address you
gave us—the homepage,
robots.txt, andllms.txt—the same way any visitor or search crawler would. The site you check may see the request in its own logs; we identify ourselves plainly so it's obvious who it was. - The tracking check requests the homepage at the address you gave us and the script files that page loads from your own domain, again the same way any visitor would, and reads them for analytics and advertising tags. Nothing is sent to any third party, and the site you check may see the requests in its own logs—we identify ourselves plainly there too.
- The speed test passes the address to Google's PageSpeed Insights API, so Google receives the URL. Since the request now comes from our server rather than your browser, Google no longer sees your IP address. Google's privacy policy covers their side.
In both cases nothing is sent until you press the button, and the address and result are held for up to 30 minutes so a repeat check doesn't re-run the same test. Nothing ties a checked address to you, and we don't use those addresses to contact anyone.
When you just read the site
Hosting. Cloudflare serves this site and keeps standard server logs—IP addresses and request times—as part of operating and securing the network.
Visit counts. We use Cloudflare Web Analytics to see how many people visit and which pages they read. It sets no cookies and creates no identifier that follows you, which is why it runs without asking. Being straight about it: it isn't nothing—it loads a small script and your IP is processed to work out which country you're in—but it cannot recognize you, here or anywhere else.
Analytics, only if you say yes. If you allow it, Google Analytics loads and stores a cookie holding a randomly generated number, so a second visit can be recognized as a return rather than a new person. Google also receives your IP address, browser and device details, and which page you're on. Until you say yes, no Google code runs on this site at all—it is not loaded and held back; it is not loaded. Code is the precise word, and it's exact: the map picture on our city pages is an image loaded from Google, which is a request to them but not a script running on you. That one is described under Maps, just below. Google's privacy policy covers their side.
Maps. Our city pages show a picture of the city. It's a picture and nothing more—there's no interactive map to load, so nothing on these pages will ever set a Google cookie or run Google's code. What it does do: the picture comes from Google, so when it scrolls into view Google receives your IP address and which page you're on. Nothing is stored in your browser and nothing about that request can recognize you later. This happens whether or not you allowed analytics—it isn't tracking, but it is a request to Google, and you should be able to know that without asking. Google's privacy policy covers their side.
Booking. The Contact page can show a Calendly scheduler, but only after you press "Show booking calendar." Until then nothing is requested from Calendly. If you do open it and book a time, you're giving your details to Calendly as well as to us—your name, email address, and anything you type into their form—and they set their own cookies to run the scheduler. Calendly is a US company, so that information is handled in the United States. There's always a plain link to the same page as an alternative, and you never have to use it: email works just as well. Calendly's privacy notice covers their side.
Fonts. The typefaces are served from our own site. Loading a page here doesn't tell Google, or anyone else, that you did.
Cookies on this site
| Cookie | Set by | What it's for | How long | Needs your OK? |
|---|---|---|---|---|
_ga, _ga_* | Google Analytics | Tells returning visits apart from new ones so visit counts mean something. | Up to 2 years | Yes |
wr-consent-v1 | This site | Remembers the choice you made below, so we don't ask again every time. Stored in your browser; it never leaves your device. | Until you clear your browser storage | No—strictly necessary |
wr-attribution-v1 | This site | Only if you arrived from a tagged campaign link. Remembers which one, so we can tell what brought you here if you get in touch. Never leaves your browser unless you submit the form. | Until you close the tab | No—strictly necessary |
cf_clearance and similar | Cloudflare Turnstile | Only on the contact form. Tells a person from a bot so the form isn't buried in spam. | Session to 1 year | No—strictly necessary |
Calendly's own cookies | Calendly | Only if you press "Show booking calendar" on the Contact page. Runs the scheduler and remembers where you are in booking a time. | Session to 1 year | No—strictly necessary |
Your cookie choice
Loading your current setting… You can change it whenever you like—nothing on this site works differently either way.
If your browser sends a Global Privacy Control signal, we treat that as a no and never ask. We honor it automatically.
What we don't do
- We don't sell your personal information, and never have.
- We don't share it for cross-context behavioral advertising—the practice where what you read here follows you somewhere else as an ad.
- No advertising or retargeting pixels, and no ad networks.
- No mailing list signup hidden inside the contact form.
- We don't profile you, score you, or make automated decisions about you.
Who else sees your information
Only the services named above, each doing one specific job: Cloudflare (hosting, spam checks, visit counts), Resend (delivering form messages as email), Google Analytics (only with your permission), Google PageSpeed Insights (only if you run the speed test), and Calendly (only if you open the booking calendar and schedule a time). We don't hand your information to anyone else. If a law or a court required us to, we'd comply—and we'd tell you unless we were legally forbidden from doing so.
How long we keep it
- Inquiries and correspondence. As long as they're useful for replying, maintaining a working relationship, meeting legal obligations, or keeping ordinary business records. Ask us to delete yours and we will.
- Messages that failed to send. If the contact form can't deliver your message by email, we keep it for 30 days so we can still read and answer it. After that it deletes itself. Ask us to remove yours sooner and we will.
- A count of recent form submissions. Held against a one-way hash of your network address so the contact form can't be used to send the same message repeatedly. The address itself is never stored, and the count expires within the hour.
- Website addresses you check with the free tools. When you run one of the tools on our tools page, the address you enter and the result are held for up to 30 minutes so that checking the same site again doesn't re-run the same test. Nothing identifies you, and we don't use those addresses to contact anyone. To stop one visitor from exhausting the shared quota, we also count recent checks against a one-way hash of the network address—we don't store the address itself, and the count expires within minutes.
- Analytics. Held by Google, not by us, and not tied to your name or email. We've set the shortest retention Google offers for event data: two months. Anything Google keeps at the user level expires after fourteen months of inactivity, and returning to the site restarts that clock.
- Server logs. Kept by Cloudflare on their schedule as part of running and securing the network.
- Booked meetings. Held by Calendly and in our calendar for as long as the meeting record is useful. Ask us to remove yours and we will.
- Cookies. In your browser until they expire or you clear them—see the table above.
Your rights
Depending on where you live, you may have some or all of these rights. We extend them to everyone who asks, rather than checking your address first.
- Know and access. Ask what we hold about you and get a copy.
- Delete. Ask us to erase it.
- Correct. Ask us to fix anything inaccurate.
- Opt out. Turn off analytics cookies, here or in your browser.
- No retaliation. Exercising any of these changes nothing about how we treat you or what we'd charge you.
How to ask. Email bill@withregardco.com and say what you want. We'll respond within 45 days, and tell you if we need longer.
How we'll check it's you. Usually by replying to the email address you contacted us from. If the request covers something sensitive, we may ask for one more detail that matches what we already hold. We won't ask for ID documents, and we won't use anything you send for verification for any other purpose.
Someone acting for you. An authorized agent can make a request on your behalf. We'll need written proof you authorized them, and we may confirm directly with you.
If we say no. We'll explain why in writing. You can appeal by replying to that email with the word "appeal"—a real person reads it again and answers within 45 days. If you're still unsatisfied, you can raise it with your state attorney general.
Children
This site is for people running businesses. It isn't directed at children, and we don't knowingly collect information from anyone under 16. If you believe a child has sent us something, email us and we'll delete it.
How we protect it
The site is served over HTTPS. Form submissions are transmitted encrypted, checked for spam, and delivered straight to an inbox rather than stored in a database on this site. The one exception: if that email fails to send, we hold onto the message so it isn't lost, and it deletes itself after 30 days. Access to that inbox is protected by multi-factor authentication. No system is perfectly secure, and we'd rather say that than imply otherwise.
Where your information goes
We're based in the United States and our service providers process data there. If you're writing from elsewhere, your information will be handled in the US, where privacy laws differ from your own.
Changes
If this policy changes, we'll update this page and the date at the top. If the change affects what we collect or who receives it, we'll ask for your cookie choice again rather than assuming the old answer still applies. What won't change is the spirit of it: collect the minimum, use it only for what you gave it to us for, and be straight with you about both.