Agitate
The Agitate app icon.

Guideline 3.1.2

Where Agitate 1.0 (5) states each thing the guideline asks a purchase screen to state, and a recording of both links opening.

Build 5 Submission 83c2bdee 21 August 2026

Title of the purchase
Agitate Pro, on the purchase screen, under Purchase details.
Length
One-time purchase, permanent. Agitate Pro is a non-consumable. There is no subscription in this app and no subscription group on the account.
Price
Taken from StoreKit for the current storefront and shown on the same row. Never hard-coded, so it is correct in every currency.
Terms of Use (EULA)
A link on the purchase screen, opening agitate-app.vercel.app/terms. Also under More → Terms of Use (EULA), and in the App Store description.
Privacy Policy
A link on the purchase screen, opening agitate-app.vercel.app/privacy. Also under More, and in the Privacy Policy field in App Store Connect.

1 The recording

Recorded on build 5. It walks More → Agitate Pro → the purchase screen, then opens the Terms of Use (EULA) and the Privacy Policy from that screen, one after the other.

Direct file: agitate-3-1-2.mp4 (2 MB, 93 seconds, no audio).

2 In the app

The purchase screen carries a block headed Purchase details directly above the buy button. It lists the product name, the length, the price for the current storefront, and then two rows that are links: Terms of Use (EULA) and Privacy Policy. Both open in the browser.

The same two links are also in the app's settings, under More, so someone who has already bought Pro and never sees the purchase screen again can still reach them.

3 In the metadata

The App Store description ends with a block naming both, in English and in German:

The Privacy Policy URL field in App Store Connect points at the same privacy page.

4 On the kind of purchase

For completeness rather than as an objection: Agitate Pro is registered as a non-consumable, not an auto-renewable subscription, and the app has no subscription of any kind. Everything the guideline lists is now present regardless, in the app and in the metadata, so nothing here depends on that distinction.