Data Handling & Confidentiality
No client data in public demos. Access and safeguards are defined for each engagement before work begins.
What this website can currently establish
The illustrations on this website do not require actual client datasets.
Data access and relevant agreements must be decided for each assignment.
Processor, hosting/log, e-mail and retention details require verification before final notices.
This is an outline of the intended approach, not a security certification.
Ask only for what a task requires
An initial scope discussion can begin with the problem, desired output, source formats and accountable roles. Do not send personal datasets, supplier agreements, complete price lists, credentials or other confidential files through this site or an unagreed communication channel.
No raw files required
A workflow description, system types, table structure and non-identifying examples are often enough to evaluate fit.
Approval before access
The dataset, access route, responsibilities and any required NDA or data-processing agreement must be agreed in advance.
Limit access by purpose
Where feasible, use bounded exports and agreed test cases; direct production write access is not implied.
Defined principles versus controls still to verify
A planned practice is not evidence of a deployed safeguard. This page therefore makes no blanket guarantee about EU-only storage, encryption, retention or full GDPR compliance.
Public demonstrations
The examples on this website are illustrative and contain no client procurement records. Future interactive demos need separate technical and provenance review.
Access and responsibilities
Scope, authorised users, permissions and export handling are decisions to make for each project.
Storage and transfer
Actual storage locations, channels, encryption, backups and retention/deletion policy have not been independently verified for proposed project work.
Third parties and logs
Hosting, server logs, e-mail, installed plugins, vendors and contractual processing roles must be inventoried before personal-data processing.
Questions to resolve before processing starts
The actual solution depends on the project, customer environment and legal roles. These steps are a pre-engagement checklist, not a statement that all controls are already deployed.
Classify needed data
Which personal, commercial or confidential information is genuinely necessary for the task?
Agree roles and instructions
Confirm controller/processor roles if applicable, confidentiality and authorised processing instructions.
Confirm transfer route
Document the permitted channel, identities, approval and access boundaries.
Define working environment
Name storage, processing tools, permitted users, intermediate files and any sub-processors.
Agree handover and deletion
Set handover, necessary retention, backup exceptions, deletion timing and responsible contacts.
This page is not the website privacy notice
The actual privacy policy must be based on verified hosting, e-mail, logs, forms, installed services and data lifecycle. Those publication and delivery checks are not complete.
Before any real data transfer
No client upload path is provided here. Do not send confidential materials to an untested form; agree and verify safeguards first.
Do you process personal data?
This may be required for a particular project. The purpose, roles, legal basis and measures must be evaluated beforehand; a blanket claim that no personal data are ever processed would be inaccurate.
Where would project files be stored?
No universal storage location is currently confirmed. The agreed arrangement needs documented verification before work starts.
Can I upload actual data to a public demo?
No. This website has no client-data upload feature and no live interactive demo handler.
More information
Define a practical scope before committing to a project.
We review source data, checks and acceptance criteria before a proposal. No blanket delivery or savings guarantee.