Process accounts, orders or payments
There is no live account registration, cart, checkout, order database or payment provider in this prototype.
Privacy policy draft
Privacy terms must describe the store that actually launches.
The current local prototype collects no checkout data and sends no support request. The production policy must be rewritten after the real platform, vendors and data flows are selected.
PrototypeNo live checkoutNo order data collected
Support toolLocal summary onlyNo request transmitted
BiometricsNo website upload fieldProduct behavior still requires evidence
Current stateStatic local prototype
No account, checkout, analytics or advertising integration was found in the prototype.
Critical boundaryDo not imply biometric guarantees
Website behavior and device-side processing are separate questions.
Launch gateMap every production data flow
Then disclose categories, purposes, vendors, retention and rights.
What the current prototype does and does not do.
This statement applies only to the local files being reviewed now, not to a future WordPress store or any production service.
Send the support summary
The Support page prepares text in the browser. It does not transmit or store the entered details.
Run analytics or advertising tags
No analytics, advertising pixel, cookie-setting script or browser storage call was found in the current prototype code.
Production data categories must be mapped before publication.
Only categories actually collected by the launched store should appear in the final policy.
01Identity and contact information
Name, email, phone and delivery address if the checkout and support flow collect them.
02Order and transaction information
Products, order status, returns and payment metadata. The selected payment provider must be identified.
03Device and usage information
IP address, browser, logs, cookies and analytics only if the production tools collect them.
04Support information
Model, Windows version, troubleshooting history, attachments and correspondence.
05Marketing information
Email preferences, advertising audiences and campaign attribution only if these features are enabled.
The website and the fingerprint reader need separate privacy evidence.
This website does not ask you to submit fingerprint images or templates. Dovryx has not yet published a model-specific statement about fingerprint-template storage or processing because that statement requires chip, firmware and Windows integration evidence for each SKU.
Disclosures required before the production policy is final.
The policy cannot be completed by changing the brand name in a template. It must match the real seller and technology stack.
01Data controller identity and contact
Legal company name, registered address, privacy contact and effective date.
02WordPress and commerce stack
Hosting, WooCommerce or other commerce tools, payment, fraud, email and support vendors.
03Cookie and tracking inventory
Necessary, analytics and advertising technologies plus consent requirements by location.
04Purposes and legal bases
Why each category is used and which jurisdiction-specific basis applies.
05Retention, deletion and security
Retention periods, deletion workflow, access controls and incident response owner.
06Consumer rights and request process
Applicable access, correction, deletion, opt-out and appeal procedures with identity verification.
07Sale, sharing and targeted advertising
Determine whether any vendor activity triggers jurisdiction-specific disclosure or opt-out duties.
08Children and international transfers
Audience age position, COPPA assessment and any cross-border processing safeguards.
Privacy questions this draft can answer.
Need the current support boundary?
The Support page explains what its local request builder does before a production contact channel is connected.