Contact AirdropBuzz

Reach the editorial desk with the details that actually matter.

Use this page for editorial corrections, project updates, developer API or MCP access, privacy requests, partnerships, or account support. The faster we can verify what you send, the faster we can review it properly.

Email the editor Submit an airdrop
Editorial email editor [at] airdropbuzz [dot] com
Best for Corrections, developer access, privacy, and support
What helps most Official links, clear context, and verifiable changes

What to include

If you want a useful response, send the essentials in the first message.

  • The page, project, account, or feature involved
  • Official links or evidence that support the request
  • What changed, what is wrong, or what you need from us
  • For API/MCP access: project purpose, endpoints, expected volume, and a portfolio or repository if available
  • For privacy/account requests: the account email and exact request; never include a password, seed phrase, or private key

Best reasons to reach out

Editorial corrections Use this when a guide needs a factual fix, a link update, or a safety clarification.
Project updates Send official announcements, roadmap changes, token details, campaign updates, and link corrections.
Partnerships Reach out for serious collaborations that fit a research-first, user-first crypto audience.
Developer access Request a named, revocable API or MCP credential for a legitimate project and include expected usage.
Privacy and account support Ask about account data, deletion, consent choices, or a security concern without sending passwords or wallet secrets.

What to expect

  • Clear, verifiable information gets reviewed faster.
  • We prioritize user value and safety over promotional urgency.
  • Not every request becomes coverage, even if it is legitimate.
  • Developer credentials are reviewed individually and may be rate-limited or revoked under the Terms of Service.
For fastest review, email editor@airdropbuzz.com and include the relevant page or project plus enough official evidence to verify your request. Never email passwords, seed phrases, private keys, or active API credentials.