Home/SOKEN Contract Review/Report Removal Policy

Report Removal Policy

Last updated: 24 October 2026

This policy describes how to request the removal of a Report produced by the SOKEN Contract Review service (the "Service") and how we process such requests.

Terms defined in our Terms of Use have the same meaning when used in this policy.

1. Scope

This policy applies to Reports hosted on our servers (including the hosted Report page and PDF) and to Published Reports in our public report library at soken.dev/audits and its public mirror repository.

2. Who May Request Removal

A removal request may be submitted by:

  1. the owner or operator of the smart contract code that is the subject of the Report;
  2. a party with a legitimate legal interest in the removal (for example, a copyright holder whose code was included in the review without authorisation);
  3. the person who originally requested the review through the Service; or
  4. a law enforcement or regulatory authority acting under applicable law.

3. Grounds for Removal

We will consider removing a Report on any of the following grounds:

  1. The requester is the verified owner of the reviewed code and wishes the Report to be withdrawn.
  2. The Report was produced from code that the requester holds copyright in and that was reviewed without the requester's authorisation.
  3. The Report contains materially inaccurate findings that could cause harm if left publicly accessible.
  4. Removal is required by a court order or applicable law.
  5. The Report was produced in violation of our Terms of Use.

4. Required Information

To submit a removal request, please email hello@soken.dev with the following information:

  1. The Report identifier or the URL of the Report you wish to have removed. If the Report has been published, include the public URL.
  2. Your full name and the organisation you represent (if applicable).
  3. An explanation of your relationship to the reviewed code (for example, owner, authorised representative, or copyright holder).
  4. The grounds on which you are requesting removal, with reference to section 3 above.
  5. If you are the code owner, proof of ownership. The simplest forms of proof are:
    • a signed message from the contract's owner or administrator address; or
    • a commit to the code repository adding a file that contains the Report identifier.
    These are the same forms of proof accepted by the verification mechanism on soken.dev. If you cannot provide on-chain or repository-based proof, please describe your connection to the code in sufficient detail for us to verify your claim.

5. How We Process Requests

  1. We acknowledge receipt of your request.
  2. We review the information you have provided and, if necessary, ask for additional evidence or clarification.
  3. If the request is substantiated:
    1. We withdraw the Report. Withdrawal removes the hosted Report page and the PDF from our servers.
    2. If the Report was published, we also remove the PDF from the public report library and its mirror repository, and trigger a refresh of the site listing.
    3. Tombstone records (containing only hashes, the withdrawal reason and status, not the Report content) are retained indefinitely so that the authenticity verification page can confirm the Report was withdrawn.
  4. If we cannot verify the request or the request does not fall within the grounds set out in section 3, we will inform you of the reason and, where appropriate, suggest alternative steps.

6. Response Timelines

We aim to:

  • acknowledge your request within 2 business days of receipt; and
  • act on a substantiated request within 5 business days of receipt.

These are targets, not guarantees. Complex requests or requests requiring additional verification may take longer. We will keep you informed of progress.

7. Counter-Notice

  1. If a Report you published is removed following a third-party request, we will notify you (where we have your contact details) and provide you with a summary of the grounds for removal.
  2. You may submit a counter-notice to hello@soken.dev if you believe the removal request was made in error or does not fall within the grounds set out in section 3. Your counter-notice should include:
    1. the Report identifier or URL;
    2. an explanation of why you believe the removal was not warranted; and
    3. any supporting evidence.
  3. We will review the counter-notice and, where appropriate, reinstate the Report or refer the matter to the original requester for resolution. We are not obliged to reinstate any Report, and our decision is made at our reasonable discretion.

8. Abuse of Process

  1. Removal requests must be made in good faith. Submitting a request that you know to be false or misleading, or using the removal process to suppress legitimate security research or censor accurate findings, constitutes abuse of this process.
  2. We reserve the right to disregard requests that we reasonably determine to be abusive, vexatious or made for an improper purpose.
  3. Repeated abuse may result in future requests from the same party being deprioritised or declined.

9. Self-Service Deletion

If you are the person who originally requested the review, you can delete the review job and its associated Report at any time without contacting us:

  • Call the review_delete_job tool through your AI client with the job identifier and explicit confirmation.

This removes the source code, findings, hosted Report page and PDF from our servers. It does not remove a copy that has already been published. To request removal of a Published Report, please submit a removal request as described above.

10. Contact

All removal requests: hello@soken.dev

Chat