Data matters.
Responsibility is clear.
What needs to be clarified before customer, contract and resident data goes into the system.
What is built into the product.
What is committed in the contract.
Pico only states what the product already has. Other certifications or commitment levels are mentioned only when supporting documentation exists.
The data belongs to the developer.
Pico commits not to take or use customer data for any other commercial purpose, in compliance with Vietnamese law. When the engagement ends, the data is handed back to the developer.
Built into the product: The developer's Admin creates accounts and assigns permissions; agencies only perform the tasks granted to them; customer and Admin interfaces are separate.
Commitment: The matrix of roles, units, projects and data scope is approved before go-live.
Built into the product: Contracts go through an approval flow; Workflow Approval supports approval levels, branching and delegation.
Commitment: Your approval process is configured and accepted.
Built into the product: Workflow Approval keeps a processing log and process versions.
Commitment: The list of actions to be logged in other modules is agreed based on your control requirements.
Built into the product: Customer data is visible only within the granted role scope; customers view their own information in the App.
Commitment: The purpose, collection scope and data sharing channels are set out in the data processing agreement.
Built into the product: All interfaces on the website and in demos use sample data, not real customer records.
Commitment: Not applicable
Built into the product: Data in the system belongs to the developer.
Commitment: Pico commits not to take or use the data for any other commercial purpose, and to comply with Vietnamese law.
Built into the product: The developer can export its own data.
Commitment: When the engagement ends, data is handed over to the developer; scope, format and schedule are set out in the contract.
Built into the product: Agreed per project
Commitment: The infrastructure option, storage location and administration contact are stated in the proposal.
Built into the product: Agreed per project
Commitment: Backup frequency, recovery time and recovery test schedule are agreed in the contract.
Put requirements in scope.
Put responsibility in the agreement.
Discuss infrastructure requirements, access rights, testing and the supporting documentation you need before finalizing the approach.