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 dataComplete service outage affecting all usersActive security breach or ongoing attackUnauthorized access to production systemsRansomware or malware infectionResponse: 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 investigationPartial service degradation affecting multiple usersDetection of vulnerability being actively exploitedSuspicious authentication patterns or access attemptsResponse: 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 exploitedMinor service disruption affecting limited usersPolicy violations without data exposureFailed intrusion attemptsResponse: 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 monitoringMinor configuration issuesInformational security alertsResponse 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.comIncident lead: support@radrly.comPrivacy / DPA contact: hello@costradar.aiLegal inquiries: hello@costradar.ai4. Incident Response Process
Detection and Reporting
Security incidents may be detected through:
Application and infrastructure monitoring / alertingUser reports of suspicious activityThird-party security researchersPeriodic security reviewsAll 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 classificationActivate appropriate incident response team membersBegin incident documentation and timelineEstablish communication channels for incident responseContainment
Immediate actions to limit incident scope and impact:
Short-term containment: Isolate affected systems, block malicious IP addresses, disable compromised accountsEvidence preservation: Take system snapshots, collect logs, document system stateLong-term containment: Apply security patches, change credentials, implement additional monitoringUser impact mitigation: Implement workarounds, provide status updatesInvestigation and Analysis
Detailed analysis to understand the incident:
Determine root cause and attack vectorIdentify affected systems and dataAssess scope of data exposure or compromiseReview access logs and security eventsIdentify indicators of compromise (IoCs)Document findings and evidence chainEradication
Remove the threat and address vulnerabilities:
Remove malware or unauthorized accessClose exploited vulnerabilitiesApply security patches and updatesStrengthen security controlsValidate eradication through testingRecovery
Restore normal operations:
Restore affected systems from clean backups if neededReset passwords and regenerate access tokensRe-enable services in controlled mannerImplement enhanced monitoringVerify system integrity and functionalityGradually restore user accessPost-Incident Review
Conducted within 5 business days of incident resolution:
Document lessons learnedIdentify areas for improvementUpdate security controls and proceduresImplement preventive measuresUpdate incident response plan as neededShare findings with relevant teams5. Notification Requirements
5.1 User Notification
For personal data breaches affecting users:
Timing: Without undue delay, within 72 hours of breach discoveryMethod: Email to affected users' registered email addressesContent: Nature of breach, types of data affected, likely consequences, measures taken, contact informationThreshold: All breaches likely to result in risk to user rights and freedoms5.2 Regulatory Notification
Required notifications to data protection authorities:
GDPR: Within 72 hours to relevant supervisory authorityCCPA: As required by California lawShopify: Notify Shopify as required for incidents affecting Shopify app/store dataAmazon Solution Provider Portal: Incident management point of contact is hello@costradar.ai; notify Amazon as required for SP-API / selling-partner data incidentsAmazon / WooCommerce: Notify affected platform partners or merchants as contracts/law requireOther jurisdictions: As required by applicable laws5.3 Internal Notification
Executive team notified within 1 hour for P1/P2 incidentsAll team members briefed on need-to-know basisRegular status updates during incident responsePost-incident report distributed to all stakeholders6. 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 subjectsLikelihood and severity of harm to individualsWhether data was encrypted or otherwise protectedWho gained unauthorized access and their intentionsWhether exposed data has been recovered or contained6.2 User Protection Measures
Following a data breach, we may:
Force password resets for affected accountsInvalidate all active session tokensRevoke OAuth tokens for third-party integrationsProvide credit monitoring services (if financial data exposed)Offer identity theft protection servicesImplement additional account security features7. Documentation and Record Keeping
All incidents are documented with:
Incident timeline with all key eventsAffected systems and data inventoryActions taken at each response phaseCommunications sent to users and authoritiesEvidence collected and analysis performedPost-incident review findingsIncident 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 recurrenceEnhance monitoring and detection capabilitiesRevise incident response procedures based on lessons learnedShare anonymized findings with security community when appropriateConduct root cause analysis for systemic issues10. 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 reviewAfter significant incidentsWhen new threats or vulnerabilities emergeFollowing changes to regulatory requirementsAfter incident response drills and exercises