the public website should be readable without asking visitors for unnecessary data. ordinary browsing of home, products, docs, blog, faq, legal pages, and event information should stay minimal by default.
privacy
collect less. explain more. never sell data.
privacy should not be a vague promise. it should be reflected in what the site stores, why it stores it, how it is protected, and the fact that personal data is not for sale.
working rules
- public pages should collect as little data as possible.
- infiniware does not intend to sell user data.
- contact submissions belong to the python backend rather than scattered client-side handling.
- account, profile, discussion, and comment data should live in the site database instead of being distributed across unrelated services.
- privacy policy language should stay readable, precise, and proportionate to what the site actually does.
if you create an account, the backend stores the data needed to operate that account, verify your email, attach a profile to you, and connect your discussions and comments to your user record.
verification codes and password-reset emails are sent from infiniware infrastructure configured through smtp. those messages exist to complete account access and security flows, not to drive marketing campaigns.
the privacy direction should be explicit: personal data is not merchandise. infiniware should not sell user data or build the site around that business model.
security means using clear backend ownership, limited data collection, verified account flows, and tighter control over where critical account and discussion data lives.