Settl.

Privacy

Privacy policy

Last updated 21 October 2026

Who we are

Settl is operated by GIBSON GROUP - FZCO, a free zone company registered in Dubai, United Arab Emirates (trade licence no. 59354, IFZA Properties, DSO-IFZA, Dubai Silicon Oasis, Dubai, United Arab Emirates).

Settl provides server-side tracking and a hosted checkout for Shopify and WooCommerce stores. Merchants (our customers) use Settl for their own shops. Shopify merchants who install the Settl app from the Shopify App Store use Settl for tracking only: their buyers always pay on Shopify's own checkout.

For anything about your data, write to support@settl-checkout.com or use the contact page.

For the personal data of a store's buyers, the merchant is the controller and Settl processes it on the merchant's behalf, only for the purposes described here (we are its processor). For merchants' own account data, Settl is the controller.

Merchants: your account

We keep your name, e-mail address and the details of your stores so you can log in and use Settl. Subscription payments are handled by Stripe (older subscriptions by Whop), or by Shopify for stores installed through the Settl app from the Shopify App Store (the plan then appears on your Shopify invoice). We receive the status of your subscription, not your card details.

When you install the Settl app from the Shopify App Store without a Settl account, we create one for you with the store owner's e-mail address from Shopify, so you can also log in on settl-checkout.com later. We don't send marketing e-mails to these accounts.

API keys and tokens you connect (payment providers, ad platforms, Shopify) are stored encrypted and only used to do what you set up.

Shoppers: on behalf of the merchant

When you buy from a store that uses Settl, we process the details needed for your order (such as name, e-mail, address, the products and the payment status) on behalf of that store. The store is responsible for this data; we act as its processor.

If the store uses Settl tracking and you accept marketing cookies, we remember which ad you came from (click IDs, for up to 90 days) and send the purchase to the platforms the store connected: Meta, Google Ads, Google Analytics 4, TikTok, Snapchat, Pinterest, X, Microsoft Advertising, Reddit and Klaviyo. For the ad platforms, e-mail addresses, phone numbers, names and city/postal code are hashed (SHA-256) before they are sent. Google Analytics 4 receives no e-mail address or phone number. Klaviyo is the store's own e-mail marketing platform and needs to know who the customer is, so it receives the e-mail address and phone number unhashed.

The storefront script and the checkout pixel only store click IDs and send events after the visitor allowed marketing/analytics in the store's cookie banner (Shopify's Customer Privacy API), and they stop when the buyer opts out of the sale or sharing of their data.

For the store's live view we keep a rough location (city level, derived from the IP address) of visitors for at most one day, and of sales for at most three days.

Shopify stores using the Settl app

What the app reads from Shopify. Only what tracking needs, through the permissions the merchant approves at install: orders (order ID and number, totals, currency, tax, shipping, discount, the products bought) and the buyer's contact details on the order (e-mail, phone, first and last name, city, postal code and country; the street address is not stored), the customer ID, abandoned checkouts, storefront and checkout events from the Settl web pixel (page views, add to cart, checkout steps, purchase), products and product cost (for profit reports) and the theme's status (to see whether the Settl app embed is switched on). The app does not create or change orders, customers or anything else in the store.

Why. To send the store's purchases and funnel events to the ad and e-mail platforms the merchant connects, to link sales to the ad click they came from, and to show the merchant their own reports (orders, match rate, live view, abandoned checkouts, ad results). Buyer data is never shared between merchants, never sold, never used for Settl's own advertising and never used to train AI models.

Billing. Stores installed through the Shopify App Store pay their Settl plan through Shopify Billing, on the merchant's Shopify invoice. Uninstalling the app ends that plan.

Data requests and deletion (GDPR). Settl handles Shopify's mandatory privacy webhooks. When a buyer asks a merchant to delete their data, Shopify sends us a customers/redact request and we delete that buyer's click history and abandoned-cart entries and remove the e-mail address and name from their tracked orders. A customers/data_request is answered by the merchant from Shopify; we help on request with the data Settl holds. 48 hours after a merchant uninstalls the app, Shopify sends shop/redact and we delete all buyer data of that store. We act on these requests as soon as they arrive, and always within 30 days.

Facebook / Meta data

Merchants can connect Facebook to see ad results in Settl. We then only read results of the ad accounts they choose (the ads_read permission): spend, impressions, clicks and the purchases Meta reports. We never change ads, never spend money and never post anything.

The access token is stored encrypted and used only to show these results to the merchant. It is deleted when the merchant disconnects Facebook in Settl, or when Settl is removed in Facebook's settings (we then receive a deletion request and remove the connection).

Google Ads data (Google user data)

What we access. Merchants can connect their Google Ads account to see ad results in Settl. Settl requests two scopes: the Google Ads API scope (https://www.googleapis.com/auth/adwords) and the Google Data Manager API scope (https://www.googleapis.com/auth/datamanager), which is only used to upload the store's purchases as conversions (see below). With it we read the ad accounts the merchant picks: account name, ID and currency, campaign, ad group and ad names and status, daily budgets, and performance numbers (spend, impressions, clicks, conversions and conversion value). We do not access e-mail, contacts, Drive, Gmail or any other Google data.

How we use it. Only to show the merchant their own Google Ads results in their Settl dashboard, next to the sales Settl tracked for their store, so they can see their real return on ad spend per campaign and per ad. If the merchant also switches on "Google Ads direct" and picks a conversion action, Settl uploads the store's paid orders to that conversion action (Google click id, order id, value, currency and a SHA-256 hash of the buyer's e-mail and phone), so Google Ads can count the sales its ads brought in. Apart from that we never create, change or pause campaigns and never spend money.

