Security Incident Response Policy
How we find, contain, report and learn from security incidents, and who we tell, how quickly.
This policy sets out how ZAZENTAX LTD ("Zazen Tax", "we", "us") finds, contains, reports and learns from security incidents affecting zazentax.com, My Account (account.zazentax.com), Zazen Optimise, Zazen Sync and the data our clients connect to them. It applies to everyone who works for us, including contractors.
1What counts as an incident
A security incident is any event that puts the confidentiality, integrity or availability of our systems or the data in them at risk. Examples:
- Someone gets into a client's data, a staff account or a production system without permission.
- A password, access token, API key or other secret is exposed, lost or stolen.
- Data from a connected platform (for example Shopify, Amazon, Google, Meta or Xero) is read, changed, deleted or sent somewhere it should not go.
- Malware is found in an uploaded document or on a device used for work.
- A device holding work data is lost or stolen.
- A service provider we use tells us it has had a breach affecting our data.
A personal data breach is an incident that leads to personal data being lost, destroyed, changed, disclosed or accessed without authority. We treat a suspected incident as real until we have shown otherwise.
2Roles
- Incident lead: a director of ZAZENTAX LTD. Decides severity, runs the response, makes the notifications in section 5 and signs off the closing review.
- Compliance lead: advises on data protection law, decides with the incident lead whether the Information Commissioner's Office and individuals must be told, and keeps the breach record.
- Everyone else: reports anything suspicious straight away (section 3) and follows the incident lead's instructions. Nobody investigates on their own, deletes evidence or talks about an incident outside the response team.
If the incident lead cannot be reached within one hour, the compliance lead takes over.
3Reporting an incident
- Staff: tell the incident lead at once, by phone or in person, then confirm in writing.
- Clients, researchers and anyone else: email privacy@zazentax.com with what you saw and when. We acknowledge reports within one working day.
The clock for every deadline in section 5 starts when we first become aware of a likely incident, not when the investigation ends.
4How we respond
- Record. Open an entry in the incident log: time found, who found it, what is known.
- Assess. Decide what systems and data are affected, which clients and platforms are involved, whether personal data is involved, and how serious the risk to people is.
- Contain. Stop the damage. Depending on the incident: rotate the exposed secret, revoke and delete affected platform access tokens, disconnect the affected integration, suspend the affected account, block the source, or take the affected service offline.
- Preserve evidence. Keep the audit log, sign-in records and cloud provider logs for the period involved before anything is changed or restored.
- Notify. Make the notifications in section 5 within their deadlines, even if some facts are still unknown, and send updates as we learn more.
- Recover. Restore from clean backups where needed, check data is complete and correct, and bring services back only when the cause is fixed.
- Review. Within 14 days of closing, write up what happened, why, and what we are changing so it does not happen again.
5Who we tell and when
| Who | When | Deadline | How |
|---|---|---|---|
| Affected clients | Any incident affecting their data or accounts | Without undue delay, and within 48 hours of becoming aware (as our Data Processing Agreement promises) | Email to the client's account contacts |
| Information Commissioner's Office | A personal data breach where we are the controller, unless it is unlikely to result in a risk to people | Within 72 hours of becoming aware | ico.org.uk report a breach |
| Affected individuals | A breach likely to result in a high risk to them, where we are the controller. Where we act for a client, the client decides and we help | Without undue delay | Email or the most direct channel available |
| Amazon | Any incident involving Amazon information or our Selling Partner API access | Within 24 hours of detection | security@amazon.com |
| Shopify | Any actual or suspected breach of merchant data or our app credentials | Within 24 hours of becoming aware | partner-security-reports@shopify.com and Shopify Partner Support |
| Xero | Any incident involving Xero data or our Xero app credentials | Immediately | api@xero.com |
| Meta, Google, Intuit, Etsy, PayPal, Pinterest, TikTok, Snapchat, X and other connected platforms | Any incident involving their data or our credentials for their platform | As soon as possible, and within any deadline in that platform's terms | The channel set out in that platform's developer terms |
| Police and Action Fraud | Where a crime is suspected | As soon as practical | actionfraud.police.uk |
Notices say what happened, when, what data and how many people are likely affected, the likely consequences, what we have done and what the recipient should do. Where facts are not yet known we say so and follow up.
6Severity
| Level | Meaning | Response |
|---|---|---|
| High | Personal data or client data exposed, a production system or staff account taken over, or a platform credential exposed | Incident lead engaged at once, containment the same day, all section 5 notifications assessed immediately |
| Medium | A weakness that could expose data but no sign it has been used, or a service outage affecting clients | Fixed within 2 working days; clients told if their service is affected |
| Low | A near miss or minor policy breach with no data at risk | Logged and fixed in normal work |
7Records
We keep a record of every incident, including ones we did not have to report: the facts, its effects, the decisions taken and why, the notifications made, and the closing review. Records are kept for at least 6 years and are available to the Information Commissioner's Office on request.
8Safeguards that support this policy
- Every sign-in, invitation, role change and platform connection is written to an audit log.
- Staff must use an authenticator app code every time they sign in.
- Access tokens and keys for connected platforms are encrypted with our own key and can be revoked and deleted per client.
- Secrets are kept in a secret store, never in code, and can be rotated without a release.
- Database backups are encrypted and kept for no more than 35 days, so a clean copy can be restored.
- Uploaded documents are scanned for malware and stored privately with public access blocked.
9Testing and review
We rehearse this policy at least once a year with a practice incident, and review it after every high-severity incident and whenever our systems, providers or platform terms change. The date of the last review is at the top of this page.
10Contact
To report a security concern, email privacy@zazentax.com, or write to ZAZENTAX LTD, 128 City Road, London EC1V 2NX.