Security
Dlong SCRM applies technical and organizational safeguards to its customer messaging service. Third-party messaging integrations are enabled only after required platform approval, account authorization, and final integration/security validation.
Current security principles
HTTPS transport
The public website is served over HTTPS. Application integrations are designed to use encrypted HTTPS connections.
Credential protection
Passwords, API secrets, access tokens, and other credentials are treated as secrets and should not be exposed in public pages, URLs, or ordinary application logs.
Access control
Administrative functionality is designed around authenticated access and role-aware controls appropriate to the deployment.
Operational safeguards
Rate limiting, retry controls, event logging, backups, and environment separation are used where appropriate to reduce operational risk.
Vulnerability reporting
If you believe you have found a security issue affecting Dlong SCRM or this website, email developer@dlongscrm.cc. Please include a concise description and reproduction details, and do not access data that is not yours.
No certification claim
Dlong SCRM does not claim ISO 27001, SOC 2, PCI DSS, or other third-party security certification unless and until such certification is formally obtained.
Platform integration controls
Third-party platform integrations are enabled only after applicable platform approval, account authorization, and final integration/security validation. Service environments and data handling are separated according to their operational purpose.