Last updated: October 2026 · Effective date: October 6, 2026 · Operator: Verdikx LLC
How Verdikx processes data
Verdikx processes merchant account data as a controller and, on the merchant’s behalf, the merchant’s end-customer data as a processor (a “service provider” under California law), to provide evidence history, order screening, refund-abuse insights, dispute preparation and submission, and returns review. The Privacy Policy describes the data in detail, including what is sent for AI processing and how deletion requests are handled.
Our commitments as a processor
- We process end-customer data only to provide Verdikx to the merchant and on the merchant’s documented instructions, which are the settings, connections and actions the merchant chooses in Verdikx.
- We do not sell end-customer data, share it for cross-context behavioral advertising, or use it for any purpose other than providing Verdikx, except the Verdikx Network fraud-prevention signals described below, which apply only to stores whose merchant opted in.
- We do not use merchant or end-customer data to train AI models. OpenAI processes it through its API, under terms that do not allow training on API data.
- People with access to the data are bound by confidentiality, and we apply the security measures in section 11 of the Privacy Policy.
- We help merchants answer their customers’ access and deletion requests. Shopify customer data requests produce an automatic export; customer redaction and store deletion requests are carried out as described in the Privacy Policy.
- We notify merchants without undue delay after becoming aware of a personal data breach affecting their data.
- When the merchant uninstalls or asks us to, we delete the merchant’s data as described in the Privacy Policy, except where the law requires us to keep it.
Verdikx Network
The Verdikx Network is opt-in. For fraud prevention only, Verdikx pools outcome events (chargebacks, won disputes, refund abuse and undisputed orders) across stores whose merchant joined by agreeing to the Verdikx Network terms. Buyer identifiers are converted to one-way keyed hashes (HMAC-SHA256 with a key held only on Verdikx’s servers) before storage, so no raw customer data is shared between merchants. Signals flow only between participating stores, which receive only aggregate counts, and only when at least three other participating stores contributed. Signals are never used for credit, employment, insurance or housing eligibility decisions. A merchant can leave at any time in Settings, which stops sharing and receiving immediately and deletes the store’s past contributions. Details are in the Privacy Policy.
Subprocessors
These providers process data for Verdikx. Providers marked as optional are used only when the merchant connects them or the feature is configured.
| Provider | Purpose | Data | When used |
|---|---|---|---|
| Shopify | Source platform, app installation, authentication and subscription billing | Store, order, customer, fulfillment, policy and dispute data you authorize; subscription status | Always (the app runs on Shopify) |
| Stripe (Verdikx billing) | Card billing for Verdikx subscriptions of workspaces that are not billed through Shopify, through Stripe's hosted Checkout and billing portal, and invoices for custom agreements with workspaces not on Shopify, sent through Stripe | Account email, internal account id, plan and billing cycle, and subscription and invoice status; for Enterprise invoices, the billing contact's email address, the company name and the invoice amount and reference. Card and bank details are entered on Stripe's hosted pages and never reach Verdikx | Only for workspaces billed by card and Enterprise customers invoiced through Stripe (Shopify stores are billed through Shopify Billing) |
| Google (sign-in) | Sign in with Google (OpenID Connect) for merchant accounts and the Verdikx team console | Your Google account email address, name and account identifier returned at sign-in | Only if you choose to sign in with Google |
| Microsoft (sign-in) | Sign in with Microsoft (Microsoft Entra ID, through Supabase Auth) for merchant accounts | Your Microsoft account email address, name and account identifier returned at sign-in | Only if you choose to sign in with Microsoft |
| Vercel | Application hosting, serverless functions and scheduled jobs | All data processed by the application in transit and during request handling; request logs | Always |
| Supabase | Database, authentication and file storage | Merchant accounts, stored store records, evidence snapshots, uploaded files and evidence packets | Always |
| OpenAI | AI-assisted drafting of dispute responses, contradiction findings, reading forwarded dispute notices, explaining flagged or held orders and customer profiles, and the Ask Verdikx in-app assistant | A limited, de-identified subset of order evidence and redacted customer-message excerpts (see the Privacy Policy); for risk explanations, screening results with a masked email (first letter and domain), the IP network prefix with its country, its state or region when the optional location lookup gives one (never its city) and its network, billing and shipping country and state, and history counts (no names, street addresses, full IPs, phone numbers or payment details); the subject, sender and text of dispute and alert emails you forward to your intake address, with email and IP addresses, IBANs and card-like numbers masked first and common formats of phone numbers, street addresses and buyer names masked too (masking is pattern-based, so an unusually written detail can still get through; order numbers and amounts are kept); for Ask Verdikx, the questions you type, the page you are on and a few non-sensitive account facts. No uploaded files. Sent through the OpenAI API with response storage off; under OpenAI's API terms this data is not used to train OpenAI's models | When AI features are enabled for the deployment |
| Stripe | Optional connection to import Stripe disputes and early fraud warnings and submit evidence you approve | Stripe dispute and payment records and the evidence you choose to submit | Only if you connect a Stripe account |
| PayPal | Optional connection to import PayPal disputes and inquiries and submit evidence you approve | PayPal dispute and transaction records, including buyer name and email; the evidence you choose to submit | Only if you connect PayPal |
| Square | Optional connection to import Square disputes and submit evidence you approve | Square dispute and payment records; the evidence you choose to submit | Only if you connect Square |
| Braintree (PayPal) | Optional connection to import Braintree disputes and submit evidence you approve | Braintree dispute and transaction records, including customer email; the evidence you choose to submit | Only if you connect Braintree |
| Adyen | Optional connection to import Adyen disputes and submit evidence you approve | Adyen dispute notifications and payment references; the evidence you choose to submit | Only if you connect Adyen |
| Checkout.com | Optional connection to import Checkout.com disputes and submit evidence you approve | Checkout.com dispute and payment records; the evidence you choose to submit | Only if you connect Checkout.com |
| Authorize.net | Optional connection to import Authorize.net chargebacks for manual response | Chargeback and transaction records, including customer email and billing details returned by Authorize.net | Only if you connect Authorize.net |
| Klarna | Optional connection to import Klarna disputes and submit evidence you approve | Klarna dispute records, order references and the evidence you choose to submit | Only if you connect Klarna |
| Afterpay / Clearpay | Optional connection to import Afterpay or Clearpay disputes and submit evidence you approve | Dispute records, order references and the evidence you choose to submit | Only if you connect Afterpay or Clearpay |
| Affirm, Airwallex, Cybersource, Mollie, Primer, Rapyd and Worldpay (beta) | Optional connections to import disputes from these processors and, where the processor accepts evidence by API (Affirm, Airwallex, Worldpay), submit evidence you approve | Dispute and payment records, which can include the buyer's name and email; the evidence you choose to submit | Only if you connect the processor |
| Razorpay, Mercado Pago, Amazon Pay and Shift4 (beta) | Optional connections to import disputes from these processors and submit evidence you approve through each processor's evidence API | Dispute and payment records, which can include the buyer's name and email; the evidence you choose to submit | Only if you connect the processor |
| WooCommerce (your own store) | Optional connection to import orders and disputes from your WooCommerce store | Orders, customers (email, name, addresses) and fulfillment details read from your store's REST API | Only if you connect a WooCommerce store |
| Rutter | Optional connection to import orders from your other sales channels | Orders from connected channels, including customer email, items, totals and fulfillment details | Only if you connect a sales channel |
| commercetools, Miva and VTEX (beta) | Optional connection to import orders from these commerce platforms | Orders, including customer email, name, addresses, items, totals and fulfillment details | Only if you connect the platform |
| Gorgias | Optional help desk connection to attach customer conversations as evidence | Tickets and messages with the customer, including name and email | Only if you connect Gorgias |
| Zendesk | Optional help desk connection to attach customer conversations as evidence | Tickets and messages with the customer, including name and email | Only if you connect Zendesk |
| Intercom | Optional help desk connection to attach customer conversations as evidence | Conversations with the customer, including name and email | Only if you connect Intercom |
| Google (Gmail API) | Optional mailbox connection to attach customer email threads as evidence | Email messages exchanged with the customer, read-only | Only if you connect a Gmail account |
| Merge.dev | Optional unified connection to other help desks | Tickets and messages with the customer, including name and email | Only if you connect a help desk through Merge |
| Freshdesk, Help Scout, LiveAgent and Re:amaze (beta) | Optional help desk connections to attach customer conversations as evidence | Tickets and messages with the customer, including name and email | Only if you connect the help desk |
| Front and Kustomer (beta) | Optional help desk connections to attach customer conversations as evidence, read with the API token or key you create | Conversations, messages and internal notes with the customer, including name and email | Only if you connect the help desk |
| Recharge | Optional subscription-history evidence | Subscription and charge history for the disputed customer | Only if you connect Recharge |
| Skio | Optional subscription-history evidence | Subscription and order history for the disputed customer | Only if you connect Skio |
| Loop Returns | Optional returns evidence | Return and exchange records for the disputed order | Only if you connect Loop Returns |
| Bold, Chargebee, NetSuite and Recurly (beta) | Optional subscription, billing and order-history evidence | Subscription, invoice, charge and order history for the disputed customer | Only if you connect the service |
| AfterShip | Optional shipment tracking evidence | Tracking numbers and returned tracking events | Only if you connect AfterShip |
| ShipStation, EasyPost and ShipBob (beta) | Optional shipping evidence from your own shipping or fulfillment account, read with the API key or token you create | Order and tracking references; returned shipment records (ship date, carrier, service and tracking number) and tracking events. Recipient names and addresses are not stored | Only if you connect the service |
| 17TRACK (beta) | Optional shipment tracking evidence with your own 17TRACK API key | Tracking numbers (registered with 17TRACK under your account) and the returned tracking events | Only if you connect 17TRACK |
| Postmark | Inbound email: receiving the dispute and alert emails you forward to your Verdikx intake address | The forwarded email, including sender, recipients, text and attachments | Only if you forward email to your intake address and Postmark is the inbound email provider configured for the deployment |
| SendGrid (Twilio) | Inbound email: receiving the dispute and alert emails you forward to your Verdikx intake address | The forwarded email, including sender, recipients, text and attachments | Only if you forward email to your intake address and SendGrid is the inbound email provider configured for the deployment |
| SEON | Optional fraud-data enrichment for order screening, using the merchant's own SEON licence key | For each screened order: buyer email, phone number and checkout IP address, order amount, billing and shipping country and the order id. SEON's verdict is stored with the screening result | Only if a merchant connects SEON and turns it on |
| Pre-dispute alert providers (Ethoca, Verifi RDR and CDRN, Chargebacks911, Midigator, Kount) | Receiving pre-dispute alerts that the merchant's alert provider sends to Verdikx | Alert details such as the alert type, amount, currency, transaction or order reference and outcome, plus the buyer's email address and the card's last four digits when the provider includes them (used to match the alert to an order) | Only if a merchant routes alerts to Verdikx |
| Shippo | Shipment tracking scans | Carrier name and tracking number. Recipient names in scan text are removed; addresses are not retained | When tracking is checked for a supported carrier |
| UPS, FedEx, USPS (direct carrier APIs) | Tracking and, where authorized, proof-of-delivery documents | Tracking numbers; returned tracking events and authorized delivery documents | Only where direct carrier access is configured |
| Sentry | Error monitoring | Technical error details with internal account identifiers | Only if error monitoring is configured |
| Resend | Email notifications, including links to customer data-request exports; inbound email when Resend receives the emails you forward to your intake address | Recipient email address and notification text; for inbound email, the forwarded email, including sender, recipients, text and attachments | Only if email notifications are configured, or Resend is the inbound email provider configured for the deployment |
| Twilio | SMS notifications | Recipient phone number and notification text | Only if SMS notifications are configured |
| Cloudflare (Turnstile) | Bot protection on website sign-in, sign-up and password reset, and on the public early access, careers, and privacy request forms | IP address and technical browser details used to tell people from automated traffic; not the account or form contents | When bot protection is configured for the deployment (never inside Shopify admin) |
| MaxMind (GeoLite2 databases; optional GeoIP2 Insights) | IP intelligence for order screening: the country and network of a checkout IP address | None for the GeoLite2 databases: we download them and look IP addresses up on our own servers, so no IP address is sent to MaxMind. Only if the paid GeoIP2 Insights service is enabled for the deployment is the checkout IP address sent (no name, email, order or store details), with answers cached by IP for 7 days | Databases: when a MaxMind licence key is configured for the deployment. Insights: only if enabled for the deployment |
Third-party data
Verdikx looks up the country and network of checkout IP addresses in MaxMind’s GeoLite2 databases on its own servers. This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com.
International transfers
Data is processed in the United States and in other countries where these providers operate. For transfers from the EU, UK or Switzerland we rely on the safeguards in our providers’ data processing terms, such as the Standard Contractual Clauses.
Changes
We update this list before a new subprocessor begins processing merchant data. Questions or a request for a data processing agreement: privacy@verdikx.com.