Foundation · 2 min
What you need to know
Can ecommerce apps create security risks?
Yes. Apps can read data, change store behavior, inject code, or depend on vulnerable providers. Their access can extend the store’s security and privacy boundary.
What should merchants check before installing an app?
Check publisher identity, support and update history, requested permissions, data practices, security information, contract terms, necessity and a safe uninstall plan.
What customer data should apps be allowed to access?
An app should receive only the customer fields and records needed for its stated function. Do not grant full history when a limited event or field will work.
Should apps receive only the permissions they need?
Yes. Least privilege limits harm from compromise or misuse and makes later review clearer. Reject an app whose required access is disproportionate to its value.
How should unused integrations be handled?
Disable and remove unused integrations, revoke credentials, stop data flows, and confirm retained provider data is handled under contract and policy.
What happens when an integration is compromised?
Revoke access, isolate affected workflows, preserve evidence, identify exposed data or actions, contact the provider, and follow the incident-response process.
How often should installed apps and integrations be reviewed?
Review apps on a risk-based schedule and after permission, ownership, provider, incident or business-purpose changes. High-access apps need a closer review.
A quick store check
For each app, record publisher, purpose, permissions, transferred data, contract owner, last review and uninstall steps.
Foundation · 2 min
Frequently asked questions
Does uninstalling an app delete provider data?
Not automatically. Confirm the provider’s retention and deletion process and revoke all remaining access.
Can an app keep data after its business purpose ends?
Only when a documented continuing requirement permits it; otherwise delete or anonymize under policy and contract.