EU DSA trader status App Store review checklist
EU DSA trader information is public storefront compliance. It should match the business users can actually contact and buy from.
Classify trader status, verify business details, and align support before releasing in the EU. Apple provides App Store Connect guidance for European Union Digital Services Act trader requirements. AppReviewReady interpretation: this is not only a form field; it affects storefront trust, buyer expectations, and compliance operations.
Classify trader status before editing fields
Confirm whether the developer distributes as a trader for EU purposes. Involve legal or business ownership when the account has multiple apps, clients, subsidiaries, or marketplace-like activity.
Do not let a release manager guess. The storefront disclosure should match the entity responsible for the app and user relationship.
Verify public business details
- Legal name, address, email, phone, and any required registration details.
- Consistency with privacy policy, terms, support page, invoice sender, and developer website.
- Support coverage for EU users and languages claimed in storefront metadata.
- Ownership changes, app transfers, or business address changes.
- Separate records for client-owned apps versus first-party products.
Treat DSA details as storefront trust
Users may use trader details to decide whether to purchase, contact support, or trust a regulated app. Inconsistent details can create support and compliance risk even if the binary is unchanged.
AppReviewReady interpretation: when EU availability is enabled, DSA information belongs in the same release checklist as pricing, support, privacy, and terms.
Add DSA checks to release operations
- Review DSA status before first EU availability.
- Recheck after company name, address, support email, ownership, or app transfer changes.
- Align customer support macros with the public trader identity.
- Confirm privacy policy and terms refer to the same responsible entity.
- Keep a screenshot or export of the configured status for audit history.
DSA compliance record
The record is useful for future releases because DSA fields can be forgotten after the first setup.
After launch, watch support complaints about contacting the business. That feedback can reveal stale public information before it becomes a compliance problem.
If the developer account publishes apps for multiple brands, verify which entity the user believes they are dealing with. A storefront that shows one legal trader while the product, invoice, and support path point to another company can create confusion.
App transfers need a DSA check before and after transfer completion. The receiving account may have different public details, support ownership, and EU availability expectations.
For small teams, assign one owner to maintain trader details when the company moves, changes phone systems, or changes support tools. Compliance fields are operational data, not a one-time launch task.
If trader status is uncertain, pause EU storefront expansion until the business owner has made a documented decision. Guessing can create a public disclosure that support and legal teams cannot defend later.
EU DSA record: Trader status: [trader/non-trader] Responsible entity: [name] Public contact: [email/phone] EU availability: [countries] Policy alignment: [privacy/terms] Last verified: [date] Owner: [legal/business]
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check EU storefront readiness
Review DSA trader status, public contact details, policies, and EU availability.
Open the tool