Data handling
SalesBreaker handles account information, customer settings, company data, execution history, engagement events, billing references, and support inquiries as needed to provide, secure, troubleshoot, and improve the service.
SalesBreaker
Security Summary
This page provides a practical English overview of SalesBreaker security and data handling for English-speaking operators. The Japanese policies and disclosures remain authoritative where applicable.
Customer data separation
Customer-specific data, including uploaded house lists and customer settings, is handled separately from the SalesBreaker company database. Customer house lists are not treated as a shared database for other customers.
Access control
Administrative and production access is limited to people who need it for operation, support, billing, security, or incident handling. Credentials and operational access are managed with care, and broad unrestricted access is not provided to external tools.
Logging and monitoring
The service uses operational logs and monitoring to support troubleshooting, abuse prevention, reliability, billing support, and security investigation. Logging coverage and review processes are being improved gradually.
Responsible operation
SalesBreaker is intended for managed business outreach workflows. Operators should review target conditions, sender information, suppression settings, and contact preferences before using the service.
Incident response
If a security or service incident is suspected, SalesBreaker investigates the scope, takes mitigation steps, preserves relevant operational information where appropriate, and communicates with affected customers when needed.
Certification status
- ISO27001: not certified yet.
- PrivacyMark: not certified yet.
- SalesBreaker is gradually improving internal controls based on service growth, customer requirements, and partner requirements.
Inquiry path
For security, privacy, account, or billing questions, use the support or account path shown inside SalesBreaker. Public English inquiry routing will be refined as the English workspace matures.