Your information
Privacy notice
Understand how information relates to our website, your account and the product carbon records you choose to share.
Who is responsible
CarbonLoop is the trading name used for the product carbon software and services described on this website. The legal entity responsible for personal information and its contact details are set out below.
- Legal company name
- [Add legal company name]
- Registration
- [Add country and registration number]
- Registered address
- [Add registered address]
- Privacy & legal email
- [Add monitored email address]
Website and platform information
This notice distinguishes the public marketing website from the connected CarbonLoop platform. The current website contact and login forms are demonstrations: their submit actions show a local message and do not send the entered details to CarbonLoop. Do not enter passwords, confidential documents or sensitive personal information into preview forms.
When a connected service is introduced, the notice must be updated to identify its actual data flows before collection begins. The website also stores your cookie decision and can load consent-controlled preferences, analytics, advertising and external media. Read the cookie notice and use “Cookie settings” to control optional categories. Hosting and access providers may separately process technical information to serve and protect this website.
The information involved
| Context | Information | Purpose |
|---|---|---|
| Enquiries and support | Name, work email, company, role and the details you choose to provide. | Respond to a request, scope a quotation and manage the conversation when an enquiry channel is connected. |
| Accounts and organisations | Business contact details, organisation membership, account permissions and subscription records. | Provide the agreed service and manage authorised access in the connected platform. |
| Product and order work | SKU data, materials, manufacturing evidence, order details and delivery/warehouse addresses. | Calculate and document the agreed footprint. Avoid including names or personal delivery details where a business location is sufficient. |
| Supplier evidence | Reports, supporting files and details of reviewers or factory contacts. | Assess the source, scope and quality of a product record or separately scoped service. |
| Technical access | IP address, request metadata, browser/device details and access/security logs where recorded by the hosting service. | Deliver the website, investigate errors and protect access. Exact provider retention is to be confirmed. |
How and why information is used
The following purpose map describes the connected service policy. Where UK/EU data protection rules apply, a lawful basis is selected for the actual activity; it is not necessary or appropriate to rely on consent for every use. Information needed for a contract or legal obligation may remain necessary even if consent for an unrelated activity is withdrawn.
| Activity | Purpose and data involved | Applicable basis where UK/EU rules apply |
|---|---|---|
| Enquiries and quotations | Use business contact details and the requested scope to answer questions, arrange a demonstration and prepare a proposal. | Steps requested before entering a contract; legitimate interests in responding to a business contact where the contract is with their employer. |
| Account administration | Manage named users, organisation permissions, subscriptions, invoices and service notices. | Performance of the relevant individual’s contract, or legitimate interests in administering an organisation’s agreement; legal obligations for required records. |
| Calculation and reporting | Process supplied catalogue, evidence, project and destination data to provide the requested workflow. | Contract or legitimate interests for our own administration; documented customer instructions where we act as a processor. |
| Safety and disputes | Investigate access issues, prevent fraud, correct misuse, preserve evidence and resolve complaints. | Legitimate interests in protecting the service and establishing or defending claims; legal obligation where applicable. |
| Optional marketing | Send opted-in news or offers and manage suppression preferences. | Consent where required, or another lawful route only where applicable rules permit it. Service access is not conditional on unnecessary marketing consent. |
| Required disclosures | Respond to a lawful regulatory request or maintain records required by law. | The relevant legal obligation, with the scope limited to what is required. |
For legitimate interests, the purpose must be necessary and balanced against people’s rights and reasonable expectations. You may object where that basis applies. An objection is assessed on its circumstances; direct marketing objections must be respected. The exact local legal bases and any regulator-specific wording must be checked against the final company jurisdiction and customer markets.
Who can see catalogue and evidence information
| Information | Intended access | Safeguard |
|---|---|---|
| Discoverable supplier catalogue | Logged-in CarbonLoop users can find agreed product records under the supplier company name. | Publish only the product fields agreed in the supplier scope; maintain a clear source, version and calculation boundary. |
| Private product records and order work | The organisation and users authorised to use that workspace. | A private SKU or customer order is not automatically added to the shared supplier catalogue. |
| Supporting files and factory evidence | Authorised customer users, the service team and an expressly engaged reviewer where needed. | A discoverable footprint does not automatically expose the underlying report, production records or contact details. |
| Website API outputs | The supplier website or partner application authorised in the integration agreement. | Specify the approved fields, product mapping and display rights. API access is not permission to export the entire database. |
| Issued recognition record | Visitors following the badge’s validation link. | Limit the record to the subject, role, level, scope, assessment basis, dates and status; avoid publishing confidential evidence or personal contacts. |
Customers must identify a responsible administrator and ensure the people who upload or share records have the necessary authority. If a business address can be used instead of a person’s home address, use the business address. Address data needed to calculate a destination does not need to become part of a public badge record.
The permissions above are the policy standard for the connected platform. If a current implementation cannot enforce them, the affected sharing feature must remain unavailable until its access controls and notices match the policy.
Retention, deletion and legal holds
The schedule below is a proposed operating standard for the connected service, prepared for adoption and implementation. It does not assert that the current preview has a production retention system. A signed agreement or mandatory law may require a different period; that difference should be documented and disclosed. Records should be reviewed and removed earlier when they are no longer needed.
| Record | Proposed default | When the period runs / exceptions |
|---|---|---|
| Unconverted enquiries and quotations | 24 months after the last substantive contact. | Delete or anonymise earlier on a valid request unless a genuine dispute or other lawful need remains. |
| Active account information | For the account relationship, then up to 12 months for necessary closure administration. | Remove obsolete user access promptly; closure retention is not continued permission to market. |
| Customer-controlled uploads, order details and private SKUs | 30-day export opportunity after service end, then deletion from active systems within a further 60 days. | Subject to documented customer instructions, applicable law and a specific retention requirement. Service access during export must be agreed. |
| Routine diagnostic and access logs | Up to 90 days. | A specific incident may require a relevant extract to be retained for investigation and its resolution. |
| Rotating backups | Expiry within 90 days after removal from active systems. | Deleted information should remain isolated from ordinary use and be re-deleted if a backup is restored. This interval requires technical validation. |
| Invoices, tax and contractual records | For the period required by the applicable law. | Keep only the necessary record; confirm the jurisdiction-specific period before launch rather than assuming a universal number. |
| Issued recognition and supporting assessment records | During validity, with a proposed 24-month post-expiry review period for essential validation history. | Confidential evidence and personal information should be minimised; a withdrawn status may need to remain visible to prevent a misleading badge claim. |
| Marketing suppression record | A minimal record while needed to respect the opt-out. | Do not reuse the suppression list as a marketing audience. |
A legal hold must identify the reason, relevant records, access restrictions and review date. It should not preserve all account information indefinitely. When a hold ends, the ordinary deletion schedule applies. Deletion may involve anonymisation where the result can no longer identify a person; removing a public listing alone does not delete backups or legally required records.
Protection and incident handling
The service policy requires proportionate safeguards for the information and risks involved: role-based access, limited administrative permissions, secure handling of credentials, appropriate protection in transit and at rest, tested recovery procedures, access logging and confidentiality obligations. Customers must also manage their users, devices and integration credentials responsibly.
A suspected breach should be assessed promptly to establish the information involved, likely impact, containment and recovery steps. Where CarbonLoop is a processor, the affected customer controller should be informed without undue delay after awareness, with further information as it becomes available. Regulatory and individual notifications depend on the applicable role, law and risk; the agreement cannot remove statutory notification duties.
A report should identify the affected account or record and a way to contact you. Do not publish vulnerabilities, credentials or another customer’s data in a support message or public post. No system can guarantee absolute security.
AI, automated calculations and personal information
Carbon calculations and any AI-assisted extraction should be treated as tools requiring review. A calculated result or suggested data field may be incomplete or wrong. Keep the source, review assumptions and correct material errors before publishing a report.
Do not include unnecessary personal information or confidential third-party documents in an AI-assisted workflow. An AI provider may only receive customer information under a disclosed and authorised processing arrangement. This notice does not grant permission to train a general-purpose model on customer uploads.
Business users and information about children
CarbonLoop’s product carbon services are intended for business and professional use, not for use by children. Do not upload children’s personal information, sensitive personal information or unrelated employee records as product evidence. If such information is discovered, restrict access while the appropriate deletion, correction or other lawful response is assessed.
Your rights and how to make a request
Depending on the applicable law, you may ask for access to your personal information, correction, deletion, restriction of processing, objection, or a portable copy of information covered by a portability right. You may withdraw consent for future consent-based processing; this does not invalidate lawful processing before withdrawal. Rights are not absolute and may be limited by another person’s rights, a legal obligation or a valid exemption.
- You can use the privacy/legal email listed above; a request made through another legally valid channel must also be recognised. Include the organisation, relevant account or record, the action requested and a safe reply address.
- We should ask only for information reasonably necessary to confirm identity and authority. Do not send passwords, API keys or identity documents with an initial request.
- If the information is controlled by your employer or another customer organisation, contact its administrator as well. A processor should assist that organisation rather than independently changing its instructions.
- Where UK/EU access-right rules apply, the ordinary response period is one month; a lawful extension may be available for complex or multiple requests, with notice and reasons as required. Elsewhere, the applicable statutory period takes priority.
- A request should normally be handled without charge. A refusal or permitted fee needs an applicable legal basis, an explanation and information about available complaint routes.
- An access request concerns your personal information. It does not automatically entitle someone to another customer’s confidential product data, source files or trade secrets.
The operational target is to acknowledge a request within five business days and keep a record of the decision and any correction. This target does not extend a legal deadline. If you are dissatisfied, ask for a privacy review and you may complain to the competent data protection authority in the jurisdiction that applies. The company and regulator details remain to be completed.
Changes and related notices
For further information on UK access-request timing, see the ICO guidance on response periods. The notice should be reviewed whenever data collection, providers, visibility or services change. Material changes should be communicated through an appropriate website or account notice. See the cookie notice for browser technologies and service terms for account and data responsibilities.
