FAQ

Open a product, enter a delivery email or Telegram, set a lookup PIN, and pay the exact USDT / TRX / ETH amount shown. Extra or missing cents will not match automatically.

After on-chain confirmation we deliver automatically from local stock, or procure from the supplier if needed (minutes to tens of minutes). The order page shows pending / paid / delivered.

Save the order ID, email / Telegram, and lookup PIN so you can reopen delivery details under Order Lookup.

Apple deliveries typically include the Apple ID, password, related Gmail / recovery mail, and for organization accounts the legal name, D-U-N-S, and address. Some units include an SMS short link and an expiry date.

Google deliveries typically include the login email, password, and Play Console access. Org units may mention a Workspace domain or payments profile. Sign in with the provided docs first — do not immediately change every recovery method.

Each product lists warranty days (for example 14, 30, or lifetime). During that window you can submit after-sales from the order page if the account cannot sign in or is suspended without cause.

Bans from policy violations, abuse, or self-changed identity, and expired SMS numbers, are usually outside free replacement. If unsure, message Telegram support with the order ID.

Use a fresh browser profile or private window so it does not collide with your personal Apple ID. Confirm the delivered email works at appleid.apple.com, then open developer.apple.com/account.

You should see Membership / team details. Publishing uses appstoreconnect.apple.com. If 2FA appears, use the delivered phone number or SMS link for the 6-digit code.

If you see “this Apple ID is not enrolled”, do not buy a new membership. Check you used the correct email, then contact Gugu — the team invite may be pending or the account type may not match.

developer.apple.com/account covers membership, certificates, App IDs, devices, and profiles — the signing side.

appstoreconnect.apple.com covers app records, screenshots, review, TestFlight, roles, and agreements — the publishing side. Both use the same Apple ID / team.

Apple is sensitive to new devices and regions. Sign in on a stable network and use the delivered SMS number. Avoid repeated wrong passwords or the ID will lock.

After the first success, review trusted devices at appleid.apple.com and remove unknowns. If you change the password, keep SMS / recovery mail working, then re-test Developer and Connect.

No code at all: check SMS expiry and whether the number is still on the Apple ID. If you cannot sign in during warranty, request after-sales.

Individual memberships are personal legal entities. Organization accounts sit under a company name, usually with D-U-N-S and a business address already attached. Sign in only with the admin email in the delivery.

Do not submit a new D-U-N-S or rename the legal entity in Apple’s forms — that can trigger review or suspension. Add people with Users and Access invitations.

In Xcode, sign in to the team and enable Automatically manage signing. Manual path: Certificates → Identifiers → Devices → Profiles.

Do not revoke distribution or push certificates casually — old builds and push stop working. Device quota resets follow what Apple shows in the account.

Start at iforgot.apple.com with the delivered recovery email / phone. Do not force-bind your own number.

If Apple asks for a personal ID that the listing did not support, stop and contact support instead of pushing the account into an unrecoverable state. Login failures are covered in warranty.

In a private window, sign in at accounts.google.com with the delivered email, then open play.google.com/console. Do not stay signed into your personal Gmail or you will open the wrong developer.

You may need to accept Play terms, enable 2-Step Verification, or finish identity checks. Continue the existing registration — do not create a new developer account (another fee, unrelated to what you bought).

Individual: registered as a person, following Google’s current individual-developer rules (including testing and rollout limits). Fine for validating a product.

Organization: business identity, usually mid or post verification, with multi-user invites. Keep email, payments, and D-U-N-S / legal info aligned with the delivery — do not switch it to another company.

Check 2-Step Verification and recovery at myaccount.google.com/security. Use the SMS short link while it is valid, or the authenticator described in the delivery.

Repeated failures trigger extra checks — wait a few hours and reuse the same browser. Never remove every recovery method at once. After SMS expiry, warranty still covers “cannot sign in” cases.

Play Console → Users and permissions → Invite user. Enter their Google account and grant only the needed app roles (Admin / Release / Finance).

Do not share the owner password with contractors. They sign in with their own Google account; you can revoke access if the owner is later changed or compromised.

Google requires some individual developers to finish identity verification and meet closed-testing tester-count and duration rules before production. Follow the checklist shown in your Console.

Organization verification differs, but policy, data-safety, and audience declarations still apply. Fake testers from emulators are a common rejection reason.

Read the Console banner and the Play policy email, then appeal via Google’s form. Also confirm payments.google.com matches the developer legal entity.

If it opened at delivery and is later suspended without cause during warranty, send screenshots and the order ID to Gugu. Policy violations on your apps are not a free replacement.

Apple and Google persist sessions in cookies. If your personal Apple ID / Gmail is still signed in, you may think you succeeded while opening your own team. A second Chrome profile or a private window avoids that.

Not recommended. Changing the legal entity or country on Apple or Google usually restarts verification and often fails. Invite extra users instead of transferring ownership.

No. Use only the official Apple / Google hosts listed here. Third-party “login helpers” are a common theft vector. Gugu support only uses the Telegram bot published on this site.