Freshworks Marketplace

App cover art submitted by the app developer that represents the app

Credit Card and Social Security Number Masker

verified badge symbolVerified by Freshworks
Protect sensitive data, such as Credit Card and Social Security numbers in your Freshservice tickets.
Published by Freshworks(about 4 days ago)
Free
download
79
Version History
Supported for
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.
Install
OverviewRatings and ReviewInstallation InstructionsPrivacy & Security
Freshservice integration with the Credit Card and Social Security Number Masker app enables IT teams to protect sensitive data by setting up rules for masking the Credit Card and Social Security numbers mentioned in the subject, description, and private/public notes of your Freshservice tickets. The app masks all digits of a credit card or social security number with ‘X’ except the last four digits. Additionally, this app has the capability to identify and mask any data that resembles a credit card or social security number. The app also provides options to set rules that exclude masking and expose credit card or social security numbers based on specific conditions, such as setting up rules applicable for: - Specific workspaces associated with your account (for example, IT or HR) - Credit card or social security numbers starting with specific digits (for example, 1234) - Specific groups or teams (for example, Database Team or Hardware Team) Learn more: https://support.freshservice.com/en/support/solutions/articles/50000010727-freshservice-integration-with-credit-card-and-social-security-number-masker
Here is a quick step-by-step flow on how to successfully integrate and use the Credit Card and Social Security Number Masker app. 1. Start installation: - Click Install to open the app configuration page. 2. Validate Freshservice OAuth Parameters: - Enter your Freshworks Org URL to validate the Freshservice OAuth Parameters and continue. 3. Select your account: - After your Freshworks Org URL is validated, select the account for which you want to install this app and continue (for example, Freshservice account). Note: You may also find an option to select a developer account, which is not applicable for installing this app. 4. Authorize the app: - Review and accept the permissions for authorization. 5. Add rules for masking (optional): - Add any rules required for masking or continue with the installation. Note: You can also add, remove, or modify rules post installation. 6. Complete installation: - After all the details are validated, click Install to complete the installation. Detailed help article to view and customize recipes: https://support.freshservice.com/en/support/solutions/articles/50000010727-freshservice-integration-with-credit-card-and-social-security-number-masker
The information listed below is provided by the App Developer Partner pertaining to the data privacy policies of the latest app version available on the Freshworks Marketplace. The App Developer Partner is solely responsible for the accuracy of the information provided.
What is End-User data?
Any information that is generated or provided by individuals while using your apps in connection with Freshworks products.
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
Does your app transfer European Economic Area (EEA) residents’s End-User Data outside of the EEA?
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?
Yes
Elaborate the encryption methodology adopted
Below methodology is used for encryption 1. Encryption: Algorithm: AES with a 128-bit key with ECB(Electronic Codebook) mode
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
close modal
close modal
Go to Developer Portal