Private Docker Space flagged as abusive: requesting review and guidance on a compliant redesign

Hello Hugging Face team,

I am following up on a moderation review request sent to safety@huggingface.co on November 5, 2026, concerning a private Docker Space under my account, @robthepirate. The Space URL and repository revision are included in that email.

The build completed and the container logged application startup at 05:26 UTC that day. At 05:35 UTC, the runtime API reported PAUSED with “Flagged as abusive.” The response available to me did not identify a specific rule or component.

The intended workload is a private operational dashboard with local CPU inference. End-to-end validation was not completed before the suspension.

The deployment included a userspace Tailscale client and a loopback-only outbound HTTP proxy to reach a fixed private, read-only data endpoint. The application was intended to expose a constrained dashboard API, rather than a general-purpose public proxy or remote shell.

I recognize that this networking component may be relevant to the platform-abuse policy. I do not know whether it triggered the flag, and I am not assuming this was a false positive.

I am prepared to remove the tunnel and outbound proxy and redesign the data access around an authenticated HTTPS endpoint or private Hub storage, subject to your guidance. That replacement has not yet been deployed.

Could the team please advise:

  1. Which policy requirement or component needs to be addressed, or what concrete remediation is required?
  2. Whether a redesign without the tunnel or outbound proxy would make this workload acceptable, and whether there are other requirements to consider.
  3. Whether the same Space can be reviewed and re-enabled after the required changes, and how to submit those changes for review while it remains paused.

I am keeping the flagged runtime suspended rather than attempting to bypass the restriction through duplicate Spaces. Sanitized build and runtime evidence can be provided privately.

Thank you for your guidance.