Skip to content

Privacy Policy

FraudPilot: High-risk order review for Shopify

Effective date: November 6, 2026

This Privacy Policy explains how Alpenglow Software LLC ("we," "us," "our"), operator of FraudPilot ("the App"), collects, uses, stores, and protects information when you install and use the App through the Shopify platform. FraudPilot is a human-review queue for orders that Shopify's risk engine flags as medium or high risk. It enriches each flagged order with the facts you need to make a call, lets you record your decision (approve, cancel, or tag), and keeps an immutable, append-only decision log you can export as chargeback-representment evidence. FraudPilot does not decide for you. It changes an order in Shopify in two ways only: adding a FraudPilot tag when a member of your staff asks it to, and, if you turn on automatic holds, placing and releasing a fulfillment hold on new orders that match the setting you choose. You can also look up any recent order by its number to see Shopify's risk details for it. See Section 1 for details.

1. Information We Collect

Data from Shopify APIs

The App requests the following Shopify access scopes:

The App changes an order in Shopify in only two ways: adding a FraudPilot tag when a member of your staff asks for it (described under write_orders above), and, only if you turn on automatic holds, placing and releasing fulfillment holds (described under the fulfillment-order scopes above). It does not cancel, edit, refund, or fulfill orders, and it does not change any customer record. Recording an Approve or Cancel decision in FraudPilot does not change the order in Shopify; you complete those actions in the Shopify Admin.

Protected Customer Data (Level 1)

The following fields are treated as Shopify Protected Customer Data at Level 1 (no name, address, email, or phone):

The App does not request or access any Level 2 Protected Customer Data (name, address, email, or phone). Those fields are withheld by Shopify unless an app is separately approved for them, and FraudPilot does not request that approval.

Data collected through the Shopify session

Shopify provides the following data as part of the standard app authentication process:

This session data is managed by Shopify's official session storage library and is required for the App to function within the Shopify Admin. The App additionally stores the staff user identifier derived from the session with each recorded decision, so the decision log accurately attributes who made each call.

Data we generate and store

As you use the App, we store:

Data we do NOT collect

We do not use artificial intelligence or machine learning to process your data, and your data is not used to train AI or machine-learning models. If you choose to use Shopify Sidekick (see "Shopify Sidekick" in Section 2), the answers FraudPilot returns to it are processed by Shopify's AI assistant under Shopify's terms, not by us.

2. How We Use Your Information

We use the data we collect solely to provide and improve the App's services:

Service-monitoring data is reviewed only by us, in a daily internal report that identifies your store only by an internal ID, not by its name or domain. We do not use it for sales outreach, pricing, benchmarking, or any purpose other than keeping the App working and improving its setup experience.

