Verso Books

https://www.versobooks.com · 43/92 checks passed · publishers

Compliance report (framework 0.8)

Gate passed (every Core check must pass) · not counted towards the gate: paused 35, draft 48, ready for review 54.

Site level: 0 (no scored checks yet).

By level

LevelResult
Level 1 — Basic 25/37 (11 failed)
Level 2 — Enhanced 9/27 (14 failed)
Level 3 — Advanced 0/10 (9 failed)

By category

CategoryResult
Accessibility 11/13
Accountability 1/5
AI & Automation 3/8
Interoperability 1/3
Privacy 8/16
Provenance 1/2
Security 6/11
Transparency 3/13
Responsibility to the Future 0/3

Level 1 — Basic

Accessibility

AI & Automation

FAIL AI use policy in place
  • policy_exists: The About page contains a brief history of Verso Books but no AI use policy or statement.
    Fix: Publish a dedicated AI policy page outlining whether and how AI is used in publishing, editorial, or site operations.
  • scope_clear: No AI usage is mentioned anywhere on the page, so scope is not explained.
    Fix: Add a clear statement describing any AI applications (e.g., translation, recommendations, editorial assistance) or explicitly state AI is not used.

Privacy

Security

Transparency

FAIL Funding/sponsorship disclosure
  • disclosure_exists: The About page contains a history of the publisher but no funding or sponsorship disclosure.
    Fix: Add a dedicated funding/ownership section to the About page identifying any investors, parent entities, or sponsors that support Verso.
  • transparent: No funding sources are identified anywhere on the page, so transparency cannot be established.
    Fix: Clearly name all funding sources (e.g., New Left Review affiliation, grants, partnerships like Rosa-Luxemburg-Stiftung) in a transparent disclosure statement.

Level 2 — Enhanced

Accessibility

Accountability

FAIL Published response timeframes
  • response_timeframe: The About page contains no mention of response timeframes for any inquiries or communications.
    Fix: Publish a clear response timeframe (e.g., on the Contact or Help/FAQs page) stating when users can expect a reply.
  • specific: Because no timeframes are published, there are no specific day-based commitments provided.
    Fix: State a concrete timeframe such as 'We respond within 5 business days' rather than vague language.
FAIL Documented complaints process
  • process_exists: The page lists contact details and FAQs but does not document any complaints or feedback process.
    Fix: Add a dedicated complaints/feedback procedure page explaining how users can submit and escalate concerns.
  • steps_clear: No complaints steps are described on the page, so clarity cannot be established.
    Fix: Enumerate step-by-step instructions (submission channel, required info, acknowledgement, resolution, escalation) for making a complaint.
FAIL Clear appeals process
  • appeals_exists: The Terms page only mentions a generic complaints handling procedure directed to Customer Service, without a documented appeals process.
    Fix: Add a clearly labeled appeals section outlining the steps, timelines, and required information for a customer to formally appeal a decision.
  • independent: Complaints are handled internally by Verso's Customer Service Department with no mention of independent review or escalation path.
    Fix: Provide an escalation route to an independent reviewer or external ombudsperson/ADR body if the initial complaint outcome is unsatisfactory.

AI & Automation

FAIL Published AI use policy (detailed)
  • detailed_scope: The page makes no reference to AI, so no scope detail exists.
    Fix: Create an AI policy section that enumerates specific use cases, systems, and contexts where AI is or is not applied.
  • limitations: There is no discussion of AI or its limitations on the page.
    Fix: Include a section acknowledging known limitations of any AI tools used, such as bias, inaccuracy, or translation errors.
  • safeguards: The page does not describe any AI-related safeguards or quality controls.
    Fix: Document editorial review, human oversight, and quality assurance procedures that govern any AI-assisted work.
FAIL AI-assisted content clearly marked
  • marking_policy: The About page contains no policy or statement about how AI-assisted content is marked or labeled.
    Fix: Publish a clear policy stating whether and how AI-assisted content is identified on the site (e.g., via labels or disclosures).
  • consistent: Without a stated marking policy, there is no evidence of consistent application of AI content marking on the page.
    Fix: Adopt and consistently apply a standardized AI-content label across all relevant pages and publications.
