Scope
This notice covers the MCC public site and launch-imminent MCC services, including identity, source hosting, and chat surfaces under marxcompute.club.
Signup And Announcements
When you sign up for MCC updates, we collect the email address you submit and basic operational metadata needed to run the signup flow, prevent abuse, maintain the list, and send announcements.
Event RSVPs
When you RSVP for an MCC event, we collect the email address you submit, optional name or handle, the event reference, RSVP status, whether you explicitly requested a microplatform invitation, and timestamps needed to operate the event list. RSVP-only records do not automatically create MCC identity accounts.
Identity
id.marxcompute.club uses Pocket ID for MCC identity and passkey login. MCC may store account fields such as username, email, display name, profile settings, app grants, login events, and audit logs. Passkeys use public-key credentials. MCC does not receive your private passkey or device unlock secret.
Source Hosting
git.marxcompute.club uses Forgejo for source hosting. MCC may store account data, public SSH keys, repositories, commits, comments, issues, pull requests, organizations, teams, permissions, activity records, and security logs. Git history and public contribution metadata may be intentionally durable.
Chat
zulip.marxcompute.club uses Zulip for MCC launch coordination. chat.marxcompute.club may also host experimental MCChat/IRC surfaces. MCC may store account records, usernames, channel or stream membership, messages, moderation actions, client sessions, and connection metadata. MCC chat surfaces are not end-to-end encrypted private messaging. History may be logged, indexed, or exported for moderation, recovery, and artifact workflows unless a channel or stream is explicitly designated otherwise.
Operational Data
MCC services may process IP addresses, user agents, request paths, timestamps, login attempts, rate-limit events, abuse-prevention events, error logs, and security audit records. We use this data to operate services, debug failures, detect abuse, and recover from incidents. We do not sell personal information or run advertising profiles.
Backups And Retention
Service databases, repositories, chat records, configuration, and operational logs may be included in backups. Deletion requests will be handled for active systems where practical, but copies may persist in backups, logs, Git history, signed artifacts, or external recipients until normal rotation or archival limits apply.
Services And Providers
MCC uses self-hosted and managed services to operate the site, identity, source, chat, mail, backups, and abuse-prevention path. These services may process data for us as part of those functions.
- Cloudflare Pages, Workers, D1, Turnstile, Web Analytics, DNS, and Tunnel for hosting, signup handling, bot checks, aggregate analytics, DNS, and private service routing.
- Hetzner for MCC virtual servers and related infrastructure.
- Resend for outbound email delivery.
- Migadu for mailbox hosting.
- Backblaze B2 or Hetzner storage services for backups if enabled for a given service.
- Tailscale for operator and administrative network access where used. Ordinary MCC users are not expected to join the MCC tailnet unless explicitly told otherwise.
Analytics
Cloudflare Web Analytics gives us aggregate traffic information. It is used to understand whether the site is being reached and whether it is being abused. We do not use third-party ad tracking.
Requests
To update or delete your signup information, or to ask about MCC account data, email [email protected]. Some records may be retained when needed for security, abuse prevention, archival integrity, legal obligations, or source-control provenance.
Changes
This notice may change as MCC infrastructure changes. Material changes will be reflected on this page.