Is it safe to connect a chargeback app to your Shopify store?

You are about to hand a stranger's software the keys to your orders, your customers and your payment disputes. That is not a reason to say no. It is a reason to know exactly what you are saying yes to.

Before you connect any chargeback app, read the Shopify app permissions it asks for on the install screen, ask why it needs each one, and check what it can still see once installed. A safe app asks for the least it needs, lets you review its work and lets you leave cleanly.

This guide is for you if:

• You are about to install a chargeback app on your Shopify store and want to know what you are agreeing to.
• You have already installed one and never looked at what it can read.
• You want a short audit you can repeat every quarter, plus the questions to put to any vendor.

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

The 30-second answer (TL;DR)

• Safety starts with Shopify app permissions: the list of store data an app asks to read or change when you install it.
• A chargeback app plausibly needs orders, customers, fulfilments and disputes. It rarely needs your whole product catalogue, your staff list or your store settings. Ask about anything extra.
• You can audit your installed apps in about five minutes. At A$40 an hour that costs about A$3.33 per app.
• Look for three things: minimal app permissions, a review step before anything is filed, and a clear way to leave.
• Removing an app removes its connection to your store, but data it already copied is covered by the vendor's own policy. Ask what that policy says.
• I could not verify any vendor's security claims, and I do not make claims about any app. This guide gives you the questions, not a verdict.
• If the answers are vague, do not install it. A weak answer on a trial day is the best warning you will get.

Quick note The misunderstanding: an app in the Shopify App Store is safe by default. The correct version: an app can reach only the access you approve, but you are the one who approves it, so you are the one who has to read it.

What to check before connecting a chargeback app

Check	What to look for	A good answer	A bad answer
App permissions	The list on the install screen	Short, and each item has a plain reason	Long, with items that have nothing to do with disputes
Approval	Whether you review each filing	You approve before anything is sent	It files on its own with no review
Honesty	Where the evidence text comes from	Only facts from your records	It can write claims you never supplied
Data	What it stores and for how long	A written policy with a retention period	No policy, or "we keep everything"
Exit	What happens when you uninstall	Access ends, and you can ask for deletion	No mention of deletion
Support	Who answers on deadline day	A named route and a response time	A contact form only

What are Shopify app permissions?

Shopify app permissions are the access an app asks for when you install it, such as reading orders or customers. The install screen lists them, and you approve or cancel. Whatever you approve is what the app can reach through its connection to your store until you remove it.

Shopify calls these access scopes in its developer documentation. As a merchant you see them as a list of plain statements, for example that an app can view or edit certain store data. I could not verify the exact wording of every scope, and Shopify changes the screens over time, so use the wording on your own screen as the source of truth. What does not change is the principle: the app gets the app permission you approve and nothing else.

That makes the install screen the most useful page in the whole process, and the one merchants read least. If you read only one thing before you click "Install", read the list of Shopify app permissions.

Why would a chargeback app need access to your store at all?

Because a chargeback response is built from your own records. To fill in an evidence packet for you, a tool has to see the dispute, the order behind it, the customer's details and the shipping or delivery record. Without that access, you would be pasting everything in by hand, and you would not need the app.

Here is a plausible mapping from job to data. It is my own reasoning about what each job needs, not a statement about any particular vendor.

Job the app does	Data it plausibly needs	Why
See that a dispute exists	Disputes from your payments account	It has to know the reason, amount and deadline
Match the dispute to an order	Orders	The order holds items, prices and addresses
Show who bought	Customer name, email, address	The bank compares these with the cardholder
Show it was sent	Fulfilments and tracking	Proof of delivery is the core of many disputes
Show your terms	Store policies	Shipping and returns policies back up your case
Remind you of the deadline	Dispute due dates, and a way to contact you	Shopify says the due date is typically 7 to 21 days after filing

Anything beyond this list is a question to ask, and every extra app permission should come with a reason. Some extra access can be reasonable, such as reading your store name for the evidence header. But if an app wants to change your products, edit your theme or read your staff accounts, ask what that has to do with a dispute.

Which app permissions should make you stop and ask?

Three kinds should: app permissions to change things when only reading is needed, app permissions over data unrelated to disputes, and app permissions that grant access to people rather than records. Each can be legitimate, and each needs a plain explanation before you accept.

