Describe what people actually experience
We start from the real visitor journey and the information a feature uses. We identify what a person enters, what happens after they submit it, which service receives it, and what choices remain with the visitor. We do not publish a privacy claim merely because it sounds standard.
Explain purpose and control
We describe why information is needed, whether it is stored on the device or handled by a separate service, and how a visitor can contact us with a question. We avoid collecting information simply because it may be useful later.
Review products separately
Davonium Technologies provides public company information and develops separate products. Their data practices may differ as features are added. We review the actual behaviour and requirements of each product before publishing a product-specific statement.
Keep draft policies clearly identified
Our public privacy, terms, and browser-storage pages remain drafts until we verify them against actual production practices and complete an appropriate review. We do not present these drafts as legal advice or a substitute for qualified legal review.
Update when behaviour changes
When a feature changes what information it collects or how it uses it, we review the public notice, related help page, and the explanation shown to users. If a visitor asks us about a specific interaction, they can contact us through the contact page.