> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leadpipe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance and geography

> Frame geography, privacy, and downstream usage carefully and clearly

## What this guide is for

Customers often ask some version of the same question: where does Leadpipe work, and how should we think about compliance?

This guide gives practical product guidance, not legal advice.

## Geography

Describe geography in practical terms:

* explain where Leadpipe is strongest today
* confirm coverage before making country-specific promises
* treat expansion questions as both product and legal questions

## Privacy and data handling

Leadpipe identifies visitors and enriches those records with useful context.

Customers should use that data in workflows they understand and review their own legal obligations before scaling usage.

The demo flow describes Leadpipe as built on a consent-based partner network. Use that as the product framing, but customers should still review their own compliance requirements before deployment.

## How to keep usage safer and cleaner

* suppress traffic you should not operationalize
* narrow workflows to your real ICP
* start with one downstream use case before scaling
* involve internal legal or compliance stakeholders where needed

## Practical next steps

* Read [Suppress unwanted visitors](/guides/suppress-unwanted-visitors) to keep low-value or unwanted traffic out of your workflow.
* Read [Trial success guide](/guides/trial-success-guide) to validate fit before scaling usage.