1. What this preview does
StarBoost currently shows a design preview with sample services, balances, orders and tickets. Actions in the preview are local demonstrations. They do not place a live order, charge a payment method or send a message to a support team.
Services, prices, start times and refill labels shown here are examples. The final offer and any limits must be confirmed before public sales begin.
2. Accounts and submitted information
The planned app will use Google sign-in for customer accounts. You should provide accurate order details and use only destinations you are authorized to submit. A public link or username may be needed to fulfill a requested service; passwords and verification codes are never required.
Account access, suspension and deletion rules will be specified in the final terms. See the Privacy Policy draft for the planned data categories.
3. Orders and delivery
Before confirming an order, the app shows the selected service, destination, quantity, Star total and any stated start or refill information. Delivery may depend on the selected service and the destination remaining publicly accessible.
Live fulfillment, status reporting, refill eligibility, cancellations and remedies are still being integrated. The final rules must explain when an order can be changed, stopped, refilled or refunded and how a customer can request help.
4. Stars and Google Play purchases
Stars are planned as in-app credits for StarBoost services. They are not cash and are not transferable to another app. On Android, a real Star package purchase is intended to use Google Play checkout; the final price and currency must be shown in that checkout before payment. The current web preview does not process payments or issue Play receipts.
Any rules for unused Stars, failed orders, chargebacks, refunds and regional consumer rights must be reviewed and published before sales start. A support request can include a Google Play order ID when a customer has one.
5. Support and policy updates
The preview ticket interface saves requests locally and does not contact support. A real support channel, response process and operator contact must be connected before launch. The final terms should show an effective date and explain how material changes will be communicated.