# Base44 EULA Rejection? Fix Guideline 3.1.2

Your Base44 app sells a subscription, and Apple rejected it under Guideline 3.1.2(c) for missing required information. Nine times out of ten the missing piece is a Terms of Use (EULA) link. This is one of the fastest rejections to clear once you know the two places the link has to appear.

## What Apple is actually checking

For an auto-renewable subscription, Apple wants the user to see the full terms before they buy. Concretely, the reviewer looks for five things inside the app:

*   The subscription title
    
*   The length of the subscription
    
*   The price, and price per unit if relevant
    
*   A functional link to your privacy policy
    
*   A functional link to the Terms of Use (EULA)
    

And in App Store Connect metadata, a privacy policy link plus a EULA link. The EULA is the one almost everyone forgets.

## The EULA link

If you do not have a custom EULA, Apple's standard one is accepted:

`https://www.apple.com/legal/internet-services/itunes/dev/stdeula/`

Put it in both places, because Apple checks both:

1.  App Store Connect: add it to your App Description, or add a custom EULA in the EULA field under App Information.
    
2.  In the app: a visible link on your paywall and on your account screen, next to your privacy policy.
    

## Where this lives in a Base44 app

Base44 apps often ship with a paywall screen but no dedicated account screen, so the link has nowhere obvious to go. Add it in both spots the reviewer checks: on the paywall itself, and wherever your users manage their profile or sign-in. On the paywall, render the title, length, and price as readable text, not just a price on the buy button. Apple treats a bare button as insufficient disclosure.

A small, real example of the paywall footer text:

```javascript
// Paywall footer, shown before the purchase button
const terms = `
  Premium renews automatically at $9.99/month unless cancelled
  at least 24 hours before the period ends. Manage or cancel in
  your App Store account settings.
`
```

State that it renews automatically and can be cancelled in account settings. That phrasing is what makes the paywall read as review-complete.

## The part that saves you a rebuild

Here is where running your Base44 app through Despia matters for this specific rejection. The App Store Connect description edit never needs a new build. But the in-app link, on the paywall and account screen, normally does. With Despia serving your web layer, that link change ships over the air, so you fix the paywall and the reviewer sees it without a fresh binary or another review queue.

Reply to the reviewer confirming the EULA link is now in the App Description and in the app, and the item closes.

## The checklist

*   Standard EULA link in the App Description
    
*   EULA and privacy links on the paywall and account screen
    
*   Title, length, and price shown as text
    
*   Auto-renew and cancellation wording near the button
    

## Get it on the stores

Ship your Base44 app to iOS and Android from your existing web codebase, and push paywall and EULA fixes over the air the moment a reviewer asks for them.

[See the setup docs at setup.despia.com](https://setup.despia.com)