Boot Store
Access Types
Access labels must keep free packs, Premium-related access, clean export credits, and future paid packs understandable and policy-aware.
Public surface
Access Types
CRYA monetization stays clear when each item says exactly what unlocks it and where purchase/account verification happens.
Public packs that can be discovered and handed off without purchase claims.
Subscription-related access where the app/backend verifies active entitlement.
One-time watermark-free export credits, separate from Premium.
Future item-specific purchases with creator attribution and app-side billing rules.
| Play billing | App-sold digital subscriptions, credits, and paid packs should use Google Play Billing where required. |
|---|---|
| Web role | Website pages focus on discovery, metadata, creator credit, and app handoff. |
| Private evidence | Receipts, purchase tokens, grants, and refunds belong in protected support/admin workflows. |
| Refunds/support | Users should use platform purchase management and private support evidence. |
Workflow
How this should work
A public page should explain the user path while protected state, permissions, and audit trails stay in CRYA Mission Control.
Check free, Premium, clean export, or paid pack language.
Use account-aware app handoff for entitlement checks.
Let backend verification update access.
Send private evidence only when access fails.
Related surfaces
Continue the journey
Move between public discovery, creator guidance, store trust, and support evidence without exposing private admin systems.