Private Credentials

Customers will provide sensitive data on tickets. This helps you secure that data.

With the advent of the GDPR and other similar privacy regulations around the globe, its important that you offer your customers methods to secure their data.  The Private Credentials add-on for Awesome Support give your customers a way to securely add sensitive data to tickets – data that is automatically removed when tickets are closed.

Customers tend to post private data in support tickets – whether you want them to or not!  From credit card numbers and passwords to health information – they inadvertently post private data in a medium that is not fully encrypted.  With this add-on however, you can collect sensitive information and store them encrypted in your database.  Configurable with up to two additional layers of encryption, you can provide a safer environment for your users to provide sensitive information.


Unlimited Credentials

In an era when everything is password protected, a single ticket can easily require multiple credentials for multiple systems.  This extension allows your users to enter as many credentials as needed, all neatly segmented into their own data card.

Easy To Use

The user simply clicks a button, enters the private data and pushes the “save” button to have confidential information saved to the ticket.  Ticket agents are notified on the ticket and can simply click a link to pop up the credentials.

Secure Upon Activation

As soon as the add-on is activated, every credential is encrypted and stored in the database.  A second encryption layer (highly recommended) is available by creating a key in wp-config – with a value that is unique to you!

An Additional Barrier Against Hackers

Good security is a multi-headed beast.  This add-on will not grant you perfect security by itself.  You still need SSL, good network firewalls and other security protocols.  But, it presents an additional barrier to would-be hackers interested in collecting your customers sensitive data.

Automatic Wipe

When a ticket is closed, all private data associated with the ticket is automatically removed from the database.  This reduces the amount of sensitive data that you store in your databases, making it a less attractive target for hackers.

Other Precautions

  • Credentials are not shown unless the agent actively chooses to view them.
  • Your customers can delete their credentials at any time.
  • Removing or changing the private key in wp-config will immediately render all prior saved credentials useless


Purchase options

  • Billed once per year until cancelled

  • Billed once per year until cancelled

  • Billed once per year until cancelled

Add to Cart


  • Your cart is empty.

Basic System Requirements

  • WordPress Version 4.9 or later
  • Awesome Support Version 5.8.0 or later
  • PHP 7.1 (7.3 or later recommended)

Additional Requirements

There are no additional requirements for this item.


Purchase options

  • Billed once per year until cancelled

  • Billed once per year until cancelled

  • Billed once per year until cancelled

Add to Cart


Recurring Subscription Notification

The pricing for this (and most other add-ons) is set as a subscription by default. However, you are free to cancel the recurring subscription at any time – you will still be entitled to the one year of free updates and support from the time of your last payment. The software will generally continue to work without additional payments. However, you should be aware that, as with all software, a future update of any of WordPress / Awesome Support Free Core could include a breaking change. At that time, if you are not on a subscription plan, you will need to purchase a new license to obtain the compatibility updates necessary for the product to continue to work.

To cancel your subscription:

  • Credit card or stripe users- just go to your MY ACCOUNT page on our website.
  • Paypal users - cancel from directly inside your Paypal account.

This notice does not apply to service products such as custom programming or to free plugins.

Related Articles and Videos

Unfortunately no related articles are available for this product right now.


Version 2.0.0

  • New: Complete revamp of the user experience with a full-screen lightbox instead of tabs.
  • New: Add a new separate field to collect a URL.

Version 1.2.4

  • Tweak: Allow height of PC window to grow to 100% - makes it more compatible with other add-ons that also use the WordPress thickbox functions.

Version 1.2.3 - July 13th, 2017

- Change: Add a column to the ticket list to display the number of credentials on the ticket
- Tweak: Cleaner CSS to prevent conflicts with other add-ons and plugins.
- Tweak: Moved the PRIVATE CREDENTIALS button to the BUTTON bar on the front end.
- Fix: Close button on back-end asked to confirm save even when nothing had changed.

Version 1.2.2 - December 23rd, 2016

- Tweak: Set maximum number of credential tabs to 5 instead of 3.
- Fix: Check if user is logged in before checking view access in private_credentials_form().
- Fix: Stop the plugin from loading resources on pages when not needed.

Version 1.2.1 - November 16th, 2016

- Fix: issues

Version 1.1.0 - November 15th, 2016

- Fix: Some jquery error conflicts

Version 1.0.9 - November 3rd, 2016

- Fix: Force use of HTTPS when FORCE_SSL_ADMIN is set to true

Version 1.0.8 - October 13th, 2016

- Misc: Code formatting and documentation.

Version 1.0.7

- Fixed: Incorrect error message in status bar when no credentials saved to ticket.

Version 1.0.6

- Fixed: Init credential to empty array. Fixes tickets list column count.

Version 1.0.5

- Added: Notification in status bar of popup to indicate decryption failure.

Version 1.0.4

- Added: Tickets list column showing # of private credentials on each ticket.
- Added: init_credentials() sets initial state and allows calling by ticket id for retrieval of credential count.

Version 1.0.3

- Fixed: Reply post was triggering save_hook().

Version 1.0.2

- Added: Second check to ensure user has view access to current ticket.
- Change: Use of new $post_id value in wp_footer() hook rather than get_the_ID() when rendering HTML form.

Version 1.0.1

- Added: $post_id var to save id initially.

Version 1.0.0

Initial Release