Security incident response
How Codexta handles events that threaten the confidentiality, integrity or availability of merchants' and shoppers' data, and what merchants can expect to be told. Last updated 14 November 2026.
Purpose: handle events that threaten the confidentiality, integrity or availability of merchants' or shoppers' data in Codexta, including the customer data of Shopify and WooCommerce shops, and meet the duty to tell merchants and Shopify.
1. Severity scale
| Sev | Meaning | Examples | Merchant notice | Target response |
|---|---|---|---|---|
| 1 Critical | Confirmed or likely unauthorised access, disclosure, loss or alteration of personal data, or a cross-tenant leak | One shop's conversations readable by another; a leaked database or backup; a stolen platform token or staff access credential in use; a leaked service key abused for data access | Yes, within 72 hours of becoming aware (see the DPA); Shopify too | Start at once, at any hour, through the incident lead and the out-of-hours contact in section 3 |
| 2 High | Weakness exploitable now with personal data in reach, or an incident without proven data exposure | A staff account compromised without confirmed data access; a webhook signature check bypass found; a tenant separation misconfiguration found | Decide within 24 h with the owner; notify if data may be affected | Same working day |
| 3 Medium | Contained control failure, no sign of data exposure | Unmasked reveal without a matching business reason; a failed retention job; an expired certificate | Usually no | 3 working days |
| 4 Low | Hygiene or near miss | Bursts of failed logins; an unused secret found in a file | No | Backlog |
When unsure between two levels, take the higher.
2. Roles
| Role | Does | Who |
|---|---|---|
| Incident lead | Declares the incident and its severity, owns the timeline and decisions | Amel Music (amel.music@kodecta.com) |
| Technical responder | Investigates, contains, collects evidence | The incident lead or the deputy |
| Communications and data protection contact | Writes merchant, Shopify and authority notices, keeps the register | The incident lead or the deputy; mailbox codexta@codecta.com |
| Executive owner | Approves notifications and external statements | The incident lead |
| Deputy for each role | Covers absence | Emir Causevic, deputy for the incident lead |
3. Detection
What exists today:
- Application and proxy logs, kept centrally for one month.
- An append-only audit record of every Codexta staff action on a shop (acting inside a shop, revealing unmasked text, retrying webhooks, uninstalling, purging, running jobs, and similar). The database refuses updates and deletes of these rows, and the merchant can read the entries for its own shop.
- A tamper-evident conversation history: each conversation entry is chained to the one before it, so altering a history breaks the chain.
- Startup checks that refuse to start a production host carrying test-only secrets.
- Per-tenant and per-session rate limits, and records of received webhooks with attempt counts.
- Reports from merchants, from Shopify or from a shopper to codexta@codecta.com.
Centralised logging with alerting is in place. The individual alert rules are not listed here, and alerts on anomalous staff reveals, failed logins or cross-tenant errors are not claimed.
Anyone who suspects an incident tells the incident lead at once, by email to amel.music@kodecta.com or codexta@codecta.com. The out-of-hours contact is Amel Music, amel.music@kodecta.com. No telephone number is published.
4. Escalation path
- The reporter tells the incident lead (any time).
- The incident lead opens an incident record (date, reporter, what was seen), sets a provisional severity, and pulls in the technical responder.
- Sev 1 and 2: the lead tells the executive owner and the communications contact within 1 hour of triage.
- The communications contact starts the notice clock from the moment Codexta became aware, and writes that time down.
5. Evidence collection
Done before containment changes the evidence, where possible.
- Record times in UTC and keep everything read-only: copy, do not edit.
- Export the application logs for the window.
- Export the staff audit rows for the affected shop and for the staff account in question.
- Snapshot the affected data from a database copy, not the live one.
- Verify the chain of the affected conversations.
- Keep the web proxy access logs. They are retained for one month, so export the window before it expires.
- Note every command run. Do not paste secrets into the incident record.
6. Containment
Choose the smallest step that stops the harm; record each step and its time.
- Revoke staff access grants for a shop; disable the staff account.
- Rotate the secrets involved: the key that protects stored credentials (and re-encrypt them), model provider keys, platform app secrets, shop keys and signing secrets.
- Revoke the affected shop's platform token and reconnect it.
- Suspend or uninstall the tenant where continued service is the risk. A purge waits for the 48-hour retention period or an explicit confirmation.
- Use the kill switches for the Meta channels and profile updates.
- If a model provider is implicated, switch the default and fallback model to another provider.
- Block abusive addresses at the web proxy.
- Do not delete evidence, conversations or logs until the incident lead says so. The nightly retention job deletes expired conversations on schedule; the incident lead can have engineering suspend it for the duration of an investigation.
7. Notification
Merchants
If personal data of a merchant's shoppers or staff may be affected, Codexta notifies that merchant's account contact without undue delay and within 72 hours of becoming aware. The notice says what happened, when, which data and shops, what Codexta has done, what the merchant should do, and who to contact. Merchants are reached at the contact on the shop's Codexta account: the shop's owners and admins who have an email address on their Codexta member record, the same addresses that receive Codexta's service alerts. If a shop has no such address on file, no notice is sent by email, because there is nowhere to send it; merchants are asked to keep an owner or admin email address on their member record.
Shopify
If protected customer data is involved, Codexta tells Shopify without delay through the Shopify Partner Dashboard contact and as the Partner Program Agreement requires.
Authorities and shoppers
The merchant, as controller, decides and notifies; Codexta helps. For data where Codexta is itself controller (the merchant account), the communications contact decides. The competent supervisory authority for Kodecta d.o.o. is the Agency for Personal Data Protection in Bosnia and Herzegovina (Agencija za zaštitu ličnih podataka u BiH), Dubrovačka 6, 71000 Sarajevo, www.azlp.ba. A merchant established in the EU also has its own supervisory authority.
A copy of every notice is kept in the incident record.
8. Recovery
Restore service from a clean state, confirm tenant separation with a test shop, re-run the nightly jobs once (which writes an audit row), and watch the logs for repeat activity.
9. Post-mortem
Within 10 working days of closing a Sev 1 or 2, blameless:
- timeline, root cause, what detected it, what slowed us;
- data affected and who was told, with times;
- fixes with owners and dates, tracked to done;
- changes to this policy, the security statement and the DPA if a claim there was wrong.
10. Register and testing
Codexta keeps one register of all incidents and near misses (date, severity, summary, notices sent, actions). The register is kept by the incident lead. A tabletop exercise is run at least once a year, using a scenario such as a staff reveal being abused or a model key leaking.