Credit Card and Social Security Number Masker
Verified by FreshworksHide sensitive data such as credit card numbers or Social Security numbers in Freshservice tickets.
Published by Freshworks(about 32 minutes ago)
By clicking on "Install", you acknowledge and agree that your access and use of this application will be governed by the developer's terms of service and privacy policy. Freshworks may share your contact and usage information with the developer.
This app will protect sensitive customer data such as credit card or Social Security numbers that are mentioned in tickets. The app will obfuscate all but the last 4 digits of the numbers; the other digits will be masked by an ‘X’. The data is protected in the Ticket Subject, Description, Private and Public Note. The app may also be configured to ignore masking numbers that start with a particular sequence of digits e.g. 99 if needed. The app can be configured to ignore masking for email tickets with subjects that match a certain set of keywords. The keywords must be entered as comma-separated values in the installation page.
What's new?
Earlier, this app would mask any 16-digit number. We've now included the LUHN algorithm to identify whether the number is that of a valid credit card or whether the data is a social security number before masking.
The following credit card formats are covered in this app:
4242424242424242 Visa
4000056655665556 Visa (debit)
5555555555554444 Mastercard
2223003122003222 Mastercard (2-series)
5200828282828210 Mastercard (debit)
5105105105105100 Mastercard (prepaid)
378282246310005 American Express
371449635398431 American Express
6011111111111117 Discover
6011000990139424 Discover
30569309025904 Diners Club
38520000023237 Diners Club
3530111333300000 JCB
6200000000000005 UnionPay
Disclaimer: This app will mask any data that resembles a credit card/Social Security number.
1) Enter valid Freshservice URL and API credentials for verification.
2) Choose if the app must obfuscate only Credit card numbers or Social Security numbers or both.
3) Provide the starting sequence of a number that must be ignored from masking, if required.
4) If the app must avoid masking numbers in email-based tickets based on keywords from the email's subject, provide the keywords as comma-separated values in the text box provided.
5) If the app must avoid masking numbers based on the group of a ticket, choose the groups to ignore masking in the dropdown provided.
Data Management and Storage
Does your app use AI or GenAI features?
No
Does your app use "Freshworks AI powered features or Freddy AI" and comply with Freshworks AI powered features and Freddy AI terms?
No
Does your app collect / process any End-User data?
Yes
What End-User data does your app collect/process?
Accesses to ticket-level information within the incident management module
What is the purpose of collecting/processing the data?
The app scans the ticket for credit card information and masks the number.
Does your app store any End-User data?
No
Does your app share End-User Data with any third party entities?
No
No
Can the End-User data be exported?
No
Can End-User data be accessed through your app logs?
Yes
Is the End-User data encrypted at rest?
NA
Is the End-User data encrypted in transit?
Yes
Elaborate the encryption methodology adopted
TLS
Does your app adhere to the OWASP (Open Web Application Security Project) security standard?
NA
Does your app permanently delete the customer data as soon as the customer uninstalls the app?
Yes
Does your app allow customers to request a custom End-User Data retention period?
No
Log in to install this app
Enter your Freshservice URL to proceed
https://
Proceed
Version History3.0 (December 2024)
Version 3.0:
* Clean up of App Logs to prevent ticket information from being exposed
2.0 (September 2024)
Version 2.0:
What's New:
App capability extended to support accounts with multiple workspaces.
By default, the app will work across all workspaces
Workspace-level configuration has been introduced to ignore masking based on groups and number-based conditions