App-store readiness checklist

Accessible privacy, terms and deletion-request pages in three languages; explicit recorded RFQ acceptance.

Contact and deletion requests are stored. Ownership verification and actual deletion are not automated; the operating procedure remains to be approved.

Public accounts, RFQ document uploads, checkout, payment processing and confirmed bookings are not enabled.

Publish only with approval, verify the public privacy/deletion URLs, email delivery, real business details, retention and production cookies/providers.

Provide an accessible privacy policy inside the app and in App Store Connect; declare actual data and third-party SDK practices in App Privacy.

Allow account-deletion initiation inside the app; deactivation alone is insufficient. Verify identity, associated-data deletion, retention exceptions and actual completion.

Check minimum functionality (guideline 4.2), stability, permission prompts, privacy manifests/SDK requirements, support details and reviewer access. A website wrapper alone may not satisfy review.

Reassess payment rules for physical versus digital services, login options and user-generated content moderation if those features are added.

Provide a public privacy URL and in-app policy access. Complete accurate Data safety disclosures including third-party services; verify them against the shipped app.

Provide both an in-app deletion path and a public web resource to request deletion of the account and associated data. The current manual request form is not a verified account-deletion system.

Test Android devices, stability and useful functionality; review current target API and testing requirements, device permissions, SDK data flows and store screenshots/support declarations.

Review billing rules for physical/digital purchases and reporting/blocking/moderation requirements for public user content if enabled. Current private RFQ forms are not a public discussion feed.