Best Practices for Collecting Information
If you collect, or plan to collect, personal information from users, it is critical that you handle that data responsibly.
On this page
Did you know?
Personal identifiable information (PII) includes obvious things like an email address, phone number, device identifier, physical location, and spending habits. However, even less obvious information like zip codes or typical commute times can be combined to help identify people without their consent.
Collect the minimum amount of personal information necessary to provide the desired functionality. For example, if you only use email to communicate with site visitors, there is no reason to also collect phone numbers.
Let customers consent to sharing their data rather than collecting their data by default. For example, include a checkbox asking for permission to collect contact information and leave it unchecked by default.
Avoid persistent caching or storage of PII, including in logs. Do not keep the information for longer than needed. The easiest way to avoid unintentionally exposing sensitive information is to delete it when you no longer need it.
Avoid sharing any PII or location information with third parties. When customers give you permission to collect and save their information, there is an expectation that the information is kept safe and not be shared with others. Sharing their information with a third party without asking for explicit permission violates those expectations. You might be complicit if the third party handle the information irresponsibly.
Secure your website traffic with HTTPS and TLS. If you are unfamiliar with HTTPS and TLS, see TLS and HTTPS for more information.
If your application uses customer contact information, be sure to use that information judiciously. The following tips describe how to handle customer data responsibly:
Respect customer email preferences. If they have opted out of marketing emails, keep
Do not store PII like names, email addresses, and physical address without explicit consent.
Do not store sensitive or payment information in the
Always use secure HTTPS for your own services to protect user information in transit.