Privacy Policy

Information collected

Mudhaven receives information you provide and limited operational information generated while you use the service.

• Account username, email address, password hash, verification state, and account-security status.
• World listings, hosting requests, resources, uploaded files, contact details, direct-message text, reply references, edit and read state, reactions, private pin, archive, and mute choices, approved-sender choices, member-created blocks, and staff communications.
• When a member reports a private message, the reason, their explanation, the single reported message, its sender and recipient labels, message timestamps, and moderation outcome are retained as a restricted safety record; surrounding conversation messages are not copied into the report.
• Hosting configuration, runtime status, build and runtime logs, resource usage, database and website identifiers, and project timelines.
• IP addresses, request metadata, login attempts, security events, moderation actions, and audit records.

How information is used

Information is used to authenticate accounts, review submissions, provision and operate hosting, send transactional email, diagnose failures, enforce limits, investigate abuse, secure the platform, and comply with valid legal obligations. Members may disable optional hosting, world, resource, forum, newsletter, and body-free direct-message email or combine it into a daily digest. Direct-message notification email and account notices identify the sender but never include message text. Verification, recovery, unlock, new-browser, and confirmed account-change security messages remain immediate and mandatory.

Sessions and cookies

Mudhaven uses first-party session, CSRF-protection, remember-login, and long-lived random browser-recognition cookies required for account security and signed-in features. The browser-recognition token is stored hashed on the server and is used to warn you when an unfamiliar browser signs in; the first browser seen establishes the account baseline without sending an alert. Members can review active database-backed sessions, revoke another browser, or clear every other session and remembered login from account security. The current service does not use third-party advertising cookies. Browser or server logs may record normal request metadata.

Two-factor authentication

When you choose to connect an authenticator app, Mudhaven stores the authenticator seed using authenticated encryption. Pending setup keys expire, readable recovery codes are shown only once, and only keyed hashes of recovery codes remain in the database. Enrolled accounts must complete a password-first authenticator or recovery-code challenge on untrusted browsers. If you explicitly trust a private browser, Mudhaven stores an expiration time beside its hashed recognition token; you can revoke every trusted browser from Account Security. Replacing recovery codes requires your current password and one active second factor, invalidates the previous set immediately, and sends a mandatory security notice. Staff cannot view authenticator secrets or recovery codes and will never request them. Account exports never include authenticator seeds, pending setup keys, readable recovery codes, recovery-code hashes, or browser-token hashes.

First-party analytics

Mudhaven measures successful public page loads and selected successful actions such as registration, verification, submissions, approvals, world connections, and resource downloads. This helps staff understand which public content and community services are useful.

• Analytics do not store a user or account ID, raw IP address, full user agent, query string, request body, uploaded filename, submitted field value, project name, or full referring URL.
• A random first-party seed expires at the end of the day. Only a keyed daily hash is stored, so analytics cannot recognize the same visitor on a later day.
• Stored dimensions are limited to public route and path, member-or-guest state, bot detection, broad device, browser, and operating-system families, external referrer hostname, and a closed list of successful action names with MUD or BYOND context.
• Raw analytics events use the configured short retention period, currently 90 days by default. Daily aggregate counts may be retained longer for historical service reporting.

Sharing and disclosure

Mudhaven does not sell personal information. Information may be shared with infrastructure, email, security, or backup providers only as needed to operate the service; with staff who need it for support and moderation; or when reasonably necessary to respond to valid legal process, prevent harm, or protect rights and systems. Public listings and approved resources display the information you choose to publish. Optional builder profiles are private by default and, when enabled, display only your username, chosen bio, optional HTTPS website, and approved contributions.

Retention and deletion

Active account and hosting records are kept while needed to provide the service. Archiving a direct-message conversation preserves its history and affects only that member’s inbox; clearing removes the member’s old view but does not erase the other participant’s copy. Account closure removes every private conversation involving the closed account from the live service for both participants. A message already submitted as safety evidence may remain as one restricted immutable report snapshot after the live conversation is removed, because moderation records may be kept longer when needed to prevent repeat abuse or resolve disputes. Member-visible login and account security events are retained for 180 days by default. Account closure uses a cooling period and staff review so hosting can be safely deprovisioned first. Closure removes the former login identity and private account records; approved public contributions may remain labeled Former Member. Deleted submissions, projects, messages, or accounts may remain temporarily in backups, logs, abuse records, or audit history.

Security

Mudhaven uses measures such as HTTPS, password hashing, email verification, rate limits, access controls, upload validation, process limits, audit logging, and restricted server permissions. No internet service can guarantee absolute security, so members should keep independent backups and report suspected compromise.

Your choices

Members may accept direct messages from Everyone, Approved people only, or Nobody; manage approved senders and blocks; enable or disable body-free account and email alerts; mute individual conversations; search conversations by participant username; privately pin, archive, restore, and mark conversations read; reply, react, and correct their own message during the 15-minute edit window; remove their own reactions; report one received message with an optional simultaneous block; clear their own conversation view; choose optional workflow email categories; update eligible submissions; remove in-app notifications; download a private JSON account-data export; request account or hosting deletion; and contact Mudhaven about access or correction questions. Account exports include direct-message content involving the requesting member, reply references, edit state, reactions, their private pin, archive, and mute choices, reports they submitted without captured evidence or private staff notes, their permission and notification settings, approved-sender choices, and blocks they created, while omitting credentials, hashes, tokens, private file contents, session payloads, and staff-only operational notes. Some records cannot be immediately removed when they are needed for security, legal compliance, service integrity, or backup recovery cycles.

Children

Mudhaven is not directed to children under 13 and does not knowingly collect personal information from them. Contact Mudhaven if you believe a child has provided personal information so the situation can be reviewed.