— Privacy · Propel Fraud & Bot Blocker

Propel Fraud & Bot Blocker Privacy Policy

Applies to Alcaris Inc., doing business as Propel Commerce, and all Propel apps

Last updated: 16 November 2026

Propel Fraud & Bot Blocker (the “App”) checks the visitors to a merchant’s Shopify store and blocks the bots, unwanted visitors and fraudulent checkouts the merchant chooses to block (the “Service”). The App is operated by Alcaris Inc., doing business as Propel Commerce (“Propel”, “we”, “us”). This policy explains what information the App collects, why, who it is shared with, how long it is kept, and the choices available.

§ 01

Who We Are and Our Roles

Questions about this policy can be sent to support@propelcommerce.io.

Store visitors and shoppers. When someone visits or checks out on a merchant’s store, the merchant decides that the App will run, which rules it applies, and why. The merchant is the controller under the GDPR and UK GDPR, and the business under the California Consumer Privacy Act as amended by the CPRA (the “CCPA”). Propel is the merchant’s processor and service provider. We process shopper information solely on the merchant’s behalf and on the merchant’s documented instructions, never for our own commercial purposes.

Merchant account and app-usage data. For information about merchants and their staff (store details, settings, and support conversations), Propel is the controller and business in its own right.

Our processing of shopper information on a merchant’s behalf is governed by our Data Processing Agreement (the “DPA”), which forms part of our agreement with each merchant.

§ 02

Information the App Collects

2.1 From merchants and their staff

When a merchant installs the App, we receive the store’s domain, name, contact email and time zone, and the access token Shopify issues so the App can work on the store’s behalf. We also keep the rules, settings and block page content (including any logo) the merchant configures, and support conversations with the merchant’s staff in the App’s support chat.

The App requests only these Shopify permissions:

write_validations: to run the App’s checkout rule, which blocks checkouts that match the merchant’s rules.
read_orders: to read the email address, cancellation reason and Shopify’s fraud risk rating of an order, so that the email of an order the merchant cancels as fraud, or, when the merchant turns this on, of an order Shopify rates High risk, can be added to the merchant’s blocklist.
write_pixels and read_customer_events: to count checkout attempts the merchant’s rules blocked.
read_themes: to check whether the App’s theme embed is turned on.

2.2 On behalf of merchants, from store visitors

When the merchant has turned on the App’s theme embed, the App checks each new visitor to the store and collects:

Network information: the visitor’s IP address, and the details derived from it: country, region, the network that owns the address, and whether the address belongs to a data center, VPN, proxy or Tor exit.
Device and browser information: the user agent (read as device and browser type), and browser characteristics used to detect automated browsers: whether the browser reports that it is automated, its languages, platform, time zone, plugin count and touch support.
Visit information: the page path visited, without its query string; the time; and the App’s decision (allowed, blocked, redirected or watched), with the reason, a risk score and the signals behind it.
Ad campaign information: when a visit arrives from an ad, the ad platform and the campaign tags in the landing page address (utm_source, utm_medium and utm_campaign). Ad click identifiers are read only to name the platform and are never stored.
A visitor identifier: a random value kept in a first-party cookie (see Section 3).
Email of logged-in customers: when a shopper is logged in to the store’s customer account, the store’s theme passes their email address to the App so the merchant’s email rules and blocklist can apply to it.

2.3 At checkout

The App’s checkout rule runs inside Shopify’s checkout. To apply the merchant’s rules, it reads the buyer’s email address and phone number, the delivery address (name, city, company, province, postal code and country) and the cart total. These are evaluated within Shopify’s checkout and are not sent to or stored by Propel, with two exceptions:

Blocked checkout attempts: when a merchant’s rule blocks a checkout, the App records the time and a one-way hash of the checkout’s token, so the merchant can see how many checkouts were blocked. No buyer details are recorded.
The merchant’s email blocklist: email addresses the merchant adds by hand and, when the merchant turns each on, the email address of an order the merchant cancels with the reason “Fraud” or of an order Shopify rates High risk, together with that order’s number. If the merchant removes a High-risk entry, the App keeps only that order’s Shopify ID, so a later rating of the same order doesn’t add the address back. Shopify’s checkout receives only one-way hashes of these addresses.

2.4 What the App does not collect

The App does not collect payment card details, passwords, the content of pages or forms, keystrokes, or full page addresses with their query strings. It does not store shoppers’ names or postal addresses.

§ 03

Cookies and Browser Storage

The App uses only first-party storage on the merchant’s own store domain. It is strictly necessary for the security of the store and is never used for advertising, analytics or cross-site tracking.

pbb_id (cookie, 30 days): a random visitor identifier, used to group a visitor’s checks in the merchant’s visitor log and to detect repeated abuse.
pbb_ok (cookie, up to about 30 minutes): a signed token that lets a visitor who has just passed a check browse without being checked again on every page.
pbb_bp (cookie): set only when someone opens one of the merchant’s private bypass links, so the merchant’s own staff are not blocked while testing.
pbb_src (session storage, for the browser tab only): the ad platform and campaign tags of the visit, described in Section 2.2.
pbb_vb (local storage): a flag that the visitor’s cart carries the marker below.
_pbb_v (cart attribute): a marker the App adds to the cart of a visitor the store blocked that day, so the same visitor cannot go straight to checkout. It is removed the next time the visitor is allowed in, and expires at the end of the store’s day.

§ 04

How We Use Personal Information

4.1 Store visitor and shopper information

We use shopper information solely on the merchant’s behalf, to provide the Service to that merchant: to decide whether to allow, block, redirect or log each visit; to apply the merchant’s checkout rules and blocklist; and to show the merchant a visitor log and reports.

