Is ChargeFix safe? What it reads and what it keeps

You are one click from installing a chargeback app, and Shopify has put a permissions screen in front of you. It lists what the app wants to read in your store. You have a dispute due in four days, a customer database you would rather not leak and a growing suspicion that nobody reads these screens. You are right to hesitate. Handing an app your orders is a real decision.

So, is ChargeFix safe? We make it, which means you should not take our word for it, and this guide is built around that. It tells you what ChargeFix reads and does not save, what it cannot do, where our proof is thin and how to check any Shopify app's permissions yourself in ten minutes. The aim is that you finish this post able to decide for your own store, whether you pick ours or someone else's.

This guide is for you if:

You are about to install a chargeback app and want to know what you are agreeing to.
You handle customer data and want a practical way to judge any Shopify app.
You are a careful buyer who would rather see a checklist than a promise.

Last updated: 30 October 2026. Written by the ChargeFix team. Reviewed against sources on 30 October 2026.

A note on bias: we make ChargeFix, so we gain if you install it. We do not claim any security certification in this post, and we do not know your risk tolerance better than you do. Where we cannot give you proof, we say what to ask for instead. Dollar figures in the worked examples are assumptions.

The 30-second answer (TL;DR)

A chargeback app needs to read your orders, fulfillment and payment dispute records to build evidence. That is a legitimate need, and it is also sensitive access, so you should check it.
What we can state about ChargeFix: it works with Shopify Payments only, customer data is read during review and is not saved, Manual mode is the default so nothing goes to the bank until you approve it and we never take a cut of wins.
What you should know: ChargeFix is new and has no public reviews. This post does not claim a security certification.
You can verify much of this yourself. The permission screen at install lists the scopes. Shopify's own documentation says what each scope allows, and the dispute evidence scopes require approval from Shopify.
Controls that protect you: start in Manual mode, test on the Free plan's 2 filings, review every draft before it goes out and uninstall if you are unhappy.
The riskiest thing a chargeback app can do is submit a wrong response, since evidence is final once submitted. That is a control question as much as a data one.

Quick note: Safety here has two parts. One is data: what the app can see and keep. The other is action: what it can do in your name. A good answer covers both, and you can test both before you commit.

At a glance

Question to ask any app	Where to check	What a good answer looks like
What can it read in my store?	Permission screen at install; scope list	Scopes match the job: orders, fulfillments, disputes
Does it save customer data?	Privacy policy; ask the vendor	Clear retention rule, stated in plain words
Can it act without me?	App settings; ask the vendor	A Manual mode where you approve each response
What happens when I uninstall?	Vendor docs; test it	Access revoked, data deletion explained
Who else sees my data?	Privacy policy; subprocessors list	Named providers, stated purposes
What if it gets something wrong?	Terms; support	A way to review before sending and a stated process for errors
How long has it existed?	App Store listing; reviews	Honest about age and track record

Why does a chargeback app need access to my store?

Because evidence lives there. A dispute response is built from the order, the shipping record, the payment details, the refund history and the customer's earlier orders. An app that cannot read those can only give you a blank form.

Shopify's developer documentation lists the access scopes an app can request. Four are central to dispute work.

Dispute records. read_shopify_payments_disputes lets an app read Shopify Payments dispute objects, so it can see which disputes are open and their reasons.

Dispute evidence. read_shopify_payments_dispute_evidences and write_shopify_payments_dispute_evidences let an app read and write the evidence on a dispute. Both require approval from Shopify before an app can declare them. That approval step is a check on the app, and it is a useful thing to know.

Orders. read_orders covers orders, fulfillments and order transactions, but only for orders created in the last 60 days. Older orders need a separate scope, read_all_orders, which also requires approval.

Customers. read_customers lets an app read customer records, which helps with purchase history.

Merchants approve these scopes when they install. You are not asked to hand over a password or card number. You are asked to approve a list.

The scopes above are from Shopify's documentation, not from ChargeFix's listing. We want you to read the live permission screen when you install, because that is what is binding, and scope lists change as products change.

