Fixed prices, paid once·Written replies within one working day
CheckoutLoom.

Marketing and retentionWin shoppers back

View all marketing →

Support and order careAnswer faster

View all support →

Product contentBetter listings

View all product content →

Inventory and pricingPrices and suppliers

View all inventory →

Finance and riskMoney and disputes

View all finance →

Shopify and WooStore-specific

View all services →

Dropshipping and EtsyMarketplaces and print

View all services →

Explore everything

Pick a way in. Every page has a fixed price and a delivery window.

All services88 automations for storesAll platformsShopify, WooCommerce and moreAll integrations82 tools we connectRequest a quote →

ShopifyStore platform

View all Shopify →

WooCommerceStore platform

View all WooCommerce →

BigCommerceStore platform

View all BigCommerce →

WixStore platform

View all Wix →

AmazonMarketplace

View all Amazon →

EtsyMarketplace

View all Etsy →

eBayMarketplace

View all eBay →

Your platform

Automation built for the store or marketplace you already sell on.

Store platforms8 platformsMarketplaces11 marketplacesAll who we serve363 pagesRequest a quote →

DropshippersSeller type

View all dropshippers →

DTC brandsSeller type

View all dtc brands →

Handmade sellersSeller type

View all handmade sellers →

Subscription boxesSeller type

View all →

B2B and wholesaleSeller type

View all b2b and wholesale →

AgenciesSeller type

View all agencies →

PrintfulPrint-on-demand

View all Printful →

Your kind of store

Pages written for how each type of seller actually works.

Seller types14 types of sellerPrint-on-demand9 platformsPopular audiences20 moreRequest a quote →

Email and SMSKlaviyo, Mailchimp and more

View all email and sms →

Support and chatGorgias, Zendesk and more

View all →

Payments and accountingStripe, QuickBooks and more

View all →

Shipping and suppliersShipStation, DSers and more

View all →

Reviews, ads and creativeJudge.me, Meta Ads and more

View all →

Automation and dataZapier, Make, Sheets

View all →

Marketplace and feed toolsGoogle Merchant, Helium 10

View all →

Works with your tools

We build inside the apps you already pay for.

All integrations82 toolsEmail and SMSKlaviyo, MailchimpPaymentsStripe, QuickBooksRequest a quote →

How-to guidesStep by step

View all 63 how-to guides →

Templates and checklistsCopy and use

View all 68 templates →

ComparisonsTools and options

View all 44 comparisons →

Cost and ROIWhat it costs

View all 34 cost pages →

GuidesLong reads

View all 14 guides →

Compliance and riskRules in plain words

View all →

Glossary and statisticsTerms and numbers

View all 17 →

Learn before you buy

Guides, templates and honest comparisons, free to use.

Resources hub256+ free resourcesBlogPractical articlesStatisticsSourced numbersRequest a quote →
Data processing agreement

How we handle your shoppers’ data when we build inside your store

When we build inside your store, we touch data about your customers. This agreement explains who is responsible for what, what we do with that data, how we protect it and what happens when the project ends.

  • Written in plain English
  • A summary above every section
  • Updated when our practice changes
You decideWe protectWe delete
The roles

Who does what with your shoppers’ data

Data protection laws give different jobs to different parties. These six points explain ours in everyday language.

  • You are the controller

    Your shoppers’ data belongs to your business. You decide why and how it is used, and you remain responsible for it.

  • We are the processor

    We handle that data only on your instructions, and only to build, test and run what you ordered.

  • We secure it

    Private storage, least-access permissions and encrypted connections protect the data, as the security page describes.

  • Subprocessors are listed and bound

    The providers we use are described below, and each one is bound to protections equal to ours.

  • You hear about breaches fast

    If personal data in our care is compromised, we tell you within seventy-two hours of becoming aware, with the facts we have.

  • We delete when you finish

    We remove your shoppers’ data from our systems ninety days after the project closes, or sooner if you ask.

01

Scope and roles

In plain EnglishYou decide how shopper data is used, and we process it only on your behalf.

This agreement applies when Checkout Loom processes personal data about your customers, such as names, email addresses, order details and conversation history, while building or running an automation in your store. For that data, your business is the controller and Checkout Loom is the processor. For data about you and your team, we are the controller, and our privacy policy applies instead.

02

What we process, and why

