Collect for a defined reason
Personal information should be collected and used for specified, legitimate purposes and not expanded into unrelated uses without an appropriate basis.
Data Protection
PacyNet's data-protection approach is built around purpose limitation, data minimisation, access control, security, accountability and appropriate handling of individual rights.
Framework
The corporate website is only one part of the framework. Product-specific controls must be proportionate to the data, users, institutions and legal obligations involved.
Personal information should be collected and used for specified, legitimate purposes and not expanded into unrelated uses without an appropriate basis.
Systems should request the minimum information reasonably required for the intended function, transaction, security control or legal obligation.
Where personal information is used operationally, PacyNet aims to provide appropriate processes for correction, validation and controlled updates.
Retention should follow the processing purpose, contractual requirements and applicable legal obligations, followed by secure deletion, anonymisation or archival controls where appropriate.
Controls may include encryption in transit, authenticated access, role separation, audit records, input validation, anti-abuse measures, backups and incident-response procedures appropriate to the system.
Data-handling responsibilities, approvals, access boundaries and significant changes should be documented sufficiently to support oversight and investigation.
Roles
For personal information submitted directly through the PacyNet corporate website and corporate portal, PacyNet may act as the data controller where it determines why and how that information is processed. The Privacy Notice explains the current website processing in more detail.
For future or deployed institutional products, PacyNet's role may differ depending on whether an institution determines the purposes and means of processing or PacyNet independently determines them. Product and customer documentation should define those responsibilities before production use.
Sensitive environments
Education, health, artificial intelligence and public-sector infrastructure can involve information that warrants enhanced governance.
Systems involving learners or children should incorporate age-appropriate privacy, authorised institutional access, safeguarding, limited visibility and carefully controlled data sharing.
Health-related information should receive heightened access, purpose, disclosure and security controls, with clear separation between PacyNet's infrastructure role and regulated healthcare responsibilities.
AI-supported processing should be designed with appropriate transparency, data-quality controls, access boundaries and human review where outputs could materially affect an individual or institution.
Government and public-institution deployments should use strict role separation, authorisation controls, auditability and contractual restrictions appropriate to the sensitivity of the information involved.
Rights
Where applicable, individuals may request information about personal data processed about them and the relevant purposes, categories, recipients and retention.
Appropriate mechanisms should exist to correct inaccurate personal data and complete information where required.
Requests for erasure, restriction or objection should be assessed against the applicable law, contractual responsibilities, retention duties and rights of other persons.
Third parties
PacyNet may rely on carefully selected third parties where necessary to operate, protect or support its systems and business processes. Selection, contractual safeguards, access scope, transfer considerations and security responsibilities should be assessed according to the information and processing involved.
Requests
The public route for website privacy questions and data-subject requests is available now.
For the detailed notice covering pacynet.com and the corporate portal, read the Privacy Notice. General website conditions are in the Website Terms.