SSL Scanning in and of itself doesn't satisfy any privacy laws.
How you configure it + your corporate policies may or may not satisfy your local/global privacy laws.
If you are going to implement SSL interception, I recommend having a very explicit corporate Acceptable Use Policy that states that all transactions on the network are monitored and logged and ensure that all employees have accepted that AUP as well as a plan and/or policies as to how the decrypted data will be handled/used and have approval/buy-in from your Legal department/corporate counsel.
Web Gateway itself can be configured to bypass SSL interception for specific categories, specific destinations, specific sources, etc.
You could do a Google search for the legal ramifications or implications of SSL interception to get a better feel for what you're looking at, but ultimately if this is a global deployment, the legal aspects need to be examined for each location and that's where the Legal department/corporate counsel/other legal resources come into play
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.