Skip to content

Privacy Policy

Last updated: September 28, 2026

Monster MSP LLC, doing business as Monster MSP, uses this website to describe its services, receive inquiries, and provide access to certain third-party tools and portals. This Privacy Policy explains what information we collect through the website, how we use it, and the third-party services involved in operating the site.

Information We Collect

We may collect information you choose to provide directly, including when you:

  • submit a contact form
  • send us an email
  • request information about services, assessments, or promotions

Depending on what you submit, this may include your name, business name, email address, phone number, message contents, and basic marketing attribution details such as the page you were on or UTM parameters included in the URL.

We may also collect limited technical and security-related information associated with website use, including IP address, browser user agent, device and browser characteristics, and anti-spam verification data.

How We Use Information

We use website information to:

  • respond to inquiries and service requests
  • evaluate potential client or partner opportunities
  • route messages to the appropriate internal team members
  • protect the site against spam, fraud, abuse, and unauthorized access
  • understand which pages or campaigns are generating inquiries
  • support normal website operations and performance

We do not sell personal information collected through this website.

Third-Party Services Used On This Site

This website relies on third-party service providers to host the site, store submitted data, deliver notifications, and operate certain embedded tools.

These providers may include:

  • Cloudflare, for site hosting, edge delivery, performance, security services, and Turnstile spam protection
  • Supabase, for application data storage, authentication, and related database operations
  • Microsoft, for contact notification delivery through Microsoft Graph
  • Google, for tag management and analytics tools when enabled
  • OpenAI, for ChatGPT Ads measurement when configured and enabled

If you interact with third-party widgets, billing portals, helpdesk portals, or linked external services, your information may also be subject to those third parties' own privacy terms and practices.

Cookies, Local Storage, and Similar Technologies

This site uses a simple cookie-preferences model with two categories: essential and non-essential.

Essential cookies and similar technologies are used for core site operation, security, consent storage, protected admin authentication, short-lived OAuth security flows, and anti-spam protections.

Non-essential cookies and similar technologies may be used by optional third-party tools such as Google Tag Manager, Google Analytics, and OpenAI's ChatGPT Ads Measurement Pixel. These tools are enabled by default for new visitors. You can turn off non-essential tools through Cookie Preferences; essential cookies remain on. The OpenAI Pixel may store an ad click reference in a first-party cookie and receive page-view, form-start, and lead-submission events. A lead-submission event is sent only after a contact or assessment form is successfully saved. When available, approximate country, city, region, and postal code derived from the visitor's IP address may be sent to OpenAI for ad measurement; city and postal-code estimates can be unavailable or imprecise. The Pixel integration does not directly include form fields in those events. The OpenAI data source currently has automatic advanced matching enabled: when enabled, OpenAI's Pixel may detect supported contact information on the page, normalize it, hash it in the browser, and include the resulting hashes with measurement events. Raw contact values are not sent by automatic advanced matching. This feature can be controlled in Ads Manager and should be used only where permitted and after appropriate notice and consent.

You can accept all cookies, accept essential cookies only, or reopen Cookie Preferences later from the site footer.

Contact Forms and Lead Handling

When you submit a message through our contact form, we may store the submission details, metadata related to the request, and limited technical context needed to review, triage, and respond to the inquiry. Messages may also generate internal notification emails so our team can follow up.

Request metadata can include the guide that led to the form, the service you selected, a saved reference, and internal notification status. We also use a request identifier to recognize retries and avoid duplicate inquiries, and a protected address-derived identifier to limit repeated requests. These operational records are separate from optional advertising measurement.

Analytics Tools

Monster MSP may use Google tag management and analytics tools to understand site usage, measure campaign performance, and improve marketing effectiveness. The OpenAI Ads Measurement Pixel records public-page views, lead-form starts, and successful lead submissions for campaign measurement. When configured, a server-side conversion event may accompany a successful submission for delivery reliability; it uses the same event identifier for deduplication and does not include raw form contact fields. These tools are treated as non-essential and stop measuring when you turn off non-essential cookies in Cookie Preferences.

Data Retention

We retain inquiry and website-submitted information for as long as reasonably necessary for business communication, recordkeeping, security, legal compliance, and operational needs.

Your Choices

If you want to request correction or deletion of information you submitted through this website, contact us at sales@monstermsp.com. We will review requests in light of applicable legal, security, and operational obligations.

You can also manage optional cookie and tracking preferences through the Cookie Preferences control available on the website.

Changes To This Policy

We may update this Privacy Policy from time to time as the site, its integrations, or business practices change. The updated version becomes effective when posted on this page.