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

# Privacy and data sources

> How StoreInspect collects, filters, and exposes API data.

StoreInspect builds a database of Shopify store and contact intelligence from public web data, storefront analysis, and enrichment workflows.

The API is designed to expose useful prospecting data while keeping sensitive contact channels behind reveal credits and filtering low-quality data before export.

## Store data

StoreInspect store records can include:

* Domain, store name, country, category, and public store metadata.
* Shopify technology signals such as apps, pixels, themes, Shopify Plus status, product counts, and Meta ads indicators.
* Estimated traffic and revenue tiers.
* Public social and storefront signals when available.

V1 API enrichment is database-only. StoreInspect does not live-scan a new or uncached domain during an API request.

## Contact data

Contact search returns previews so you can decide whether a reveal is worth spending a credit.

Preview responses do not include:

* Email addresses
* Phone numbers
* LinkedIn URLs
* Full last names
* Raw source URLs

Contact reveal responses can include contact channels after credits are spent or if the contact was already revealed for your account.

## Hygiene and filtering

StoreInspect filters contact channels before exposing them through the API.

Revealed emails are limited to exportable contact data. Bounced, catch-all, guessed, suppressed, or otherwise non-exportable emails are not returned by API reveal responses.

Contact channels may be unavailable when StoreInspect does not have enough confidence that the channel is usable or appropriate to expose.

## Request logging

StoreInspect logs API activity for support, security, quota enforcement, and abuse prevention.

Request logs are designed to be privacy-safe:

* Raw API keys are not logged.
* Revealed email addresses, phone numbers, and LinkedIn URLs are not stored in request logs.
* Request IDs are included in responses so support can investigate issues without weakening logging rules.
* IP address and user-agent values are hashed rather than stored as raw values.

## Customer responsibilities

You are responsible for how you store and use data returned by the API.

Use revealed contact data only for legitimate business purposes, follow applicable privacy and outreach laws, honor opt-outs and suppression requests, and avoid redistributing or reselling StoreInspect data unless your contract explicitly allows it.