MercuryServer · Titan privacy notice
Updated October 12, 2026. Music made this place. Looking after the people who keep it going matters too.

This notice covers mercuryserver.com, its forums and the Horizon views of the community. MercuryServer is administered by Kamal and supported by TitanArray infrastructure. In this notice, “we” means the MercuryServer administration responsible for this service. It does not describe every service in the Titan family.

For a privacy question or request, use Contact Us and put “Privacy request” in the subject. You can also email registrations@mercuryserver.com. Include your username and the relevant page links; do not send your password or identity documents in your first message.

What we receive and why

• Your account: username, email address, password verification data, registration date, account settings and any profile details you choose to provide. These let us operate membership, sign-in, account recovery and your preferences.
• Your contributions: posts, replies, uploads, reactions, subscriptions and other actions you take in the forum. We use them to display conversations, deliver requested notifications, maintain the archive and moderate the community.
• Private communications: private messages, contact requests and reports you submit. These support communication, moderation and assistance. Private messages are not part of the public Horizon feed. They are stored by the forum; they are not end-to-end encrypted.
• Technical records: IP addresses, request times, requested pages, browser information, session records and error/security logs. These help deliver pages, prevent abuse, investigate failures and protect accounts. The forum may record account activity such as last visits.

Account information is needed for member features. Browsing public conversations does not require an account. Optional profile fields and contributions are your choice; avoid posting sensitive information about yourself or anyone else.

Public means public

Public posts, profile information you make public, usernames and uploads can be seen by visitors, indexed by search engines, quoted by other members and copied outside MercuryServer. Horizon presents permitted public material from the same forum record. It does not make private messages public. Visibility depends on the forum’s permissions and your settings.

MercuryServer is a long-running community archive. Closing an account does not automatically remove every post, quotation or copy made by others. Tell us which information concerns you so we can assess removal, correction or anonymisation, including other people’s rights and the integrity of conversations.

Separate Horizon conversations and reply alerts

Horizon conversations are stored separately from the legacy forum inbox. Existing MercuryServer members verify their native account before a Horizon member identity and session are linked to that stable forum user ID. We do not copy forum passwords or import native private messages. Native account restrictions also restrict linked Horizon access.

Conversation access is limited to its participants. Messages are not end-to-end encrypted. A report creates a restricted moderation case containing the reported message and necessary context; authorized administration can review it. Messages remain stored for operation and recovery, including backups. This release has no automatic expiry or message deletion control; archiving affects only your inbox view. Contact the administration about access, correction or removal requests.

In-app alerts cover new Horizon messages, replies to your public topics, quoted public posts and topics you choose to follow. Preferences, mute and block controls let you manage these alerts. Existing public posts are baselined rather than replayed as historical notifications. Synchronization is periodic, and an alert rechecks current public visibility when opened. Private native forum posts and native messages are excluded. Email and browser push are not enabled by this release.

Horizon uses secure member-session and request-verification cookies. Drafts and retry identifiers may be kept in the browser tab’s session storage. Ordinary message links do not trigger the public link-preview fetcher. The public preview service fetches permitted public HTTPS page metadata without your account cookies; visiting a linked website remains your choice.

Cookies and browser storage

The forum uses first-party cookies for sessions, sign-in, security and choices such as forum preferences and read state. These commonly use the bb prefix. A remembered sign-in can persist beyond the current browser session. Browser storage also remembers presentation choices, including compact forum density and whether you dismissed the Titan notice.

You can clear or block cookies and site storage in your browser. Doing so may sign you out, reset preferences or prevent member functions from working. Dismissing a notice is not permission for unrelated tracking. A browser “Do Not Track” signal is not a reliable site-wide opt-out here; use your browser controls and contact us about a specific privacy request.

TOTM.FM, music and connected services

The turntable displays current public track metadata from our spiritual twin, TOTM.FM, and may load track artwork from it. Those requests disclose normal connection information, such as your IP address, to TOTM. The metadata request does not send your MercuryServer sign-in cookies. The glow and EQ are playback animations, not microphone recording or analysis of sound in your room.

If you choose “Open member playlist,” MercuryServer checks your signed-in membership and uses a short-lived, single-use handoff to TOTM. The exchange supplies your MercuryServer user ID, username/display name, forum group, account status and join date. It does not supply your forum password or email address. TOTM’s own features and data practices apply once you enter that service; review its notices before using them.

Forum posts can contain external images, media players and links. Loading an embed or following a link can send connection information to its provider and may allow that provider to use cookies under its own policy. The native forum also loads a JavaScript library from Google’s hosted library service, and older page markup contains an external Host-Tracker uptime badge. These external requests are separate from MercuryServer’s account database.

Who can receive information

Public material is available to its audience. Authorised administrators, moderators and technical operators may access information needed to run the service, handle reports, recover accounts and investigate abuse. TitanArray supplies the hosting infrastructure. Other service providers involved in delivery, email, embedded media or a feature you choose receive the information needed for that interaction.

The support page identifies SynOct LLC as the payment processor for contributions. Payment services have their own notices; do not put card details into a forum post or private message. Information may also be disclosed where required by law, to respond to valid legal requests, or when necessary to protect people, accounts and the service. This notice does not authorise unrelated sale or advertising use of account information.

Retention and security

Account records remain while they support membership and account administration. Public contributions form part of the continuing archive while they remain published. Messages, reports and moderation records may be retained to support their participants, resolve disputes and prevent repeated abuse. Technical logs and backups can retain information separately from the live site for operational, recovery and security purposes.

There is no single automatic deletion period covering all historical MercuryServer data. A removal request is assessed by data type, purpose, legal obligations and effects on others. Removing information from the live site may not immediately remove it from backups or third-party caches. We will explain relevant limitations when handling your request rather than promise an unverified deletion deadline.

Public connections use HTTPS. Access controls and backups support operation and recovery, but no online service is risk-free. We do not claim universal encryption at rest, end-to-end encryption, zero-knowledge storage or that recovery is impossible. Use a unique password and keep private or sensitive material out of public posts.

Your choices and rights

Use your forum settings to review profile visibility, preferences and available notification controls. Contact the administration to request access, correction, deletion or a copy of your personal information, or to object to or restrict a particular use. Depending on where you live and the law that applies, these may be legal rights and you may be able to complain to your local privacy regulator. We may need proportionate information to verify that a request concerns your account.

Where applicable law requires a legal basis, we use account information to provide the service you request; security, moderation and archive information for legitimate operational and community interests, balanced against your rights; information necessary to meet legal obligations; and consent where a particular optional use requires it. You can withdraw consent for that use without changing the lawfulness of earlier processing.

The service and its providers may process information outside your country, including in the United States. Following a link or using a service does not waive your privacy rights. Contact us for information about a particular transfer or provider; this notice does not claim that every country offers identical protections.

Children and changes

MercuryServer is a general music community, not a service directed at children under 13. If you believe a child has provided personal information without appropriate permission, contact the administration so we can investigate and take the necessary action. Do not rely on historical references to faxed parental forms as a current verification service.

We will update the effective date when this notice changes and provide additional notice where a material change or applicable law requires it. A new notice does not by itself authorise an incompatible new use of information already collected.