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:
read_orders: used to build and enrich the review queue. For each order Shopify flags as medium or high risk, the App reads and stores the order name/number, order date, order total and currency, line-item count, the line items themselves (product title, quantity, and line total), the payment gateway name(s), AVS (address verification) and CVV result codes, fulfillment status, Shopify's own risk assessment and risk signals, the order's Shopify Protect status, and the sales channel it came through. For flagged orders placed by a customer account, the App also counts how many orders that customer placed before the flagged order, in total and within the 24 hours and 7 days before it (counts only; the other orders' contents are not read or stored). To show how a flagged order compares with your usual orders, at most once a day the App also reads the totals of up to 250 of your most recent orders from the last 60 days and also reads their item counts, and stores only the medians (your typical order total and typical number of items per order); the individual orders are not stored. In this policy, a "flagged order" also includes any order a member of your staff adds to the review queue by hand (see "Add to review" below) and any order one of your review rules sends to the queue (see "Review rules" below). The App reads the network (IP) address recorded on the order, but stores it only in coarsened form (see "Protected Customer Data" below). The App does not access or store customer names, postal addresses, email addresses, phone numbers, or payment card information through this scope. To monitor that the App is working for your store, once a day we also read how many orders were created in the last day and in the last week, how many of the last week's orders Shopify flagged, and the order identifiers of up to 250 orders Shopify flagged since you installed the App (looking back at most 7 days). We compare those identifiers with your review queue to find any flagged order that did not arrive, and then discard them; they are not stored. The resulting counts are not stored in our database. They are included in a daily internal report sent only to us (see "Service monitoring" in Section 2 and the Resend entry in Section 5) and are used only for service monitoring.- Order Lookup (
read_orders): when a member of your staff enters an order number on the Order Lookup page, the App reads that order's Shopify risk level and risk details, even if Shopify did not flag the order, and, on the Standard plan, the card's AVS and CVV result codes and the payment gateway name(s). Only orders from the last 60 days can be looked up. Shopify's risk details can include the approximate location of the IP address used to place the order and whether the billing or shipping address is consistent with it; the App displays these as Shopify provides them. The results are shown to you and are not stored: the App keeps no order number, order identifier, or risk details from a lookup, unless a member of your staff then adds the order to the review queue (see "Add to review" below). The order number you enter appears in the page address in your browser. - Add to review (
read_orders,read_customers): a member of your staff can add any order from the last 60 days to the review queue, for example from Order Lookup, including an order Shopify rated low risk or did not rate. The App then reads and stores the same data it stores for a flagged order, as described in this section, and records which staff member added it. - Review rules (
read_orders; Standard and Professional plans, off unless you turn a rule on): you can choose to send orders to the review queue when their total, or the number of items in them, is over an amount you set. When a rule is on, each time Shopify assesses one of your orders the App reads that order's total, currency, item count and creation time along with Shopify's risk level. If the order matches a rule, the App places it in your review queue and treats it as a flagged order; if it does not, nothing about it is kept. Rules apply only to orders created after you last turned a rule on or lowered it. Orders Shopify does not assess (for example POS or draft orders) are not checked. - Order alerts (Professional plan, off unless you turn them on in Settings): you can choose to get an email when Shopify flags one of your orders high risk, or when one of your review rules sends an order to your review queue. When you turn alerts on, the App stores the email address you enter (it suggests your store's contact email, but stores nothing until you save) and your alert choices. Before the first alert, the App emails that address a confirmation link, and alerts start only after the link is used. For each alert the App stores the order's name/number, total and currency, why it is in your queue (Shopify's high-risk rating or the review rule it matched) and whether the alert was sent. Alerts contain only that information and links back to the App; they never contain customer names, email or postal addresses, phone numbers or payment details. At most one alert email is sent every 15 minutes; orders in between are grouped into the next email.
- Card-testing alert (
read_orders): to warn you about a possible card-testing run, every 30 minutes the App reads the abandoned checkouts created on your store in the last 24 hours. For each one it reads only the time it was created, its total and currency, and the title of its first line item. It does not read the name, email address, phone number, postal address, or IP address entered at checkout, any payment or card information, notes, or the checkout recovery link. These details are used to count checkouts and are then discarded; nothing about an individual checkout is stored. If the count for one product, or for your store as a whole, rises far above its usual level (or is very high and there is too little history to compare it with), the App stores an alert (see "Data we generate and store") and shows it to you on the App's home page. - Protection Checkup (no scope beyond those above): when you open the Protection Checkup page, the App reads your store's Shopify plan name, whether the store is a Shopify Plus or partner development store, and its customer accounts setting (whether customer accounts are off, optional, or required, and which version of customer accounts you use) and shows them to you on that page. To suggest how your payment capture setting is configured, it also reads your 25 most recent orders over
read_orders, whether or not Shopify flagged them, and for each one only its sales channel and the type, status, and time of up to 10 payment transactions, including whether each was a card payment. It does not read card details or any customer details for this, and it uses only online-store card orders. If your store has classic customer accounts turned on, the App also reads your store's public login page (/account/login), as any visitor would, to see whether Shopify's hCaptcha is switched on for login and sign-up. The login page contains no customer data, and only the result (on, off, password-protected, or couldn't tell) is used. None of this is stored in our database: the login page result is kept in server memory for up to 2 minutes so the page does not re-read it on every click, and everything else is discarded once the page is shown. The App never changes any Shopify setting. read_customers: used to read, for a flagged order, the Shopify Customer identifier (the customer's GID) and a short order-history summary for that customer: how many orders they placed before the flagged order, the date their customer account was created, and their lifetime amount spent. The identifier lets the App recognize a repeat buyer across your own prior decisions; the summary is shown to you as risk context (for example, a brand-new account placing its first order). These are the only customer fields the App reads. It does not read or store the customer's name, email address, phone number, or address, and it does not modify customer records.read_shopify_payments_disputes(chargeback alerts): if your store uses Shopify Payments, the App reads the chargebacks and inquiries filed against your orders, when Shopify reports a new or changed dispute and every 2 hours to catch any it missed (the first check looks back 120 days). For each dispute it stores the dispute identifier, its type (chargeback or inquiry), status, reason, amount and currency, the dates it was opened, is due for a response, and closed, and the identifier and name of the order it belongs to. It also reads and stores Shopify's risk level (high, medium, low, or none) for that order, even if the order was never in your review queue. The App does not read the buyer's name, email address, postal address, or card details from a dispute. We use this data to alert you when a dispute opens or closes, show its response deadline, fill in the evidence page for that order, and, for a chargeback on an order you decided in FraudPilot, record whether it was won or lost. On the Free plan the App shows only how many new disputes there are. FraudPilot never responds to a dispute or submits evidence; you do that in Shopify.write_orders: used only to add a tag to an order when a member of your staff asks for it:fraudpilot-reviewwhen they record a Tag decision (available on every plan), and, on the Standard plan, a dated tag such asfraudpilot-card-test-20261027when they record Cancel for a group of possible card-testing orders and choose to tag them in Shopify. The App does not use this scope to read any additional data, and it does not use it to cancel, edit, refund, fulfill, or hold orders. If your store has not yet approved this permission, a Tag decision is recorded in FraudPilot only and the order is not tagged in Shopify.write_merchant_managed_fulfillment_ordersandwrite_third_party_fulfillment_orders(automatic holds, optional): the App asks for these only when you turn on automatic holds in Settings (Standard plan); a store that never turns them on never grants them. They are used only to hold and release fulfillment. For each order FraudPilot is to hold or release, the App reads that order's fulfillment orders: each one's identifier, status, the actions Shopify allows on it, and the identifier and handle of each fulfillment hold on it and whether FraudPilot placed it. It then places a hold with the reason "high risk of fraud" for a High risk order (or "other" for a Medium risk order or one your own review rule added) and the note "FraudPilot: waiting for your review", and later releases only holds marked as its own. The hold and its note are visible on the order in your Shopify Admin and may be visible to your fulfillment service or fulfillment app. The App reads no customer data through these 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):
- Coarsened network (IP) prefix and country: the App reads the client IP recorded on the order and immediately reduces it to a
/24network prefix (the final part of the address is discarded) and derives a country using a local geographic-IP database bundled with the App. The raw IP address is never stored, and no external lookup is performed for this. The coarsened prefix and country are used only to surface order velocity and geographic context for the flagged order, and to recognize whether the same network has appeared in your prior decisions. - Shopify Customer identifier (GID): used only to recognize repeat buyers across your own past decisions, as described above.
- Customer order-history summary: the number of orders the customer placed before the flagged order (in total, and within the prior 24 hours and 7 days), their account creation date, and their lifetime amount spent. Used only to give you risk context on that flagged order; stored with the order's review artifacts and decision-log snapshot, and deleted with them (see Section 6).
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:
- Shop domain
- Staff member name, email address, and user ID
- Account role (store owner or collaborator) and email verification status
- Locale preference
- Session tokens, access tokens, and refresh tokens
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:
- Review queue items: the flagged orders awaiting your review, and their queue state (for example, needs decision, snoozed, decided).
- Enrichment snapshot: the order facts and risk signals described above, captured at review time so the record reflects what was known when the decision was made.
- Decision log entries (append-only): for each decision, the order identifier, the acting staff user identifier, the action taken (approve, cancel, or tag), your reason or note, a snapshot of the risk facts at decision time (including the customer order-history summary above), the associated Shopify Customer identifier, and the coarsened
/24network prefix. - Dispute outcomes: if you record how a chargeback or dispute resolved (for example, "won in representment"), we store that outcome against the related decision. When chargeback alerts are on, the App also fills in the outcome (won or lost) from Shopify's dispute status for orders you decided in FraudPilot, notes that it was filled in automatically, and never overwrites a won or lost outcome you entered.
- Chargeback alerts: the dispute data described under
read_shopify_payments_disputes, when the App first saw each dispute, when its status last changed, and when you dismissed the alert. - Card-testing alerts: when the App detects an unusual burst of abandoned checkouts, it stores the product title the burst concentrates on (if any), the number of abandoned checkouts in the hour, the usual hourly number for that product or for your store (when known), the typical checkout total and its currency, the times the hour started and ended, when the burst was detected, and when you dismissed the alert. An alert contains no customer, checkout, or order identifiers.
- Automatic hold settings and records: whether automatic holds are on, when you last turned them on, which orders to hold (for example, High risk only) and the mode (Hold or Notify only). For each order in your review queue that the setting applies to: whether FraudPilot wants it held, the risk level or rule it matched, the hold's status (for example, held, released, or failed) with a short error code if it failed, why and when the hold ended (for example, approved, released by staff, switched off, or plan changed), the identifiers of the fulfillment holds FraudPilot placed, and the times and attempt counts the App uses to retry. A hold history for the order: what happened (for example, would hold, held, released), when, the risk level or rule, the number of fulfillment orders, a short error code, and who did it (FraudPilot, or the identifier of the staff member who clicked Release hold). If a customer data deletion request covers an order FraudPilot is holding, the App deletes its records for that order and leaves the hold in place. It keeps only a count of such orders and when the last one happened, with no order name or identifier, to show you a notice in the App for 14 days. The count is replaced by the next such request after that and is deleted with your shop data when you uninstall. For your store, we also keep the times FraudPilot last checked your plan and permissions for automatic holds, and, each time you agree to the automatic holds terms (when you turn automatic holds on, and again when you switch from Notify only to Hold), when you agreed, the identifier of the staff member who did (or your store's Shopify domain if Shopify gave the App none), and the version (effective date) of the Terms you agreed to. Each new agreement replaces the earlier record. These records contain no customer names, contact details, customer identifiers, or network data.
- Protection Checkup answers: for each item on the Protection Checkup checklist, the answer you chose (done, not yet, or doesn't apply), that you set it, and when it last changed. The answers contain no customer, checkout, or order data.
- Store contact email: your store's contact email address, read from Shopify and stored so we can send the daily review digest (when enabled). This is your own merchant email, not customer data.
- Review rule settings: the amounts you set for your review rules and when you last turned a rule on or lowered it. For an order a rule sent to the queue, which rule it matched.
- Usage and setup records: for your store (not per staff member), how many times the App's home page was opened (counted at most once per hour) and when it was last opened, when an order's review page was first opened, the status of the one-time import of recently flagged orders, when the setup guide was shown, clicked, completed, or dismissed, and each time the Order Lookup page found an order, together with the Shopify risk level (high, medium, low, or none) of that order. The order number and order identifier are not recorded. We also record whether and when the App asked Shopify to show its App Store review prompt, how many times it has asked, the response code Shopify returned, and when the App may ask again (whether you left a review is not recorded). For stores on, or moving to or from, the paid FraudPilot plan, we record each live check of the subscription plan: how long it took, the plan before and after it, and how many page loads reused the previous check. See "Service monitoring" in Section 2.
- Public product count: the number of published products, read once a day from your storefront's public
meta.jsonpage (no access scope is used). It is not stored in our database; it appears only in the daily internal report described in Section 2. - Help messages and feedback: if you send a message from the in-app Help page, we store the topic you choose (for example, a problem, a how-to question, feedback, or billing), your message, and, for feedback only, an optional satisfaction rating. You may also give a contact email address; we store it only if you also tick the box allowing us to email you about that request, and we record when you sent the message with that box ticked. When you report a problem, we automatically attach your plan and setup progress so you do not have to look them up.
- How you found the App: once setup is finished and your review queue has loaded, the App asks how you found it, until you answer or skip the question. If you answer, we store your choice from a fixed list (for example, App Store search, Shopify Sidekick, an AI assistant, or a search engine) and, if you choose "Other", the short text you type. You can skip the question. We also record whether the question was shown to you, answered, or skipped.
Data we do NOT collect
- Customer or shopper names, postal addresses, email addresses, or phone numbers
- Raw (full) IP addresses
- Payment card or banking information
- Product catalog, inventory, or theme code (the App reads two public storefront pages, described above, only to count published products and to check whether hCaptcha is on, and keeps nothing else from them)
- Storefront visitor or web-analytics behavior data
- Marketing or advertising data
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:
- Review queue: we surface orders Shopify has flagged as medium or high risk, and orders your own review rules send to the queue, so you can review them in one place rather than scanning the raw Orders list.
- Enrichment: we assemble the order facts, risk signals, geographic and network context, order velocity, and your own prior decisions for the same buyer or network into a single review panel.
- Decision recording: we record the decision you make (approve, cancel, or tag), together with your reason and the evidence snapshot, into the immutable decision log. For a Tag decision, we first add the
fraudpilot-reviewtag to the order in Shopify and record the decision only after Shopify confirms it, and the log notes whether the tag was added in Shopify or recorded in FraudPilot only. - Card-testing alert: we count recent abandoned checkouts and warn you on the App's home page when there is an unusual burst, which can be a sign that stolen cards are being tested on your store. The alert is information for you; the App takes no action on any checkout, order, or customer.
- Protection Checkup: we list Shopify settings that can make card testing harder, show you the two we can read, and remember the answers you mark so you can see what is left. We also show two hints that are never saved: a guess at your payment capture setting from how your recent online card orders were charged (read over
read_orders), and, for classic customer accounts, the login page check described in Section 1. The App never changes your Shopify settings. - Shopify Sidekick (optional): if you ask Shopify Sidekick, Shopify's AI assistant in your Shopify Admin, about your review queue or recent decisions, Sidekick asks FraudPilot for a summary and FraudPilot returns it. On every plan, the summary contains how many orders are waiting (in total, high risk, and medium risk), how many are snoozed, how long the oldest has waited, and up to five of the most urgent waiting orders, each with its order name (for example, #1042, or its Shopify order ID if it has no name), its risk level, and how long it has waited. On the Standard plan, it also contains how many waiting orders show each of FraudPilot's own reason labels (for example, "CVV did not match" or "Brand-new customer account placing its first order"), how many orders those reasons were counted over and whether that covers only the most recent 200, and, for the last 30 days, how many orders were decided, your approve, cancel, and tag counts, and your approve rate. It contains no customer names, contact details, or customer identifiers, no network (IP) or location data, no order totals or line items, and no text from Shopify's risk assessment. FraudPilot does not receive your questions or Sidekick's replies, and it does not store the summaries it returns; a request can at most trigger the routine subscription plan check described under "Usage and setup records" in Section 1. Sidekick is operated by Shopify, which processes your conversations, including these summaries, under its own terms and privacy policy.
- Representment evidence: we let you export the decision log and its evidence snapshots as a CSV file, and, on the Standard plan, open a printable evidence page for a disputed order (the dispute, the order's line items, the customer's account age and earlier order counts, AVS and CVV results, and your decision record), which you can use to contest chargebacks. FraudPilot does not send these to anyone. When you share an export or evidence page with Shopify, a payment provider, or a bank, you choose what to share, and that copy is outside FraudPilot.
- Outcome tracking: we store dispute outcomes you record, or that the App fills in from Shopify's dispute status, so you can see how your decisions held up.
- Subscription management: we store your current billing plan to gate features appropriately.
- App functionality: we use your shop domain and session data to authenticate requests and deliver the App within the Shopify Admin.
- Automatic holds (only if you turn them on): we hold fulfillment on new orders that match the setting you chose, release the hold when your staff approve the order, click Release hold, or turn automatic holds off, check that placed holds are still in place, and show you which orders are held and any hold that failed. In Notify only mode we only mark the orders that would have been held. The 60-day preview in Settings reads your orders from the last 60 days (at most 1,000) over
read_orders: for each, its creation and cancellation time, fulfillment status and the time of its first fulfillment, item count, total and currency, and Shopify's risk level. It counts which would have been held, shows the result, and stores nothing. - Help and support: we use your help messages and feedback to answer you, fix problems, and improve the App. We email you about a message only if you gave an email address and agreed to be contacted about it.
- How you found the App: we use your answer, combined with other merchants' answers, to understand which channels bring merchants to the App and where to spend our own marketing effort. We do not share it with anyone.
- Service monitoring: we check that every order Shopify flags reaches your review queue, using the aggregate order counts described in Section 1 and your store's public product count, and we keep basic records of your use of the App (when it was last opened, how many times, which setup steps were completed, how often Order Lookup was used, how many card-testing alerts were raised, and how many disputes were recorded as won) so we can spot and fix problems.
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:
- 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_ordersscope, and the customer identifier and customer order-history summary over theread_customersscope. - 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_ordersscope. An order that matches a rule is handled like a flagged order from here on; for any other order these values are discarded. - 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_ordersscope. It does not fetch the customer identifier or the client IP for a lookup, and it does not store the result. - 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_ordersscope, 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. - 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_ordersscope, uses them to suggest how your payment capture setting is configured, and discards them. - When Shopify reports a new or changed dispute, and every 2 hours, the App reads your Shopify Payments disputes over the
read_shopify_payments_disputesscope and stores the dispute data described in Section 1. - The client IP on the order is reduced to a
/24network 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. - 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.
- 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.
- 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 thefraudpilot-reviewtag to the order in Shopify; if Shopify does not confirm the tag, nothing is recorded and you are shown an error. - 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
- All data is stored in a PostgreSQL database hosted on Railway (United States).
- Shopify access and refresh tokens are encrypted at rest using AES-256-GCM encryption.
- All connections use HTTPS/TLS encryption in transit.
- We store the client IP only in coarsened
/24form; the raw IP is never persisted. - We do not sell your data. We do not share your data with third parties for marketing, advertising, or profiling purposes.
- In the event of a data breach affecting your data, we will notify you and Shopify within 24 hours of discovery, in accordance with Shopify's Partner Program Agreement and applicable law.
5. Third-Party Services
The App uses the following third-party services to operate:
| Service | Purpose | Data 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
- While installed: review queue items, enrichment snapshots, decision-log entries, dispute outcomes, chargeback alerts, card-testing alerts, order alert records, automatic hold records, and Protection Checkup answers are retained for as long as the App is installed on your store. The decision log is retained deliberately, because it is your representment evidence. Usage and setup records, help messages and feedback, and your answer about how you found the App (Section 1) are also retained while the App is installed and deleted with your shop data.
- Operator reports and alerts: the daily internal operator report identifies your store only by an internal ID, which is deleted with your shop data, so a past report can no longer be linked to your store. An alert about a failed privacy request that names your store is deleted from our mailbox once the request is resolved. Our email provider (Resend) keeps a copy of sent email for 30 days. Help message notifications and our email replies already delivered to our support inbox are not part of the App's database and are not removed by the automated deletion; contact us to have them deleted.
- Turning off order alerts: untick both alert boxes in Settings and save, or use the unsubscribe link in any alert email (one click, no login). Either way the App deletes the stored alert address immediately and sends nothing further. Uninstalling the App also deletes the alert address straight away; the alert records are deleted with the rest of your shop data when Shopify sends the shop deletion request (typically 48 hours after uninstall). Our email provider (Resend) keeps a copy of sent email for 30 days.
- Tags in Shopify: a
fraudpilot-reviewtag the App adds to an order is part of your Shopify order record, not data we hold. It stays on the order after you uninstall the App or after a deletion request. You can remove it in the Shopify Admin. - Holds in Shopify: a fulfillment hold FraudPilot placed is part of your Shopify order record. Uninstalling leaves FraudPilot holds in place. Turn automatic holds off and wait until Settings no longer shows any orders being released, or release them in Shopify under Orders > On hold. It's fine to release a FraudPilot hold yourself.
- On uninstall: when you uninstall the App, Shopify sends a shop-redact request (typically 48 hours after uninstall). On receiving it, all data associated with your shop is permanently deleted, including sessions, queue items, enrichment snapshots, decision-log entries, dispute outcomes, chargeback alerts, card-testing alerts, automatic hold records, Protection Checkup answers, help messages and feedback, your answer about how you found the App, and your shop record. Deletion is completed within the timeframe below.
- GDPR / privacy shop-redact: if Shopify sends a shop data erasure request, all shop data is deleted within 30 days (and in practice promptly on receipt).
- Customer redaction: on a customer redaction request (see Section 7), the review artifacts, decision-log rows, hold history, dispute outcomes, chargeback alerts, and order alert records tied to the affected order(s) are deleted within 30 days.
7. Your Rights
You have the right to:
- Access: view your review queue, enrichment snapshots, and full decision history in the App, and export the decision log as CSV.
- Deletion: uninstalling the App deletes all your data (see Section 6). You may also contact us to request deletion without uninstalling.
- Data portability: export your decision log from the App, or contact us to request an export of your stored data in a machine-readable format.
- Correction: contact us if you believe any stored data is inaccurate. Note that the decision log is append-only by design; corrections are made by recording a new decision rather than altering a historical entry.
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:
- A
customers/data_requestsurfaces the review artifacts, decision-log rows, hold history, dispute outcomes, and chargeback alerts we hold for the requested customer's orders. - A
customers/redactrequest deletes the order-linked review artifacts, decision-log rows, hold history, dispute outcomes, chargeback alerts, and order alert records for the specified orders. If FraudPilot is holding one of those orders, the hold stays in place and the App tells you, so you can decide whether to cancel the order or release the hold in Shopify (see Section 1). - A
shop/redactrequest deletes all data for your shop.
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: