Skip to content
CartAbandon

Abandoned cart recovery security, built for the people who sign off

CartAbandon keeps abandoned cart recovery secure by encrypting shopper contact data and store tokens at rest, encrypting all traffic in transit, asking for the smallest store permissions it needs, and never touching card data. Consent records, a DPA in the panel and data deletion are included on every plan.

Ecommerce director comparing a printed revenue report with figures on her second monitor

Your shoppers' data stays protected at every step

A recovery tool holds sensitive things: shopper emails and phone numbers, cart contents and access to your store. This page explains how we handle each of them. It is written for founders, finance leads, IT and anyone who has to approve a new tool.

Area What CartAbandon does Plan
Data at rest Shopper contact data and store access tokens are encrypted All plans
Data in transit All traffic uses encrypted connections (TLS) All plans
Store access Least-privilege scopes, only what recovery needs All plans
Card data Never stored or processed by CartAbandon All plans
Consent Source and timestamp per contact and channel All plans
DPA Available to sign in the panel All plans
Team access Roles for team seats Scale and Plus
SSO SAML single sign-on Plus
Audit log Record of who changed what Plus
Data residency Choice of EU or US Plus
Uptime SLA of 99.9 percent Plus

Encryption protects contact data and store keys

Shopper emails, phone numbers and other contact fields are encrypted at rest in our database. The access tokens that let CartAbandon read your store are encrypted too. A copy of the database on its own does not reveal them.

Every connection is encrypted in transit: between your store and our servers, between your browser and the panel, and between our servers and the providers that deliver messages.

CartAbandon asks for the smallest store access it needs

When you connect a store, CartAbandon requests only the permissions recovery needs: carts and checkouts, orders, customers and consent fields, products and stock levels, and discount creation for unique single-use codes.

  • Shopify connects through app install with OAuth. You see the scopes before you approve.
  • WooCommerce connects with REST API keys you create in your admin. You choose the key permissions.
  • Magento (Adobe Commerce) connects with an integration token with the resources you allow.

You can disconnect at any time from your store admin or from the CartAbandon panel. Setup steps for each platform are on the integration pages, starting with the Shopify abandoned cart app.

Card data never touches CartAbandon

CartAbandon does not see, store or process card numbers. When a payment fails, the recovery message contains a secure link back to your store's own checkout or your payment operator's page. The shopper updates the card there. We only receive the fact that a payment failed and the decline code, which the failed payment recovery flow uses to pick the right message.

Your team gets the right access and nothing more

  • Roles. On Scale (5 seats) and Plus (unlimited seats), each person gets a role. A copywriter can edit messages without changing discount guardrails or billing.
  • SSO with SAML. On Plus, your team signs in through your identity provider. When someone leaves, removing them there removes their access.
  • Audit log. On Plus, every change to flows, guardrails, roles and settings is recorded with the person and time.

Consent and privacy are built into every send

Marketing email, SMS and WhatsApp go only to people with a recorded consent. For each contact and channel we store where consent came from and when. That record is visible in the panel next to every send.

  • One-click unsubscribe in every email
  • STOP keyword handling for SMS
  • WhatsApp opt-out
  • Quiet hours by the shopper's time zone
  • Transactional payment-failure notices kept separate from marketing

The rules follow GDPR, TCPA, CAN-SPAM and CASL. Your store remains responsible for how it collects consent, and CartAbandon respects what you collected.

No ad pixels, no cookie banner

The storefront script uses only first-party, strictly necessary identifiers. It fires no ad pixels. That is why it does not need a cookie banner.

We describe our processors by category

CartAbandon uses a small set of subprocessors to run the service: a hosting provider, an email delivery provider, an SMS and WhatsApp provider, a payment operator for your subscription and an AI model provider that drafts message text. The DPA in your panel describes each category and what data it receives. AI drafts use message context, not full customer records.

You decide when data is deleted

  • On request. A shopper can ask to be forgotten. You can delete their contact and recovery history from the panel, or we process it when you forward the request to support@cartabandon.com.
  • On cancel. When you cancel, your plan runs to the end of the paid period. After that, shopper data from your store is deleted on a fixed schedule described in the DPA.
  • On disconnect. Disconnecting a store stops all reading of new data from it.

Plus includes a 99.9 percent uptime SLA

Recovery logic runs on our servers, not in your storefront. The storefront script is small and loads asynchronously, so your store keeps working even if our service is slow. On Plus, uptime is covered by a 99.9 percent SLA, with priority support and invoicing on annual plans. Compare plans on the pricing page.

FAQ

Questions about abandoned cart recovery security

Does CartAbandon store card numbers?

No. Card data never reaches CartAbandon. Payment update links send the shopper to your store's own checkout or your payment operator's page, where the card is updated.

Is shopper data encrypted?

Yes. Shopper contact data and store access tokens are encrypted at rest, and all traffic is encrypted in transit.

Can we sign a DPA?

Yes. The data processing agreement is available in the panel on every plan. You can review and accept it there.

Can we keep data in the EU?

Yes, on Plus. Plus lets you choose EU or US data residency for your stores.

Does the storefront script slow down my store or need a cookie banner?

No. It is one small asynchronous script that uses only first-party, strictly necessary identifiers and fires no ad pixels, so it does not need a cookie banner.

What happens to our data when we cancel?

Your plan runs to the end of the paid period. After that, shopper data from your store is deleted on the schedule described in the DPA.

Check the revenue at stake before you review the paperwork

Run a quick estimate for your store. No store connection needed.

See what your store loses each month

We read your public homepage only. No login needed.

Platform Detected

Detected from your URL. Change it if it looks wrong.

USD

Your typical order total. A rough number is fine.

You used today's free estimate. to run more.

Takes 20 seconds. No email needed.

  1. Reading your storeChecking your homepage, platform and product category.
  2. Matching benchmarksApplying typical abandonment and recovery rates for stores like yours.
  3. Drafting a sample messageWriting one recovery message with your store name.