• Write access where read access would do. An app that only needs to look at an order does not need to edit it. Ask why it needs to change anything.
• Unrelated data. Product catalogue, discount codes and marketing lists have little to do with a dispute. If the app asks for them, ask what they are for.
• People, not records. Staff accounts and collaborator access let someone act as you. Shopify lets you give outside people access to your store, and an app asking you to do that is asking for more than a data connection.
• Payment details. I could not verify exactly what payment data any Shopify app can reach, and I do not claim anything about it. If a vendor says it handles card data, ask how, and ask for it in writing.

If a vendor cannot tell you in two sentences why it needs an app permission, the answer is no for now.

How do you audit your installed apps in five minutes?

Open your Shopify admin, find the list of installed apps, and for each one check what it can access, when you last used it and whether you still need it. Remove anything you do not use. The whole job takes about five minutes per app the first time and less on later rounds.

Use this checklist. It works for a chargeback app and for every other app on your store.

APP PERMISSION AUDIT (5 minutes per app)

App name: ______________________   Installed on: ____________
Last time I used it (date): ____________   Still needed (Y / N): ______

[ ] I have read the list of permissions it holds
[ ] Every permission has a reason I can state in one sentence
[ ] No permission looks unrelated to what the app does
[ ] It cannot change things it only needs to read (or I know why it can)
[ ] I know who at the vendor to contact if something looks wrong
[ ] I have read its privacy and data policy (retention period noted: ______)
[ ] I know what happens to my data if I remove it
[ ] If it files anything for me, I review it first

Decision: keep / reduce / remove      Next review date: ____________

Illustration 1: what does the audit cost?

Say your time is worth A$40 an hour. Five minutes is one twelfth of an hour, so the audit costs A$3.33 per app. If you have a chargeback app and two other apps with access to orders and customers, auditing all three takes 15 minutes, or A$10. Doing it every quarter costs A$40 a year. These are illustrations of the time, not a statement of how long your apps will take.

Illustration 2: what does one bad filing cost?

Suppose an app files a packet with an error on an A$180 order, and you would have won it with a correct packet. You lose the A$180, plus the A$25 fee that Shopify's fee table lists as refunded only if you win. That is A$205. At A$3.33 an audit, A$205 buys about 61 audits. This does not mean apps file bad packets often. It shows why a review step before filing is worth more than it looks.

What should an app let you control?

An app should let you review what it is about to send, change it and stop it. It should also let you leave without losing a deadline. If a tool files evidence on its own and you only find out afterwards, you have given up the one check that protects your name.

Shopify's own process shows why. Shopify submits the evidence you have saved on the due date, and once the deadline has passed a dispute cannot be changed. So a wrong packet that goes out cannot be taken back. A review step before submission is the safety net.

Ask the vendor these four things, since no app permission list answers them for you:

1. Can I see the full packet before it is sent?
2. Can I edit it?
3. Can I choose to have nothing sent?
4. Is there a record of what was sent and when?

Does an app make up evidence?

It should not. A chargeback response is a statement to a bank that you stand behind. If a tool writes claims that are not in your records, you are putting your name to something you did not check. Ask whether the text comes only from your data and whether anything is generated, and keep the review step so you read it.

This matters more than it sounds. Shopify's help centre says that for product not received disputes it adds AI-generated insights to the evidence it submits. That is Shopify's own process, described on its own help page. Any other tool that generates text should tell you plainly what it generates and let you check it. If you want the facts behind a particular dispute type, see the product not received guide.

What happens to your data when you uninstall?

When you remove an app from your store, its connection to your store ends. What it has already copied is a separate matter, and it is governed by the vendor's data policy, not by Shopify. Ask each vendor how long it keeps data and how you can ask for it to be deleted.

This is the part of the audit most merchants skip, and it is where I could verify the least. I did not find a single authoritative statement on what each vendor retains. So treat the answer as something you need to ask for in writing, not assume. A good vendor will state a retention period and a deletion route without being pushed.

EMAIL TO SEND A VENDOR BEFORE YOU INSTALL

Subject: Questions about data access before I install

Hi,

I run a Shopify store in Australia and I am considering your chargeback app.
Before I install, could you tell me:

