The first message does one thing: align the spec

The goal of the first message is to tell the other side what you want, not to prove who you are. Sending sensitive data early only raises misuse risk and does not speed things up. An effective first message is short, clear and verifiable.

What not to send and why

DataWhy notDo instead
Passwords, codes, recovery codesEquals handing over controlNever in chat, under any circumstance
ID, passportCan be used to impersonate youOnly on official pages, by yourself
Bank cards and tax numbersFinancial and tax safetyOnly on the official payments page
Login screenshots of your accountsLeaks account and association infoNot needed
Your Google account credentialsThey do not need to log into your accountInviting a member needs an email address, not a password

The test is simple: if a process asks you to give someone something that lets them log in, it is not a safe process.

Also useful in this topic cluster:

What to send: the inquiry template

Buy / sell Google Play developer account
Entity: personal / organization
Country:
Fresh / aged:
Empty / with apps:
App type and category:
Preferred handover: owner transfer / other
Timeline:

Following this template, two or three sentences usually let the other side judge whether your need is feasible.

What each field means

  • Entity: personal or organization, deciding publishable categories and the closed-testing bar; see personal vs organization
  • Country: registered country, affecting payouts and tax and usually not switchable later
  • Fresh / aged: create date, affecting whether closed testing is needed
  • Empty / with apps: whether historic apps exist, affecting inheritance risk
  • App type and category: decides whether it is a restricted category
  • Handover: official owner transfer first; usually not applicable to monetized personal accounts

The more specific the fields, the more verifiable the terms and the shorter the chat.

When each item is actually needed

  1. Spec alignment: text spec only
  2. Account sheet check: they provide account fields; you provide no credentials
  3. Verification: you log into your own Google account on your own device and compare Console
  4. Official transfer: identity and payments data only on official pages, entered by yourself
  5. After handover: you set your own recovery info and two-step verification

At no step do you send a password in chat.

If someone asks for data anyway

If the other side asks for ID, passwords or 'log in for a moment' in the first message you can refuse and ask for a written spec and process first. A legitimate process does not collapse because you declined.

See the guaranteed-approval pitches guide for more warning signs and the how-buying-works guide for the full flow. Inquiry and terms happen only on Telegram @hagee66.

Related reading:

Related

Related desks