Before posting a gaming-account screenshot, remove details that identify you or someone else. Keep only what another person needs to understand your question. If a short description does the job, you can skip the image altogether.
Imagine you want to ask about an error message. Your screenshot also includes your full name, an account number and a bank notification at the top of the screen. The error is relevant; the other details are not. This is an illustrative example, not a screenshot from a real account.
Make a copy for the public question
Keep the original privately if you need a record for an official support request. Edit a separate copy for sharing. That lets you remove unnecessary details without losing your own record.
Start by cropping to the part you want to discuss. Then check the whole saved image, including the corners and notification area. Look for:
- Your real name, photo, email address and phone number.
- Account or player IDs, payment details and transaction references.
- Passwords, one-time verification codes and recovery information.
- QR codes, barcodes or links containing account-specific information.
- Other people's names, profile pictures and private messages.
- Notifications from other apps, including banking or messaging apps.
Remove details that are not needed for the public question. Do not publish passwords or verification codes. If you cannot tell whether an edited detail is still readable, leave out the image and explain the issue in words.
Open the exported copy before posting. Checking the saved file helps avoid accidentally attaching the original. These are practical sharing precautions, not a guarantee that an image contains no identifying information.
Send account details only through a verified support route
A public discussion and a support case have different needs. A forum reader may only need the wording of an error. An official support team may ask for a case or transaction reference to locate a record.
Find the support route from the service's own official website or app. An unsolicited direct message from someone calling themselves an agent does not verify their identity. If a request seems unrelated to your issue, ask why that information is needed before sending it. Do not give a person your password or a verification code so they can “help.”
For example, a public question could say: “The page shows an error when I open account history. Which help section explains this?” You can leave out your account number and payment record. If verified support later needs a specific reference, handle that separately through its official channel.
My real name appears on the screen. Can everyone see it?
Seeing your name while logged in does not, by itself, establish who else can see it. A private account view, a public profile and a support record may show different fields. Do not post your entire profile just to ask whether it is private.
Check the service's visibility settings and help information, or ask support which fields are public. Until you have an answer, treat the screenshot as containing personal information. This guide cannot confirm the privacy practices or security of a particular operator.
What if you have already posted it?
If you control the post, remove it or replace the image with a version that leaves out the private details. If someone else controls it, use the platform's reporting or removal process. Removing a post does not guarantee that earlier viewers have not saved a copy.
If a password was exposed, change it through the official account settings. If payment information was exposed, contact the relevant payment provider through its official support route. Avoid reposting the same unedited image while asking for help.
The Philippine National Privacy Commission's reminder on sharing images explains that exposing personal data can create risks such as fraud and identity theft. It is a reason to check what you share—not proof that a particular account has been compromised or a legal ruling about your post.
Before pressing “Post,” ask: is the recipient right, is every visible detail necessary, and am I attaching the edited copy? For more reader-focused guidance, browse our safer play articles.