Is ChargeFix safe with customer data? What it reads and what it keeps

Here is what we can say plainly.

It reads order, fulfillment, payment and customer records during review. This is how it builds the evidence and scores it. When a dispute arrives, ChargeFix looks at what Shopify holds about that order so it can check the evidence item by item.

Customer data is read during review and is not saved. The review uses the data to produce a score and a draft. We do not keep a copy of your customers' personal details in our own store.

A filing is recorded. A dispute counts as one filing the first time its evidence is saved or filed, and usage resets on the 1st of each month. That is how plan limits work, and it means the app keeps enough to count, not a library of customer data.

It works with Shopify Payments only. It does not connect to Stripe direct, PayPal or other processors, so those disputes and data are out of its reach.

It does not send alerts or prevent disputes. It works after a dispute exists.

We are being specific about what we say and what we do not. We are not publishing a scope-by-scope table from ChargeFix in this post, because the install screen is the authoritative source and a copy here could go out of date. Read the screen. If anything on it surprises you, stop and ask us.

What does ChargeFix not claim?

This section matters because security pages often overclaim.

We do not claim a security certification in this post. If you need one for your policies, ask us directly and we will answer, rather than you assuming from silence that we hold one.

We do not claim a track record. ChargeFix is new and has no public reviews yet. That is a real risk factor for a careful buyer, and it is why we point you to controls that do not depend on trust.

We do not claim to lower your dispute count, reach other processors or guarantee wins. No chargeback tool controls what a bank decides, and ChargebackWiz's own site says as much about its product.

We do not claim to know your legal obligations. Privacy law varies by state and by the data you hold, and this is not legal advice.

How do you read the permission screen?

Use the same method on any app. It takes about five minutes.

Count the scopes. A response tool needs a handful, not thirty.
Match each to the job. Orders, fulfillments, disputes and dispute evidence make sense. Products, themes, marketing and discounts do not.
Look for write access. Writing dispute evidence is expected. Write access to orders, customers or products needs a reason. Ask for it.
Check the order history reach. If the app can read only 60 days of orders, ask how it handles disputes on older orders. Disputes often arrive months after the sale.
Look for anything about other stores or people. An app asking for data it has no reason to use is a flag.

Here is how that works in practice, as an illustration of the method, not as a copy of any app's real list.

Scope	What Shopify says it allows	Does a dispute response app need it?
read_shopify_payments_disputes	Read dispute objects	Yes, to see open disputes
read_shopify_payments_dispute_evidences	Read dispute evidence	Yes, requires Shopify approval
write_shopify_payments_dispute_evidences	Write dispute evidence	Yes if it files for you, requires approval
read_orders	Read orders, fulfillments and transactions from the last 60 days	Yes
read_all_orders	Read older orders	Likely, since disputes arrive late; requires approval
read_customers	Read customer records	Maybe, for purchase history
write_orders	Change orders	Ask why
write_products	Change products	Almost never

If the screen you see differs from your expectation, the question to ask is simple: "What do you do with this?"

What questions should you ask any chargeback vendor?

Send these by email before you install. The answers, and how quickly they arrive, tell you a lot.

Which scopes do you request and why?
Do you store customer personal data? If so, which fields and for how long?
Who are your subprocessors, such as hosting and email providers?
How do you handle a request to delete a customer's data?
What happens to our data when we uninstall?
Can your app submit evidence without our approval? How do we switch that off?
If a draft contains an error, who is responsible and what is the process?
Do you hold any security certification, and can you share it?
How long has the product been live and how many stores use it?
How do I reach a human?

A vendor that answers plainly, even when the answer is "no, we do not hold that", earns more trust than one that sends a brochure.

What can go wrong with a chargeback app?

Think in terms of failure modes, not just data theft.

Wrong response submitted. Evidence is final once submitted, so an error stays. The control is Manual mode and a review habit.

Over-broad access. An app that can change orders or customers can damage them. The control is reading the scope list.

Data kept longer than expected. The control is asking about retention and checking the privacy policy.

