TRADIUM / Security & data
Trust starts with clarity.
Access has boundaries.
We distinguish the corporate website from the live experience and from the controls to be agreed for a project handling business data.
The corporate website
Styles, fonts and application files are served from the site. The contact dialog prepares a message locally for review and optional sending through an email application. It does not claim a server submission that has not happened.
- No payment details or passwords are requested by the corporate website.
- Google Maps loads only when selected.
- Hosting may process technical logs and performance measurements to deliver and protect the site.
The separate /experience workflow
The standalone experience uses fictional examples and displays actual persistence and AI generation when its connected services succeed. It has its own privacy notice and security verification. A generated draft is separate from approval or human review.
- Read the experiment notice before starting.
- No store credentials or customer data are needed.
- Generation depends on available quota and services.
When designing business integrations
We define necessary data, access, approval points and error handling before operation. Retention, deletion, hosting and processor requirements are reviewed for the engagement.
- Service keys belong in a server environment, outside visitor-facing code.
- Minimum access needed for the agreed workflow.
- Verification before disclosing order data or taking sensitive actions.
Security enquiries
Report observations about the TRADIUM website to info@tradiumeg.com with the subject Security. Include a description and reproduction steps without credentials or customer data. This page explains our approach; it is not a security certification.