FAIL Human oversight of AI documented
  • oversight_exists: The page does not document any human oversight process for AI-generated outputs.
    Fix: Add a statement describing human oversight practices for any AI-assisted content on the site.
  • review_process: No editorial review or approval workflow for AI content is described anywhere on the About page.
    Fix: Describe the editorial review and approval steps that AI-assisted content must pass before publication.
  • accountability: No individual or role is named as accountable for AI-generated content, though a Publishing Director is listed for general publishing.
    Fix: Designate and publicly name a role (e.g., Publishing Director or editor) responsible for AI-generated content.

Interoperability

Privacy

FAIL Cookie banner partner disclosure
  • partner_sharing_mentioned: The banner mentions personalization, marketing, and analytics but does not disclose data sharing with third-party partners.
    Fix: Update the banner copy to explicitly state that data is shared with third-party partners and link to a partner list.
  • partner_count_specific: No specific numeric count of partners is stated anywhere in the banner or on-page consent copy.
    Fix: Add a specific partner count (e.g., 'We share data with X partners') in the banner with a link to the full list.

Provenance

Security

Transparency

FAIL Funding disclosed with detail
  • detail: The page provides no amounts, percentages, or categories describing funding streams.
    Fix: Break funding down by category (e.g., book sales, grants, donations, institutional partnerships) with approximate percentages or amounts.
  • complete: Without any disclosure, the page cannot demonstrate coverage of all major funding streams.
    Fix: Publish a complete funding disclosure covering every material revenue source, including co-publishing collaborations like the one mentioned with Rosa-Luxemburg-Stiftung and Karl Dietz Verlag.
FAIL Governance structure disclosed
  • governance_exists: The page provides a historical narrative of Verso's publishing list but does not describe its governance or editorial structure.
    Fix: Add a dedicated section outlining Verso's governance and editorial decision-making structure, including any board, editorial committee, or ownership arrangement.
  • roles_clear: Only Nicole Aschoff is named as Publishing Director; no other key roles or responsibilities are identified on the page.
    Fix: Include a staff or leadership list that identifies key editorial, operational, and managerial roles along with their responsibilities.
FAIL Algorithm explanation if applicable
  • algorithm_explained: The About page describes Verso's publishing history but does not mention or explain any algorithms used on the site.
    Fix: Add a section (or link to one) disclosing any algorithms used on the site, such as recommendations or search ranking, and explaining their purpose.
  • impact_clear: There is no description of how any algorithmic decisions affect users browsing or purchasing on the site.
    Fix: Include a plain-language explanation of how algorithmic outputs (e.g., recommended books, personalized content) influence what users see and do.
FAIL Annual data practices statement
  • annual_statement: The About page links to a privacy policy but provides no evidence of a regular or annual review of data practices.
    Fix: Add a statement to the privacy policy noting the cadence of review (e.g., 'reviewed annually') and surface the latest review date.
  • dated: The page references a privacy policy link but shows no date or version on any data practices statement visible here.
    Fix: Include a 'Last updated' date or version number on the privacy policy and link it from the About page.

Level 3 — Advanced

Accessibility

FAIL Published accessibility statement
  • known_issues: The visible page content is an 'About Verso' history and does not acknowledge any known accessibility issues or limitations.
    Fix: Add a section to the accessibility statement that lists specific known accessibility barriers or non-conformant areas of the site.
  • remediation_timeline: No timeline or commitment for fixing accessibility issues appears anywhere on the page.
    Fix: Include a stated target date or ongoing schedule for remediating identified accessibility issues in the accessibility statement.
  • feedback_channel: The page offers only general 'Contact' and 'Help and FAQs' links with no accessibility-specific feedback channel or response-time commitment.
    Fix: Provide a dedicated accessibility contact (email or form) along with a stated response-time commitment for accessibility feedback.

Accountability

FAIL Published moderation policies
  • policy_exists: The page is a terms of service about orders, shipping, and ebook licensing, with no moderation policy published.
    Fix: Publish a dedicated moderation policy covering user-generated content such as blog comments or book club contributions.
  • criteria_clear: No moderation criteria (e.g., prohibited content, acceptable use standards) are stated anywhere on this terms page.
    Fix: Add a clearly enumerated list of what content is allowed or prohibited on Verso's platforms.
  • enforcement: There is no description of how moderation decisions are made, appealed, or enforced on this page.
    Fix: Document the enforcement process, including who reviews content, what actions may be taken, and how users can appeal decisions.

