Privacy and Data Handling

A clear note on data and privacy.

A short, honest explanation of how demonstration enquiries, implementation scenarios, and data handling are approached at this stage of TraceLogic. Not a legal privacy policy. A practical statement of intent.

How enquiries are handled

When you send a demo enquiry, your name, email address, and the contents of the message are received via email. The information is used to respond to your enquiry, schedule the demo, and follow up after the demo.

Enquiry information is not shared with third parties. It is not used for advertising. It is held only as long as needed to handle the enquiry and any reasonable follow-up.

Synthetic or approved test data

Demonstration scenarios use synthetic or approved test data. TraceLogic does not need to claim live client data use at this stage. Real customer data is not used in the demo unless explicitly scoped and agreed in writing as part of an implementation engagement.

If an implementation engagement involves real or sensitive data, data handling is scoped during the implementation discussion: data minimisation, access controls, retention, and deletion are agreed before any such data is used.

Privacy-conscious by design

TraceLogic is designed with privacy-conscious implementation as a core design direction.

Tenant-scoped governance. Decisions in one tenant are not visible to another.
Role-based lifecycle. Submitter, reviewer, executor are distinct roles with scoped access.
Evidence preserved, not duplicated. The frozen decision record is retained as the reference for later inspection; secondary copies are minimised.
Replay from frozen evidence. Internal policy decisions can be re-run against their frozen inputs and policy snapshot; external-source decisions are reconstructed and integrity-verified from their stored record without re-calling the source.
Human accountability retained. The platform supports decisions; it does not silently make them.
Not a security or compliance certification. TraceLogic does not currently claim ISO 27001, ISO 42001, SOC 2, or any other certification. Security validation is in active development, not a finished posture. Data handling for an implementation is agreed in scoping, case by case.

Questions on data handling?

Reach out and we will share more detail relevant to your implementation scope.