Personal data Klyra processes and how long it is kept
Which personal data Klyra collects, where it is stored and how long it stays available for your team.
Klyra processes personal data of staff, customers and suppliers to run shifts, clocking, HR and traceability: knowing which data is collected and for how long it is kept is essential to answer an audit or an employee request. This guide summarises what happens to data during normal use of the app.
Categories of data collected
The main data processed are staff personal details and contacts, clock-in and attendance records, HR documents such as contracts and health fitness certificates, recipe and traceability data that may include the names of the operators involved, and customer data recorded in the invoicing or made-to-order production module.
Klyra does not collect sensitive data that is not necessary for the business: it never asks about health, opinions or orientation unless explicitly required by a module you activate voluntarily, such as health fitness certificates for kitchen staff.
Where data is stored
Data is stored on cloud infrastructure with access restricted to authorised technical staff and encryption both in transit and at rest. Each organisation has its data logically isolated from other organisations on the platform.
- Encrypted communication between the app and the servers
- Regular backups with a limited retention period
- No data shared between different organisations
How long data is kept
Operational data such as shifts, clock-ins and deliveries stays available for the whole contract and for the retention period after cancellation described in the subscription section. HACCP documents and traceability records follow the minimum retention set by food safety regulation instead, which is often longer than the contractual one.
Minimisation and purpose
Every piece of data collected is tied to a specific app feature: nothing extra is requested "just in case" or "for the future". Disabling a module stops new processing of the related data while keeping the history already recorded.
Cosa trovi in questa guida
- personal data
- data retention
- GDPR processing
- employee data
- customer data
- data minimisation
Problemi frequenti
- You do not know where your organisation data is stored → check the data processing document linked to your contract, available under Administration, Settings, Compliance.
- An employee asks what data you hold about them → use the personal data export feature described in the dedicated article instead of answering manually row by row.
- You think an unnecessary field is being requested → report it to support with the exact screen, so the team can check if the field is really needed.
- HACCP documents seem to be kept longer than expected → that is correct, they follow the minimum food safety retention period rather than the software contract term.
Domande frequenti
Does Klyra store data about the restaurant’s end customers?
Only if you use modules that require it, such as invoicing or made-to-order production: without those modules active, no such data is collected.
How long do clock-ins of a former employee remain visible?
They stay in the history for the period required by your contract and by legal obligations on attendance and payroll, even after the employment ends.
Is data shared with other companies using Klyra?
No, each organisation only sees and manages its own data, logically isolated from other organisations.
Guide collegate
Questa guida ti è stata utile?
Hai ancora bisogno di aiuto?
Descrivi il problema: alleghiamo in automatico pagina, sede, organizzazione e ruolo.
Contatta l’assistenza