🛡 Maya App Guardian

Freelancer guide for daily app publishing work. Use these commands in your own Telegram group only. The bot shows only apps assigned to your group.

🛡️ Critical Work Rules: Security & Separation

These rules protect the publisher account, the Google Play Console, and your own work. Follow them exactly.

1️⃣ Use only the prepared work browser

Use only the prepared Firefox Portable/work browser for this publishing work.

2️⃣ Do not open work links outside the work browser

Open every work link only inside the prepared browser.

  • CloudFront app asset links
  • Google Play Console links
  • MediaFire/file links
  • Business or work-related links
  • Training or task links

Do not open them on phone, Chrome, normal Firefox, or a personal browser.

3️⃣ Keep Gmail separated

The work Gmail must stay only inside the prepared Firefox Portable browser.

Do not add it to your phone, Chrome, personal browser, or personal email use.

4️⃣ Do not mix Google Play environments

Never open another Google Play Console from the same browser/profile.

Never use the work Gmail with another client or another Play Console.

5️⃣ Why separation matters

Google Play Console accounts are sensitive. Mixing devices, browsers, IPs, emails, or other console histories can increase risk. Keep each publisher workflow clean and separated.

6️⃣ Ask before clicking

If anything is unclear, Google asks for verification, an error appears, or the screen is different from the training video, stop and ask before continuing.

7️⃣ No sensitive data in Telegram

Do not send passwords, Gmail passwords, recovery codes, 2FA codes, payment details, cookies, or private account credentials in Telegram.

8️⃣ Accuracy over speed

Follow the exact procedure. Do not guess, skip steps, or improvise.

📦 See your apps Use /apps, /pending, and /status PACKAGE to know what to work on.
🚀 Move app states Use /start_app, /sent_review, and /live as the app progresses.
🚨 Report issues Use /issue PACKAGE issue text when something blocks your work.

Normal App Cycle

Follow the state shown by the bot. Do not skip steps.

📌 assigned
🚀 pending_publishing
📤 in_review
✅ live
📦 status check

Commands You Need

👋 How do I check that the bot knows my group?

Run this in your freelancer Telegram group:

/whoami

You should see your freelancer name, freelancer ID, and assigned developer. If the bot says unknown group, ask the admin to add your group.

📦 How do I see all apps assigned to me?

Use:

/apps

This lists only apps visible to your group. You cannot see apps assigned to other freelancers.

⏳ How do I see only pending work?

Use:

/pending

This shows apps and update tasks that still need work. If nothing is pending, the bot will say so.

🔎 How do I check one app in detail?

Use /status with the package name:

/status com.example.app

The status message has three sections:

Section Meaning
🚀 Main app state The normal publishing state, such as assigned, pending_publishing, in_review, or live.
🛠 Updates Separate update tasks for an existing app.
🚨 Issues Problems reported for this package.
🚀 How do I start working on a newly assigned app?

When the app is assigned and you are ready to start publishing, run:

/start_app com.example.app

This changes the state to pending_publishing.

After this, the normal next command is /sent_review PACKAGE when the app has been submitted to review.
📤 What do I do after submitting the app to review?

When the app is submitted in Play Console and waiting for review, run:

/sent_review com.example.app

This changes the state from pending_publishing to in_review.

After this, the normal next command is /live PACKAGE when the app becomes live.
✅ What do I do when the app is live?

When the app is approved and live, run:

/live com.example.app

This changes the state from in_review to live.

After this, you can check it anytime with /status PACKAGE.
🚨 How do I report an issue?

Use /issue, then the package name, then the problem text:

/issue com.example.app data safety file is not provided yet

Write the issue clearly. The admin will see it and it will appear in the app status.

Do not run only /issue PACKAGE. The bot needs the issue text too.
🛠 What if I receive an update task?

Admin creates update tasks. You can see them with:

/pending

or:

/status com.example.app

When the update is submitted to review, run:

/update_sent_review com.example.app

When the update is approved/live, run:

/update_live com.example.app
Update tasks are separate from the main app state. The main app can stay live while an update task moves through its own workflow.
🔁 Which command comes next for each state?
Current state What it means Next command
assigned The app is assigned to you, but work has not started. /start_app PACKAGE
pending_publishing You are working on publishing or submitting the app. /sent_review PACKAGE
in_review The app is submitted and waiting for approval. /live PACKAGE
live The main app workflow is complete for now. /status PACKAGE
pending_update An update task is waiting or in progress. /update_sent_review PACKAGE
update_in_review The update is submitted and waiting for approval. /update_live PACKAGE
🔒 What should I avoid sending to the bot?

Do not send private credentials or sensitive account details in Telegram.

  • No passwords.
  • No recovery codes.
  • No 2FA secrets.
  • No payment or card details.
  • No cookies or session tokens.

For issues, describe the operational problem only.

Copy-Paste Examples

Replace com.example.app with the real package name from the bot.

/apps
/pending
/status com.example.app
/start_app com.example.app
/sent_review com.example.app
/live com.example.app
/issue com.example.app short clear issue text here
/update_sent_review com.example.app
/update_live com.example.app