We do not sell your data, and we do not use it for advertising, marketing, or cross-store or advertising profiling. The one exception is your optional answer to how you found the App, which we use only as described above to plan our own marketing; it is never shared or used to target you. The App shows you risk context about a flagged order (such as the customer's order history with your store); it does not build profiles of customers across stores. Every decision recorded in the App (approve, cancel, or tag) is one a member of your staff made. The only automated processing that acts on an order is the optional automatic hold: if you turn it on, FraudPilot places a fulfillment hold, under the setting you chose, on new orders that match it. A hold pauses fulfillment until a person on your staff approves the order or releases the hold, or FraudPilot releases it (see Section 1). FraudPilot never cancels, refunds, or refuses an order, and any decision on a held order is made by a person. Your staff can release a hold at any time, in the App or in Shopify.

For the purposes of applicable data protection laws, you (the merchant) are the data controller for the order and customer data made available through the App. Alpenglow Software LLC acts as a data processor, processing that data solely on your behalf and as described in this policy. For any data we collect directly from you (such as support communications) and for the service-monitoring records described in Section 2, we act as an independent data controller.

3. How We Process Order Data

Order and risk data flows through the App as follows:

  1. When Shopify flags an order as medium or high risk (or when the App reads a flagged order via the Admin API, or a member of your staff adds an order to the queue), the App fetches the order facts and risk signals over the read_orders scope, and the customer identifier and customer order-history summary over the read_customers scope.
  2. If a review rule is on, when Shopify assesses an order the App also reads its total, currency, item count and creation time in the same request over the read_orders scope. An order that matches a rule is handled like a flagged order from here on; for any other order these values are discarded.
  3. When you use Order Lookup, the App fetches the risk level and risk details of the order you entered, and on the Standard plan its AVS and CVV result codes and payment gateway name(s), over the read_orders scope. It does not fetch the customer identifier or the client IP for a lookup, and it does not store the result.
  4. Every 30 minutes, the App reads the created time, total, and first product title of your store's abandoned checkouts from the last 24 hours over the read_orders scope, counts them, and discards them. It stores a card-testing alert only when the count is far above the usual level for that product or for your store, or is very high with too little history to compare it with.
  5. When you open the Protection Checkup page, the App reads the sales channel and the payment transaction types, statuses, and times of your 25 most recent orders over the read_orders scope, uses them to suggest how your payment capture setting is configured, and discards them.
  6. When Shopify reports a new or changed dispute, and every 2 hours, the App reads your Shopify Payments disputes over the read_shopify_payments_disputes scope and stores the dispute data described in Section 1.
  7. The client IP on the order is reduced to a /24 network prefix and resolved to a country using a local geographic-IP database in the same step. The raw IP is discarded and never written to storage.
  8. The App assembles an enrichment snapshot from these facts, adds order-velocity and prior-decision context drawn only from your own store's records, and places the order in your review queue.
  9. If automatic holds are on, when a new flagged order matches your setting the App records that it should be held. About every 20 minutes, the App reads that order's fulfillment orders over the fulfillment-order scopes, places the hold, and records the result; it later releases the hold the same way. It checks a placed hold every 6 hours for the first 7 days and daily after that, and stops tracking a hold someone released or that ended in Shopify.
  10. When you make a decision, the App writes an append-only decision-log entry capturing the action, your reason, and the evidence snapshot as it stood at that moment. For a Tag decision on a store that has approved write_orders, the App first adds the fraudpilot-review tag to the order in Shopify; if Shopify does not confirm the tag, nothing is recorded and you are shown an error.
  11. Enrichment and decision records are displayed to you in the App and can be exported for representment.

The decision log is append-only: the App exposes no path to edit or delete a logged decision through normal use. This is what makes the log usable as tamper-resistant evidence. The only paths that remove decision-log rows are the data-deletion obligations described in Section 6 (customer redaction, shop redaction, or a deletion request you make).

4. Data Storage and Security

5. Third-Party Services

The App uses the following third-party services to operate:

ServicePurposeData shared
Shopify Admin API Authentication, order and risk-assessment data, customer identifier, Shopify Payments dispute data Session tokens, GraphQL order, customer, and dispute queries; if automatic holds are on, fulfillment-order reads and hold and release requests (with the reason and the note "FraudPilot: waiting for your review")
Shopify Sidekick (Shopify's AI assistant, only if you use it) Answering questions you ask Sidekick about your FraudPilot queue and decisions inside the Shopify Admin. FraudPilot sends a summary to Shopify only when you ask Sidekick; Shopify processes it under its own terms. The queue and decision summary described under "Shopify Sidekick" in Section 2: counts, FraudPilot's reason labels (Standard plan), and the order name, risk level, and waiting time of up to five orders. No customer names, contact details, customer identifiers, or network data.
Railway Application and database hosting All stored data (encrypted in transit; access tokens encrypted at rest)
Resend Transactional email: a daily review digest to Standard-plan stores (when enabled; contact us to stop receiving it), and a daily internal operator report and error alerts sent only to us, and help message notifications to our support inbox; if you turn on order alerts, alert and confirmation emails to the address you choose Merchant digest: recipient email address and queue counts. Operator report (sent only to us): your store's internal ID (not its name or domain), plan, install and uninstall dates, setup progress, app-open and decision counts, and the order and product counts described in Sections 1 and 2. An alert about a failed privacy request may name your store's domain so we can resolve it. Help message notifications (sent only to our support inbox): your shop domain, the topic, your message, any rating, the plan and setup progress attached to problem reports, and your contact email only if you agreed to be contacted (so our reply goes to you). Order alerts (only if you turn them on): the address you chose, your shop domain, and for each order its name/number, total, currency and why it is in your queue. No customer identifiers or order-level personal data are sent.
Northwest Registered Agent Hosting for our support mailbox (support@alpenglowsoftware.com), where help message notifications arrive and from which we reply The help message notifications described above, and any email you exchange with us. No customer personal data
Inngest Background job scheduling Job parameters and short job results: your shop ID, your store domain (for the daily plan check), your store contact email (for the merchant digest, when enabled), and whether each email was sent. The operator report itself is not stored in job results. Inngest keeps this job history for a limited period set by our plan. No customer personal data is placed in job payloads or results.

The App also uses geoip-lite, an open-source geographic-IP database that runs entirely on our server. No data is sent to any external service for IP-to-country resolution.

If we add or replace a sub-processor in a way that materially affects how your data is processed, we will update this Privacy Policy and notify you through the App.

6. Data Retention

7. Your Rights

You have the right to:

Regarding your customers. FraudPilot does not collect customer names, addresses, email addresses, or phone numbers. It does store Level 1 data tied to a flagged order: the Shopify Customer identifier, the coarsened /24 network prefix, and the customer order-history summary described in Section 1. Because this data can be associated with an order, and through your Shopify records with an identifiable customer, we treat the order-linked review artifacts and decision-log rows as personal data rather than as anonymous data. FraudPilot honors Shopify's customer privacy webhooks for this data:

These requests delete the data FraudPilot holds. They do not remove a fraudpilot-review tag from an order in your Shopify store; as the controller of your order records, you can remove the tag in the Shopify Admin if a customer's request requires it.

If a customer contacts you with a data request, you may contact us and we will assist. We respond to all data requests within 30 days.

8. International Data Transfers

Your data is processed and stored on servers located in the United States. By using the App, you consent to the transfer of your data to the United States for processing.

9. Cookies and Tracking

The App does not use cookies, tracking pixels, or any third-party analytics or advertising technologies. Apart from the basic first-party usage records described under "Service monitoring" in Section 2, it does not track your behavior within the Shopify Admin. FraudPilot has no storefront component: it adds nothing to your storefront and collects nothing from your store's visitors. It reads two public pages of your storefront, described in Section 1, the same way any visitor could.

10. Children's Privacy

The App is designed for use by Shopify merchants (business users) and is not directed at children under 13. We do not knowingly collect personal data from children.

11. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the effective date at the top of this page. Continued use of the App after changes constitutes acceptance of the updated policy.

12. Contact Us

If you have questions about this Privacy Policy or want to exercise your data rights, contact us at:

Email: support@alpenglowsoftware.com