Privacy Policy

Sitehandle Ask your own question

Hi. Ask anything about Sitehandle.

Our AI chatbot can make mistakes.

Last updated: November 18, 2026

What changed on November 9, 2026: we added “The client portal” section below, for Sitehandle clients who use the portal. This notice stays here for at least 30 days.

This Privacy Policy explains what information Sitehandle (“we”, “us”) collects when you visit sitehandle.com, how we use it, who we share it with, and what rights you have over it. If anything here is unclear, email us at hello@sitehandle.com and we’ll answer plainly.

What we collect

Information you give us through the chatbot

The homepage is a live AI chat interface. When you send messages, we store the full conversation in our database so we can respond intelligently, improve the service, and follow up if you ask to be contacted. If you provide contact details (name, email, website URL, company) during the conversation, we save those as a lead record linked to your conversation. We do not require account creation; we identify conversations with an anonymous session ID stored in your browser.

What the chat saves: your name, email and website, what you need done, and any offer the chat showed you, if you share them. It also saves a random visitor ID that is stored in your browser, so we can tell that two chats came from the same person. These are kept with your lead record so our team can follow up.

Page activity: on our site we keep a log of what you do on the page, such as which sections you open, what you click and how far you scroll. It is tied to the same visitor ID and is kept for 180 days, then deleted.

Automatically collected technical information

When you visit the site, our analytics and monitoring tools automatically collect: IP address (truncated before storage), browser type and version, operating system, device type, referring page, pages visited, time spent on each page, and interaction events (clicks, scrolls, chat messages sent). Exact fields vary by tool; see the “Cookies and tracking” section for specifics.

How we use it

Chat content and lead information: to understand what visitors want, deliver accurate answers, and follow up on qualified leads. Technical information: to measure traffic, diagnose performance issues, improve the site’s usability, and detect abuse. We do not sell personal information.

Cookies and tracking

We use four tracking services, each with its own scope and opt-out path:

Google Analytics 4 (via Google Tag Manager)

We use Google Analytics 4 (operated by Google LLC) to understand which pages visitors view, how they found us, and which interactions lead to conversions. GA4 uses cookies (primarily _ga and _ga_*) to distinguish unique visitors and sessions. IP addresses are automatically truncated by Google before any processing. GA4 events we collect include standard pageview/session data and custom chatbot events (messages sent, intent classification, lead capture). You can opt out of Google Analytics on any site by installing the Google Analytics Opt-out Browser Add-on. Google’s full privacy practices are described at policies.google.com/privacy.

Google Tag Manager itself does not collect personal data — it is the deployment tool we use to load GA4 and other tags. Google’s Tag Manager terms are at marketingplatform.google.com/about/analytics/tag-manager/use-policy.

Microsoft Clarity

We use Microsoft Clarity (operated by Microsoft Corporation) to understand how visitors interact with our site through behavioral metrics, heatmaps, and session recordings. Clarity captures anonymized playback of visitor sessions, including mouse movements, clicks, scrolls, and page navigation. Clarity automatically masks form input fields and other sensitive elements, and we have not disabled this default masking. We use this data to identify usability issues and improve the visitor experience. We do not receive or store any personal data that you type into form fields or similar inputs — those are masked before Clarity processes them. Microsoft’s handling of Clarity data is governed by Microsoft’s Privacy Statement at microsoft.com/privacy/privacystatement. To learn more about Clarity’s practices or opt out, see clarity.microsoft.com/terms.

Meta Pixel (two pages only)

We use the Meta Pixel (operated by Meta Platforms, Inc.) on two pages only: sitehandle.com/homepage-upgrade/ and sitehandle.com/free-homepage-upgrade/. It does not run on any other page of this site. On those two pages it records that the page was viewed and whether you sent us a request. It uses cookies (mainly _fbp, and _fbc when you arrive from a Meta ad) so Meta can tell us which of our ads led to visits and requests. Meta may link this activity to your Facebook or Instagram account under its own privacy policy at facebook.com/privacy/policy. You can stop Meta from using this activity to choose the ads you see in your Meta ad settings at facebook.com/adpreferences/ad_settings, and you can block or clear these cookies in your browser at any time.

Chatbot functional storage

The chatbot uses your browser’s localStorage (not a cookie) to remember your conversation so you can continue it if you navigate away and come back. This data is stored only on your device, is cleared 7 days after your last visit, and can be cleared at any time through your browser’s site data controls. The chat also keeps its random visitor ID in localStorage; you can clear it the same way.

Who we share your data with

Chat message content is sent to OpenAI and Google to generate assistant responses. OpenAI’s handling of API data is described at openai.com/policies/privacy-policy and, under OpenAI’s business terms, API content is not used to train their models. Google’s handling of Gemini API data is described at ai.google.dev/gemini-api/terms.

Analytics data is processed by Google (GA4 / GTM) and Microsoft (Clarity) under their respective privacy terms linked above.

Ad measurement: if you send us a request after clicking one of our Meta ads, we may send Meta a hashed copy of your email address, Meta’s lead ID and the click ID from the ad link. Hashing turns your email into a code before it leaves our systems, so Meta can match it to its own records without us sending the email itself. We use this only to measure which ads led to results. We do not send Meta your phone number.

Calls and texts are processed by Twilio under its privacy terms at twilio.com/en-us/legal/privacy.

Hosting infrastructure: the site runs on Hostinger, which has access to server-level logs and database contents strictly for providing the hosting service.

Client portal data is handled by the companies listed in “The client portal” section below.

