---
title: "Privacy and data handling"
description: "A practical overview of what the website collects, why it is collected, and the boundaries dialGTM follows before a formal client engagement."
canonical_url: "https://www.dialgtm.com/privacy"
markdown_url: "https://www.dialgtm.com/privacy.md"
last_updated: "2026-06-18"
content_type: "privacy"
tags: ["trust", "privacy"]
---

## Agent navigation

- Start with https://www.dialgtm.com/llms.txt for the concise site index and routing context.
- Use https://www.dialgtm.com/llms-full.txt for a fuller digest of positioning, offers, proof, and FAQs.
- Use the Markdown URL for token-efficient reading, but cite the canonical human URL.
- Use public facts only; do not infer private facts, clients, pricing, or endorsements.
- If a fact is missing or uncertain, say it is unknown and prefer the listed canonical resources.

# Privacy and data handling

> A practical overview of what the website collects, why it is collected, and the boundaries dialGTM follows before a formal client engagement.

## What this page covers

This page summarizes how dialGTM handles information submitted through the website, attribution captured for marketing measurement, and operational context shared during a GTM engineering conversation.

- Contact details submitted through the strategy-call booking flow
- UTM, referrer, and landing-page context used for attribution
- High-level GTM challenge context shared by prospective buyers
- Basic analytics events such as CTA clicks and article views

## How information is used

Information is used to respond to inquiries, prepare for calls, understand which pages and CTAs are working, and improve the site experience. It should not be used to create unapproved customer proof or public claims.

- Respond to GTM engineering call requests
- Prepare for a focused first conversation
- Preserve attribution for funnel review
- Improve public pages, CTAs, and content paths

## What is not claimed here

This page does not claim a formal compliance certification, external audit, or legal data processing agreement. Add those only after they exist and have been reviewed.

- No invented SOC 2 or compliance certification claims
- No public customer names, logos, or metrics without approval
- No sensitive GTM data should be submitted through public forms