Security and data protection
Effective date: 20 October 2026
This page describes how Parcel Rules, operated by Artie Codes Pty Ltd (Australia), secures the limited data it handles, how we guard against data loss, and how we respond if a security incident occurs. It is written to sit alongside our privacy policy.
Our data footprint
Our security posture starts from how little data we hold. Parcel Rules does not store your customers' personal information. Shipping and delivery rules run inside Shopify Functions on Shopify's own infrastructure, where the delivery address (country, province or state, and postcode) is read transiently to evaluate a rule and is never stored, logged, or sent to our servers. The only data we retain is the session and authentication data needed to connect to your store, plus your app configuration, which lives in Shopify-owned metafields. Because we store no customer personal data, the attack surface for that data is effectively nil.
Data loss prevention
Our data loss prevention strategy is built on minimisation first, then protection of the little that remains:
- Minimisation. We collect and keep the smallest amount of data needed to run the app. Customer personal data is processed transiently and never persisted, so it cannot be lost from our systems.
- Managed, encrypted storage. Session and configuration data is held on Fly.io in the Sydney (Australia) region, on volumes encrypted at rest. Traffic to and from the app is encrypted in transit over TLS/HTTPS.
- Backups. We rely on Fly.io's managed volume snapshots, which are encrypted at rest. Backups are retained only as long as needed for recovery.
- Environment separation. Development and testing are performed against separate development stores and are isolated from production data and credentials.
- Secret management. API keys and tokens are stored as managed secrets (Fly.io secrets), never committed to source control.
- Monitoring. Operational logs (which contain no customer personal information) are sent to Better Stack so we can detect errors and anomalies early.
- Deletion. Session data is deleted on uninstall, and we honour Shopify's privacy webhooks (
customers/data_request,customers/redact,shop/redact).
Encryption and access
- Data is encrypted in transit (TLS/HTTPS) and at rest (encrypted Fly.io volumes).
- Backups and snapshots are encrypted at rest.
- Access to production systems is limited to the operator and protected by strong, unique passwords and two-factor authentication on the underlying accounts (Shopify Partners, Fly.io, and source control).
- Because no customer personal data is stored, there is no standing access to customer personal data to grant or log.
Security incident response policy
A security incident is any event that compromises, or is reasonably suspected to compromise, the confidentiality, integrity, or availability of data handled by Parcel Rules. We follow these steps:
- Detect and record. Incidents may be identified through monitoring and alerts (Better Stack), reports from merchants, Shopify, or third parties, or our own review. On discovery, we record the time, nature, and scope of the incident.
- Contain. We take immediate steps to limit impact, for example rotating credentials and tokens, revoking access, isolating affected components, or taking the affected service offline.
- Assess. We determine what data, systems, and stores were affected and whether any personal data was involved. Given our footprint, most incidents will involve session or configuration data rather than customer personal data.
- Notify. If an incident affects data belonging to a merchant or their customers, we notify Shopify and the affected merchants without undue delay, and in any case within 24 hours of confirming the incident. Where the Australian Privacy Act Notifiable Data Breaches scheme applies, we also notify the Office of the Australian Information Commissioner (OAIC) and affected individuals as required by law.
- Remediate. We fix the root cause, restore affected services from clean backups where needed, and verify the issue is resolved.
- Review. After resolution we conduct a post-incident review and update our controls and this policy to reduce the chance of recurrence.
To report a suspected security issue, email support@artie.codes. We aim to acknowledge reports within one business day.
Changes to this policy
We may update this page from time to time. Material changes will be reflected by a new effective date at the top of the page.
Contact
- Security: support@artie.codes
- Privacy: support@artie.codes
- Operator: Artie Codes Pty Ltd, Australia