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:
- the systems that hold or move client and customer data: our Cloudflare Workers (one Drive Loyalty service per store, each with its own database and storage), our Google Cloud services (the dashboard, reporting pipeline and data warehouse), and the integrations we connect to merchants' own Shopify, Klaviyo, Meta and Google accounts;
- the credentials that reach those systems;
- the devices and accounts used to operate them.
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
- Merchant account data: store and account identifiers, names, and the connection details needed to run the apps.
- Consumer data: shoppers' email addresses and the loyalty, wishlist and support activity the apps record for them. We keep only the fields each feature needs; reporting data in our warehouse is held as aggregates, not customer contact details.
- Transaction data: order-linked loyalty activity (points earned and redeemed, rewards) and aggregated sales and marketing performance.
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
- Least privilege. Every integration asks only for the permissions its features use. API tokens are scoped to the specific account and resources they need.
- Strong authentication. Every administrative account (Cloudflare, Google, Shopify Partners, Meta, Klaviyo, the password manager) is protected by multi-factor authentication. Hardware security keys (YubiKey) are used where the platform supports them.
- Staff and client access to dashboards goes through Cloudflare Access, with explicit per-client allow lists. Merchants authenticate inside their own Shopify admin. Service-to-service calls use per-store secrets.
- Access reviews. Privileged and administrative access (owner and admin logins, API tokens, service accounts) is reviewed quarterly. Standard user access (client and user allow lists) is reviewed every six months. Access no longer needed is removed at the review, or immediately when a client relationship ends.
4. Secrets and credential management
- Every secret is stored as exactly one item in a dedicated 1Password vault. Systems reference that item, or the deployed platform's encrypted secret store, and copies are not kept. This makes any rotation a single change.
- Secret values are never committed to source control, never printed into logs, and never shared over chat or email.
- A credential register records every secret, where it is used, and how it is rotated. Unattended jobs use a read-only service account whose token is rotated at least every 90 days.
- Repositories and working folders are scanned for exposed secrets (gitleaks and our own sweeps) every quarter. Anything found is rotated as an incident.
5. Application and infrastructure security
- Managed platforms. Production runs on Cloudflare and Google Cloud, which patch and harden the underlying infrastructure. All traffic uses HTTPS/TLS, and data is encrypted at rest by those platforms.
- Isolation. Each Drive Loyalty store runs as its own service with its own database and storage, so a fault or compromise in one store's service cannot reach another's data.
- Web application protections. The services:
- verify every incoming webhook's signature (HMAC);
- validate and bound all input;
- authenticate every admin endpoint;
- apply rate limits and per-store kill switches;
- set strict content security policies;
- use OAuth with PKCE and one-time state for account connections;
- sit behind Cloudflare's network protections and Cloudflare Access.
- Secure development. Every change is reviewed by an independent reviewer before release, with automated test suites and targeted security tests. Releases are logged and can be rolled back. Dependencies are kept to a minimum: the Drive Loyalty service has no third-party runtime packages.
- DNS and email. Our domains use DNSSEC where supported, and our sending domains are authenticated (SPF, DKIM, DMARC).
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.
| Severity | Definition | Remediation target |
|---|---|---|
| Critical | Exploitable, affects an internet-facing service or exposes data or credentials | Within 3 days |
| High | Serious weakness with limited exposure or no known exploitation | Within 14 days |
| Medium / Low | Hardening and defence-in-depth items | At 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
- Automated monitoring alerts the operator to:
- service errors and failures;
- stalled or missing data;
- unhandled data-erasure requests;
- configuration problems reported by each service's own health checks.
- Platform audit logs are kept:
- Cloudflare account and Access logs;
- Google Cloud data-access audit logs for secrets and the database.
- Cloudflare and Google Cloud account alerts cover security-relevant events. Billing alerts flag unexpected usage.
8. Incident response
A written incident response plan (12 September 2026) defines three severity levels.
- Containment: within an hour of a confirmed incident.
- Assessment: the same day.
- Recovery: fix the cause, redeploy and verify.
- Notification, without waiting for the full picture:
- affected merchants;
- Shopify, for any merchant or customer data received through a Shopify app;
- other affected platform partners, including Klaviyo;
- where required, the New Zealand Office of the Privacy Commissioner and affected individuals under the Privacy Act 2020. Australian obligations apply where Australian customers are affected.
Every incident is closed with a timeline, root cause and the changes made.
9. Devices
The operator's work laptop runs:
- full-disk encryption (BitLocker);
- Microsoft Defender anti-malware with real-time and tamper protection;
- the Windows firewall on all network profiles;
- a standard (non-administrator) everyday account;
- a password or Windows Hello login, with automatic screen lock after inactivity.
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:
- Cloudflare (hosting and network);
- Google Cloud (hosting and data warehouse);
- Shopify (the platform our apps run in);
- Klaviyo (the merchant's own email platform);
- Anthropic (AI model for the shopping assistant);
- Resend (transactional email).
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
- Security and privacy: Matthew Wells, matt@quickbyte.digital
- App support: support@onecounter.app
This policy is also available as a PDF on request from matt@quickbyte.digital.