Security Incident Response Policy

Last reviewed: October 10, 2026

1. Purpose and Scope

This policy explains what Quaffable ("we," "our," or "us") does when personal data or customer data in our platform may be at risk, and when we will tell the people affected.

It covers any suspected or confirmed unauthorised access to, or loss or disclosure of, personal data or customer data held in Quaffable (a "security incident"). That includes data we receive from Shopify stores, payment data handled through Stripe, and data stored with our hosting provider (Heroku).

Our customers are the businesses that use Quaffable. Each customer controls the data of its own members and buyers, and Quaffable processes that data on the customer's behalf. This policy describes how we protect that data and how we keep customers informed.

2. Roles and Reporting

  • Incident lead: Thomas Sinclair (Founder) is responsible for running our response to any security incident.
  • Reporting an incident: anyone who suspects a security incident involving Quaffable, including customers, members, researchers and our own team, should email security@quaffable.app. This mailbox is monitored, and reports are acknowledged as soon as possible.

3. How We Respond

  1. Detect and report: suspected incidents are reported to the incident lead straight away, whether they come from monitoring, our team, a customer, a provider or an outside report.
  2. Assess: within 24 hours we assess how serious the incident is, what data and which customers are affected, and whether it is still happening.
  3. Contain: we stop further access, for example by rotating credentials and API tokens, revoking sessions, and blocking accounts or addresses involved.
  4. Fix: we find and fix the underlying cause.
  5. Recover: where data has been lost or damaged, we restore it from backups.
  6. Review: after the incident we review what happened and what we changed, and update our safeguards and this policy where needed.

4. Who We Notify, and When

  • Affected customers: without undue delay, and within 72 hours of confirming that an incident affects their data. We will tell them what happened, what data is involved, what we have done, and what they should do.
  • Shopify: when Shopify merchant or customer data is involved, we notify Shopify immediately, and no later than 24 hours after becoming aware of an actual or suspected breach, as required by the Shopify API License and Terms of Use and the Shopify Partner Program Agreement. We keep Shopify updated as our investigation progresses.
  • Regulators: we assess suspected breaches under the Notifiable Data Breaches scheme in the Privacy Act 1988 (Cth) within 30 days, and notify the Office of the Australian Information Commissioner (OAIC) where a breach is likely to result in serious harm. Where the GDPR applies, we give the customer what it needs to notify its supervisory authority within 72 hours.
  • Affected individuals: where the law requires it, we notify affected individuals directly or through the relevant customer.

5. Records

We keep a log of every security incident, including the facts, the data affected, the decisions we made and the notices we sent. This includes incidents that turn out not to be notifiable.

6. Policy Review

We review this policy at least once a year and after every security incident. The date at the top of this page shows when it was last reviewed.

7. Contact Us

To report a security incident, email security@quaffable.app. For anything else, including questions about how we handle personal data, see our Privacy Policy or contact us:

Email: gday@quaffable.app
Location: Tasmania, Australia

Think something's wrong?