The hosted page comes down with the decision.

What this deployment does

When a person revises the evidence behind a published claim, revokes that claim, or saves a new claim version, Superlimen withdraws the hosted page before the action returns. A later visit to that page does not show the withdrawn snapshot.

Superlimen then attempts withdrawal on each connected WordPress, Webflow, or Contentful destination for that claim, up to three jobs in the same request. Each attempt waits up to eight seconds.

If the destination does not accept the withdrawal, the job stays visible in the workspace, ahead of completed deliveries, and is retried up to eight times. The owner can attempt an open withdrawal again from that queue. The daily scheduler is the backstop for those retries and also attempts queued withdrawals after evidence expires. A response from the connector does not confirm that the public URL is gone.

Disabling a connector attempts withdrawal of the copies already sent to that destination. The hosted Superlimen page stays up while the claim itself remains approved.

What can remain outside Superlimen

A destination outage, a rejected credential, or an address Superlimen will not call can leave the external copy in place until a later retry succeeds. The hosted page still stays withdrawn when the claim is no longer valid.

The application and its database run in London. Company identity providers, model providers, and the customer's CMS are outside this commitment. Publishing a new page to a CMS remains queued for the scheduler.

What this page is

This page states the publication-integrity behavior of the current deployment. It sets no uptime percentage and no service-credit schedule. A signed customer agreement would be a separate document.

An independent SOC 2 examination has not been started, and no SOC 2 report exists. The control boundaries are on the security page.