Privacy

Depending on how you use Modfolio, we may process:

• Account identity — Discord user id, username / global name, avatar URL, email (when Discord provides it), and Modfolio user/profile ids
• Profile content — handle, display name, bio, pronouns, locale/timezone, skills, availability, open-to-work preferences, avatar/banner media you upload
• Experience and trust data — claimed or verified moderation roles, tenure, community associations, references, endorsements, application answers, and verification status
• Community / team data — claimed servers, team membership, invites, role mappings, listing content, and Discord guild metadata needed to operate claims and the bot
• Support — tickets, messages, optional contact email (logged-out), and attachments you upload
• Billing — subscription/entitlement state and payment-provider references (Paddle processes card data; we do not store full payment card numbers)
• Technical and anti-abuse metadata — hashed IP addresses, coarse client signals (for example user-agent / Accept-Language heuristics), rate-limit counters, session-bound handles, and audit events
• Product analytics — event data in PostHog (EU) when you allow analytics cookies

• Provide accounts, profiles, communities, recruiting, and support
• Verify moderation experience and keep current-staff signals honest
• Prevent scraping, spam, impersonation, and other abuse
• Send transactional email (security, tickets, exports, billing)
• Operate paid features and fulfill purchases
• Understand product usage (analytics only with consent; see Cookies)
• Comply with law and enforce our Terms

Sign-in uses Discord OAuth. We store encrypted Discord tokens where needed to refresh guild membership and power features you use. On account erasure we attempt to revoke Discord tokens.

If you install the Modfolio bot on a Discord server, we process guild and member/role information required for claims, staff rosters, member counts, and related community features, under the authority of the server's administrators who install it.

Optional connections (for example Steam) store provider account ids and public profile fields you authorize so they can appear on your Modfolio profile.

To protect users and the Service we process short-lived access metadata: HMAC-hashed IP addresses (not raw IPs in long-term audit logs), request volume, and coarse client signals. Rate-limit counters are ephemeral (on the order of ~30 days). Related anti-scrape audit entries are retention-limited and anonymised on account erasure where applicable.

We may use challenges (Cloudflare Turnstile), view quotas, canary records, and automated content checks (including optional OpenAI moderation for some text) to reduce abuse. We do not sell this data.

We use essential cookies/storage for sign-in, security, and remembering cookie preferences. Analytics (PostHog, EU cloud) loads only if you choose "Accept all" (or equivalent) and Do Not Track is not enabled. You can change this anytime via Manage cookies in the site footer.

Appearance preferences may be stored in a cookie or account setting so the UI stays consistent across visits.

We share data with processors that help run Modfolio, including roughly:

• Hosting / app platform (e.g. Vercel)
• Database (e.g. Neon Postgres)
• Object storage for media and exports (e.g. Cloudflare R2)
• Email delivery and inbound replies (e.g. Resend)
• Background jobs (e.g. Inngest)
• Rate-limit / KV store in production (e.g. Upstash Redis)
• Payments (Paddle) when you buy paid features
• Analytics (PostHog EU) when you consent
• Optional content moderation (OpenAI) when enabled
• Discord, for OAuth and bot features you use

Public profile and community pages show the information you (or a community admin) choose to make visible. We do not sell personal data.

We keep data only as long as needed for the purposes above. In practice:

• Account data — until you erase the account, plus limited records we must keep for safety or law (for example ban / abuse signals)
• Export packages — signed download about 72 hours, or sooner after download + a short grace period; request metadata may be kept longer for audit
• Anti-scrape rate / audit signals — short TTL (~30 days for many counters / related audits)
• Anonymised audit after erasure — retained for a limited period (product target: years-scale, then delete/aggregate)
• Email outbox — delivery logs needed to operate mail and webhooks; anonymised or detached on erasure where designed

Depending on where you live, you may have rights to access, export, correct, delete, or object to certain processing. In Modfolio you can:

• Request export or erasure in Settings → Your data
• Dispute a CLAIMED experience that names you via Dispute a claim (Discord sign-in required)
• Manage email preferences in Settings → Email (transactional / legal messages may still send)
• Contact us via Support if something looks wrong

Community owners can run community-scoped data requests where the product exposes them; last-owner account erasure may require transferring ownership first.

Modfolio is for users 13+ (see Terms). We rely on Discord's account age rules and OAuth sign-in; we do not run a separate age-assurance flow in v1. If you believe a child under 13 has an account, contact Support.

Privacy questions: Support. We may update this notice as the product evolves; the "Last updated" date will change, and material changes may get additional notice when practical.