Security Incident Response Policy

Security Incident Response Policy

Last Updated: November 15, 2026

1. Purpose and Scope

This Security Incident Response Policy establishes the procedures CostRadar.ai follows to identify, respond to, and recover from security incidents that may affect the confidentiality, integrity, or availability of our services and user data.

This policy applies to all security incidents affecting CostRadar.ai systems, infrastructure, and data, including personal data breaches as defined by GDPR and other applicable data protection regulations.

2. Incident Classification

2.1 Severity Levels

Critical (P1)

Incidents with immediate and severe impact requiring emergency response:

  • Confirmed data breach with exposure of sensitive personal data
  • Complete service outage affecting all users
  • Active security breach or ongoing attack
  • Unauthorized access to production systems
  • Ransomware or malware infection
  • Response: Best effort, as soon as the CEO sees the report. There is no staffed 15-minute rota. Notification: Personal-data breaches to the Polish authority (UODO) within 72 hours where GDPR Article 33 requires it. Affected sellers without undue delay. TikTok Shop without undue delay when TikTok Shop data is involved.

    High (P2)

    Significant incidents requiring urgent attention:

  • Potential data exposure requiring investigation
  • Partial service degradation affecting multiple users
  • Detection of vulnerability being actively exploited
  • Suspicious authentication patterns or access attempts
  • Response: Best effort the same day the report is seen. Notification: As soon as the facts support a notice.

    Medium (P3)

    Incidents with moderate impact:

  • Security vulnerability discovered but not exploited
  • Minor service disruption affecting limited users
  • Policy violations without data exposure
  • Failed intrusion attempts
  • Response: Best effort within a few business days. Notification: If customers or a platform need to know.

    Low (P4)

    Minor incidents with minimal impact:

  • Security events requiring monitoring
  • Minor configuration issues
  • Informational security alerts
  • Response Time: Within 24 hours Notification: As appropriate

    3. Incident Response Team

    3.1 Roles and Responsibilities

    CEO, all incident roles

  • Marcin Nowak is Incident Commander, technical lead, communications contact, and the person who decides on regulatory notices. Radrly has not appointed a statutory Data Protection Officer.
  • Report incidents to support@radrly.com.
  • A post-incident review is completed within 5 business days. Corrective actions are GitHub issues labelled security.
  • 3.2 Escalation Contacts

  • Security contact: support@radrly.com
  • Incident lead: support@radrly.com
  • Privacy / DPA contact: hello@costradar.ai
  • Legal inquiries: hello@costradar.ai
  • 4. Incident Response Process

    Detection and Reporting

    Security incidents may be detected through:

  • Application and infrastructure monitoring / alerting
  • User reports of suspicious activity
  • Third-party security researchers
  • Periodic security reviews
  • All suspected incidents must be reported immediately to support@radrly.com.

    Initial Assessment and Triage

    Within the response time for the incident severity:

  • Confirm the incident is legitimate (not a false positive)
  • Determine incident severity and classification
  • Activate appropriate incident response team members
  • Begin incident documentation and timeline
  • Establish communication channels for incident response
  • Containment

    Immediate actions to limit incident scope and impact:

  • Short-term containment: Isolate affected systems, block malicious IP addresses, disable compromised accounts
  • Evidence preservation: Take system snapshots, collect logs, document system state
  • Long-term containment: Apply security patches, change credentials, implement additional monitoring
  • User impact mitigation: Implement workarounds, provide status updates
  • Investigation and Analysis

    Detailed analysis to understand the incident:

  • Determine root cause and attack vector
  • Identify affected systems and data
  • Assess scope of data exposure or compromise
  • Review access logs and security events
  • Identify indicators of compromise (IoCs)
  • Document findings and evidence chain
  • Eradication

    Remove the threat and address vulnerabilities:

  • Remove malware or unauthorized access
  • Close exploited vulnerabilities
  • Apply security patches and updates
  • Strengthen security controls
  • Validate eradication through testing
  • Recovery

    Restore normal operations:

  • Restore affected systems from clean backups if needed
  • Reset passwords and regenerate access tokens
  • Re-enable services in controlled manner
  • Implement enhanced monitoring
  • Verify system integrity and functionality
  • Gradually restore user access
  • Post-Incident Review

    Conducted within 5 business days of incident resolution:

  • Document lessons learned
  • Identify areas for improvement
  • Update security controls and procedures
  • Implement preventive measures
  • Update incident response plan as needed
  • Share findings with relevant teams
  • 5. Notification Requirements

    5.1 User Notification

    For personal data breaches affecting users:

  • Timing: Without undue delay, within 72 hours of breach discovery
  • Method: Email to affected users' registered email addresses
  • Content: Nature of breach, types of data affected, likely consequences, measures taken, contact information
  • Threshold: All breaches likely to result in risk to user rights and freedoms
  • 5.2 Regulatory Notification

    Required notifications to data protection authorities:

  • GDPR: Within 72 hours to relevant supervisory authority
  • CCPA: As required by California law
  • Shopify: Notify Shopify as required for incidents affecting Shopify app/store data
  • Amazon Solution Provider Portal: Incident management point of contact is hello@costradar.ai; notify Amazon as required for SP-API / selling-partner data incidents
  • Amazon / WooCommerce: Notify affected platform partners or merchants as contracts/law require
  • Other jurisdictions: As required by applicable laws
  • 5.3 Internal Notification

  • Executive team notified within 1 hour for P1/P2 incidents
  • All team members briefed on need-to-know basis
  • Regular status updates during incident response
  • Post-incident report distributed to all stakeholders
  • 6. Data Breach Specifics

    6.1 Data Breach Assessment

    For every suspected data breach, we assess:

  • Types of data exposed (email, passwords, financial data, etc.)
  • Number of affected users/data subjects
  • Likelihood and severity of harm to individuals
  • Whether data was encrypted or otherwise protected
  • Who gained unauthorized access and their intentions
  • Whether exposed data has been recovered or contained
  • 6.2 User Protection Measures

    Following a data breach, we may:

  • Force password resets for affected accounts
  • Invalidate all active session tokens
  • Revoke OAuth tokens for third-party integrations
  • Provide credit monitoring services (if financial data exposed)
  • Offer identity theft protection services
  • Implement additional account security features
  • 7. Documentation and Record Keeping

    All incidents are documented with:

  • Incident timeline with all key events
  • Affected systems and data inventory
  • Actions taken at each response phase
  • Communications sent to users and authorities
  • Evidence collected and analysis performed
  • Post-incident review findings
  • Incident records are retained for 7 years to comply with regulatory requirements and support future investigations.

    8. Testing and Training

    8.1 Incident Response Drills

  • A tabletop exercise is planned at least once a year, covering a leaked platform token or a compromised server. Exercises are not quarterly, and none has been recorded yet.
  • 8.2 Team Training

  • The CEO completes a yearly security and privacy awareness refresh. There is no larger incident-response team to train.
  • 9. Continuous Improvement

    After each incident, we:

  • Update security controls to prevent recurrence
  • Enhance monitoring and detection capabilities
  • Revise incident response procedures based on lessons learned
  • Share anonymized findings with security community when appropriate
  • Conduct root cause analysis for systemic issues
  • 10. Contact Information

    To report a security incident or for incident-related inquiries:

    Security incident contact

    Report immediately to support@radrly.com. Acknowledge high-severity reports as quickly as practical during business hours; escalate critical incidents as received.

    11. Policy Review

    This Incident Response Policy is reviewed and updated:

  • Annually as part of regular policy review
  • After significant incidents
  • When new threats or vulnerabilities emerge
  • Following changes to regulatory requirements
  • After incident response drills and exercises