Data Safety
ArrayHash separates website, analytics, payment and licensing data from merchant WordPress and WooCommerce data. ArraySubs does not transmit store metrics to ArrayHash.
- Website forms collect name, country and email
- Plugin data stays on the merchant site
- Payment and licensing providers handle purchase flows
- Effective date
- April 10, 2026
- Last reviewed
- June 7, 2026
- Analytics
- Always-on GA4/GTM
- Payment providers
- Payment and licensing providers
Two data contexts
ArrayHash website data and merchant WordPress store data are not the same thing.
ArrayHash website
The website collects the fields needed for signup, license request, newsletter, support and contact forms. GA4/GTM analytics loads on every visit as necessary measurement, and retargeting loads only after the visitor opts in. Payment and licensing providers process checkout, license and transaction workflows.
Merchant WordPress site
ArraySubs runs inside the merchant's own WordPress and WooCommerce installation. Store customer data, order data, subscription data, user accounts, logs and business metrics stay in the merchant's environment unless the merchant sends information to ArrayHash manually.
Website data map
| Data | Collected | Purpose |
|---|---|---|
| Name, email, country, business type, subject, message body and optional product-update consent | Yes | Signup, license request, newsletter, support and contact workflows. |
| GA4 page and session analytics | On every visit | Aggregate website performance and content measurement. |
| Payment, invoice, tax and license records | Yes, through payment and licensing providers | Checkout, payment processing, licensing, refunds and compliance. |
| Advertising and retargeting tags | Only after retargeting opt-in | Loaded only when the visitor opts in; marked by the array_hash_re_ok cookie. |
| Heatmaps and session recordings | No | ArrayHash does not use heatmap or session recording tools. |
Plugin data map
| WordPress or WooCommerce data | Sent to ArrayHash? | Where it stays |
|---|---|---|
| Plugin or theme installation and activation events | No | Not collected by ArrayHash. |
| Feature usage telemetry | No | Not collected by ArrayHash. |
| WooCommerce store revenue, orders, products and subscription metrics | No | Merchant WordPress and WooCommerce environment. |
| WordPress admin emails, user emails and customer emails | No | Merchant WordPress database and merchant systems. |
| WordPress, WooCommerce, PHP or plugin logs | No | Merchant server and hosting environment. |
Merchant responsibilities
Merchants control the customer data processed by their own WooCommerce stores.
If you operate a WooCommerce store with ArraySubs, you are responsible for your own customer privacy notices, checkout consent, lawful basis, payment gateway configuration, hosting controls, backups and data-subject request handling for your store data.
- Maintain a store privacy policy that describes your WooCommerce checkout and subscription workflows.
- Handle customer access, correction and deletion requests for data in your own WordPress database.
- Review your hosting, payment gateway, email and analytics providers for your own store.
- Do not send secrets, full card numbers, passwords or unnecessary customer exports to ArrayHash support.
Security measures
Transport
ArrayHash serves website traffic over HTTPS and uses provider controls for payment, license and account workflows.
Access
Personal data access is limited to people and providers who need it for support, billing, licensing, analytics or legal purposes.
Storage
ArrayHash does not store card details and does not store WooCommerce store data from merchant WordPress sites.
Sub-processors and providers
| Provider | Purpose | Data involved |
|---|---|---|
| Google Analytics 4 | Aggregate website analytics | Website usage, device, browser and approximate location signals collected on every visit. |
| Advertising and retargeting tags | Campaign measurement and retargeting (via Google Tag Manager) | Loaded only after the visitor opts in to retargeting. |
| Stripe | Payment processing and card handling | Checkout and transaction data required to complete payment. |
| Checkout and licensing provider | Checkout, licensing, accounts, tax and transaction support | License, account, invoice, refund and payment-related records. |
| Hosting provider | Website hosting and security | Server logs and operational security data. |
Breach response
If ArrayHash becomes aware of a personal data breach affecting data under ArrayHash control, we will investigate, contain the issue, notify affected people where required, and notify supervisory authorities where required by law.
Merchants remain responsible for breach assessment and notification obligations related to their own WordPress, WooCommerce, hosting, payment and customer systems.
Contact
Data safety questions can be sent to [email protected]. For privacy rights, include the email address connected to your ArrayHash signup, newsletter, support, checkout or license record.
Email data safety questionRelated policies
Each page covers one part of how ArrayHash handles privacy, payments, licenses, refunds, and accessibility.
Privacy Policy
What the ArrayHash website collects, why it is used, cookie consent behavior, and how to exercise privacy rights.
Read policyRefund Policy
The 30-day ArraySubs Pro refund guarantee and how refund requests are handled.
Read policyTerms of Service
The terms for using the ArrayHash website and ArraySubs Pro licenses.
Read policyNeed a privacy, billing, or accessibility answer?
Email ArrayHash. We route rights requests, refund questions, and accessibility reports to the right place.