Billing surprises. Percentage-based fees can grow with your recoveries. The control is understanding the pricing before you install. ChargeFix uses flat monthly plans and never takes a cut of wins.

Vendor disappears. New products can close. The control is not putting the only copy of your evidence in the app, and keeping your own policy and shipping records.

Mismatch with your processor. An app that does not support your gateway does nothing for those disputes. ChargeFix covers Shopify Payments only. See our post on Stripe and Shopify Payments limits.

None of these is unique to us, and each has a practical control.

What controls protect you while you test?

You can limit risk without trusting anyone.

Start in Manual mode. In ChargeFix, Manual mode is the default. Nothing is sent to the bank until you review and approve it. Automatic mode is available on Starter and above, and we suggest you try it only after you have seen how the tool scores your own orders. Our post on automatic vs manual chargeback response covers the choice.

Test on the Free plan. It includes 2 filings a month. Use them on real disputes, compare the drafts with what you would have written and see how much customer data the app asks for.

Review every draft. Check names, amounts, dates and claims, and confirm each claim has a file. Our guide to the response letter generator has a three minute checklist.

Keep your own copy. Save the evidence pack and the final response in your own files.

Know the exit. Uninstalling an app from the Shopify admin ends its access to your store. Ask the vendor what it does with data it holds afterward.

Watch the first month. Look at which disputes the tool scored strong and weak, and whether the outcomes made sense.

These steps cost almost nothing. They are worth doing for any app that touches your orders.

Illustration: the cost of one bad automatic submission

A store has an average order of $120 and 20 disputes a month. It switches on automatic mode on day one without reviewing any drafts. In the first month, 2 responses go out with a weak or wrong claim and lose. Assume that, reviewed by a human, those 2 would have been accepted or fixed, with a 40 percent win chance if fought well. All numbers are assumptions.

Item	Calculation	Result
Swing per case	$120 + $15	$135
Expected wins lost per bad submission	40% x $135	$54
Bad submissions	2
Expected cost of the 2 errors	2 x $54	$108
Time saved by skipping review	20 x 2 min at $30 an hour	$20
Net cost of no review	$108 - $20	$88

Skipping review saved $20 of time and cost an expected $108 of recoveries, a net loss of $88 in the first month. These figures are illustrative, but the shape is real: review time is cheap and wrong final submissions are not. That is why Manual mode is the default and why we suggest trying automatic mode on lower value, routine disputes only after you trust the scores.

Illustration: a ten minute trial plan

Plan a trial like a small experiment. A store has the Free plan's 2 filings and a dispute due in five days.

Step	Time	What you check
Read the permission screen	5 min	Scope count, write access, order reach
Read the privacy policy	5 min	Retention, subprocessors, deletion
Install and connect	3 min	The app sees only Shopify Payments disputes
Open one live dispute	8 min	Does the evidence match your records?
Compare with your own draft	10 min	Does the letter claim anything you cannot show?
Decide on the rest	5 min	Keep, adjust, or uninstall

The whole check takes about 36 minutes. At $30 an hour that is $18 of your time. The decision it informs affects every dispute for the next year. If the trial shows the tool inventing a fact or asking for access that makes no sense, you stop, and you have lost $18.

Illustration: what the safest app can still not do

An app has narrow scopes, a clear retention rule and a manual default. It still cannot change the following, and you should not expect it to.

Limit	Why it remains
Bank decisions	The issuer decides every dispute
Your dispute count	Card programs count disputes you win; Visa's acquirer monitoring program set its excessive tier at 1.5% from 1 April 2026 for merchants with 1,500 or more fraud and dispute cases a month
Missing evidence	No app can create a signature or record you never saved
Other processors	A Shopify Payments app does not see Stripe direct or PayPal disputes
Your review duty	Evidence is final once submitted

A safe app lowers the chance of harm. It does not replace your review.

Is a new app with no reviews too risky?

It is riskier than an established one in one way: you have less outside evidence. It is not riskier in the ways you can test yourself.

