Day 5 — Operations, legal and cost limits are set

You clarify what can cost you money, time or trust after publishing.

A login is not cost control. Anything that triggers a paid feature needs a server-side approval first: request → check → reserve budget → start provider → record usage. Remote config may hide buttons, but it is never the security boundary — the server always makes the final call. And a single “AI on/off” is too coarse: switch individual capabilities separately and keep the free manual route available when you pause the expensive one.

Paste this prompt into the AI tool you work with:

My app does: [SHORT DESCRIPTION]. Paid or external calls: [LIST OR “none”]

1. List which legal texts, support routes and data declarations my release goal requires.
2. Propose a separate switch plus daily and monthly limit for every paid feature.
3. Describe a server-side kill switch that also stops an old app version.
4. For each point, tell me how I can tell it actually takes effect.

Explicitly mark anything you are not sure about.

Write your legal and support pages, create icon, splash and description texts, and set a hard cap for every paid feature.