Web Insights

Personally Identifiable Information (PII) Security

It's critical to ensure your users' data security and compliance with PII management.

What is PII?

PII, or Personally Identifiable Information, refers to any data that can be used to identify an individual. This includes, but is not limited to:

  • Full name
  • Email address
  • Phone numbers
  • Physical address
  • Tax file number
  • Date of birth
  • IP address
  • Financial Information (credit card numbers, bank account details)
  • Login Credentials (usernames, passwords)
  • Health Information

Collecting PII via Public Web Forms

Web forms are common tools for collecting user information for various purposes such as registrations, subscriptions, purchases or enquiries. We recommend the following best practices for web forms that collect PII:

Clearly inform users about the data being collected and the purpose.

This can done using a one to two sentence statement directly visible on the form above the submit button. Greater detail could be provided by linking to a separate privacy policy page.

Obtain explicit consent from users before collecting their data.

This can be done using a checkbox alongside a statement of consent. The checkbox field would be required to be checked by the user before the form can be submitted.

Storing PII in the Database

When PII is stored in your website's database, it is essential to:

Use strong encryption methods to protect data at rest.

Our preferred form plugin (Craft Formie) has an option to encrypt form field data. We turn this on by default for forms initially created by us during the development process and we recommend you enable this for any future forms as well.

Implement access controls to restrict control panel access to authorised personnel only.

If multiple users are accessing the back-end of your website, we need to ensure that the right people have the right permissions, so access to the PII is limited.

Regularly update and patch database management systems to address security vulnerabilities.

We recommend jumping on board our maintenance plans to ensure your website CMS can be kept up to date and have regular check-ups. Find out more about how we keep your website up to date here.

Consider your data retention settings

Data retention policies should be defined and enforced to determine how long PII is stored. Only retain PII for as long as necessary to fulfill the purpose for which it was collected. For any web forms that store PII we recommend a 14 day data retention period.

Make sure you have a process in place for easy data deletion

It's important to ensure data deletion processes comply with relevant regulations (ie. GDPR). When a user requests for their data to be completely removed from your website storage system, you must be able to action this quickly and easily.

Email Notifications

If your system sends email notifications containing PII, we recommend the following:

Avoid including sensitive PII in emails where possible.

If your form data is being stored in the website database or connected directly to a CRM then your notification emails may not need to display the information.

Use encryption methods (e.g., TLS) to protect emails in transit.

Our websites and email sending systems do this by default so your emails are secure.

Train staff to handle emails containing PII securely and recognise phishing attempts.

It's recommended to consider employing security and data retention policies surrounding your staff email accounts. Are your systems and email accounts protected by multi-factor authentication (MFA)? Does sensitive data stored in emails get purged after a certain amount of time?

External Integrations (CRMs)

When connecting your website to external systems such as Customer Relationship Management (CRM) platforms, ensure:

  • Secure API connections with strong authentication mechanisms (e.g., OAuth).
  • Regular audits and reviews of third-party service providers to ensure their compliance with data protection standards.
  • Clear data mapping and documentation to understand what PII is shared with external systems and for what purpose.

Security Best Practices

To enhance the overall security of PII on your website, we recommend adopting the following best practices:

  • Enable MFA (multi-factor authentication) on your website CMS
  • Regularly conduct security assessments and vulnerability scans of your website and infrastructure.
  • Establish an incident response plan to address data breaches or security incidents promptly.
  • Provide training for staff on data protection principles and security practices.

Of course - we're always happy to talk further and help you with implementing these best practices.

Conclusion

Protecting PII is a shared responsibility between us and our clients. By understanding and implementing these practices, you can help safeguard your users' data, comply with regulatory requirements, and build trust with your audience. If you have any questions or need further assistance, please do not hesitate to contact us.

Introduction

As your trusted website development and hosting partner, we prioritise the security and privacy of your users' data. This article outlines essential considerations for managing Personally Identifiable Information (PII) collected through public web forms on your website. Understanding these aspects will help ensure compliance with data protection regulations and maintain the trust of your users.

Use our simple check-list Download PDF