Sending a goAML Support Screenshot? Remove These Details First
When a UAE business encounters an error in the goAML system, a screenshot can be one of the quickest ways to show support staff what is happening.
A screenshot can capture the error message, the page where the problem occurred and other useful technical information.
But there is an important point that businesses should remember:
A screenshot can contain much more information than the error you are trying to report.
A goAML screen may display account details, organisation information, email addresses, user information, report data or other sensitive content. If that information is not necessary for troubleshooting, it should not be unnecessarily shared.
The UAE Financial Intelligence Unit (UAEFIU) publishes goAML troubleshooting guidance and asks users to provide specific information in certain support situations. Its current FAQ also contains screenshots illustrating common registration and login problems.
This guide explains what businesses should review before sending a goAML support screenshot.
Why Should You Check a Screenshot Before Sending It?
The purpose of a support screenshot is usually simple:
Show the problem clearly enough for the support team to understand what happened.
It is not necessary to expose every piece of information visible on the screen.
For example, suppose a user receives an error message after attempting to log in.
The useful part may be:
- The error message
- The page or section where it appeared
- The relevant button or field
- The approximate step that produced the error
The screenshot may also contain information that is irrelevant to the problem.
That information should be reviewed before the image is shared.
1. Never Include Passwords
A password should never be deliberately exposed in a support screenshot.
If a password field is visible, make sure the actual password is not displayed.
This is particularly important because the goAML login process can involve multiple authentication steps. UAEFIU guidance explains that users may encounter username, password and Google Authenticator-related authentication screens during access.
If a screenshot accidentally captures a password or another authentication secret, do not treat the screenshot as a normal troubleshooting image.
Stop and assess what has been exposed before sharing it.
2. Remove OTPs and Authentication Codes
One-time passwords and authentication codes should not be included in a support screenshot unless the relevant official support process specifically instructs you to provide information of that type.
The UAEFIU's current FAQ discusses email OTPs, SMS OTPs and Google Authenticator codes as part of SACM and goAML access procedures. It also explains that Google Authenticator passcodes change periodically.
These codes are authentication information, not ordinary troubleshooting details.
If the problem is an OTP error, a safer screenshot may show the error message rather than the actual OTP.
For example:
Useful:
“OTP expired” error message.
Unnecessary:
The actual six-digit OTP.
3. Check for Email Addresses
A screenshot can sometimes display a registered email address.
If the email address is not necessary to explain the problem, consider hiding it before sharing the screenshot.
This is particularly relevant when the screenshot includes:
- Account settings
- Login information
- Password-reset screens
- User-management pages
- Registration details
- Email notifications
However, do not hide information that official support specifically needs to identify your account or investigate the issue.
The goal is minimum necessary disclosure, not removing everything from the image.
4. Check Organisation Information
goAML screens can contain organisation-related information.
Depending on the page, a screenshot could potentially show:
- Organisation name
- Organisation ID
- User information
- Registration details
- Branch information
- Internal reference information
Some of this information may be necessary for support.
Therefore, do not automatically remove everything.
Instead, ask:
Does the support team need this information to understand or identify the issue?
If not, consider masking it.
If the support instructions specifically request the information, provide it through the appropriate official support channel rather than trying to remove information that is required for identification.
5. Be Especially Careful With Report Information
A goAML screenshot can potentially show information connected with reporting activity.
The UAEFIU explains that STRs submitted through goAML can contain relevant information about the suspected crime, parties involved, reasons for reporting and possible red flags.
That means a screenshot from a report-related page could contain significantly more sensitive information than a simple login-error screenshot.
Before sharing a report-related image, check whether it includes:
- Customer names
- Account information
- Transaction details
- Internal reference numbers
- Suspicion details
- Case information
- Supporting evidence
- Other customer or third-party information
If the support team only needs to see a technical error, there may be no reason to expose the underlying customer or report information.
6. Do Not Share an Entire Screen When One Section Is Enough
A common mistake is taking a full-screen screenshot when only one part of the page is relevant.
For example, if the problem is an error appearing beneath a specific field, the entire browser window may not be necessary.
A better approach is to capture the smallest useful area that shows:
- The relevant page or section
- The action that produced the error
- The error message
- Enough context for support to understand where the error occurred
This can reduce accidental exposure of unrelated information.
7. Hide Browser Tabs and Personal Information
Before sending a screenshot, look beyond the goAML page itself.
The screenshot may include:
- Other browser tabs
- Bookmarks
- Personal email notifications
- File names
- Desktop notifications
- Internal company information
- Other application windows
These details may have nothing to do with the goAML problem.
Crop the screenshot where practical.
If cropping is not possible, close or hide unrelated information before taking the screenshot.
8. Do Not Edit the Error Message Itself
There is an important difference between removing unrelated sensitive information and changing the evidence of the error.
Do not alter the actual error message.
Do not change:
- Error wording
- Error codes
- System messages
- Dates relevant to the problem
- Status messages
- Technical details needed for diagnosis
If you need to hide unrelated information, use cropping or masking around the relevant error.
The purpose of the screenshot is to provide accurate troubleshooting evidence.
9. Do Not Hide Information That Support Specifically Requests
Privacy protection does not mean refusing to provide information required for account verification or troubleshooting.
The UAEFIU's current FAQ gives examples of information that may be required for specific support situations. For example, when a user has forgotten a goAML username, the published guidance asks for information such as the entity name, registered name, registered email address, Emirates ID number, passport number, date of birth and Org ID, while specifically noting that copies of the Emirates ID and passport are not required for that particular request.
This illustrates an important principle:
Follow the specific information request rather than sending everything visible on your screen.
If support asks for certain details, provide those details through the official channel and according to the instructions given.
10. Use the Official Support Channel
A carefully prepared screenshot is only useful if it is sent through an appropriate support channel.
The UAEFIU publishes official goAML support and troubleshooting information through its Policies & Guidance resources and FAQ.
Businesses should avoid sending screenshots containing sensitive information to:
- Unverified email addresses
- Random social-media accounts
- Unofficial WhatsApp numbers
- Public forums
- Unrelated third-party websites
When in doubt, start with the official UAEFIU guidance and published support contact information.
A Simple Screenshot Review Before Sending
Use this checklist before attaching a goAML screenshot to a support request:
| Check | What to Look For |
| Password | Is any password visible? |
| OTP | Is an SMS/email OTP or authentication code visible? |
| Authenticator | Is a current authentication code visible? |
| Is a personal or registered email unnecessarily exposed? | |
| Organisation | Is company information visible that support does not need? |
| Customer data | Are customer names or account details visible? |
| Reports | Is STR/SAR or other report information visible? |
| Transactions | Are transaction details exposed? |
| Browser | Are unrelated tabs or notifications visible? |
| Error | Is the actual error message still clearly visible? |
| Context | Is enough of the page shown to understand the problem? |
| Channel | Is the screenshot being sent through an official support channel? |
Example: A Login Error Screenshot
Imagine a user is receiving an error while accessing goAML.
A poor screenshot might show:
- Username
- Password field
- Google Authenticator code
- Registered email
- Full browser window
- Organisation information
- Error message
The user may only need to show:
- The relevant login screen
- The error message
- The error code, if displayed
- The section where the error occurred
That provides support with useful context without unnecessarily exposing authentication information.
Example: An Upload Error Screenshot
The UAEFIU's FAQ provides specific guidance for document-upload problems, including attachment size, file naming and the requirement to click the Upload button before submitting.
If the issue is an upload error, a useful screenshot might show:
- The upload area
- The visible error message
- The file type or upload status, if relevant
There may be no reason to show unrelated customer documents or the contents of a confidential file.
Also remember that the current FAQ states that individual attachments should not exceed 5 MB and that file names should be short, in English and without special characters; report attachments have a separate 20 MB capacity per report.
Example: An OTP Problem
If the problem is an expired OTP, the screenshot should focus on the error.
The UAEFIU's FAQ specifically notes that OTPs may expire and directs users to contact the support team when refresh is required.
A screenshot showing:
“OTP expired”
may be useful.
A screenshot showing:
the actual OTP
is generally unnecessary.
The distinction is simple:
Show the problem, not the secret used to authenticate.
What If You Already Sent a Sensitive Screenshot?
If you realise that a screenshot contained information that should not have been shared, do not panic.
First determine exactly what information was exposed.
For example:
- Was it only an email address?
- Was an OTP visible?
- Was a password visible?
- Was customer information included?
- Was report information exposed?
The appropriate response depends on what was disclosed.
If an authentication secret such as a password was exposed, consider the relevant account-security response immediately.
If sensitive customer or reporting information was disclosed, follow your organisation's internal incident and confidentiality procedures and seek appropriate professional guidance where necessary.
Do not simply assume that deleting the screenshot from your computer removes information already transmitted to another party.
Screenshot Hygiene Is Not Permission to Alter Regulatory Records
There is another important distinction.
Removing unrelated sensitive information from a support screenshot is different from changing information in a regulatory submission.
A screenshot used for troubleshooting can be cropped or masked to reduce unnecessary exposure.
A submitted STR, SAR or other regulatory report should not be altered simply to make a screenshot look cleaner.
The UAEFIU's STR process explains that reporting entities submit relevant information through goAML and that the FIU may contact the reporting entity for further information or clarification.
Therefore:
Protect the screenshot. Do not manipulate the underlying regulatory record.
Best Practice: Capture, Review, Then Send
A simple three-step process can prevent many avoidable problems.
Step 1: Capture
Take a screenshot showing the error and enough context to understand it.
Step 2: Review
Before attaching it, inspect the entire image for:
- Passwords
- OTPs
- Authentication codes
- Personal information
- Customer information
- Report details
- Unrelated browser content
Step 3: Send
Use the official support route and provide only the information necessary to explain or resolve the issue.
This approach makes the support request clearer while reducing unnecessary information exposure.
Final Thoughts
A goAML support screenshot can be useful when a business encounters a registration, login, upload or reporting problem.
But the screenshot should be treated as a support document, not as a complete copy of everything visible on the screen.
Before sending it, remove or mask unnecessary passwords, OTPs, authentication codes, personal information, customer information and unrelated screen content. At the same time, keep the actual error message and relevant technical context intact.
The UAEFIU already provides official goAML FAQs, technical guidance and troubleshooting instructions for common issues. Businesses should use those official resources and follow the specific information requested for each support situation.
Need help resolving goAML registration or technical issues? Contact our team for professional goAML registration and compliance assistance.
Frequently Asked Questions
Should I send a full screenshot when contacting goAML support?
Not necessarily. Send enough of the screen to clearly show the problem and relevant context. Avoid unnecessarily exposing unrelated or sensitive information.
Should I hide my OTP from a goAML support screenshot?
Yes, unless the official support instructions specifically require information about the OTP itself. The actual authentication code is generally not necessary to demonstrate an error.
Can I hide my password in a screenshot?
Yes. Passwords should not be unnecessarily exposed in support screenshots.
Should I hide my Org ID?
Not automatically. If the support team needs the Org ID to identify your organisation, provide it through the appropriate official channel. If it is unrelated to the troubleshooting issue, avoid unnecessarily displaying it.
Can a screenshot contain customer information?
It can, particularly when the screenshot is taken from a report or transaction-related page. Review the image carefully and avoid exposing customer information that is not necessary for troubleshooting.
What should I show in a goAML error screenshot?
Ideally, show the relevant page or section, the action that caused the problem and the complete error message or error code, while removing unrelated sensitive information.
Where can I find official goAML troubleshooting guidance?
The UAEFIU publishes goAML FAQs and other technical and reporting guidance through its official Policies & Guidance resources.
Does screenshot privacy mean I can edit a submitted STR?
No. Protecting a support screenshot is different from altering a regulatory submission. The underlying regulatory record should not be changed simply to create a cleaner screenshot.
Need help with goAML registration or reporting?
Talk to our team and get your filings handled correctly the first time.