Security and data protection

How Live Shoppers protects the shopper data it handles for stores, and what we do if something goes wrong. Last updated 4 November 2026.

Only what is needed

We record the events listed on the privacy page and nothing else: no IP addresses of shoppers, no checkout emails, phone numbers, addresses or payment details. Customer names are shown in the live view; only the first name and last initial are written to disk.

Encryption

In transit: every connection (the storefront pixel, the app inside Shopify admin, Shopify's API and webhooks) uses HTTPS.
At rest: data lives on Railway, which encrypts all stored data, including volumes and their backups, with AES-256.

Access

A store's staff see only their own store, through Shopify's signed session tokens. Requests are checked against the store's app before any data is returned.
Operator access is limited to the owner, through a secret admin key, and is used only for setup and support.
Operator accounts (hosting, Shopify Partners, email) use unique strong passwords and two-step verification.
Every request that can read shopper data is logged (who, which store, what, when; never the data itself). The log is kept for 14 months.

Separate test and live data

Test stores have their own records and test-mode billing. Test data never mixes with a live store's data.

Keeping, backing up and deleting

Events are kept for up to 400 days and then deleted automatically.
The data volume is backed up daily and weekly by Railway (encrypted). Backups expire on Railway's schedule (daily 6 days, weekly 27 days).
Shopify's privacy webhooks are honoured: a customer redact removes that customer's id and name; a shop redact deletes everything recorded for the store.

If something goes wrong

Contain: rotate the affected secrets (app secret, admin key, hosting token) and revoke store access tokens if needed.
Assess: use the access log and hosting logs to find what was reached, which stores, and when.
Notify: tell every affected store and Shopify within 72 hours, with what happened and what they should do.
Fix and review: close the cause, restore from backup if data was lost, and write down what changed.

Report a security problem to adam@inlinex.com.sg.