AppVerix Order Edit: Privacy Policy

Last updated: 19 October 2026

AppVerix Order Edit (“the app”) is published by AppVerix (“we”, “us”). This policy explains what the app collects when a merchant installs it, why, where it is kept and how to have it deleted.

For personal data of a store’s customers (shipping addresses and order identifiers in the edit log), the merchant is the controller and we are the processor.

1. What we collect and why

From the merchant’s store, through the Admin API:

  • Shop domain: to identify the store and open the app in the admin. Stored.
  • An access token: so the app stays installed and can edit orders. Stored in the login session until you uninstall.
  • Rules: window, allowed edits, excluded products and tags. Stored.
  • Order identifiers and the shipping address / line snapshots needed to apply an edit and to show the merchant log. Stored.
  • Signed edit-link tokens and their expiry. Stored.
  • Billing state from the platform (plan active, trial or none). Stored as a cache.
  • Compliance log: topic and identifiers from a privacy webhook, never names or emails from the payload.

2. What we do not collect

We do not store payment card numbers, passwords, or a customer’s full email in the edit log (the customer page shows a masked email when the order has one). Phone numbers from a privacy webhook are discarded. We set no advertising cookies and use no analytics pixels.

3. Who processes data for us

Where data leaves the EEA/UK, we rely on the provider’s Standard Contractual Clauses or other approved transfer mechanisms.

  • Cloudflare (cloudflare.com): hosting and the D1 database. Sees everything in section 1. Globally distributed.
  • The commerce platform the app runs on, which also handles billing.

4. How long we keep it

  • Rules, links and the edit log: while the app is installed.
  • When you uninstall: we delete the login session right away. A shop/redact request about 48 hours later deletes the store’s rules, links, logs and shop row.
  • A customer deletion request (customers/redact): we delete that customer’s edit-log rows.
  • Server logs: up to 7 days, without personal data.

5. Your rights and data requests

The app answers the three privacy webhooks: customers/data_request (we log that it arrived and can list that customer’s edit-log identifiers), customers/redact (we delete those rows) and shop/redact (we delete the store).

Merchants can write to support@appverix.com for a copy of their data or to have it deleted. We answer within 30 days. A store’s customers should contact the store first. If you are in the EEA/UK you may complain to your local data protection authority. In Brazil the LGPD applies.

6. Security

  • All traffic uses HTTPS (TLS).
  • The database runs on Cloudflare D1, which encrypts data at rest.
  • Webhooks are verified by HMAC; unsigned requests are rejected.
  • Customer email links are HMAC-signed and expire with the window.
  • The admin checks a session token on every request and uses no third-party cookies.

7. Data processing agreement and security

The AppVerix Data Processing Addendum sets out our commitments, and our security and incident response policy describes how we protect data.

8. Changes and contact

If we change this policy in a way that matters, we update the date at the top. Contact: support@appverix.com