Collect only what a feature needs
We start by asking what information a feature needs and why. We avoid collecting a field simply because it may be useful later, and we explain the purpose in the relevant product information.
Keep public reading open
Visitors can read the company website and public guides without creating a site account. Our contact flow prepares an email for the visitor to review and send; it does not create a server-side support ticket.
Do not send secrets through public support
We do not need passwords, one-time codes, recovery codes, full payment details, or private keys to investigate an ordinary website issue. A useful report includes the public page, what the visitor expected, what actually happened, and steps to reproduce it without exposing private data.
Distinguish company pages from product services
Ready2Go Learning, Marvel Chat, and Davonium Nexus have separate purposes and may have different information needs as they develop. We keep their public status clear and review product-specific privacy information against the current experience.
Policy review
Our privacy and browser-storage pages remain drafts until they have been checked against actual production data flows and applicable requirements. Contact us if you need clarification about a particular interaction.