A shared responsibility
This page explains data protection responsibilities and confirmed arrangements for the Glidesk website, Glidesk Portal, Staff App (Glidesk FR) and Manager App (Glidesk Audit). Glidesk is a trading name of Idenicus Ltd, company number 15846364, registered at 128 City Road, London EC1V 2NX, United Kingdom.
The Privacy Policy explains what information is processed, why, who receives it and how individuals can exercise their rights. This page complements that notice with the responsibilities and safeguards to address when using Glidesk. It does not replace a customer data processing agreement or an employer’s workforce notice.
Controller and processor responsibilities
Idenicus Ltd is the controller for its website enquiries, demo bookings, customer relationships and own business administration. Customers are generally the controllers of workforce information processed through Glidesk Portal and the apps; Idenicus Ltd acts as processor on their documented instructions.
Customers determine the purposes, lawful grounds, authorised users and workforce settings for their deployment. Processor obligations include acting on lawful documented instructions and assisting the controller with applicable data protection duties. The relevant customer agreement must describe these responsibilities.
Data processing agreements and suppliers
A binding controller–processor agreement is required where Glidesk processes personal data for a customer. It must address the processing scope, confidentiality, appropriate security, subprocessors, assistance with rights and incidents, return or deletion of data and information needed to demonstrate compliance.
Before deployment, agree the applicable DPA and supplier arrangements with the Glidesk team. This page is not a substitute for a signed agreement and does not claim that a particular DPA, audit report or certification has been issued.
Website and demo services use Netlify, Neon, Microsoft and Cloudflare; map displays use OpenStreetMap. Integration providers receive customer information only where the connection is available, agreed and enabled. The Privacy Policy explains these services separately from the workforce platform.
Biometrics, worker choice and monitoring
Biometric templates are used solely to verify worker identity at clock-in and clock-out. Employers must identify a lawful basis and an applicable special category condition, explain the processing to workers and assess whether the use is necessary and proportionate.
Where explicit consent is relied on, workers need a genuine choice and a suitable alternative without disadvantage. Consent must be withdrawable. Camera or location permission on a device does not itself establish valid consent to employer processing.
A data protection impact assessment is required where processing is likely to result in high risk; biometric recognition requires careful assessment before introduction. The customer must address the risks, alternatives and safeguards for its actual deployment. This page does not claim that a customer-specific assessment has already been completed.
Clock-in location and continuous monitoring are different activities. Employers must explain which features are enabled and their boundaries. Website facial and liveness animations and indoor heatmaps remain illustrative; the optional live-device demonstration has its own controls and disclosures.
Confirmed workforce retention and hosting
Customer workforce data processed through the portal and apps is hosted within the European Economic Area. Website, booking, analytics, map and integration services are considered separately; this is not an EEA-only claim for every supplier.
Biometric templates are retained while a worker remains active and deleted within 30 days of departure or withdrawal of consent, whichever comes first. Consent-based biometric use stops on withdrawal; the deletion period does not authorise continued checks. Customers must action or notify departures and withdrawals.
Relevant attendance, payroll and HR records are typically retained for up to six years, according to the record type, legal requirements and customer instructions. Platform technical logs are retained for up to 12 months. The Privacy Policy provides the full retention explanation, including the separate lifecycle of enquiries and booking records.
International transfers require an applicable lawful mechanism and any necessary assessment and supplementary safeguards. The service arrangements should identify relevant processing locations, remote access and transfer safeguards.
Access, security and deployment evidence
Portal and app access depends on the organisation’s configured roles and permissions. Customers should authorise only the access needed for each role and maintain appropriate joiner, role-change and leaver arrangements.
For a deployment review, request the current evidence relevant to authentication, access administration, encryption, backups, recovery and security testing. These controls must be assessed against the service and risks involved; this page does not assert a particular MFA configuration, encryption standard, audit certification or recovery guarantee without supporting evidence.
Reporting concerns and personal data breaches
Report suspected security incidents to security@idenicus.co.uk. For privacy concerns and rights requests, contact privacy@idenicus.co.uk or info@glidesk.com. Include enough context to identify the issue, without sending passwords or unnecessary sensitive records.
Under UK GDPR, a processor must notify its controller of a personal data breach without undue delay. A controller must assess the risk and notify the ICO of a notifiable breach without undue delay and, where feasible, within 72 hours of awareness. High-risk breaches can also require notification to affected people without undue delay.
These are legal responsibilities, not a promise that every technical incident is reportable or a separate contractual response-time guarantee. The applicable service agreement should set out incident contacts, cooperation and notification arrangements.
Rights, accountability and further information
Individuals can use the Privacy Policy to understand their rights and how to make a request. For workforce records, the employer is normally the first contact as controller; Glidesk assists within its processor role. For information Idenicus Ltd controls, contact us directly.
Customers should maintain their processing records, workforce notices, lawful-basis assessments, retention instructions and any required impact assessments, and review them when their use of Glidesk changes.
The shield beside this page’s footer link identifies data protection information. It is not an independent certification seal or a guarantee that every customer deployment is compliant.
