" gmail Archives - Page 2 of 3 - LuxSci FYI Blog: Learn about HIPAA email encryption, secure email encryption, and more

Posts Tagged ‘gmail’

LuxSci takes email privacy seriously … Google owns your Gmail data forever

Wednesday, April 16th, 2014

In recent news, Google is warning consumers that Gmail and google apps are actively scanning your email.

What does this mean?  Google on Tuesday edited its privacy policy to say:

Our automated systems analyze your content (including emails) to provide you personally relevant product features, such as customized search results, tailored advertising, and spam and malware detection. This analysis occurs as the content is sent, received, and when it is stored.

When you upload, submit, store, send or receive content to or through our Services, you give Google (and those we work with) a worldwide license to use, host, store, reproduce, modify, create derivative works (such as those resulting from translations, adaptations or other changes we make so that your content works better with our Services), communicate, publish, publicly perform, publicly display and distribute such content.

Read the rest of this post »

Gmail is Always Playing Catch Up

Monday, April 7th, 2014

In case you missed it, Gmail’s “big announcement” last week was that it would:

  1. Only allow secure (over https / SSL) web connections from users to its servers, and
  2. Make sure that all email traveling between its servers over the Internet uses SSL so it can’t be eaves dropped upon.

This is generally a very good thing.   Its always nice when companies catch up to normal standard procedures by improving their policies.  This makes the Internet an incrementally more secure and safe place.

Just be careful not to give them too much credit as this is really a case of playing “catch up” and not doing anything new or special.  

Read the rest of this post »

Secure? Google Mail Getting Increasingly Less Private

Thursday, December 19th, 2013

In the news this week: Gmail is trying to make its web interface faster and a little safer … but are they trading away some of your privacy in the process and making Gmail addresses better targets for email marketers?

What is Google Doing?

Instead of waiting for you to click a “show images” button on every message that is displayed, Google is pre-loading all the images on their servers, scanning for viruses, and then displaying them automatically inline. You can turn this off in your Settings.

On this surface, this gives you:

  1. Images right away — fewer clicks
  2. Safer images — they have been scanned for viruses and malware

Sounds good so far, but…

Read the rest of this post »

Are Replies to my HIPAA-Compliant Secure Emails also Secure?

Friday, October 11th, 2013

HIPAACustomers of LuxSci HIPAA-compliant email accounts can send secure email messages in a secure and compliant manner to anyone with an email address.   One common question is whether the replies back to these messages will also be HIPAA compliant.  This is especially a concern when customers choose to use TLS only a a secure means of email delivery.

In this article we will break down the various ways that messages are sent securely from LuxSci to recipients across the Internet, and how replies behave — and whether they are secure and compliant.  At the end, we provide some recommendations for best practices for maximizing data security.

Read the rest of this post »

HIPAA Compliance is Needed for Emailed Appointment Reminders

Friday, September 20th, 2013

HIPAA ComplianceTwice in the past few weeks I have received appointment reminders or scheduling information from doctors via email — via insecure, non-HIPAA-compliant email.

An email message contains identifying information: my email address and my name.  The appointment email messages also contain information about “the past, present, or future provisioning of health care to an individual” … me!  Taken together, this means that these email messages are ePHI (more details – what is ePHI?) and needed to be secured in a HIPAA compliant manner.

That they were not compliant was obvious to me:

Read the rest of this post »

LUXSCI