Reviews are social proof, and they have limits. Competitor listings that we read on 30 October 2026 show a range, from an app with a few hundred reviews to ones with a handful or none. Several recent entrants have no reviews at all, and one lists a single review. A high rating on a handful of reviews tells you little, and a long review history tells you about the past product, not today's.

What you can do instead is lean on direct checks.

Ask questions and judge the answers. Speed and clarity matter.
Test with low stakes. The Free plan exists for this.
Prefer reversible choices. Manual mode, flat pricing and an easy uninstall all keep you in control.
Revisit after a month. Look at what the tool did and decide with data.

We would rather you try ChargeFix carefully than trust it blindly. If you want a longer record before you decide, wait and check the listing again later, and use another tool in the meantime. Our chargeback software comparison checklist can help you choose.

How does this compare with other kinds of risk?

Context helps. Your store already relies on many apps with access to orders: shipping tools, email platforms, reviews, loyalty programs and accounting links. Each reads customer data. The question is not whether to allow any access, but whether each app's access matches its job and whether you have read the screen.

A dispute app is somewhat unusual in that it can take an action with consequences, since a submitted response is final. That is why we spend more of this post on control than on encryption. Most real-world harm from a wrongly configured tool comes from an action taken without review, not from an attack.

What is the difference between reading data and saving it?

The two words sound close and mean very different things. When an app reads data, it looks at it in order to do a job, such as scoring a dispute. When an app saves data, it keeps a copy somewhere it controls, which creates a store of customer details that has to be protected, backed up and eventually deleted.

For a chargeback tool, reading is unavoidable. Saving is a choice. Our choice is that customer data is read during review and is not saved. The consequence is a smaller pile of your customers' details sitting outside your store. The trade-off is that the tool works from what Shopify holds at the time, so if a record has been edited or removed in Shopify, that is what the tool sees. Any vendor can make the same choice or the opposite, and the useful move is to ask which one they made.

What should a privacy policy tell you?

You do not need to be a lawyer to read one for the points that matter. Look for plain answers to these.

What data is collected. Names, emails and addresses are different from order totals and tracking numbers. The policy should say which.
Why it is collected. A stated purpose tied to the service, such as building a dispute response.
How long it is kept. A number or a clear rule. "As long as necessary" is not an answer.
Who else gets it. Hosting, email and analytics providers should be named or described.
How you can ask for deletion. A contact route and a promised timeframe.
What happens on uninstall. Whether data is deleted, kept or anonymized.

If the policy is vague on two or more of these, email the vendor. A short, honest reply is a good sign. A reply that dodges is also an answer.

Who on your team should be allowed to install apps?

Many stores worry about a vendor and forget their own door. Shopify lets you create staff accounts with limited permissions, so not everyone needs the ability to approve an app that reads orders. A sensible habit is to let one or two trusted people approve new apps, to ask them to read the permission screen each time and to review the full app list every quarter.

Remove anything you no longer use. An unused app with access to your orders is risk without benefit. If a contractor installed something years ago and left, check it. This costs nothing and often finds an app nobody remembers approving.

What should you do if something goes wrong?

Plan before you need it, and keep the plan short.

Stop the action. If a draft looks wrong, do not submit it. If an automatic response went out, note the dispute and the time.
Uninstall if you need to. Removing the app from your Shopify admin ends its access to your store.
Write to the vendor. Describe what happened, with order numbers and dates, and ask for their account of it.
Keep records. Save screenshots, emails and the evidence pack.
Tell your team and, if customer data is involved, check your own legal duties. Notification rules vary by state, and we are not lawyers.

The point of the plan is calm. A store that knows its steps handles a problem in an afternoon instead of a week.

Common mistakes when approving an app

Clicking through the permission screen. It takes two minutes to read and tells you what you are agreeing to.
Ignoring write access. Read access is usually low risk. Write access to orders or customers is not.
Assuming ratings equal safety. They measure satisfaction, not data practice.
Turning on automatic mode on day one. Review a batch first.
Not asking about retention. "We do not store it" and "we store it for a year" are very different answers.
Leaving unused apps installed. Remove anything you no longer need.
Forgetting your own records. Keep policy copies and shipping records outside any one app.
Treating our word as proof. Check the screen, the policy and the answers to your questions.

