Guide summary
Premium, clean exports, and store purchases
Clear billing language protects users, support, and Play review. Do not describe clean exports as Premium and do not describe future paid packs as included unless the entitlement says so.
Subscription access for premium tools, templates, and ad-free workspace while active.
One-time watermark-free export entitlement for a supported export flow.
Future paid packs remain item-specific and creator-attributed.
Use order/account evidence privately; never post purchase tokens in public threads.
| Google Play Billing | Use Play Billing for app-sold subscriptions, clean exports, and paid app-side digital items where required. |
|---|---|
| Refund/cancellation | Users should use platform purchase management where applicable and contact support with account-safe evidence. |
| Entitlement sync | Premium state, clean export balances, and item access should come from Firebase/Cloud Functions, not public page claims. |
| Admin grants | Manual grants belong in protected Mission Control with role checks and audit records. |
| Ads | Ad placements, rewarded gates, and cooldowns should remain admin-controlled and policy-aware. |
Workflow
Use this sequence
A practical flow that maps the public docs back to app behavior and support evidence.
Premium, clean export, or store pack.
Use the same provider/account used for purchase.
Let the app sync with backend purchase verification.
Send private evidence if access still fails.
Never share tokens or receipts in public community chat.
Related CRYA docs
Continue with the next useful page
The docs should move users between package work, safety, billing, store review, and support without exposing private admin systems.