Separate access data from evidence
Protected delivery may contain a password, mailbox access, token, session file or API link. These serve different purposes, but each can be sensitive. Keep the original package separate from screenshots and recordings you share when reporting a problem.
After initial verification, configure the available security and recovery methods. Do not change fields at random: an app password, main password and 2FA secret are not interchangeable. Some settings can be changed only where the purchased option supports them.
Keep these items private
- Full TData and SESSION files with their accompanying parameters.
- Main and recovery-mailbox passwords.
- Refresh tokens, auth_token and other access tokens.
- Backup codes, authenticator secrets and active delivery links.
A link that opens an archive or retrieves a code may grant access without another sign-in. Do not post it in a public chat or save it in a shared public document.
Using checking services
Our Telegram and Gmail guides identify specific tools. Read what each tool accepts before using it. The Gmail checker takes addresses, not passwords. Providing an archive link to the Telegram service gives it session access. Following a help link does not mean AKKUNO has automatically sent your order there.
If exposure is suspected
Review the available security settings and retain a description of what happened. Contact support if you are unsure which data was exposed. Do not publish the secret itself as proof. Recovery or session transfer can be restricted for particular options, so follow the limitations in the individual listing when using general advice.
