Data Handling
How we treat the information entrusted to us.
Last updated: 4 October 2026
Production Data Principle
We strictly avoid using live customer production data in development or staging environments. Anonymized mock data is enforced across all engineering pipelines.
Purpose First
We request and use project information only when it has a clear purpose related to understanding, delivering, maintaining, or supporting the agreed work.
Minimum Necessary Access
Team members and approved collaborators should access only the information reasonably necessary for their specific responsibilities.
Client Credentials
Where project access credentials are required, we encourage the use of dedicated project accounts, role-based permissions, temporary access, and secure credential-sharing methods rather than sending passwords through ordinary messages.
Storage
Project files and information may be stored in approved systems used for communication, design, development, documentation, hosting, or project management. We aim to avoid unnecessary duplication of confidential information across tools.
Third-Party Platforms
Some projects require third-party platforms, cloud providers, hosting providers, repositories, analytics tools, or other external services. Where they are required, access should be limited to the project purpose and governed by the relevant provider terms and any applicable client agreement.
Confidential Information
Information identified as confidential, or which is reasonably understood to be confidential, should not be disclosed outside the project team except where authorized, contractually required, or legally required.
Production Data
We avoid using real production or personal data for development and testing when realistic alternatives such as dummy, masked, or anonymized data can reasonably be used.
Backups and Copies
Temporary copies, exported files, and backups should be limited to what is reasonably necessary for project delivery, recovery, or contractual obligations.
Project Completion
After project completion, access rights should be reviewed. Credentials, repositories, accounts, and files should be transferred, retained, archived, or removed according to the project agreement and legitimate operational or legal requirements.
Incident Handling
If we become aware of a security or data incident affecting information entrusted to ZORS CRAFT, we will assess the situation, take reasonable steps to contain the issue, document relevant facts, and communicate with affected clients or parties where appropriate or legally required.
Client Responsibilities
Secure projects are a shared responsibility. Clients should maintain appropriate access controls, avoid unnecessary sharing of sensitive credentials, keep authorized contacts current, and promptly inform ZORS CRAFT when access should change or be revoked.
Questions
Questions or audits regarding project data handling can be sent to hello@zorscraft.id.