Security

Zonely adopts security-oriented development and operation approach. Objective; to protect accounts, software integrity and service continuity.

Human audit and access limits

Do not only evaluate the safety through an automatic decision or artificial intelligence output. Limit access authorizations, review records and let suspicious transactions to the support team. WAF and server protections are handled with secure application development, update and correct configuration.

Data privacy and security contain different responsibilities. Data protection and privacy policy View this distinction on pages.

General security measures

• Access control and authorization layers.
• Observe suspicious session and transaction behaviors.
• Encryption and secure storage in appropriate areas.
• Log inspection and event intervention processes.
• Planned maintenance and security updates.

User responsibilities

• Use strong password and do not share.
• Activate additional verifications such as 2FA if there is an image.
• Webhook URLs API Keep keys and integration tokens hidden.
• Manage the contacts you provide panel access with minimum authorization.

Responsible security notice

If you have identified a vulnerability, we want to inform you about it in a responsible way through the support system. The affected area in the notifications accelerates the process of sharing steps and technical details of reproduction.

Limits

Security researches should not be in the form of leaking data, access to user accounts, overloading systems or deduction of service. The purpose is to help show and close the deficit.

Log and review

Logs related to security events can be examined and temporary measures can be applied to prevent risk from spreading. These steps are to protect the integrity of the service.