Screenshots That Help (and Ones to Avoid Sending)

Choose evidence that answers a specific question

A useful screenshot has a clear purpose. It should help explain what you expected to see, what appeared instead or where a particular account-related issue occurred. Before selecting an image, write down the question it is meant to answer. If you cannot explain why the image is relevant, it probably does not need to be included in the enquiry.

For example, an image of a dashboard section that does not display expected information may help illustrate a feature-related question. A screenshot of an account message may clarify an access problem. However, an image showing several unrelated dashboard sections can introduce unnecessary information and make the relevant detail harder to identify. One focused image is often more useful than a collection of loosely related captures.

Which screenshots are useful for common problems?

For an account question, a screenshot may help show the general page or message associated with the problem. For a dashboard issue, it may demonstrate that a particular section is not displaying the expected information. For a feature availability question, an image may provide context about the function being discussed, provided it does not reveal unrelated personal data. Always accompany the image with a short written explanation.

Different functions require different context. A question about GPS location tracking or a geofence alert is not the same as a question about supported messaging information or website blocking. The screenshot should illustrate the specific concern rather than expose a wider collection of device activity. If the problem can be explained accurately in words, ask whether an image is necessary before sharing one.

• A relevant account or dashboard message.
• The specific section associated with the reported issue.
• A visible error or unexpected display.
• A general feature-related screen that answers a defined support question.

Information to remove before sharing

Screenshots can reveal more than their intended subject. Check the entire image, including its edges and background, for email addresses, phone numbers, names, contact photographs, message previews and other personal information. Notifications may also expose private conversations even when the main screen appears harmless. Remove or obscure details that are not required to explain the issue, while keeping the relevant evidence readable.

Be particularly careful with images containing account information or data belonging to another person. Do not assume that a screenshot is safe simply because it comes from the online dashboard. If the relevant information cannot be separated from sensitive material, ask support whether a written description or another appropriate form of evidence would be sufficient. Never send passwords, authentication codes or unrelated private records as supporting material.

• Passwords and authentication codes.
• Unrelated messages and conversation previews.
• Names, telephone numbers and personal contact details.
• Unnecessary location details or identifying information.
• Information belonging to people outside the support enquiry.

When a screenshot should not be sent

Some images create more privacy risk than practical value. Avoid sending full conversation histories, entire contact lists, extensive location records or collections of personal photographs when the issue concerns a single dashboard function. These materials may contain information about children, employees and other people who have not been involved in the support conversation. Their availability within a monitoring account does not automatically make sharing them appropriate.

Take particular care with material associated with keystroke logging, periodic screen capture, live screen streaming and call recording. These functions are more intrusive and should be used only where proportionate, age-appropriate and legally permitted. A support question rarely justifies sharing extensive captured activity by default. Ask whether the issue can be assessed using a general description or a limited image that does not expose the underlying personal content.

Consent, ownership and transparency before submission

Before sharing a screenshot, establish that you are entitled to provide the information it contains. Parents and legal guardians should maintain an open, age-appropriate conversation with their children about monitoring and the handling of collected information. Employers should have a written monitoring policy and give employees notice about monitoring on company-owned devices. A screenshot should not become a way to circulate information that would otherwise be inappropriate to collect or disclose.

The phrase screenshots to send to support should always be interpreted narrowly: relevant images from devices and accounts you are legally authorised to supervise, with unnecessary personal details removed. Local laws differ, especially where communications, location information and recordings are involved. Check local requirements or seek qualified legal guidance when necessary. Transparency and appropriate consent should guide both monitoring and evidence sharing.

Check the image and keep a copy of the enquiry

Before submission, inspect the image at full size. Confirm that the relevant message or dashboard section is readable, that the image has not been cropped so tightly that its context is lost and that no unrelated personal information remains visible. Give each attachment a neutral description that explains its purpose. Avoid filenames containing sensitive personal details or information about the device user.

Also consider whether the image is genuinely needed. mSpy features and setup requirements vary according to the operating system, version, plan, configuration and permissions on the monitored phone. A screenshot cannot establish that a feature is supported or guarantee a particular technical outcome. The official website provides the current feature list and setup information. Your next step is to prepare a short written explanation, select only the necessary evidence, review it for privacy and retain a record of what you submit.

Questions readers ask