How beta email data is handled.

For buyers, we collect the email address submitted to save a guide preview or purchase a guide. For purchases, payment details are handled by Stripe; Pinned stores purchase status, guide access records, and related metadata.

When a guide opens, Pinned uses a random browser-session cookie to count one view per guide and session. The database stores a one-way, guide-specific hash rather than the cookie value. This guide-view metric does not store an IP address, device fingerprint, buyer email, or access link.

For creators, we collect account details, profile information, social links, payout contact information, guide content, and the places submitted in their guides.

We use buyer emails to send guide access, receipts, support messages, and free-list saves. When the visible disclosure says the email is shared with the creator, the creator may receive or export that email with consent context.

We do not sell buyer or creator email lists. If Pinned later sends marketing email directly, unsubscribe controls and suppression handling must be in place before that feature launches.

Pinned may use providers such as Supabase for database hosting, Vercel for hosting, Stripe for payments, and Resend or another email provider for transactional email.

These providers process information only as needed to operate the beta product.

Data is transmitted over HTTPS and stored with access-controlled providers. Payment card details are collected and processed directly by Stripe and never touch Pinned's servers.

Email hello@pinnedby.com for access issues, deletion requests, or privacy questions.