CarbonLoop logoCarbonLoop
Platform
Platform tools
How it worksThe complete product-to-report workflowCarbon DatabaseFind product records and carbon dataCarbon CalculatorCalculate products and customer ordersCarbon OffsettingExplore projects, credits and evidence
Promotional Products Industry
Industry overview ↗
Types of accounts
SuppliersYour catalogue and website carbon dataDistributorsYour orders, destinations and reportsPartnersYour platform or member network
Carbon & sustainability servicesFactory visits · ISO product studies · Company GHG · Verification support
Explore services →
Pricing
Company and resources
About Carbon LoopMission, story, and long-term goalsResources / BlogGuides, news, and educationContact / Custom SetupCustom platform and campaign support
Login / Sign upTalk to us
← Legal & trust centre

Responsible access

Acceptable use

Protect the shared catalogue, the people using it and the credibility of the records it holds.

Expanded 22 October 2026Applies to the scope described below

On this page

01Use authorised access02Provide honest evidence03Upload only what is needed04Represent results fairly05Respect the service and other users06Security research and automated access07Concerns and enforcement08Fair investigation and correction process09Application and policy updates
All policies →
01

Use authorised access

  • Use only the accounts, organisations and records you are authorised to access.
  • Keep passwords and API credentials private; do not publish shared keys or bypass access controls.
  • Respect the integration limits and permissions agreed for your account.
  • Report suspected unauthorised access through the support or legal contact in your agreement.
02

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.
03

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.

04

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.

05

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.

06

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.

07

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.

08

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.

09

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.

Explore the related policies

Privacy notice →Cookie notice →Website terms →Platform service terms →Carbon & recognition guidance →

Carbon Loop powered by Carbonstop

Ready to calculate promotional product carbon data?

Book a demo and see SKU data become reports, offsets, and certificates.

Talk to us
CarbonLoop logo

Product carbon software for promotional product teams.

From product data to carbon proof.

Platform

How it worksCarbon DatabaseCarbon CalculatorCarbon Credit CentrePricingLogin / Sign up

Who we help

Industry overviewSuppliersDistributorsPartnersCarbon & sustainability services

Company

About CarbonLoopResourcesRecognition & badgesContact us

Legal & trust

Trust centrePrivacy noticeCookie noticeWebsite termsService termsAcceptable useCarbon & recognition
CarbonLoop · Product carbon calculations
Offsets are purchased separately inside the platform.