1. Which store permissions you request, and the reason for each one.
2. Whether any permission lets the app change my store data, and why.
3. Whether I review and approve every filing before it is sent.
4. Whether evidence text is written only from my records.
5. How long you keep my store and customer data, and where it is stored.
6. How I can ask for my data to be deleted if I stop using the app.
7. Who I contact if something goes wrong near a deadline.

Thank you,
[Name], [Store name]

How do you check a vendor you have never heard of?

Look for a plain privacy policy, a named company, a support route and a trial that lets you test before you commit. A real business can answer questions in writing. You cannot verify a vendor from the outside with certainty, and I do not claim to, but you can see whether it behaves like one that expects to be checked.

Use this short list, and keep the app permission list from the install screen next to it:

• A named company and an address. Anonymous vendors are harder to hold to anything.
• A privacy policy that is specific. It should say what is stored and for how long, not just that data is "protected".
• Reviews you can read. Look at the dates and at how the vendor replies. I do not use ratings here, because I could not verify any, and a few good reviews prove little.
• A free trial or free plan. You can test on a closed dispute before you rely on it.
• Willingness to answer. Send the email above and see how long it takes and how precise the reply is.

How do you test a chargeback app safely?

Install it on a trial, run a closed dispute through it, and compare the packet with your own records. Check what the app can see, what it asks to change and what it would send. Then decide with the audit checklist in hand, before you rely on it for a live deadline.

Here is a plan you can start tomorrow, Thursday 15 October 2026. It takes about a week.

Day and date	What to do
Thu 15 Oct	List every app on your store that can see orders or customers. Note the date you installed each.
Fri 16 Oct	Run the five-minute audit on each one and mark keep, reduce or remove.
Mon 19 Oct	Remove any app you no longer use. Note what it was for.
Tue 20 Oct	Shortlist one chargeback app. Read its app permission list and privacy policy before installing.
Wed 21 Oct	Send the vendor email above. Note the date you sent it.
Thu 22 Oct	Read the reply. Decide whether it answers the questions in plain words.
Fri 23 Oct	If satisfied, install on a trial and run one closed dispute through it.
Mon 26 Oct	Compare the packet with your records. Check nothing in it is wrong or invented.
Tue 27 Oct	Decide: keep, or remove and note why.
Thu 28 Jan 2027	Repeat the audit. Put a reminder in your diary now.

What if you already installed one and never checked?

Check it now. Open the app's details, read the app permissions, and answer the audit questions. If anything is unclear, send the email above. If you do not get a plain answer, reduce or remove the app. The cost of checking is small, and the cost of an unknown connection is open-ended.

Do not panic and do not assume the worst either. A long app permission list is a reason to ask questions, not proof of a problem. Most apps behave as described. The point of an audit is to replace an assumption with a fact. If you find an app you no longer use, remove it first and think about it afterwards.

What should you do if something looks wrong?

Remove the app, check your store for changes you did not make, and contact the vendor and Shopify support. Change passwords for any account that might be affected. Write down what you saw and when, because dates help everyone who has to investigate.

Take the steps in order, starting with the app permission that was granted:

1. Remove the app from your store so its connection ends.
2. Check your recent orders, customers and settings for anything you did not do.
3. Change the passwords of staff and any linked accounts, and turn on two-step sign-in if it is off.
4. Contact the vendor in writing and keep the reply.
5. Contact Shopify support and describe what you found.
6. Check your open disputes and their deadlines, because removing a tool does not move a due date.

I could not verify what formal obligations apply to an Australian business after an incident involving customer data. If customer data may have been exposed, ask an adviser about your duties instead of guessing.

What's different for Australian merchants?

Australian merchants hold customer data about Australian shoppers, so privacy law may apply to what you collect and who you share it with. I could not verify how it applies to a specific app, so ask a professional. You also pay A$25 per dispute, which makes a bad tool costly.

Three Australian points:

• Your customers' data is yours to look after. When you connect an app, you are choosing to share it. That is a decision for you, not for the vendor, so make it deliberately.
• Where data is stored matters. I could not verify the storage location for any chargeback app. Ask each vendor where data is held and whether it leaves Australia, because that can matter for your own privacy obligations.
• The dollar stakes are local. A wrong filing on a disputed order costs the order value plus the A$25 fee, as in Illustration 2. Choose tools you can review, keep each app permission narrow and keep your internal deadline two days early.

