Privacy Policy
How DMHA handles Website, account and connected-store information.
This policy covers the public website, beta applications and enabled DMHA E-Commerce Manager services. Planned supplier ordering is not described as an enabled feature.
DMHA Systems Privacy Policy
Last updated: 9 November 2026
Information you provide
When you submit a beta application, DMHA Systems stores the information requested in the application form, including your name, email address, business or store name, ecommerce platform, optional store URL, application response, contact consent, application status and created or updated timestamps.
The beta application table does not intentionally store applicant IP addresses.
Why we collect it
We use beta application information to review potential participants, communicate application decisions, administer beta participation, understand intended product use and respond to related enquiries.
How application information is used
Authorised DMHA Systems administration uses the information to assess applications and record whether an application is pending, approved, rejected or removed from the beta. Applicants may receive transactional messages about application or participation status. We do not sell beta application information.
First-party website analytics
DMHA Systems uses first-party website analytics to understand use of the public website and the beta application funnel. The analytics uses random browser-generated visitor, session, page-visit and event identifiers. Visitor and session identifiers are transformed with a secret keyed one-way derivation before they are stored.
Analytics records approved public page paths, sessions, measured engagement while a page is visible and focused, coarse country and region supplied through Cloudflare, coarse device, browser and operating-system categories derived from the user agent, and the referring domain where available. Beta conversion events record that the beta form entered view or that an application was submitted successfully, but do not contain the application form responses.
The analytics database does not store IP addresses, raw user-agent strings or complete referring URLs. DMHA Systems does not use fingerprinting for this analytics. Infrastructure, network and security providers may still process network and device metadata when delivering and protecting the website under their own systems and policies.
Raw first-party analytics records are retained for 12 months. When a browser signals Global Privacy Control or Do Not Track, the website does not initialise visitor or session analytics tracking, and matching analytics collection requests are also ignored by the server.
Infrastructure and service providers
The website uses Cloudflare Pages for hosting, Cloudflare Turnstile for anti-abuse checks, Cloudflare D1 for beta application storage, Cloudflare Access for internal administration and Cloudflare Email Service for transactional beta messages.
Although the application table does not store IP addresses, hosting, security, network and anti-abuse providers may process network and device metadata as part of delivering and protecting the service under their own systems and policies.
Retention
Beta application data is retained while the application or beta participation is active, and for up to 12 months after the last application-status change, unless a longer period is required for legal, security, or dispute-resolution purposes.
Security
DMHA Systems uses access controls, protected administration routes, server-side validation and established Cloudflare security services to reduce unauthorised access. No internet service can guarantee absolute security.
Questions and requests
For a privacy question or a request concerning a beta application, contact [email protected]. We may need to verify identity before acting on a request.
Policy updates
This policy may be updated as the website, beta programme or product changes. Material updates will be published on this page with revised wording or an updated date.
Connected stores and customer order information
When a merchant connects a Shopify Store to DMHA E-Commerce Manager, DMHA accesses the minimum order data needed for enabled functions. This includes order and line-item references, products, quantities, prices, refund and fulfilment status, tracking details, and buyer display names where Shopify grants access. Data is separated by merchant Account, Workspace and Store.
DMHA uses this information to import and display Sales Log orders, calculate sales totals, reconcile deliveries and provide authorised fulfilment updates. Automatic supplier ordering is a separate planned merchant-authorised feature, not enabled merely by connecting a Store. When that feature is available and the merchant enables it, only delivery details genuinely required by the selected supplier or carrier, such as recipient name, shipping address or phone number, will be transferred.
DMHA does not sell buyer information, use it for advertising, or include protected buyer information in AI prompts by default. Account permissions control access to buyer data; access is audited using user identity, Store, action, time and record count without logging the buyer's details. Shopify, authorised suppliers and couriers, and the hosting and security providers needed to operate the service may process relevant information.
Connected-store retention and customer requests
Buyer contact and tracking details from tagged test orders are removed after 30 days without a Shopify update. For fulfilled or cancelled orders, these details are removed after 180 days without an update. Details required for still-open delivery remain until fulfilment or review, taking disputes and legal holds into account. The order and financial ledger is retained separately for applicable accounting, tax and dispute obligations.
Customer-data access-audit metadata is retained for 365 days. Workspace backup archives omit customer names and tracking information; recovery rejects legacy archives containing this data. Separate infrastructure database snapshots are covered by the backup retention and recovery process.
Merchants can request access, correction or deletion of stored customer information through [email protected], subject to identity verification and applicable legal requirements. Merchants review and expressly accept the Merchant Data Processing Agreement in their authenticated Website Account before launching Commerce.