Apart from the companies named in this policy, including Meta for the ad measurement described above, we do not share, sell, or rent personal information to any third parties. We will disclose information only if legally compelled (valid subpoena, court order, or similar).

We also send dispute records to Stripe and your card issuer when you dispute a charge.

Phone calls and text messages

When you call or text a Sitehandle phone number, our phone provider, Twilio, handles the call or message. We see your phone number, the time of the call or text, what you wrote, and any voicemail you leave. We use this only to reply to you and do the work you ask for.

We do not share or sell mobile phone numbers or text message consent with third parties or affiliates for marketing or promotional purposes. You can reply STOP to any text from us to stop receiving texts, or HELP for help. Message and data rates may apply. Full details are in our Text Message Terms.

The client portal

This section covers portal.sitehandle.com, for Sitehandle clients and their staff.

What we collect in the portal

When you use the portal, we collect:

  • Names and email addresses
  • Sign-in records, including IP address and device
  • Approvals
  • Messages and files
  • Billing records
  • Each person’s role and last sign-in
  • The IP address and device stored with each approval

Before anyone signs in, we also keep a list of email addresses seen in our emails, Teams and Slack threads with your business, and where we saw each one. We use it for sign-in: company addresses sign in automatically, and Gmail-style and outside addresses wait for our approval.

How we use portal data

We use portal data to:

  • Run your account
  • Do and bill the work
  • Keep records of approvals and payments
  • Keep the portal secure
  • Send sign-in emails

Card and bank details

Stripe holds your card and bank details, not us. We never hold your full card or account number.

For a card, Stripe shows us the brand, the last 4 digits and the expiry date. For a bank account, it shows us the bank’s name and the last 4 digits. Stripe’s privacy policy is at stripe.com/privacy.

Who handles portal data

These companies handle portal data for us:

  • Stripe, for payments
  • Postmark, for sign-in emails
  • DigitalOcean, for portal hosting, with DigitalOcean Spaces for encrypted offsite backups
  • ReliableSite, for our dashboard server
  • Microsoft, for our team’s mailbox and Teams
  • Slack, for client conversations there
  • Twilio, for texts
  • WhatsApp (Meta), for messages sent there
  • Coda, for project and task records
  • Supabase software on our own server, for a fast copy of our records
  • GitHub, for project files
  • Zoho Vault, for stored logins
  • Browser Use, for automated browser work
  • Anthropic, OpenAI and Google, for the AI tools our team uses on client work
  • QuickBooks, for accounting
  • Teamlogger, for our team’s time records
  • n8n, for automation between these systems
  • Ruttl, for page feedback
  • Hostinger, for websites we host

If you dispute a charge, we send our records to Stripe and your card issuer. That means your agreement, approvals, notices and proof.

We do not sell portal data.

Cookies in the portal

The portal uses essential cookies only. They keep you signed in, keep forms safe and help Stripe prevent fraud. The portal has no third-party analytics, ad trackers or chat widget. So there is no cookie banner.

How long we keep portal data

We delete portal data 12 months after a client leaves. “A client leaves” means their plans have ended and no work is open. We keep billing and consent records longer, as tax law and card network rules require.

The deletion covers the portal and our client records. Billing and consent records are kept as described above.

We keep billing and consent records for 7 years.

Security and breach notice

We limit who can access portal data. Data is encrypted between your browser and the portal. Each client company sees only its own data. We tell you if a breach affects your data, as the law requires.

Your portal data requests

To ask for your portal data or ask us to delete it, email hello@sitehandle.com with the subject line “Privacy request”. We can’t delete billing and consent records early if we must keep them. Your rights under “Your rights” below work the same way for portal data, except for records we must keep.

How long we keep your data

The chat’s server logs, including the page activity log, are kept for 180 days and then deleted. Lead records (your contact details and what you asked for) are kept until you ask us to delete them. Google Analytics data is retained for 14 months (the minimum GA4 setting) and then automatically purged by Google. Clarity session recordings are retained for up to 30 days by default per Microsoft’s policy. Server access logs are rotated weekly.

Client portal data follows the rules in “The client portal” section above.

Your rights

Regardless of where you live, you can request that we:

  • Send you a copy of the personal data we hold about you
  • Correct any inaccurate personal data we hold
  • Delete your personal data from our systems
  • Stop processing your personal data for any specific purpose

To make any of these requests, email hello@sitehandle.com with the subject line “Privacy request” and include enough detail that we can identify your data (for example, the email address you used during a chat). We’ll respond within 30 days.

California residents (CCPA/CPRA): you additionally have the right to know what categories of personal information we collect, the right to opt out of any “sale” or “sharing” of personal information (we do not sell or share personal information as those terms are defined under the CCPA), and the right to non-discrimination for exercising these rights.

EU/UK/EEA residents (GDPR/UK GDPR): you additionally have the right to data portability, the right to lodge a complaint with your local data protection authority, and the right to withdraw consent where processing is based on consent.

Children’s privacy

Sitehandle is not directed at children under 13. We do not knowingly collect personal information from anyone under 13. If you believe a child has provided personal information to us, email us and we will delete it.

Changes to this policy

We will update this policy if we add new tracking tools, change data retention, or otherwise materially change how we handle information. The “Last updated” date at the top reflects the most recent change. Substantial changes will be announced at the top of this page for at least 30 days.

Contact

MSH Studios, Inc., doing business as Sitehandle
Email: hello@sitehandle.com
Website: sitehandle.com