I could not verify whether the Privacy Act covers your store, and the answer depends on your size and what you collect. Treat that as a question for an accountant or lawyer.

How is app access different from collaborator access?

App access is a data connection to your store, approved on an install screen. Collaborator access gives a person a login to your admin so they can act as a user. They are different doors. You should treat a request for a login with more caution than a request for a data connection, and review both.

Shopify lets you give outside people access to your store, and some vendors ask for it to "set things up". For a chargeback tool that is rarely needed, because the tool reads records through its connection. If a vendor asks for a login, ask why the connection is not enough, and ask what the person will be able to see and change. If you do grant it, give the narrowest role you can, set a date to remove it and write that date down.

Type of access	What it is	Who holds it	How to review it	How to end it
App connection	Data access approved on the install screen	The app	Check the app permission list in your admin	Remove the app
Collaborator or staff login	A user account in your admin	A person	Check the list of users and their roles	Remove the user
Shared password	A login you gave out directly	Whoever you told	You cannot see who has it	Change the password

The last row is the one to avoid altogether. A shared password cannot be narrowed, cannot be reviewed and cannot be ended for one person without changing it for everyone. If a vendor asks for one, treat that as an answer to your question about how it works.

How do app permissions change over time?

They can change when an app updates. A vendor may add a feature that needs more access, and Shopify may ask you to approve it. You will only notice if you read what you are approving. A quarterly check of each app permission catches changes that a one-off look at install time misses.

When you are asked to approve new access, treat it as a fresh install decision. Read what is being added, ask what it is for and say no if the reason is thin. An app that worked on its old app permissions can usually keep working on them, and a good vendor will explain what a new feature needs and why. I could not verify how Shopify handles every case of changed access, so read the prompt on your own screen.

Keep a simple record of what each app held when you last checked. A two-column note is enough: the app, and its app permissions in your own words. When the list changes, you will see it.

Illustration 3: what does a store-wide audit look like?

Say your store has 12 apps, and four of them touch orders or customers. You audit those four at five minutes each, which is 20 minutes, or A$13.33 at A$40 an hour. You find one app you stopped using last year and remove it. The other apps pass. Done four times a year, the audit costs A$53.33, which is 80 minutes of your time. The cost of the audit is small enough to run every quarter, and the one removed app was an open connection you did not need.

Are there signs an app is cutting corners?

Yes, though none proves anything alone. Several together are a reason to look harder. Treat them as prompts to check the app permission list and ask questions, not as proof of bad faith, since a young vendor can be honest and badly documented.

Watch for these signs:

• An app permission list that does not match the pitch. An app that says it handles disputes but asks for your whole catalogue.
• No privacy policy, or one that says nothing specific. "We take security seriously" is not a policy.
• Pressure to act fast. A discount that expires today is not a reason to skip a read of the app permissions.
• No named company or contact. If you cannot find who runs it, you cannot hold anyone to anything.
• Promises about results. Shopify says it does not decide disputes and strong evidence does not guarantee a win. A tool that guarantees wins is promising something nobody controls.
• Evasive answers. If a plain question gets a vague reply, the vagueness is the answer.

Equally, do not treat a polished website as proof of safety. A good looking page costs little to make. What costs more, and tells you more, is a clear written answer to your seven questions.

What does a sensible setup look like?

A sensible setup is small. One chargeback tool with the minimum access it needs, a review step before filing, a written record of what it can see, a quarterly audit in your diary and an exit plan you have already tested in your head. None of it needs technical skill.

Here is the setup in one table, with the check you run for each part.

Part of the setup	What good looks like	How you check it
Access	Only the data a dispute needs	Compare the app permission list with the table earlier in this guide
Approval	You approve each filing	Run a closed dispute and see whether anything is sent without you
Evidence	Text comes from your records	Read the packet against the order
Data policy	Retention period and deletion route in writing	Ask by email and keep the reply
Exit	You can leave without missing a deadline	Note your open disputes and their due dates before you remove anything
Review	A date in your diary	Set the reminder on the day you install

