Hidehouse Craft just became Founder #053
Crafters Market
New · Light / Dark
Cart
Trust Center/Vendors
Transparency

Who sees your data, and why.

Every third-party service that touches Crafters Market data is listed here — what it does, what data it receives, and why we send it. This page reads from the same source as Privacy Policy §4a, so the two can never drift.

Version 1.0 · Last updated 2026-06-30 · 13 vendors · Read the full Privacy Policy

Stripe

Payments, Stripe Connect, subscriptions

Payments
Data received
Buyer billing information (card metadata, address), Maker identity and banking information for KYC, transaction metadata, dispute and chargeback data.
Why we send it
Process Buyer payments, Maker payouts, Crafters Plus subscription billing, and dispute/chargeback workflows.
Governing terms
Stripe Privacy Policy · Stripe Connected Account Agreement · Stripe Services Agreement
View vendor privacy policy

Cloudflare

CDN, DDoS protection, edge security

Hosting / CDN
Data received
IP addresses, request metadata, and (where TLS is terminated at the edge) request contents in transit.
Why we send it
Performance, abuse mitigation, DDoS protection. Not used for advertising.
Governing terms
Cloudflare Privacy Policy
View vendor privacy policy

Google Analytics 4 (GA4)

Product analytics

Analytics
Data received
Pseudonymous identifiers, page-view events, coarse geolocation. Configured with IP anonymization where supported.
Why we send it
Measure site usage, funnels, and retention.
Governing terms
Google Analytics Terms of Service · Google Privacy Policy
View vendor privacy policy

Google Ads

Advertising, conversion tracking

Advertising
Data received
Hashed identifiers and conversion metadata. No plaintext personal information is transmitted.
Why we send it
Run off-site ad campaigns; import conversion events for attribution.
Governing terms
Google Ads Terms · Google Privacy Policy
View vendor privacy policy

Google Search Console

SEO / indexing telemetry

Analytics
Data received
Aggregated query and click data. Does not receive user personal information.
Why we send it
Monitor organic-search performance and site health.
Governing terms
Google Privacy Policy
View vendor privacy policy

Meta Ads & Conversions API

Advertising on Facebook / Instagram

Advertising
Data received
Hashed identifiers and conversion metadata.
Why we send it
Run off-site ad campaigns on Meta surfaces; import conversion events.
Governing terms
Meta Privacy Policy · Meta Business Tools Terms
View vendor privacy policy

Pinterest

Advertising and catalog feed (if enabled)

Advertising
Data received
Catalog metadata for Maker Listings and hashed identifiers for conversion attribution.
Why we send it
Product catalog syndication and ads attribution.
Governing terms
Pinterest Privacy Policy · Pinterest Business Terms
View vendor privacy policy

TikTok

Pixel and Events API (if enabled)

Advertising
Data received
Hashed identifiers and conversion events.
Why we send it
Ads attribution on TikTok surfaces.
Governing terms
TikTok Privacy Policy · TikTok Commercial Terms
View vendor privacy policy

Sentry

Error monitoring (if enabled)

Monitoring
Data received
Client and server error stack traces, request metadata, pseudonymous user identifiers.
Why we send it
Find and fix bugs.
Governing terms
Sentry Privacy Policy
View vendor privacy policy

Mailgun

Transactional email delivery

Email
Data received
Recipient email addresses and message content.
Why we send it
Deliver Order confirmations, security notices, dispute updates, payout notifications.
Governing terms
Mailgun Privacy Policy
View vendor privacy policy

Shippo

Shipping-label purchase and rate lookup

Shipping
Data received
Shipping address, package dimensions, payment metadata (when Maker uses on-Platform label purchase).
Why we send it
Purchase and track shipping labels.
Governing terms
Shippo Privacy Policy
View vendor privacy policy

AI Service Providers (OpenAI, Anthropic, Google Gemini)

Operational AI (search, listing optimization, translation, moderation, ad copy)

AI
Data received
Prompts and content necessary to perform the specific task. Not sent for AI Model Training under the Creator-Owned AI Policy.
Why we send it
Power search relevance, listing optimization, translations, on-platform moderation, and ad-copy generation.
Governing terms
Provider-specific: OpenAI Privacy Policy · Anthropic Privacy Policy · Google AI / Cloud Terms
View vendor privacy policy

Emergent Universal Key

LLM aggregator / key management

AI
Data received
Server-side only — routes AI requests to the underlying provider without exposing plaintext keys to the Platform runtime.
Why we send it
Aggregate LLM access across providers under a single managed key.
Governing terms
Emergent Terms of Service
View vendor privacy policy

Each vendor listed above has its own privacy policy that governs its own processing. When we add, remove, or replace a vendor in a way that materially changes what information is shared, we update this list and, where required by law, notify affected users. See Privacy Policy §4a for the authoritative legal text.