Understand access, subscriptions, and connections across developer tools
Know what to check when moving from the emonster.dev portal to an individual product.
Written By Enrique Bonansea
Last updated About 4 hours ago
Review the product’s own plans
emonster.dev introduces a family of focused tools. Each product has its own purpose, product page, and pricing. Review the current product’s plans, billing period, limits, and availability before subscribing.
A shared portal or help center does not establish an all-products subscription. Use the access and billing status shown inside the product you intend to use.
Check access in the destination product
Follow the product link from the portal and use its current sign-in or access flow. Signing into one product does not by itself confirm an entitlement in another. A waitlist registration or interest in a product also does not confirm that its dashboard or planned features are available.
Connect Apple services in the correct place
Each tool asks for the access relevant to its own job. Follow that product’s connection instructions and permission explanation. A common emonster brand or support center is not authorization to share Apple credentials or data between tools.
Do not copy another product’s required Apple role or connection settings without checking the destination product’s guide. In particular, Apple Ads authorization and App Store Connect API-key setup are different connections.
Get help with access or billing
Use Support in the affected product and name the product and issue. For current prices, cancellations, data requests, or account changes, use its own published terms and available controls.