Your privacy is important to us. This policy explains how we collect, use, protect, and handle your personal information.
Last Updated: November 26, 2025
We collect information that you provide directly to us, including:
We collect this information when you request services, instant demos, create an account, communicate with us, or engage with our platforms.
We use the information we collect to:
We process your data lawfully, transparently, and only for legitimate business purposes.
We implement robust security measures to protect your information:
Your security is our top priority, and we apply the same rigorous standards to our own systems.
We do not sell your personal information. We may share your data only in these circumstances:
All third parties are bound by strict confidentiality agreements and data protection requirements.
When you connect SLASH to third-party services (like Slack or Jira), SLASH sends data FROM your SLASH account TO those services. Here's what happens:
How It Works:
When you enable an integration, SLASH automatically sends specific data to the connected service. This data flows FROM SLASH TO the third-party service (not the other way around).
- What Data is Sent: When vulnerabilities are found or pentest status changes, SLASH sends this information TO your Slack channels:
- Vulnerability titles and descriptions
- Severity levels (Critical, High, Medium, Low)
- Status changes (e.g., "New", "In Progress", "Resolved")
- Pentest progress updates
- Report publication notifications
- Comments added to vulnerabilities
- Where It Goes: This data appears as messages in your configured Slack channels
- Purpose: To notify your team in real-time about security findings
- You Control: You choose which events trigger notifications and which Slack channels receive them. You can disconnect anytime.
- Third-Party Privacy: Once data is sent to Slack, it's subject to Slack's privacy policy (https://slack.com/privacy-policy)
- What Data is Sent: When vulnerabilities are discovered, SLASH automatically creates Jira issues and sends this data TO your Jira instance:
- Vulnerability titles and descriptions
- Severity levels and CVSS scores
- Remediation steps and recommendations
- Pentest metadata (project name, dates, etc.)
- Status updates when vulnerabilities change state
- Where It Goes: This data becomes Jira issues/tickets in your Jira project
- Purpose: To automatically create and track vulnerability remediation tasks in your project management system
- You Control: You configure how issues are created (as Stories, Epics, Tasks, or Bugs) and can disconnect anytime
- Third-Party Privacy: Once data is sent to Jira, it's subject to Atlassian's privacy policy (https://www.atlassian.com/legal/privacy-policy)
You have the following rights regarding your personal information:
To exercise these rights, contact us at [email protected]. We will respond within 30 days.
We retain your information only as long as necessary:
After retention periods, data is securely deleted or anonymized.
SecurityWall stores Customer Data in accordance with industry best practices and compliance requirements:
We ensure that Customer Data storage complies with applicable data protection laws and industry regulations.
SecurityWall will remove Customer Data in accordance with the following policy:
- Legal obligations (e.g., court orders, regulatory requirements)
- Legitimate business interests (e.g., dispute resolution, fraud prevention)
- Industry standards (e.g., security assessment records retained for 7 years)
- Contractual obligations with customers
- Permanently deleted from active systems within 30 days
- Removed from backup systems within 90 days (backup rotation cycle)
- Securely overwritten to prevent recovery
- Verified through deletion audit logs
- Data may be archived (moved to secure, encrypted long-term storage) before final deletion if required for legal or compliance purposes
- Archived data remains encrypted and is only accessible for legal or regulatory purposes
- Archived data is subject to the same retention periods and will be permanently deleted upon expiration
For specific data removal requests or questions about our archival process, contact [email protected].
SecurityWall operates globally, and data may be transferred internationally:
Your data receives the same level of protection regardless of location.
We may update this Privacy Policy periodically:
We encourage you to review this policy regularly.
For privacy-related questions or to exercise your rights:
Email: [email protected]
Phone: +1 307 393 9425
Mail: SecurityWall, Sheridan, WY
Data Protection Officer: Available for GDPR and privacy inquiries
We're committed to protecting your privacy and will respond to all inquiries promptly.