Security Incident Response Policy
Last updated: November 8, 2026
This policy explains how Loger Labs (“Loger,” “we,” “us”) finds, contains, investigates and reports security incidents affecting the Loger Shopify app, our website, and the data they handle. It sits alongside our Privacy Policy and applies to everyone who works on Loger.
1. What this covers
Systems. The Loger embedded app and its APIs, the loger.io website, the database and storage behind them, the hosting they run on, the secrets and tokens they use, and the accounts that control all of these (code hosting, hosting, database, Shopify Partner, Google and Meta developer accounts, email).
Data. Merchant account details, store and catalog content, order financials, Shopify customer numbers (Loger does not store customer names, email addresses, phone numbers or postal addresses; see Section 3.7 of the Privacy Policy), advertising performance data, and the access tokens that let Loger read a merchant’s Shopify, Google and Meta accounts.
A security incident is any event that has, or may have, compromised the confidentiality, integrity or availability of that data or those systems. Examples: someone reading data they should not; a stolen or leaked key, token or password; malicious code reaching our software or a dependency; a vulnerability being actively exploited; data deleted or altered without authority; a provider telling us it was breached.
2. Who does what
| Role | Responsibility |
|---|---|
| Incident lead | Loger’s founder. Decides severity, directs the response, makes the notification decisions in Section 5, and signs off the review. If the incident lead is unavailable or involved, the next most senior person at Loger takes over. |
| Everyone at Loger | Reports anything suspicious at once, to the incident lead, and does not try to hide, delete or “quietly fix” it. |
Outside contractors and subprocessors that touch Loger data are required to tell us promptly of any incident on their side.
3. How we find out
- Monitoring: server and browser error reporting, hosting and database logs, and the alerts and notices that Shopify, Google, Meta and our providers send us.
- Reports from others: merchants, researchers or anyone else who writes to support@loger.io with the word “Security” in the subject. We acknowledge every report within one business day. We welcome good-faith research and will not take action against anyone who reports a vulnerability responsibly, avoids reading or changing other people’s data beyond what is needed to show the problem, and gives us reasonable time to fix it.
- Our own review: unusual activity found while doing other work is treated as an incident until shown otherwise.
4. Response steps
1. Triage (start immediately, finish within the first working day). Open an incident record with the time, who found it and what was seen. Decide what happened, which systems and which merchants may be affected, and set a severity:
| Severity | Meaning | Examples |
|---|---|---|
| Critical | Confirmed or likely access to personal data, tokens or credentials by someone unauthorised, or an attacker in control of production. | A leaked database key; a merchant’s Shopify token used by someone else; code changed in production without our knowledge. |
| High | A serious weakness that can be exploited, with no evidence yet that it was. | A route that returns another store’s data; a secret committed to a public place. |
| Medium | A weakness with limited reach, or an incident with no personal data involved. | An outage caused by an attack; a vulnerable dependency that is not reachable. |
| Low | A minor issue or a false alarm worth recording. | A failed probing attempt that was blocked. |
2. Contain (Critical and High: begin at once). Stop the harm before understanding all of it. Depending on the incident:
- revoke and replace the affected secret: the database service key, the Shopify app secret, the key that seals stored access tokens, the scheduled-job secret, and any Google or Meta credentials;
- revoke merchants’ access tokens that may be exposed, so Shopify, Google or Meta access has to be granted again;
- switch off or remove the affected route or feature, and pause automated advertising actions with the Sell kill switch where they could be misused;
- remove the attacker’s access (sessions, accounts, deploy keys) and lock the accounts involved.
Keep evidence: do not delete logs, and copy the relevant ones to a safe place before anything rotates out.
3. Investigate. Work out how it happened, since when, what data and which merchants were reached, and whether the activity has stopped. Where the logs cannot say, we assume the wider possibility and say so when we report.
4. Fix and recover. Remove the cause, restore from clean sources if anything was altered, confirm the fix, and watch for a repeat. Restore service as soon as it is safe, not before.
5. Notify as set out in Section 5.
6. Review as set out in Section 6.
5. Who we tell, and when
When we confirm that personal data or access credentials were, or may have been, exposed:
- Affected merchants: without undue delay, and no later than 72 hours after we confirm it, by email to the address on the Loger account.
- Shopify: at the same time, through Shopify Partner support, as Shopify requires of apps. If the incident involves data that came through Shopify, we follow Shopify’s instructions for the merchants concerned.
- Google and Meta: if their data or their credentials are involved, through their developer channels.
- The supervisory authority: where the law requires, the Swedish Authority for Privacy Protection (IMY), within 72 hours of becoming aware of a personal data breach.
- Customers of a store: where the law requires it, we give the merchant what they need to tell their customers, since the merchant is the one in touch with them.
A notice says, in plain words: what happened and when; which data and which stores were involved; what we have done; what the merchant should do, if anything (for example reconnecting an account or changing a password); and how to reach us. We tell people what we know and what we do not yet know, and we send updates as it changes. We do not wait for a full investigation to give a first notice.
6. After an incident
Within 14 days of closing a Critical or High incident, and sooner where practical, we write a short review: the timeline, the cause, what worked, what did not, and the changes we will make. Those changes are tracked to completion. Where the lessons change how we handle data, we update the Privacy Policy and this policy.
We keep the incident record, the evidence and the review for at least three years.
7. Keeping this policy working
- We review this policy at least once a year and after every Critical or High incident.
- We keep the means to respond ready: access to the accounts and secrets listed in Section 4, a current list of the providers in Appendix A of the Privacy Policy, and the contact routes to Shopify, Google and Meta.
- Everyone with access to production systems protects their accounts with strong, unique passwords and two-step sign-in.
8. Contact
To report a security issue, or to ask about this policy: support@loger.io (subject: “Security”).
Loger Labs, Djupedalsvägen 27, 54136 Skövde, Sweden.