MCP activity and scientific calculations
The public observatory keeps the most recent 50 activity events in application memory. These events contain the software client’s declared name and version, an opaque session identifier, called tool, event state, timestamp and, when available, duration and execution backend. The history is replaced as new events arrive and disappears when that gateway process restarts.
Client names are self-reported. They do not verify an AI model or provider. Do not put an email address, personal information or secret into clientInfo. Calculation arguments, scientific results and detailed mission or composition events are not published in this activity stream. They pass through the calculation service to answer the requesting client.
Contributor registrations are persistent
After your explicit Start action, the coordinator retains a registration containing your chosen alias, installation identifier, client version, declared resource identifiers and hardware, offers, pause state and last heartbeat. It stores a SHA-256 hash of the authentication token, not the original token. The original coordinator token remains in the local client’s protected settings file.
The registry holds at most 128 registrations. Registrations have no automatic age-based deletion in this pilot. Pausing or becoming stale makes resources unavailable; it does not delete their registration. Aliases, short opaque public IDs, reported hardware and offers, states and heartbeat ages are visible through public network status. Authentication tokens, installation IDs, raw resource identifiers and client IPs are not included in that public response.
Revocation and previously accepted work
Use Revoke registration in the local dashboard to remove the active coordinator registration and invalidate its outstanding assignments. The client reports a network failure instead of claiming that an unreachable coordinator accepted revocation. Revoke before changing a registered public alias.
Previously accepted samples stay in retained job records and cumulative totals. Internal job records may retain an opaque contributing-worker identifier until that job is pruned; public receipts show a contributor count rather than those internal identifiers. Revocation does not retract an already published synthetic receipt or copies obtained by another visitor.
Public synthetic jobs and bounded receipt retention
Contributor jobs contain only pi_chunk_v1 parameters: sample count, seed and backend preference. Receipts expose their status, completed counts, final estimate when complete, contributor count, verification time and job timestamps. No private dataset, file or arbitrary program is accepted by this pilot.
The coordinator retains at most 64 job records, with no more than 16 active jobs or 320 retained chunks. A job has a 120-second execution lifetime. That lifetime is not the retention period: completed or expired records remain until admission of new work requires space, when the oldest terminal records are pruned first. A pruned receipt returns 404. Cumulative validated-sample and completed-job totals survive receipt pruning.
Separate public contributor activity journal
The contributor endpoint /api/network/v1/activity keeps at most 256 transition events in memory and returns at most 128 per response. Events describe synthetic job creation, assignments, accepted verified chunks, completion, expiry and released leases. They include job identifiers, timestamps, sample counts and, where relevant, the same short public worker identifier and CPU/CUDA backend used in public status.
This journal publishes no authentication tokens, full private worker identifiers, raw resource identifiers, installation IDs, IP addresses, hostnames or aliases. The website may join a short worker identifier to the separately published status alias. Each response also includes a bounded snapshot of up to 16 active and eight terminal synthetic job receipts; this 24-receipt snapshot does not replace the 64-record storage limit above.
The event ring resets on coordinator restart. A reset response is recent history, not evidence of fresh computation; restored job receipts do not generate invented historical events. An assignment is not proof that execution began, and event animation is not a GPU utilization measurement. This journal is distinct from the gateway’s 50-event MCP observatory.
Local client storage and controls
The client stores its settings, installation identifier and coordinator credentials in the user profile: %LOCALAPPDATA%\ScoreCompute\contributor on Windows, or $XDG_DATA_HOME/scorecompute/contributor, normally ~/.local/share/scorecompute/contributor, on Linux. Closing the client does not delete those settings. Every new launch starts paused.
The browser dashboard is a protected loopback control surface. It receives a separate local control secret; the coordinator authentication token is not exposed to the page. The client runs only the compiled public workload and does not upload private files or download executable jobs.
Rate limits, infrastructure and backups
The contributor coordinator uses private in-memory IP-based rate buckets for admission. Inactive buckets are reclaimed after 120 seconds and all buckets reset when the process restarts. These addresses are not stored in the coordinator’s durable registration/job state or published in status. This is distinct from persistent worker records and receipts.
The origin configuration disables ordinary access logging for the contributor API. Hosting, operational error logs and Cloudflare’s network and security services are separate from these application stores; they may process connection metadata needed to deliver and protect requests. The 50-event observatory limit does not define their retention.
Restricted operational backups may preserve earlier coordinator state during deployment and recovery. Revocation removes the active registration; it does not automatically rewrite older backups. This notice does not promise immediate erasure from every infrastructure layer or a backup expiry period that has not been configured.
Questions about your data
Use the ScoreZenith contact page for questions about the service or retained data. Do not send authentication tokens. A public alias or job identifier can help locate the relevant record without exposing a credential.
Read the contributor installation and workload guide, or review the MCP connection and privacy boundaries.