docs: clarify Telegram Mini App credential safety

[RobQocharyan123]

Summary

Clarifies the existing Telegram Mini App guidance by:

• stating that Mini Apps and support flows must not request Telegram credentials or wallet recovery secrets;
• directing users to verify unexpected Telegram destinations through an independently published official website or support route; and
• adding the required minimal contributor metadata using the public GitHub identity only.

Disclosure

I am affiliated with Pointify, a Telegram Mini App publisher. This contribution is non-promotional, adds no Pointify link or product claim, and requests no backlink or specific link attribute.

Validation

• Compared against the current develop source.
• Checked open pull requests for duplicate Telegram or Mini App guidance.
• Both GitHub web commits are Verified.

[NFTDreww]

Most of this proposed section overlaps with what's already here:

"avoid logging in or providing information to mini apps that redirect outside of Telegram," "triple-check the username," and the support-DM guidance together already cover the "verify unexpected routes out-of-band" and "don't hand credentials to a Mini App" points.

The one thing the current text doesn't do is name wallet secrets explicitly, which matters for audience imo. I suggest folding that specificity into the existing Mini Apps and Support bullets rather than adding a standalone section, this keeps the guide non-redundant and adds a clarifying new point.

Something like:

- Exercise Caution with Mini Apps: Avoid logging in or providing information to mini apps that redirect outside of Telegram. Never enter or send a login code, Two-Step Verification password, seed phrase, private key, or recovery phrase to a Mini App, no legitimate Mini App needs them.

[scode2277]

Hey @RobQocharyan123, thanks for this contribution!

Small note on the attribution first: I updated your role in the list. To be credited as a writer of a page we look for a substantial amount of added content, so that is the only reason for the change. Nothing against what you added, there is just a distinction to make between the two. If you want to land on the writer side, take a section or a topic and build it out, we'll be happy to review it and get it in.

On the PR itself, @NFTDreww left a review as the steward of the framework, as soon as he approves the content, this will be ready to go!

Thanks again 🙏🏻

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
frameworks	✅ Ready (View Log)	Visit Preview	7dc80b4

[scode2277]

Thanks again @RobQocharyan123 and thanks @NFTDreww for the review!🙏🏻

gtg now @mattaereal!