Account data
When you sign in with GitHub, VibeExchange stores your GitHub id, handle, display name, avatar, email when provided, session rows, profile preferences, staff status, and notification preferences.
VibeExchange stores the data needed to run accounts, pledges, governance, refunds, repo activity, and notifications. We keep profile visibility and email notification controls in your account settings.
Last updated June 12, 2026
When you sign in with GitHub, VibeExchange stores your GitHub id, handle, display name, avatar, email when provided, session rows, profile preferences, staff status, and notification preferences.
Listings, pledges, wallet ledger rows, refund requests, reviews, Q&A posts, follows, updates, votes, milestones, repo activity, and moderation actions are stored so the marketplace can operate and show an auditable build trail.
Payment checkout and webhook metadata is stored for reconciliation. Card details are handled by the payment provider; VibeExchange stores provider ids and payment state, not full card numbers.
In-app notifications are always stored in VibeExchange. If email delivery is configured and enabled in your settings, notification payloads may be sent to the configured email delivery provider.
VibeExchange uses session cookies for sign-in and OAuth state. Analytics may be collected through the configured site analytics provider when enabled.
You can edit your profile visibility, backed-listing visibility, and email notification preference from account settings. Staff can assist with account and data requests.
For account or data requests, use the contact channel listed on the VibeExchange site or contact the operator directly.