In plain EnglishWe process shopper data only to deliver the automation you ordered.
  • Subject matter and purpose: building, testing, launching and supporting the automation described in your order.
  • Types of data: contact details, order and cart information, customer conversations, marketing consent status and, where your service needs it, payout and dispute records.
  • Who the data is about: your customers and prospects, and your suppliers where order routing is involved.
  • Duration: the length of the project plus ninety days, unless you ask us to delete sooner.
03

Our commitments

In plain EnglishWe follow your instructions, keep the data confidential and help you meet your own duties.
  • Process the data only on your documented instructions, which include your order, your brief and your messages in the client portal.
  • Make sure that everyone on our team who can see the data is bound to confidentiality.
  • Help you respond to requests from your shoppers about their data, for example to see or delete it.
  • Help you meet your own duties about security, breaches and impact assessments, within reason and on request.
  • Tell you if we think one of your instructions would break data protection rules.
04

Security

In plain EnglishWe protect the data with technical and organisational measures that suit its sensitivity.

We use encrypted connections, private storage, least-access permissions, individual accounts with strong authentication and activity logging. Access to shopper data is limited to the team members working on your project. The security and access page explains how we request, use and remove access.

05

Subprocessors

In plain EnglishWe use a short list of providers, and we bind each one to the same level of protection.

To deliver our services we use providers in these categories: cloud hosting and storage, email delivery, helpdesk and messaging tools, AI model providers used to draft copy and replies and payment processing for our own billing. Each provider processes data only for the purpose we give it and is bound by terms that protect it. We tell you before we add a provider that would handle your shoppers’ data, and you may object if you have a reasonable concern.

06

International transfers

In plain EnglishWhere data moves across borders, we use safeguards that travel with it.

If shopper data is processed in another country, we rely on recognised safeguards, such as approved contractual clauses, and we choose providers that commit to them.

07

Breaches

In plain EnglishWe tell you within seventy-two hours of becoming aware of a breach affecting your shoppers’ data.

If we become aware of a security incident that affects personal data we process for you, we notify you without undue delay and in any case within seventy-two hours. We tell you what happened, which data is affected, what we have done and what you may need to do, and we keep you informed as we learn more.

08

Audits and questions

In plain EnglishYou can ask us how we protect the data, and we answer honestly.

On request, we provide the information reasonably needed to show that we are following this agreement, and we cooperate with reasonable questions from you or your regulator. For anything involving a detailed audit, contact us through the contact form so that we can agree how to do it without disrupting your project.

09

Return and deletion

In plain EnglishWhen the project ends, we delete your shoppers’ data and confirm it.

Ninety days after your project closes, or sooner if you ask, we delete the personal data we hold for you, including copies and backups in the ordinary cycle, and confirm in writing that we have done so. We may keep data we are required by law to keep, and we tell you what and why.

10

Changes

In plain EnglishWe update this agreement when our practices or providers change, and we tell you about important changes.

If a change affects how we handle your shoppers’ data in a significant way, we tell you before it takes effect and give you a chance to raise a concern.

Questions

Questions people ask about this policy

Does this apply to every project?

It applies to any project where we handle personal data about your customers, which includes most of our services. It sits alongside the terms of service and forms part of them.

Do I need to sign it?

No. Ordering a build means the agreement applies, and it is available on this page at any time. If your business needs a signed copy, ask through the contact form.

Which AI providers see my shoppers’ data?

Only the providers needed to draft copy and replies inside your build, and only for that purpose. We do not allow providers to use your shoppers’ data to train their public models.

How do I get my shoppers’ data deleted?

It is deleted ninety days after the project closes, or sooner when you ask. We confirm the deletion in writing.

What happens if there is a breach?

We tell you within seventy-two hours of becoming aware, with the facts we have, and keep you informed as we learn more.

Who is the controller and who is the processor?

You decide why and how your shoppers’ data is used, which makes you the controller. We process it only to build and support your automation.

Do you use sub-processors?

We use a small set of named providers for hosting, email and AI. The list is available on request and we tell you before we add a new one.

Where is the data stored?

In the regions of the platforms you already use. We build inside your tools, so shopper data mostly stays where it already lives.

How long do you keep shopper data?

Only while we need it for your project and any support period, and then we delete it or return it as you ask.

Can I audit how you handle data?

You may ask us to describe our handling in writing, and we answer plainly. Our security practices page sets out the controls we follow.

Need something specific for your business?

If your business requires particular terms or a signed copy, tell us and we will work it out with you.

  • Breach notice within 72 hours
  • Deletion after ninety days
  • Providers bound by the same terms