Responsible access
Acceptable use
Protect the shared catalogue, the people using it and the credibility of the records it holds.
Provide honest evidence
- Identify sources, estimates, dates, product versions and calculation boundaries accurately.
- Do not fabricate factory records, verification statements, credit retirements or award status.
- Do not alter a third-party report to suggest a wider scope than its author verified.
- Correct material errors when discovered and avoid continuing to publish a superseded result.
Upload only what is needed
You must have the right to provide uploaded material. Avoid sensitive personal information and unnecessary individual contact details in BOMs, catalogues, order descriptions and factory evidence. Do not upload malware, unlawful material or information obtained without permission. Confidential evidence must use the access arrangements agreed for the service.
Represent results fairly
Do not imply that an estimate is independently verified, that a credit purchase reduces the original footprint, or that a badge covers products or activities outside its record. Do not copy another organisation’s badge or change its level, role, identifier or validation link. Follow the carbon and recognition guidance.
Respect the service and other users
Do not disrupt the service, probe another user’s records, exploit vulnerabilities, send unsolicited messages through the platform, or scrape restricted catalogues for resale. Security testing requires prior written agreement on its scope. API use and data reuse must follow your contract.
Security research and automated access
Obtain written permission before testing security controls, simulating attacks or scanning non-public endpoints. A responsible initial report should describe the issue and affected location without exploiting it beyond what is necessary to demonstrate the concern. Do not extract another organisation’s records, interrupt service, create persistent access or disclose a vulnerability publicly before an appropriate response can be assessed.
Normal API use is governed by the authorised integration scope. Do not evade request limits by rotating identities, bulk-export restricted catalogue data, or use the service to build a competing resale dataset without an express licence. Automated activity must preserve attribution and data-use restrictions.
Concerns and enforcement
Report a suspected error, misuse or misleading credential to [Add support/legal email], including the relevant record or page link and a short description. Avoid sending unnecessary confidential data in an initial report.
The service agreement must set out investigation, correction, access restriction, notice and appeal processes. Immediate restrictions may be needed to address active security risks, subject to applicable law and the agreement. Enforcement should reflect the evidence and seriousness of the issue.
Fair investigation and correction process
A report should identify the account, record, badge or endpoint, the concern and evidence you are entitled to share. The reviewer should distinguish a technical error, a data-quality dispute and deliberate misuse. Preserve relevant evidence securely; do not circulate another customer’s confidential files to prove a point.
- Triage urgent security, privacy or clearly misleading credential concerns promptly.
- Notify the affected customer of the substance of an allegation where lawful and safe, and give a reasonable chance to respond.
- Prefer a targeted correction, access restriction or temporary withdrawal over an unnecessary organisation-wide block.
- Record the reason, affected records, remedial steps and review date for an enforcement action.
- Provide a route to request reconsideration by someone other than the original decision-maker where practicable.
- Restore access or correct public status when the evidence supports it; do not leave a disproven allegation presented as fact.
The proposed appeal window is 30 days after the decision notice. A review target is 15 business days after receipt of sufficient information, with an update if more time is needed. These are programme operating targets to adopt, not a guarantee that every dispute resolves within that period.
Application and policy updates
The policy applies to users, administrators, contractors and integration clients using an organisation’s access. Administrators should communicate it to authorised users and remove access when it is no longer required. A material change should be notified through an appropriate account or contract notice; enforcement must follow the applicable agreement and mandatory law. The version in force at the relevant time should remain identifiable.