If you can tick every row, you have done what a merchant can reasonably do about app permission risk. You still cannot prove a vendor is safe from the outside, and I do not claim you can. You can show that you checked, that you kept the access small and that you can remove it quickly.

Common mistakes

1. Clicking install without reading the list. The app permissions screen is the only moment the vendor must tell you what it wants.
2. Assuming the App Store has checked everything. Listing in a store is not a guarantee of how an app handles your data. Check for yourself.
3. Leaving unused apps installed. An app you forgot about still holds whatever access you gave it. Remove it.
4. Accepting broad app permissions to save time. If an app asks for far more than its job needs, ask why, and say no if the answer is thin.
5. Letting a tool file without review. A wrong packet cannot be changed after the deadline. Keep a review step.
6. Not asking about deletion. Removing an app ends its connection. It does not tell you what happens to data already copied.
7. Trusting reviews instead of reading the app permission list. A few good reviews tell you little. Ask your own questions and read the reply.
8. Never repeating the audit. Apps update, and so do their app permissions. A quarterly check catches changes.

Frequently asked questions

Is it safe to connect a chargeback app to my Shopify store?

It can be, if you read the permissions it asks for, confirm each has a clear reason, keep a review step before anything is filed and know how to leave. I could not verify any vendor's security, so I give you checks, not a verdict. Ask your questions in writing before you install.

What Shopify app permissions does a chargeback app need?

Plausibly disputes, orders, customer details, fulfilments and your store policies, since a response is built from those records. It rarely needs your product catalogue, staff list or settings. That mapping is my own reasoning, not a vendor claim, so compare it with the install screen and ask about anything extra.

Can I see what an app can access after I install it?

Yes. Your Shopify admin lists installed apps, and you can review what each can reach. I could not verify the exact screen names, which Shopify changes over time, so use the labels on your own screen. Check at least once a quarter, and remove any app you no longer use.

What happens to my data when I uninstall an app?

Removing an app ends its connection to your store. Data it already copied is governed by the vendor's own policy, not by Shopify. I could not verify any vendor's retention period, so ask each one in writing how long it keeps data and how to request deletion.

Should a chargeback app file disputes without my approval?

I would not allow it. Shopify submits what is saved on the due date, and a dispute whose deadline has passed cannot be changed, so a wrong packet cannot be taken back. Choose a tool that lets you review, edit and stop every filing before it is sent.

How often should I audit my Shopify apps?

Once a quarter is enough for most stores, plus a check whenever an app asks for new permissions. In this guide a five-minute audit costs about A$3.33 per app at A$40 an hour. Set a diary reminder when you install a new app so the next check is not left to memory.

Do chargeback apps see my customers' card numbers?

I could not verify exactly what payment data any Shopify app can reach, and I make no claim about it. If a vendor says it handles card data, ask in writing how it is handled and where it is stored. If the answer is vague, treat that as a warning and do not install.

What should I do if I think an app has misused my store data?

Remove the app, check recent orders, customers and settings for changes you did not make, change passwords, and contact the vendor and Shopify support in writing. Check your open disputes too, because removing an app does not move a deadline. If customer data may be exposed, ask an adviser about your duties.

Does Australian privacy law apply to my chargeback app?

I could not verify how it applies to your store or to a specific app, because the answer depends on your size and the data you collect. You hold your customers' data, so choose what you share deliberately, ask vendors where data is stored, and ask an accountant or lawyer about your own obligations.

Start free trial with ChargeFix

ChargeFix is a Shopify app that helps you prepare chargeback evidence. You review and file it, or let Auto mode handle them. It never invents facts, so once you have checked the Shopify app permissions on the install screen against this list, you can try it on a real dispute during the free trial.

Start free trial

Sources

• Shopify Help Center, "Chargebacks and inquiries" (process, fees, store status)
• Shopify Help Center, "Responding to chargebacks and inquiries"
• Shopify Help Center, "Managing chargebacks in the Shopify admin"
• Shopify Help Center, "Preventing chargebacks and inquiries"
• Not verified in this pass: exact wording of Shopify access scopes, vendor data retention, and application of Australian privacy law to specific apps. Check Shopify's current app permission pages and an adviser before relying on any of them.
• Stripe, Dispute evidence best practices: further reading on how to format convincing evidence
• Adyen, Manage disputes: further reading on how another payment provider handles disputes