HaloTrack — Security and incident response

Team: HaloTrack is run by one developer, the only person with access to production. Policy: every account used to run the app (Cloudflare, Shopify Partners, GitHub, email) has a unique password of at least 12 characters kept in a password manager, and two-factor authentication.

Infrastructure: Cloudflare Workers and D1. Data is encrypted in transit (TLS) and at rest, including D1 point-in-time backups. Shopify access tokens are additionally encrypted with AES-256-GCM.

Test and production: development and automated tests use local emulators with synthetic data and a separate Shopify development store. Production data is never copied into test environments.

Access logging: every access to shop data (merchant admin, storefront lookup, Shopify webhook) is logged with time, shop, route and result — no customer data — and kept for 90 days. Administrative changes are recorded in Cloudflare's account audit log.

Data loss prevention: we store no customer personal data, the order email is never written to storage or logs, secrets live only in encrypted Worker secrets, and storefront lookups are rate-limited.

Incident response: 1) contain — rotate secrets, revoke tokens, disable affected routes; 2) assess scope from the logs; 3) notify affected merchants within 72 hours, and Shopify and authorities where required; 4) fix and record the root cause; 5) review this policy. Report security issues to support@addsum.top.

Privacy · DPA · Security

✉ support@addsum.top

2026-10-31