GDPR, Anonymization of Customer Data

In accordance with the directives for GDPR The General Data Protection Regulation is a regulation in EU law on data protection and privacy in European Union and European Economic Area., individual customers' data privacy has to be protected. Data Governance is the process that classifies sensitive data and anonymizes it on request for data protection regulations.

NOTE
Based on our experience, FintechOS selected which information to anonymize. The financial institution can validate or add/remove attributes from the anonymization process within Innovation Studio.

There are two scenarios when the data can be anonymized:

Automatically
After 5 years (not counting the year of closure) the contractual relationship between a customer and a bank has ended. Certain data is automatically anonymized by the system: the scheduled job named FTOS_IB_CreateAnonymizationRequests runs a server-side script.
Manually
Upon user request, the bank can manually select a customer for which the data to be anonymized.

The types of information that are anonymized are username and password and:

The anonymization is done based on a rule. Both requests manually and automatically, anonymize the data in the entity FTOS_IB_UserXCustomer that have the status Inactive. Manually, the bank representative searches for the user or customer or automatically, the system anonymizes all the records which meet the rule.

IMPORTANT!
All the records in FTOS_IB_UserXCustomer, which will be anonymized, must be in the Inactive state first before anonymization.

FTOS_IB_UsersEnrollment	FTOS_IB_Users
	Name
	System User ID
	User Name
	Name
	Middle Name
	Last Name
	Personal ID Number
	Customer ID CoreBanking
	Document No.
	Email Address
	Mobile phone number
FTOS_IB_Users	Name
	Full Name
	Name
	Middle Name
	Last Name
	Personal ID Number
	Customer ID CoreBanking
	Document No.
	System User ID
	Unique Identifier IB
	Email Address
	Mobile phone number
FTOS_IB_UserXCustomer	Name
	System User ID
	ClientID
	Accounts
	SecurityLimitAmount

FTOS_IB_Mailbox_IN_Messages	Customer
FTOS_IB_Mailbox_IN_Messages	IB user ID
FTOS_IB_Mailbox_OUT_Messages	Attachments
	Customer
	IB user ID
FTOS_IB_Payment	payerFirstName
	payerMiddleName
	payerLastName
	payerAccount
	Payer Address
	Payer Postcode
	beneficiaryName
	beneficiaryIBANAccount
	paymentReason
	name
	transactionId
	ultimatePayer
	ultimatePayerID
	ultimateBeneficiary
	purposeOfPayment
FTOS_IB_PaymentExt	firstAuthorizerUserID
	secondAuthorizerUserID
	thirdAuthorizerUserID
	fourthAuthorizerUserID
FTOS_IB_FCYPaymentExt	FTOS_IB_FCYPaymentId
	accountNumber
	beneficiaryAddress
	beneficiaryPostCode
	paymentattachments
FTOS_IB_BGBudgetPaymentExt	obligatedPartyPayer
	companyIdObligatedParty
	personIdObligatedParty
	personIdObligatedPartyForeigner
	documentNo
	documentDate
FTOS_IB_UtilityPaymentContract	FTOS_IB_UtilityPaymentContractid
	Name
	ibUser
	customerId
FTOS_IB_UtilityPaymentService	Name
FTOS_IB_UtilityPaymentService	utilityPaymentServiceParentId
FTOS_IB_UtilityPaymentTransaction	Name
	utilityPaymentContractid
	userXTransactionTypeid
	Transaction_ID
	paymentDetails
FTOS_IB_Templates	FTOS_IB_TemplatesId
	templateFriendlyName
	schemaType
	currency
	visibleAllUsers
	payerAccount
	beneficiaryName
	beneficiaryIBANAccount
	paymentAmount
	paymentCurrency
	paymentReason
	paymentType
	name
	paymentCategory
	beneficiaryAddress
	detailsOfCharges
	settlementDate
	obligatedPartyPayer
	companyIdObligatedParty
	personIdObligatedParty
	personIdObligatedPartyForeigner
	budgetTypePayer
	budgetTypeCode
	budgetTypeDescription
	docTypeName - Document Type
	docTypeName - Document No
	documentDate
FTOS_IB_BulkFiles	FTOS_IB_BulkFilesId
FTOS_IB_BulkFiles	bulkFileName
FTOS_IB_UserXBankAccount	Alias
FTOS_IB_BankAccount	IBAN
	availableBalance
	Reason for the blocked amount
	blockedAmount
	Currency
	Balance
	Loan number