Privacy Policy
How Markit handles Discord identity, community membership, and listing data.
Pilot version · Effective July 29, 2026
Data we use
Markit uses your Discord identity, servers you can manage, approximate server member count supplied by Discord, selected community, current guild membership and eligible roles, listings you submit, moderation records, and limited operational logs. Pilot access requests do not collect a written application or requester email address.
Why we use it
This data reviews pilot access, provides role-gated marketplace access, publishes and synchronizes listings, prevents abuse, supports moderation, and keeps the service reliable.
What we do not collect
Markit does not read Discord message history, presence, private messages, or full server member lists. Exact addresses should never be placed in listings.
Service providers
Vercel processes application traffic, Supabase Postgres stores structured marketplace data, Cloudflare routes tenant domains and provides Turnstile, Discord provides identity and community integration, Resend delivers access alerts, and Sentry receives redacted error and performance events. Markit does not use object storage for listing media.
Retention and control
Rejected pilot access requests are removed after 90 days and approved access audit records after one year. Expired sessions, handoff tickets, idempotency records, and delivery state are routinely cleaned up. Text listings and marketplace audit records remain available to the community while needed for marketplace operation, moderation, safety, and legal obligations. Disconnecting removes the stored Discord OAuth grant and current community membership record.