Sharing. We do not share, sell or transfer Google user data to anyone. Each merchant only sees their own accounts. The data only passes through the infrastructure that runs Settl (Vercel for hosting, Supabase for the database), which process it on our behalf and cannot use it for anything else. We do not use it for advertising, and we do not use it to develop, improve or train AI or machine-learning models.

Protection. All traffic uses HTTPS (TLS). The Google refresh token is encrypted (AES-256-GCM) before it is stored, the encryption key is kept separately from the database, and only Settl's server can read it. Access to our systems is limited to the Settl team.

Retention and deletion. Google Ads report numbers are fetched when the merchant opens the dashboard and are cached for at most 10 minutes; we do not keep a permanent copy. The encrypted refresh token and the list of chosen accounts are kept only while Google is connected. They are deleted right away when the merchant clicks Disconnect in Settl, and access stops when Settl is removed in their Google account (myaccount.google.com/permissions). When a merchant deletes their store or account, all related Google data is deleted. Merchants can also ask us to delete it via the contact page; we do this within 30 days.

Settl's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

TikTok, Snapchat and Pinterest Ads data

Merchants can connect their TikTok Ads, Snapchat Ads or Pinterest Ads account to see ad results in Settl. With their permission we only read the ad accounts they choose: account name, ID, currency and time zone, campaign, ad group and ad names, status and budgets, and performance numbers (spend, impressions, clicks or swipes, purchases or checkouts and purchase value). We use this only to show the merchant their own results next to the sales Settl tracked. Access is read-only: we never create or change campaigns and never spend money.

We do not share or sell this data and do not use it for advertising or to train AI models. Tokens are encrypted (AES-256-GCM) before they are stored. Report numbers are fetched when the merchant opens the dashboard and cached for at most 10 minutes. Tokens are deleted right away when the merchant clicks Disconnect in Settl, or deletes the store or account.

Our own website and ads

On settl-checkout.com we use the Meta pixel to measure our own ads, only after you click Accept in the cookie banner. It then sees which pages you visit, whether you create an account, start a payment or pay for a plan, and we send these events (with your e-mail address hashed) to Meta. This is separate from our customers' stores: it never runs on checkout pages or shops. Click Only necessary and nothing is loaded or sent.

We also count visits to settl-checkout.com ourselves, without cookies: which pages are viewed, where visitors came from (referrer or utm tag), and a rough location from the IP address. A visitor is a daily-changing code made from the IP address and browser, so we can't follow anyone across days. When you're logged in, we link the visit to your account. We keep this for at most 90 days.

How long we keep data

Account data: as long as you have an account.

Ad click data for tracking (click IDs, hashed e-mail used for matching): 90 days, then deleted by a scheduled job.

Abandoned carts and checkouts: 30 days. Live view: visitors 1 day, sales 3 days. Log of e-mails Settl sent: 90 days. Visits to settl-checkout.com: 90 days.

Tracked orders (with the buyer's e-mail and name): as long as the store uses Settl, so the merchant can see their history. They are deleted when the merchant deletes the store or account, and, for Shopify stores on the Settl app, when Shopify sends shop/redact after the app is uninstalled.

Who we share data with

Only with the services needed to run Settl (our sub-processors) and with the platforms the merchant chooses to connect. We don't sell data.

Sub-processors: Vercel (hosting and serverless functions, EU region Frankfurt), Supabase (database, login and file storage), Resend (sending e-mails), Mapbox (maps in the live view; it receives no buyer contact details) and, for our own subscriptions, Stripe, Whop or Shopify Billing.

Platforms the merchant connects, which receive the store's events as described above: Meta, Google (Google Ads, Google Analytics 4), TikTok, Snapchat, Pinterest, X, Microsoft Advertising, Reddit and Klaviyo, and for Settl's checkout (not available through the Shopify App Store app) the payment provider the merchant uses. Several of these are in the United States; transfers outside the EU/EEA rely on the providers' Standard Contractual Clauses.

Security and incident response

All traffic uses HTTPS (TLS 1.2 or higher), including webhooks, the web pixel and the calls to ad platforms. The database is encrypted at rest by our provider. Shopify access tokens and all API keys and tokens merchants connect are additionally encrypted with AES-256-GCM, with the key kept separately from the database. Buyer e-mails used for matching are stored as SHA-256 hashes. Access to production systems is limited to the Settl team.

Found a security problem? Write to support@settl-checkout.com with "Security" in the subject.

If there is a security incident that affects personal data, we contain it straight away (for example by rotating keys and revoking tokens), work out which stores and buyers are affected within 24 hours, and notify the affected merchants without undue delay and at the latest within 72 hours of becoming aware of it, so they can meet their own obligations. When Shopify merchant or buyer data is involved, we also notify Shopify. Afterwards we fix the cause, write down what happened and review this procedure.

Your rights

You can ask to see, correct or delete your data. Shoppers can best contact the store they bought from; we help the store with the request. Merchants can contact us directly. We answer requests within 30 days.

Privacy policy · Settl