Privacy Policy

Mercureon stores account records mapped from Clerk, including email address, display name, avatar URL, internal user ID, account status, and timestamps.

The platform stores researcher applications, researcher profiles, campaign records, membership tiers, posts, updates, comments, reports, notifications, media metadata, payment records, ledger entries, and audit logs needed to operate the service.

Mercureon stores Stripe identifiers and payment state for reconciliation and support. Full card details are handled by Stripe and are not stored by Mercureon.

Data is used to authenticate users, enforce access controls, review researchers and campaigns, process payments, deliver notifications, moderate comments, provide support, maintain audit history, and operate platform security.

Researcher profile, campaign, public post, public update, and public comment content may be visible to visitors. Gated content is shown only according to membership or pledge eligibility rules.

Mercureon relies on service providers including Clerk for authentication, Stripe for payments and payouts, Supabase Postgres for database hosting, UploadThing for media uploads, Inngest for background jobs, Resend for email delivery, Sentry for error monitoring, and Vercel for hosting.

These providers may process data as needed to deliver their services. Mercureon should keep provider configuration limited to what is necessary for the MVP.

Mercureon may retain records needed for payment reconciliation, legal obligations, moderation, abuse prevention, audit history, security, and dispute handling.

Access to operational data should remain limited to authorized platform administrators and server-side application code. Direct client-side database access is not part of the current architecture.

This privacy policy is a product-aligned draft for the current MVP. It should receive professional privacy and legal review before Mercureon expands beyond limited staging or controlled demos.