Last Updated: August 7, 2026
This page sets out the additional terms that apply to CarbonGuru accounts with Embedded Offsetting enabled. It supplements our Terms of Service and Privacy Policy, which continue to apply in full.
13. Merchant Embedded Offsetting
If you enable Embedded Offsetting on your CarbonGuru account, this section applies to you in addition to the rest of these Terms.
13.1 What you’re enabling. Embedded Offsetting lets you display CarbonGuru-calculated carbon footprints on your own store’s product pages using a snippet you install, and — if you choose — automatically purchase carbon offsets or removals for your customers’ orders, billed to the payment method on file for your CarbonGuru account. You control which products are covered, which project portfolio is used, and what your product pages display.
13.2 Your responsibilities. You are responsible for: installing and maintaining the snippet correctly on your own storefront domain; only ever pointing the snippet at pages on the domain you registered with us; keeping a valid payment method on file for the purchases you’ve enabled; and making sure any claims your store makes about carbon offsetting to your own customers are accurate and not overstated. CarbonGuru is not responsible for how you describe or market Embedded Offsetting to your customers.
13.3 How we read your product pages. To calculate footprints for your catalog, CarbonGuru operates an automated fetcher, CarbonGuruBot, that reads product pages on your registered domain only, honors your site’s robots.txt, and identifies itself honestly (see our CarbonGuruBot page for its user-agent string and IP addresses). You can stop CarbonGuruBot at any time by disconnecting Embedded Offsetting from your account.
13.4 Purchases are final. Purchases made through Embedded Offsetting follow the same rule as every other CarbonGuru purchase (see “Carbon Offset and Removal Purchases” in the Terms of Service): once carbon credits are retired on a registry, the purchase is non-refundable. This applies whether the purchase was initiated by you, by your store’s checkout flow, or automatically through your webhook integration.
13.5 Fees. Embedded Offsetting is included with qualifying CarbonGuru account tiers (currently Plus and above) and carries its own facilitation fee structure and catalog limits, described in your account dashboard and merchant setup guide, not repeated here because they are pricing terms we may adjust — see your account for current figures.
13.6 Shopper data. CarbonGuru acts as a data processor with respect to your customers’ data in connection with Embedded Offsetting, on the terms set out in the Embedded Offsetting Data Processing Addendum below. That addendum is incorporated into these Terms for merchant accounts with Embedded Offsetting enabled.
13.7 Termination. You may disconnect Embedded Offsetting at any time from your account settings. Doing so stops CarbonGuruBot from visiting your store, stops new purchases, and does not affect purchases already made (§13.4). We may suspend Embedded Offsetting for a store that violates “Acceptable Use” of these Terms, including attempts to point the snippet or API at domains you have not registered.
CarbonGuru Embedded Offsetting — Data Processing Addendum
Last Updated: August 7, 2026
This Data Processing Addendum (“DPA”) forms part of the CarbonGuru Terms of Service for any merchant account with Embedded Offsetting enabled. It describes how CarbonGuru processes data in connection with that feature.
1. Roles
For data about your own customers (“shoppers”) arising from their visits to your store, you are the controller and CarbonGuru is the processor, acting only on your instructions as set out in this DPA (namely: displaying a carbon footprint and, where you’ve enabled it, offering and fulfilling a carbon offset or removal purchase). For data about you as a merchant (your account, your catalog, your payment method), CarbonGuru is the controller, governed by the main Privacy Policy, not this DPA.
2. Processing is limited to serving the embed
CarbonGuru processes shopper-related data solely to: (a) serve a footprint and, if enabled, an offset/removal price for the page a shopper is viewing on your store; (b) let a shopper complete an offset/removal purchase you’ve configured; and (c) calculate and retire the corresponding carbon credits. CarbonGuru does not use this data for any other purpose — not advertising, not profiling shoppers, not building shopper-level histories, and not sharing it with any party except the sub-processors named in §4.
3. What CarbonGuru actually receives about a shopper
Per product page view, a shopper’s browser sends CarbonGuru exactly two kinds of fields about your store and its pages: your store’s publishable handle, and the page URL(s) your store’s template printed (the product page being viewed, and any product tiles on it), together with a protocol version number. Never page content, and never anything the shopper typed. The display exchange is stateless and cookieless — CarbonGuru sets no cookie and stores no identifier that could tie one shopper visit to another, on your store or anywhere else. CarbonGuru does not know who your shoppers are, does not receive their name, email, or account information, and does not run any analytics on the pages it serves to your shoppers.
If a shopper completes a purchase, CarbonGuru additionally processes the order data your store sends via your webhook or receiver integration (order line items, amounts, and — if you use the confirmation snippet — an order attribution token) strictly to create and fulfill the corresponding offset/removal purchase and bill your CarbonGuru account. This order data is retained as your account’s transaction history, the same as any other CarbonGuru purchase.
4. Catalog acquisition — what’s retained, and why it’s different from shopper views
To calculate a footprint for a product on your store, CarbonGuru’s automated fetcher (CarbonGuruBot, see our CarbonGuruBot page) reads that product’s own page once, at your instruction (Embedded Offsetting enabled + your domain registered), and stores the resulting product-level catalog record — the product’s URL and the carbon footprint calculated from it. This is retained as long as the product stays in your catalog; it is not a record of any individual shopper’s visit, and it is captured once per product, never once per page view. CarbonGuruBot’s fetches are logged in CarbonGuru’s standard learning-system infrastructure on the same terms as any other page CarbonGuru’s analysis pipeline processes — used only to build and maintain the extraction/analysis pipeline itself, never resold, and never used to build a profile of your shoppers (it has none to build one from — see §3).
5. Sub-processors
CarbonGuru uses the same sub-processors disclosed in the main Privacy Policy “Data Sharing” section: AI service providers (to identify products from fetched page content), and carbon offset/removal fulfillment providers (currently CNaught and Stripe Climate) to retire credits against the purchases you’ve enabled. Payment processing for your own CarbonGuru account billing is handled by Stripe and PayPal, as described in your merchant account terms. None of these sub-processors receive shopper identity — only what §3 describes CarbonGuru itself receiving.
6. Security
All traffic to and from the embed is encrypted via HTTPS. Your publishable handle is read-only and cannot authorize purchases or access your account; your server-side API key (used only for your own integration, never sent to a shopper’s browser) is hashed at rest and can be rotated independently. Display requests are rate-limited using short-lived, salted, non-reversible identifiers — never a shopper’s raw IP address stored anywhere.
7. No refunds
As set out in the Terms of Service (“Carbon Offset and Removal Purchases”, extended by §13.4 for merchant purchases), once a carbon credit is retired against a purchase made through Embedded Offsetting, that purchase is final. This DPA does not create any refund right beyond what the Terms provide.
8. Your rights and obligations as controller
You remain responsible for your own store’s compliance obligations to your shoppers (for example, any disclosure your jurisdiction requires about third-party services used on your site). CarbonGuru will provide reasonable assistance responding to a verified data subject request from one of your shoppers about data described in §3 — in practice, because CarbonGuru holds no shopper identity, most such requests will have nothing to locate.
9. Term
This DPA applies for as long as Embedded Offsetting is enabled on your account and terminates automatically when you disconnect it (§13.7 of the Terms). Catalog records described in §4 persist as ordinary catalog data after disconnection, the same as any other product you remove from active processing, unless you request deletion.
10. Contact
Questions about this DPA: support@carbonguru.io.