Accounts & services
Platform service terms
A clear scope for what your account does, how data is shared and which services need a separate agreement.
Formation, documents and agreed scope
A service order requires an identified contracting entity, an authorised customer representative and a clear written acceptance or connected checkout process. The marketing site’s preview forms do not create that order. No paid work should begin merely because a person views a plan, requests a quotation or tests a demonstration.
The proposed agreement consists of the accepted order or statement of work, any signed amendments, applicable data-processing schedule, these service terms, and any specifically incorporated policy. A negotiated provision should prevail over inconsistent standard wording only to the extent of that inconsistency. Data-protection obligations take precedence for personal-information handling, and mandatory law always takes priority.
- The order identifies the parties, service start, subscription or project term, price/currency/tax treatment and payment schedule.
- The scope identifies account roles, included capacity, product range, calculation boundary, deliverables, assumptions and dependencies.
- The order identifies any API access, specialist work, independent verification, credits or support commitment that is actually included.
- Changes to scope, fees or timetable require an agreed written change; a conversation about a possible feature is not automatically a committed deliverable.
Account roles and calculation boundaries
| Role | Service scope | Boundary or agreement |
|---|---|---|
| Supplier / factory | Manage a catalogue and its CO₂e data, make agreed product records discoverable to logged-in CarbonLoop users, and optionally connect the supplier website. | Factory gate or FOB, as agreed. Supplier pricing is a custom quotation. A distributor account is required for calculations beyond that supplier boundary. |
| Distributor / end user | Calculate projects, product quantities and delivery routes, including an agreed final warehouse destination; prepare reports and optional credit records. | The selected plan, project inputs, transport stages and stated report boundary. |
| Partner | Connect a platform, organisation or network to CarbonLoop for an agreed group of users or workflow. | Separate partnership/API scope, permissions, usage and commercial terms. |
How platform allowances are counted
| Allowance | Counting approach |
|---|---|
| Users | Named users authorised within the organisation. Do not share credentials to evade the plan’s user limit. |
| Active projects | Only open projects count under the published plan description; locked, completed and archived projects do not count as active. |
| Calculation credits | The pricing page describes one credit for a PDF/AI calculation or a SKU calculation using new or changed data. Confirm the event before processing; exporting an existing result is not automatically a new calculation. |
| Private SKUs | A product added to the private library counts as one SKU, including an incomplete record, as described on the pricing page. |
| API requests | The agreed endpoint request and rate limits apply. Specify handling of failed calls, retries and any bulk endpoint in the API schedule. |
| Reset and carry-over | The accepted plan must identify the billing/reset date and whether unused allowances carry over. No carry-over or paid overage is assumed where it is not stated. |
If a limit is reached, the service should explain the affected action and available choices before a paid change. Usage corrections and disputed metering should be reviewed against the relevant logs. Do not change counting rules retroactively to create an unexpected charge.
Your data and permissions
You must have authority to upload product data, supplier reports, contact details and supporting evidence, and to grant the use and sharing agreed for the service. Provide accurate inputs, identify estimates and update records when the product or evidence changes. Retain your source records.
Customer materials remain subject to their owners’ rights. The service agreement should grant only the rights needed to store, process, calculate, display and share agreed data. It must distinguish discoverable catalogue fields from confidential documents. Independent reports must identify the verifier, scope, date and any restrictions on reuse; submitting a report does not automatically give every product verified status.
The customer authorises processing only as necessary for the agreed service and visibility choices. CarbonLoop must not sell customer-controlled personal information or treat a confidential upload as a general public-data licence under these proposed terms. Derived calculations and shared product fields require a clear permitted-use scope; removal of a catalogue listing and deletion of its underlying evidence are separate actions.
A corrected input may require a new calculation and report version. Keep the earlier result’s context where an audit trail is necessary, rather than silently overwriting the evidence behind an already issued claim. A customer requesting deletion must identify whether it seeks to remove a listing, revoke access, delete personal information or end the service.
Customer data-processing schedule
Where CarbonLoop processes personal information on behalf of a customer, a data-processing agreement should apply before the processing starts. The following schedule describes the intended scope; it must be tied to the actual order and provider schedule.
| Schedule item | Scope / obligation |
|---|---|
| Subject and duration | Product carbon calculation, catalogue/order management, evidence handling and reporting for the agreement term and documented closure/retention period. |
| Data subjects and information | Customer users, business contacts and any individuals identified in authorised delivery or evidence records; contact/account details and necessary order/address/evidence information. Special-category data is outside the ordinary scope. |
| Instructions and purpose | Process only documented lawful instructions, including agreed catalogue/API visibility. Notify the customer if an instruction appears to breach applicable data-protection law. |
| People and safeguards | Bind authorised personnel to confidentiality and apply risk-appropriate technical/organisational safeguards described in the actual security schedule. |
| Subprocessors | Use an identified authorised list, apply equivalent relevant obligations and give the agreed notice and opportunity to object to material changes. The actual list is still required. |
| Rights and assessments | Assist proportionately with individual-rights requests, security assessments and applicable impact assessments, considering the processing and available information. |
| Incidents | Notify the customer without undue delay after awareness of a personal-data breach, provide available facts in stages and cooperate on containment and legally required notices. |
| End of processing | Return or delete customer-controlled data under the agreed export/deletion policy unless law requires retention; document any exception and keep it protected. |
| Accountability | Provide reasonable information to demonstrate compliance and allow proportionate agreed audits without exposing another customer’s data or compromising security. |
| Transfers | Identify locations and implement the applicable transfer mechanism and assessment before any restricted international transfer. |
Confidentiality and intellectual property
Each party should protect non-public information received in connection with the service and use it only for the agreed purpose. Disclosure is limited to authorised people and providers who need it and are bound by suitable obligations. Information is not confidential merely because it has been supplied if it was already lawfully public, independently developed or lawfully obtained without a confidentiality duty.
If disclosure is legally required, limit it to what is required and notify the other party where lawful. Return or delete confidential materials on service end according to the agreed retention and legal-hold rules. Necessary retained copies remain protected.
Customers retain their rights in uploaded product, business and evidence materials. CarbonLoop and its licensors retain their rights in the software, methods, templates, brand and underlying licensed datasets. The customer receives the agreed right to use reports and outputs for its business, subject to third-party source licences and fair carbon-claim presentation. No customer-logo marketing permission or exclusivity is implied.
Calculations and evidence
A footprint is an estimate based on its functional unit, boundary, data, factors and method at a stated time. Factory-gate, FOB and delivered footprints cover different stages and should not be compared without matching scope. Results may change when inputs or methods change. Users must review outputs before using them in customer or public claims.
Software calculations, evidence review, an on-site visit, a formal ISO-aligned study and independent verification are distinct activities. Only the work specifically commissioned and evidenced is included. A CarbonLoop account or badge does not itself constitute ISO certification.
Factory, ISO/GHG and API services
Factory evidence collection, product footprint studies, company GHG inventories and verification preparation require a written scope. Agree the site(s), reporting period, applicable standard, evidence access, responsibilities, timetable and deliverables. An independent assurance or certification body’s decision remains its own.
Website API work requires agreed identifiers, authentication, authorised fields, calculation endpoints, usage limits, update rules and integration responsibilities. Keep API credentials private. No availability commitment, compatibility guarantee or public-data licence is implied before it is agreed.
Delivery, review and changes to specialist work
For factory visits, product studies, company GHG inventories and verification preparation, agree the site or entity, products, reporting year, functional unit, boundary, applicable method/standard, evidence requirements, milestones and deliverables. The customer should arrange authorised access and identify safety or confidentiality constraints before a visit. The team must follow agreed site rules and may reschedule unsafe or unauthorised work.
A deliverable should identify its source data, assumptions, exclusions and review status. The proposed review process gives the customer ten business days to identify material departures from the agreed scope, with enough detail to assess them. The team should correct an agreed in-scope defect or explain the finding. Silence alone does not turn an unverified study into an independently verified one or waive mandatory rights.
New products, additional sites, missing source data, changed boundaries and a new reporting period may require a written scope/timetable change. Independent verification, certification or registry decisions are made by the relevant body, not guaranteed by CarbonLoop. A factory inspection is evidence collection within its scope, not a guarantee of all factory practices.
API and integration conditions
- Document the authorised website/application, endpoints, product identifiers, request/response fields, units, boundary indicators and evidence-status fields.
- Use assigned authentication, protect keys in an appropriate server-side environment and rotate/revoke them on suspected compromise. Do not embed a confidential key in public browser code.
- Respect agreed rate and request limits. Use bounded retries and do not generate repeated calls that unnecessarily load the service.
- Display the date, unit, boundary and material limitations needed to understand a result. Do not remove evidence status or present a stale response as a newly verified result.
- Agree caching, permitted retention and how updates, corrected records and revoked permissions reach the customer website. Availability of a product record does not grant unrestricted redistribution rights.
- Document integration testing, error handling, customer/provider responsibilities and any deprecation notice in the scope. No backward-compatibility or uptime guarantee is created without that agreement.
An API connection does not expand a supplier footprint beyond factory gate or FOB. Downstream project calculations require the appropriate distributor workflow and its inputs.
Subscriptions, trials, fees and payment
The distributor pricing page currently describes Basic, Professional and Enterprise plans with a seven-day free trial, monthly or annual billing, and an Enterprise+ custom scope. The plan summary and accepted order must show the current price, currency, included users, project capacity, calculation allowance, private SKU allowance and any API limit. Supplier/factory accounts and partnerships are individually quoted.
- Show the total payable amount, applicable tax treatment, billing period and any mandatory fee before acceptance. Do not add an unrequested paid module or recurring charge.
- A free trial starts on the activation date stated in the account confirmation. Explain any trial limits and what happens to entered data when it ends. A trial must not convert to a paid plan unless the customer has expressly accepted the conversion, charge and renewal arrangement.
- Annual plans are billed upfront only where the customer chooses annual billing. State the actual annual total and savings rather than presenting an annual commitment as a cancellable monthly price.
- Renewal is automatic only if the accepted order clearly says so. State the renewal period and cancellation deadline before acceptance. Proposed policy: send an annual-renewal reminder at least 30 days in advance and notify material renewal price/term changes before the customer must decide.
- An allowance is not a transferable carbon credit. Additional usage or add-ons require the agreed capacity and price; do not silently charge for exceeding a limit.
- Where an invoice is disputed in good faith, notify the billing contact promptly with the disputed amount and reason. Both sides should work to resolve it; undisputed amounts remain due under the order.
- Failed payment should trigger a notice and a reasonable opportunity to correct it. No late interest, collection fee or acceleration applies unless expressly agreed and lawful.
Carbon credits, factory visits, formal studies, verification-body fees and custom integration are separate charges unless the order expressly includes them. A subscription does not guarantee a particular carbon-credit price or availability.
Cancellation, refunds and changing plans
The proposed cancellation policy allows a customer to give written notice through the billing/support contact or an available account cancellation control before the next renewal. Confirm receipt and the effective date. Cancellation stops future renewal; access normally continues through the paid period unless an earlier closure is requested or lawful suspension applies.
- Do not require a telephone conversation or sales approval as the only way to stop renewal. Identify who is authorised to cancel an organisation’s account.
- A change in team size or usage does not automatically cancel a plan. Upgrades, downgrades, prorating and when new limits apply must be shown before the change is accepted.
- Unused subscription time is not automatically refundable solely because the customer stops using the service, but mandatory remedies, an expressly agreed refund, erroneous charges and service-failure rights remain available.
- If CarbonLoop ends a prepaid service for convenience and no equivalent agreed service is supplied, the proposed policy is a proportionate refund for the unused portion. This does not limit other mandatory remedies.
- For separately scoped work, cancellation charges should reflect completed work and documented unavoidable commitments, subject to the order and law; do not charge the entire remaining project fee automatically.
- Credit orders have separate project/registry and retirement terms. Once units are retired, retirement generally cannot be treated as an ordinary subscription reversal; explain any irreversible step before purchase and preserve applicable statutory rights.
No policy excludes a refund, repair, repeat performance, compensation or other remedy that the law requires. The final commercial agreement should make the applicable remedies and claim process easy to find.
Credits and recognition
Calculating emissions does not purchase or retire credits. A credit claim requires evidence of the relevant project, quantity, retirement and allocation; do not count the same retirement twice. Credits are separate from reducing emissions within the reported activity.
Recognition must relate to its named product, company or organisation, level, period and evidence. Only an issued badge linked to its live recognition record should be displayed as a credential. Follow the carbon and recognition guidance; a sample asset grants no award or endorsement.
Support, complaints and service changes
Use the support route in your order and identify the account, affected action, time and relevant error or record reference. Never send passwords or full API secrets. Priority support, training, account management or 24/7 coverage applies only where included in the accepted plan or scope; no specific resolution time is inferred from the word “priority”.
The proposed ordinary complaint targets are acknowledgement within five business days and a substantive response or progress update within 15 business days. Complex evidence disputes may take longer, with reasons and an expected next update. Privacy and statutory requests retain their own deadlines. Escalate unresolved matters to the designated complaints contact before an agreed independent dispute route, without restricting a right to approach a regulator or court.
Maintain a clear notice for material changes to a paid service, renewal term or price. Do not retrospectively remove an agreed deliverable or materially reduce a prepaid service without the contractual remedy and any required customer choice. Emergency changes needed for security or law should be explained as soon as practicable.
Suspension, termination and data exit
A proportionate restriction may be necessary for a credible security threat, unlawful activity, material misuse, repeated non-payment after notice or a material contract breach. Where safe and lawful, explain the reason, affected functions and steps to remedy it before suspension. Urgent protective restrictions may precede notice; review them promptly and keep unaffected access available where practicable.
For a remediable material breach, the proposed default is written notice and 15 business days to remedy, unless the law or agreed scope requires otherwise or the risk makes that period unreasonable. A disputed good-faith complaint should not itself trigger retaliation or deletion. Termination and any refund must follow the agreement and mandatory law.
The proposed exit procedure provides a 30-day opportunity to request an agreed export of customer-controlled data after service end, subject to lawful verification and any necessary secure access. Specify file formats, attachments, calculation metadata and any one-off extraction cost in advance. Do not promise that another platform can import the export without its own conversion work.
After the export window, remove customer-controlled records from active systems within a further 60 days under the proposed retention schedule, with backups expiring within 90 days after active deletion. Required financial records, legal holds and limited credential-status history may need separate retention. These intervals require implementation before becoming effective. A withdrawn badge may retain a minimal status record to prevent misrepresentation.
Confidentiality, valid payment obligations for work already supplied, lawful record retention and other provisions intended to survive continue for their proper scope. Closing a subscription does not reverse a carbon-credit retirement.
Responsibility, remedies and disputes
Both parties should exercise reasonable care in the obligations they undertake. The customer is responsible for the inputs, permissions and claims it controls; CarbonLoop remains responsible for the work and obligations it agrees to provide. An input-data limitation does not excuse a failure to perform an agreed review or correction.
Carbon estimates have methodological and data uncertainty. That uncertainty must be communicated with the output; it is not a blanket exclusion of responsibility. A verification body’s independent decision is outside CarbonLoop’s control, but commissioned preparation work must still match its agreed scope.
The ACCC contracts guidance explains why Australian mandatory rights cannot be removed by contract; other markets have their own protections. Nothing excludes a mandatory guarantee, remedy or liability that cannot lawfully be limited, including applicable consumer or small-business protections. No blanket “all sales final” rule, unlimited customer indemnity or arbitrary unilateral right to change a signed agreement is introduced here. Any negotiated liability cap or specific indemnity must be fair, lawful and expressly stated in the signed agreement; none is silently assumed in these pages.
The proposed process is direct discussion, a written complaint and, where agreed, independent mediation before litigation, except for urgent protective relief or rights that cannot be delayed. Governing law, contracting entity and court/forum details remain legal-entity fields to complete.
