All pages
Listing requirements
Requirements are numbered so automated and human review findings can cite them directly. Most rules are checked automatically as soon as you submit a version. Rules marked human are checked by a reviewer, which is mandatory whenever a version declares fan_charges, chat_channel, chat.read, chat.write, fans.read, agency.write or chat.transport.
1. Content
- 1.1 Store assets (icon, screenshots and channel icons) must be safe for work on both sites. Adult apps (
audience: "adult") are listed on the adult site only and still require safe-for-work store assets. - 1.2 Nothing your app renders may misrepresent craving, a Resident or a Visitor.
2. Listing
- 2.1 The app name is your own: it must not include
craving(or use acraving-slug, which is reserved for official apps by craving) or name another platform. - 2.2 A webhook endpoint is configured and accepts a signed
pingrequest with2xx. - 2.3 Tagline, description, at least 2 screenshots, and support, privacy and terms URLs are present and reachable over
https://. - 2.4 App names and listing copy do not reference OnlyFans, Fansly, Fanvue or Patreon.
- 2.5 Your webhook endpoint survives a 5-request burst without returning
5xx(429withRetry-Afteris allowed). - 2.6 The support URL resolves to a working page where a Resident can get help.
3. Consent and scopes
- 3.1 Declared
scopesandeventsmatchcapabilities(enforced when saving the manifest). - 3.2 Request only the scopes your app needs. Heavy scopes and capabilities are reviewed by a person (human).
4. Home blocks
- 4.1 Framed blocks (
render: "frame") load and postcraving:readywithin 6 seconds; drawn blocks (render: "json") return a validformat: "1"JSON document up to 256 KB within 20 seconds. - 4.2 Never collect card details or show payment forms inside a block frame.
- 4.3 Framed block URLs allow embedding on craving (no
X-Frame-Options: DENYorSAMEORIGIN, and anyContent-Security-Policyframe-ancestorsdirective allowshttps://craving.com https://*.craving.com). - 4.4 App icons, screenshots and channel icons return an
image/*content type.
5. Security and privacy
- 5.1 Privacy policy and terms URLs are distinct, reachable
https://pages. - 5.2 Your server verifies
X-Craving-Signatureon every request from craving. - 5.3 Every manifest URL uses
https://on a public hostname (no IP literals,localhostor.internalhosts), sits on a declared origin, and never exposes acrvs_client secret in client-accessible HTML. - 5.4 You hold the rights to all icons, screenshots and images your app serves.
- 5.5 Visitor and Resident data is limited to what your app needs to function and is deleted within 30 days of
installation.uninstalled.
6. Endpoints
- 6.1 Every
tools[].invoke_url,channel.send_urlandchannel.history_urlaccepts a signed dry-run POST ("dry_run": true) and answers2xxJSON within 8 seconds.
7. Money (human)
- 7.1
fan_chargesapps provide a working refund path and never collect payment details outside craving checkout. - 7.2 Prices shown in a Home block or chat tool match what craving checkout charges.
What happens after submit
The automated reviewer runs immediately and records each check under Versions on your app page, cited by requirement number. A light version (no heavy capability or scope) goes live automatically when every check passes. If any check fails, the version is rejected with the failing check IDs so you can fix them and submit again. A heavy version that passes the automated checks moves to the admin review queue. You receive a review.decided webhook plus an email and push notification when a final decision is made.
After publishing
craving may suspend an app that violates these requirements (app.suspended). Suspending an app immediately hides its listing and disables its blocks, chat tools and channels across all installations until the issue is resolved and the app is restored (app.restored).