How beta application information is handled.

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.

We use beta application information to review potential participants, communicate application decisions, administer beta participation, understand intended product use and respond to related enquiries.

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.

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.

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.

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.

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.

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.

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.