To catch bots that move between stores, the App counts how often each IP address is checked across all stores using it. These counters expire within two minutes, and a high count raises the risk score. No other information from one merchant’s store is used for another merchant.

We do not use shopper information for our own advertising or marketing, we do not use it to build profiles for any other business, and we do not sell or share it (as those terms are defined by the CCPA). We retain, use and disclose it only for the purposes set out in the DPA.

4.2 Merchant information

We use merchant account information and support conversations to operate and provide the App, to respond to support requests, to secure and improve our products, and to send service messages and messages about Propel products. Merchants can opt out of marketing messages at any time using the unsubscribe link in the message or by emailing us.

§ 05

Sharing and Sub-processors

We do not sell personal information and we do not share it for cross-context behavioral advertising. We disclose it only to the sub-processors that host and run the App:

Shopify Inc. App platform, checkout and theme integration.
Render Services, Inc. Application hosting, database and data store, including the AI assistant in the support chat (United States).
Amazon Web Services, Inc. Stores the block page logo a merchant uploads (Amazon S3, in Oregon, United States) and delivers it to blocked visitors through Amazon CloudFront, which receives those visitors’ IP addresses to deliver the image and keeps temporary cached copies of the logo at locations around the world.
proxycheck.io IP address risk lookups. When a merchant’s settings need it, the App sends a visitor’s IP address, and nothing else, to learn whether it belongs to a VPN or proxy. Query logging is turned off on our account.
Crisp IM SAS The App’s support chat (European Union). Crisp receives the merchant’s store domain and contact email, a summary of the App’s settings and recent visit totals so our team can help, and the conversation itself. It receives no information about the store’s visitors or shoppers.
OpenAI, Inc. The AI assistant that answers in the App’s support chat (United States and other countries). It receives the support conversation and a summary of the store and the App’s setup: the store’s ID, name, domain and time zone, its install date, its plan and the plan’s limits, its storefront address, protection mode, free boost status and recent visit totals. It receives no information about the store’s visitors or shoppers. Under the API terms that apply to us, data sent to OpenAI is not used to train its models.

IP location data is provided by DB-IP under the Creative Commons Attribution 4.0 licence. The App uses a copy of that database on our own servers, so no visitor information is sent to DB-IP.

We may also disclose personal information where the law requires it, for example to respond to a lawful request from a court or regulator.

§ 06

Your Rights

6.1 Residents of the EU, EEA and UK

You have the right to access the personal data held about you, to have it corrected or erased, to restrict or object to its processing, to receive it in a portable form, and to lodge a complaint with your local supervisory authority.

6.2 California and other US state residents

Depending on your state of residence, you may have the right to know what personal information is collected about you and how it is used and disclosed, to request its deletion or correction, and to opt out of its sale or sharing. Propel does not sell or share personal information.

6.3 How to make a request

For information collected when you visited or checked out on a merchant’s store, the merchant is the controller: please contact that merchant. When Shopify passes us a merchant’s customer data request, we provide the merchant with that customer’s blocklist entries and visitor log records. When Shopify passes us a customer deletion request, we delete that customer’s blocklist entries and the visitor log records that carry their email address.

If you believe you were blocked by mistake, use the “Contact the store” link on the block page, or contact the merchant directly. Merchants can remove any rule or blocklist entry at any time.

§ 07

Data Retention and Deletion

Visitor log: kept for 7 or 30 days, depending on the store’s plan, then deleted automatically.
Daily totals: counts of visits by outcome, reason, country, ad platform and campaign name, with no personal information, kept for 400 days.
Blocked checkout attempts: kept for 90 days.
Email blocklist: kept until the merchant removes an entry, or until a deletion request described in Section 6 or the store deletion described below. When the list reaches 10,000 entries, the oldest High-risk entry is removed to make room. The ID of an order whose High-risk entry the merchant removed is kept until a deletion request covering that order, or the store deletion.
Short-lived caches and counters: rate-limit counters, and lookup results kept by IP address so the same address is not looked up on every visit, expire within two minutes to seven days.

On uninstall: the App stops checking visitors and checkouts. The store’s data is kept until Shopify sends its store deletion request (shop/redact), about 48 hours after uninstall, so a merchant who reinstalls does not lose their setup.

On Shopify’s store deletion request: we delete the store’s rules, settings, block page logo, visitor log, daily totals, email blocklist, blocked checkout records and access tokens. We keep only the store’s domain, name and contact email, so we can recognise a reinstall and answer support questions.

§ 08

International Transfers

Personal information handled through the App is stored in the United States, on the infrastructure of the sub-processors listed in Section 5. A blocked visitor loads the block page logo, if the merchant uploaded one, from the nearest Amazon CloudFront location, which may be outside the United States. Support conversations with merchants are held by Crisp in the European Union; when the AI assistant answers, OpenAI processes them in the United States and other countries. Where personal data is transferred out of the European Union, the European Economic Area or the United Kingdom, the transfer is protected by the European Commission’s Standard Contractual Clauses, the UK International Data Transfer Agreement or Addendum where applicable, or another lawful transfer mechanism, as set out in the DPA.

§ 09

Changes

We may update this privacy policy to reflect changes to our practices or for operational, legal or regulatory reasons. The date at the top of this page shows when it was last revised, and we will notify merchants of material changes through the App or by email.

§ 10

Contact Us

For questions about our privacy practices, or to make a complaint, contact us at support@propelcommerce.io or by mail:

Alcaris Inc., doing business as Propel Commerce
170-422 Richards St
Vancouver, BC V6B 2Z4
Canada