What we checked, and what you should check

We read Shopify's developer documentation on API access scopes, including the dispute, order, customer and fulfillment scopes and the approval requirement for dispute evidence scopes, along with Shopify's help pages on the chargeback process, Shopify's Protect terms, ChargebackWiz's site and the Shopify App Store listings of several competing apps, all on 30 October 2026. We describe ChargeFix's behavior from our own product knowledge: it works with Shopify Payments only, reads customer data during review without saving it, defaults to Manual mode and never takes a cut of wins. We did not publish ChargeFix's scope list here, because the install screen is the authoritative source.

The order values, error counts, win chances and hourly values in the illustrations are our assumptions. This post is not legal advice, and privacy obligations vary by state and by the data you hold. Check the live permission screen, privacy policy and Shopify documentation before you decide.

Frequently asked questions

Is ChargeFix safe to install on my Shopify store?

We can tell you what it does: it works with Shopify Payments only, reads customer data during review without saving it, defaults to Manual mode so nothing goes to the bank until you approve it and never takes a cut of wins. It is also new with no public reviews. Check the permission screen and test on the Free plan before committing.

What does ChargeFix save about my customers?

Customer data is read during review and is not saved. A filing is counted the first time a dispute's evidence is saved or filed, which is how plan usage works, and usage resets on the 1st of each month. If you need more detail for your own policies, ask us directly.

Can ChargeFix send evidence without my approval?

Not in Manual mode, which is the default. Nothing goes to the bank until you review and approve it. Automatic mode is available on Starter and above for stores that want routine cases handled with less touch. Because evidence is final once submitted, we suggest reviewing a batch of drafts before switching to automatic.

What permissions do chargeback apps ask for?

Typically dispute records, dispute evidence read and write, orders and sometimes customers. Shopify's documentation says the dispute evidence scopes require Shopify's approval, and that read_orders covers only orders from the last 60 days, with older orders needing read_all_orders. Match each scope to the job and ask why for anything extra.

Does ChargeFix have a security certification?

This post does not claim one. If you need a certification for your own policies, ask us directly and we will answer plainly. We would rather you hear a clear answer than infer one from silence. You can still check the permission screen, privacy policy and Shopify's documentation yourself.

What happens to my data if I uninstall?

Uninstalling an app from your Shopify admin ends its access to your store. What the vendor keeps afterward is a question for the vendor, so ask in writing before you install. For ChargeFix, customer data is read during review and not saved, but check the privacy policy and ask us about any records kept for billing and filing counts.

Is it risky that ChargeFix has no reviews yet?

It means you have less outside evidence, so lean on direct checks. Read the permission screen, ask the vendor questions, test on the Free plan's 2 filings in Manual mode and review every draft. If you prefer a longer track record, wait and use another tool meanwhile. Our comparison checklist can help.

Can a chargeback app hurt my store?

Mainly through a wrong response that is final once submitted, or through over-broad access. Manual mode, a review habit and a close read of the scopes control both. No app can change a bank's decision or lower your dispute count, so judge it on how it helps you decide and prepare, not on promised outcomes.

What should I do first?

Open the Shopify admin and look at the permission list of the apps you already have, starting with any that touch orders. Then read the permission screen of the chargeback app you are considering, match each scope to its job and email the vendor the ten questions above. If the answers satisfy you, test on the Free plan.

Start free trial with ChargeFix

If you want a chargeback app that defaults to your approval, reads customer data during review without saving it and never takes a cut of what you win, ChargeFix starts free and moves to flat monthly plans as your volume grows. It checks your order evidence item by item, tells you honestly whether a case is worth fighting and drafts a letter from your real records, so you review a draft instead of starting from nothing. Nothing goes to the bank until you say so, and paid plans include a 14-day free trial.

Start free trial

Is ChargeFix safe? Data, permissions and a 10 minute check you can run on any Shopify app