SECURITY / POLICY
Incident Response Policy
How we detect, contain, notify and learn from security incidents.
Last updated: November 7, 2026 · Owner: Data Protection Officer, lin@kolect.ai
What counts as an incident
A security incident is any event that compromises, or may have compromised, the confidentiality, integrity or availability of customer data or our systems. Examples include unauthorized access to an account or server, a leaked credential, data shown to the wrong workspace, loss or corruption of data, and an outage of a production service.
Roles
Incident lead: Lin Shao, Data Protection Officer. Decides severity, coordinates the response, approves external notifications and closes the incident.
Responders: engineers on the team, working under the lead’s direction. They contain, investigate and fix the problem, preserve evidence and write the incident record.
Reporting
Staff who notice a possible incident report it immediately in the team’s internal operations channel and directly to the Data Protection Officer. Automated health checks, watchdogs and release smoke tests post alerts to the same channel. Customers, creators, platform partners and researchers can report to lin@kolect.ai or hello@kolect.ai.
Response steps
- Detect and report through the channels above.
- Assess scope and severity: which systems, workspaces and data, and whether personal data is involved.
- Contain, for example by rolling back the release, turning off the affected feature, revoking and rotating exposed credentials, or removing access.
- Eradicate and recover: fix the root cause through the normal reviewed change process, restore data if needed and confirm normal operation.
- Notify as described below.
- Learn: write an incident record covering the timeline, impact, root cause, fix and prevention and, where worthwhile, add a regression test or automated check.
Notification
If an incident involves unauthorized access to, or disclosure of, customer personal data or platform data, we notify affected customers and the relevant platform partner, such as TikTok Shop, Meta, Shopify or Google, without undue delay and no later than 72 hours after we confirm it, or sooner where the platform’s agreement requires. Notifications state what happened, what data was affected, what we have done and what the recipient should do. We notify regulators and individuals where applicable law requires it.
Records and review
Incident records are kept for at least three years. The Data Protection Officer reviews this policy at least once a year and after significant incidents or changes.