One Counter

Information Security Policy

quickByte digital (Matthew Wells trading as quickByte digital), maker of One Counter

Version 1.0, 29 October 2026

One Counter is made and operated by quickByte digital (Matthew Wells trading as quickByte digital), NZBN 9429053695291, Wellington, New Zealand.

1. Purpose and scope

This policy sets out how quickByte digital protects the data it handles. quickByte digital (Matthew Wells trading as quickByte digital, NZBN 9429053695291, Wellington, New Zealand) builds and operates the One Counter apps for Shopify (One Counter: Drive Loyalty and One Counter: Dashboard) and runs marketing reporting for retail clients.

It covers:

quickByte digital has one operator, Matthew Wells, who owns this policy and is accountable for it. The policy is written for that reality and only commits to what one person can reliably keep. It is reviewed at least once a year and whenever the business or its systems change materially.

2. Data we handle

Data is used only to provide the services to the merchant that connected it. It is never sold, and never combined across merchants. Retention and deletion follow our Privacy Policy and the platforms' rules, including Shopify's data-erasure requests, which we honour within 30 days.

3. Access control

4. Secrets and credential management

5. Application and infrastructure security

6. Vulnerability management and patching

Vulnerabilities are found through security advisories for the platforms and libraries we use, our quarterly reviews and sweeps, the independent review of every change, and reports from clients or platform partners.

SeverityDefinitionRemediation target
CriticalExploitable, affects an internet-facing service or exposes data or credentialsWithin 3 days
HighSerious weakness with limited exposure or no known exploitationWithin 14 days
Medium / LowHardening and defence-in-depth itemsAt the next quarterly maintenance

A critical issue that cannot be fully fixed within 3 days is contained within that time (for example by switching off the affected feature or revoking the affected credential) until it is fixed.

7. Monitoring and detection

8. Incident response

A written incident response plan (12 September 2026) defines three severity levels.

Every incident is closed with a timeline, root cause and the changes made.

9. Devices

The operator's work laptop runs:

Production credentials are held in the password manager, not on disk in plain text.

10. Third parties

We rely on established providers, chosen for their security programmes:

Each processes data only to provide its part of the service. They are listed in our Privacy Policy.

11. Business continuity

Merchants keep full ownership of their Shopify, Klaviyo, Meta and Google accounts and can disconnect our apps or revoke access at any time without our involvement. Source code is held in version control, configuration is reproducible from it, and credentials can be re-issued from the vault. Encrypted backups of configuration are refreshed quarterly.

12. Contacts

This policy is also available as a PDF on request from matt@quickbyte.digital.