Interoperability

Security

FAIL Incident response plan published
  • plan_exists: The About page describes Verso's publishing history and offers no published incident response plan or security policy.
    Fix: Publish a dedicated incident response policy page outlining how the organization detects, manages, and responds to security incidents.
  • notification_commitment: The page contains no commitment to publicly notify users of significant security incidents.
    Fix: Add a stated commitment to notify affected users and the public in the event of a significant security or data incident.
  • timeframe: No timeframe for disclosing incidents to affected users appears anywhere on the page.
    Fix: Specify a concrete disclosure timeframe (e.g., notification within 72 hours of confirming an incident) in the incident response policy.

Transparency

FAIL Algorithmic decision criteria published
  • criteria_published: The page does not publish any specific criteria used in algorithmic decision-making.
    Fix: Publish the specific input signals and criteria (e.g., purchase history, popularity, editorial curation) used in any automated decisions on the site.
  • weighting: No information about the weighting or prioritization of algorithmic criteria is provided on the page.
    Fix: Describe how different criteria are prioritized or weighted in algorithmic outputs, even at a high level.
  • auditable: The page offers no technical or procedural detail that would allow an external party to audit any algorithm.
    Fix: Provide documentation, a transparency report, or a contact channel for researchers that includes enough detail to enable independent review of algorithmic systems.
FAIL Open source code or tech docs
  • open_source: No link to source code or repository is provided on the about page.
    Fix: Add a link to a public code repository (e.g., GitHub) for any open-source components of the website or publishing tools.
  • tech_docs: No technical documentation about the site's infrastructure or APIs is published or linked.
    Fix: Publish basic technical documentation or a developer page describing the site's stack, data formats, or any available APIs.

Responsibility to the Future

FAIL Environmental / sustainability disclosure
  • disclosure_exists: The About page details Verso's publishing history but contains no environmental impact or sustainability disclosure.
    Fix: Publish a dedicated sustainability or environmental impact statement describing the company's environmental practices and commitments.
  • specific_metrics: The page provides no specific figures on carbon emissions, energy use, or other environmental metrics.
    Fix: Include quantified environmental metrics such as annual carbon footprint, energy consumption, and emissions data in a published disclosure.
  • hosting_disclosure: There is no mention of the carbon or energy profile of the website's hosting infrastructure.
    Fix: Disclose the hosting provider's energy sourcing (e.g., renewable-powered data centers) and the site's associated carbon or energy footprint.
FAIL Succession and continuity plan
  • plan_exists: The about page is a historical narrative of Verso's publishing achievements and contains no published plan for organisational failure or exit.
    Fix: Publish a succession or wind-down plan describing what happens to the organisation, its catalogue, and website if Verso ceases operations.
  • data_and_content_fate: The page never addresses what would happen to user data or published content in the event of the organisation's closure.
    Fix: Add a section specifying how user accounts, data, and published titles would be preserved, transferred, or deleted if the business exits.
  • custodians_or_mirrors: No custodians, mirrors, or archive partners are named for preserving content beyond the mention of publishing collaborators for individual book projects.
    Fix: Identify designated custodians, archival partners, or mirror repositories responsible for maintaining the catalogue and site if Verso shuts down.
FAIL Worker wellbeing policy
  • policy_exists: The About page describes Verso's publishing history and catalogue but contains no published policy on worker wellbeing or working conditions.
    Fix: Publish a dedicated worker wellbeing or working conditions policy and link to it from the About or Job Openings pages.
  • specific_commitments: The page makes no specific commitments regarding pay, hours, mental health, or benefits for staff.
    Fix: Add concrete commitments on pay, working hours, mental health support, and benefits within a worker wellbeing policy.
  • accountability: The page names editorial leadership but identifies no accountability or oversight mechanism for worker conditions.
    Fix: Designate a responsible person or team and describe an oversight process (e.g., reporting or review procedure) for worker conditions.