Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Tuesday May 01 2018, @02:02PM   Printer-friendly
from the no-you-see-me,-now-you-don't dept.

Submitted via IRC for TheMightyBuzzard

Google will slowly be rolling out a number of changes for consumer Gmail users and G Suite users. Some of the changes improve usability and productivity, while others are meant to maximize data and user protection. Some of the new security options should help enterprise users meed GDPR compliance needs.

[...] Gmail confidential mode will allow users to:

  • Set expiration dates for emails or revoke previously sent messages
  • Secure access to the contents of emails by requiring recipients to enter a password
  • Restrict the recipients’ ability to forward, copy, download or print emails.

These things will be possible because these emails will not be actually downloaded in the recipients’ inbox, but will be placed on a separate page/window where their content can be viewed, and the email will show that page.

Guess I'll be switching to ProtonMail for my webmail needs, which, granted, are few.

Source: https://www.helpnetsecurity.com/2018/04/26/gmail-self-destructing-emails/


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Wednesday May 02 2018, @10:04AM

    by Anonymous Coward on Wednesday May 02 2018, @10:04AM (#674517)

    Except your company, who will most likely fire/sue you for willfully violating the GDPR.

    That would be willfully violating the GDPR by sending personal data to Google?

    Under normal HIPAA rules (and I'm guessing GDPR), it is not allowed to send personally identifiable information (PII) via email because email is considered insecure. This provides a way for companies to actually email you information while complying by any relevant data protection laws.

    The insecure part is the protocol, not the inbox. Attempting to change what happens after the data lands in the inbox will not change that.