All articles

Before you post a screenshot in a chat: cover the number, code, API key, and device pairing QR code

A typical screenshot in the community chat looks like this. Someone asks "why didn't my code arrive?" The screen shows an order card with the full phone number, next to it a window with a freshly issued API key, and on top a bank notification with a code. We can work out the problem from a shot like that, but the number, the key, and a code from another service all went into a public chat along with it. Below is a checklist for sharing a screenshot safely with support or in a chat, while keeping everything we need to answer you in the frame.

What to cover before you send it

Look at the whole frame, including pop-up notifications, other tabs, and suggestions in the search bar. Black out:

  • The full phone number. Keep the country code and the last three or four digits. If we need the whole number, send it to the support bot or by email.
  • The code and the link from the SMS. If registration isn't finished yet, the code may still be valid, and for troubleshooting it's enough to know whether it arrived or not. Some services send a link instead of a code (the dashboard recognizes it and offers to open it in a browser). Cover that link the same way, since it can also be used to sign in to the account.
  • The API key string. The dashboard shows it only once, when the key is issued, and after that stores only its fingerprint. That's why people often screenshot a key "to keep it handy," and that screenshot later ends up in a chat. The key's name can stay.
  • The phone pairing QR code, if you're a supplier. It's a one-time sign-in token for the supplier app, valid for five minutes. Anyone who scans it in time can connect their own phone to your account. The same QR code is also available in "Settings."
  • Your two-factor authentication code, and especially the QR code shown when you set it up. It contains the secret that generates every code after that.
  • Your crypto wallet address, for example from the withdrawal form. The address reveals its entire transfer history.
  • Your account email and the contact details in your profile.
  • ICCIDs and full phone numbers on the "SIM cards" screen, if you're a supplier.

What to keep so we can answer the first time

Buyers should keep the order status, service, country, timer, and the exact error text, whether it came from us or from a third-party service. Add the time of the event with your time zone: without it, we have to search for your order among similar ones. Suppliers need to show the "Sales" column on the "SIM cards" screen, which gives the reason a SIM is idle, along with the device status and the time of the last ping.

A message we can answer without asking anything back looks like this: "The SIM ending in …4821 isn't selling. The 'Sales' column says 'device offline,' and the last ping was at 13:20 UTC+3, even though the phone is on and online. The number and ICCID are covered in the screenshot."

It's fine to ask a short question in the community chat, but send details about an order, your balance, or a withdrawal to our support bot on Telegram or by email. Cover your secrets there too: we don't need your key, your password, or your two-factor code to look into the problem. If "support" messages you privately after you post in the public chat and asks for a code or key, don't reply, and let us know through the bot.

How to cover it

Use a solid, opaque box. Blur and pixelation on short strings like a code can sometimes be reversed, and a semi-transparent highlighter in a phone photo editor often lets the text show through. A safer option is to crop the image so the secret isn't in it at all, then open the finished file at full size before you send it.

If a secret already got into the shot

Delete the message, but treat the secret as exposed: while the screenshot was up in the chat, someone could have saved or forwarded it. What to do next depends on the type of secret.

  1. Phone pairing QR code. Open your device list. If you see a phone you didn't connect, contact support right away. If there are no unfamiliar devices and the five minutes are up, that QR code won't work anymore.
  2. Two-factor code or setup QR code. A single code expires quickly. But if your password or the setup QR code was also in the shot, change your password and set up two-factor authentication again on the sign-in page.
  3. Code or link from an SMS. If registration isn't finished yet, complete it yourself. Then change the password on that third-party service and turn on two-factor authentication there, if it offers it.
  4. Phone number, email, wallet address. These can't be revoked. Delete the message and watch closely for any emails and private messages that come after it.

The most urgent case is an API key. It stays valid until it's revoked, and anyone who still has the screenshot can use it. Open the API keys section, write down the exposed key's last-used date, and revoke it right away. If that date is later than your post and you weren't using the key at that time, contact support. Then create a new key, swap it into your software, and end sessions on your other devices from the sign-in page.

Numbers mentioned in this article

Your first number in a minute

Signing up takes a minute, topping up a couple more, and the code arrives in 20 seconds.

Buy a number
No subscription feeCancel with a refund in the first hour