Privacy notice
Privacy notice for Lemorange Attendance.
Lemorange Ltd handles information you send through attendance.cy and information that is stored in the Attendance product. When an organisation uses Attendance, that organisation decides how the data of its workforce and its visitors is used. Lemorange Ltd processes that data on its behalf and under its instructions.
Last updated: 14 November 2026
1. Who we are and who this notice covers
Lemorange Ltd is a company registered in Cyprus and based in Nicosia. It operates attendance.cy and provides Lemorange Attendance. For any privacy matter, email support@lemorange.com or call 80012900.
This notice covers four groups of people:
- people who visit attendance.cy or contact Lemorange Ltd;
- customer administrators and other authorised users;
- staff whose details are entered into Attendance by their employer or another organisation;
- visitors, contractors and other non-employees whose details are entered into Attendance when they are invited to a workplace.
A customer agreement and data-processing agreement may give additional information for a particular deployment. Where such an agreement differs on processing performed by Lemorange Ltd for a customer, the signed agreement takes priority.
This notice is about the Attendance product and attendance.cy. For Lemorange Ltd's other websites and services, see the company privacy policy at https://lemorange.com/privacy.
The processor terms for customers are in the Data Processing Terms at attendance.cy/dpa. The list of sub-processors is at attendance.cy/privacy#sub-processors. The notice for visitors is at attendance.cy/visitor-privacy.
2. When Lemorange Ltd is responsible and when the customer is responsible
Lemorange Ltd is the controller when it uses personal data for its own purposes. Examples include website enquiries, customer and billing administration, service security, support records and website analytics enabled with consent.
For workforce data entered into an Attendance workspace, the customer is normally the controller. The customer decides why it uses the system, whose data is included, which attendance methods are permitted, who may see the data and how long the data is kept.
In that situation, Lemorange Ltd acts as processor. It uses the data only to provide, protect and support Attendance under the customer agreement and documented instructions, unless applicable law requires otherwise.
Lemorange Ltd is not the employer and does not decide how a worker is assessed, paid or treated.
For visitor data, the customer that invites the visitor is the controller. The host and the customer decide who is invited, why, and for how long the record is kept. Lemorange Ltd is the processor.
For Safety check, the customer is the controller. The customer decides when to send a safety check, to whom, and what it does with the answers. Lemorange Ltd is the processor.
3. Where the data comes from
- Directly from you when you submit a form, contact us, create an account or ask for technical support.
- From your organisation when it adds users, workers, departments, sites, schedules and rules to Attendance.
- From terminals and mobile devices when an attendance attempt, synchronisation or permitted-method check takes place.
- From an HR, payroll, access-control or other integration authorised by the customer.
- Automatically from technical service logs where needed for sign-in, security, diagnosis and abuse prevention.
Lemorange Ltd does not buy personal-data lists or build advertising profiles from Attendance workforce data.
- From a host or manager at a customer, when they invite a visitor and type the visitor's name, email, phone and company.
- From visitors, when they open their pass, confirm details or ask to delete their data.
- From tablet kiosks placed at a workplace, when staff or visitors use a card, a PIN or a reception call.
- From doors, readers and intercoms that the customer has connected to Attendance.
4. What we collect through attendance.cy
- Contact and enquiry information: name, organisation, role, email address, optional telephone number, employee and site counts, current attendance method and your message.
- Security information: submission time, source page and technical information needed to limit unwanted or malicious requests. The contact form stores a non-reversible hash of the source IP address rather than the address itself.
- Website analytics: pages visited, referral source, device and browser type and approximate region through Google Analytics, but only after you allow it.
- Business records: account, contract, billing and support information if your organisation becomes a customer. Full card details may be sent directly to the payment provider and not stored by Lemorange Ltd.
5. What Attendance may hold
The data depends on the functions selected by the customer. Not every customer uses every category below:
- Work and contact information such as name, employee code, telephone number, job title, department, site and user permissions.
- Rosters, shift changes, availability, leave requests, messages, approvals, calculated hours, payroll codes and audit history.
- Attendance records such as date and time, entrance or site, terminal, method, result and any later correction or approval.
- Credentials selected by the customer, such as a PIN, an RFID or NFC card number and a QR code. Terminal PINs are not hashed: they are stored so that the terminal can check them, and only administrators who manage people can see them. One-time app invitation codes are stored hashed.
- For mobile use, device identifier and type, operating system, app version and notification token. If the customer enables the relevant checks, Attendance may also record location, accuracy, distance from the workplace, Wi-Fi identifiers and IP address at the time of an attempt.
- Terminal and integration information such as device identifiers, connection status, synchronisation logs and identifiers exchanged with an authorised HR or payroll system.
- Visitor records, safety check records, kiosk data, door and intercom records, Team Moments posts and payroll records, as described in sections 6 to 11.
For a private deployment on customer servers, the data may remain entirely within the customer environment. The customer agreement defines the deployment model.
6. Visitors
If a separate visitor register and pass service is supplied, a host may invite a visitor. Depending on the customer's settings, these fields and flows may be used:
- your name, email address and telephone number, as the host entered them;
- your company, if the host entered it;
- the host you are visiting;
- the planned and actual times of the visit, including when you arrive and leave;
- a pass token, which is a random code in the link of your invite and pass page.
Your organisation's customer is the controller of this data. Lemorange Ltd processes it on the customer's behalf.
We use this data to send you the invite, to show your pass, to let reception and security know that you are expected, to alert your host when you arrive, and to keep a record of who was on site. The customer may also keep the record for site security and for safety in an emergency.
Invites are sent by email. The host alert on arrival can be sent by WhatsApp, if the customer has turned it on. Visitors are not sent marketing messages.
How long we keep it. The host organisation sets the period and tells visitors. Intercom still images are kept for 30 days by default, and call records have a separate period.
Your rights as a visitor. To access, export or delete your record, ask the customer that invited you; its managers can export or delete it. You can also write to support@lemorange.com and we will pass the request on. The visitor notice has more detail.
7. Biometrics and location data
Where the customer enables it and the law permits its use, compatible terminals may use a face image, facial template or fingerprint template. Storage and synchronisation depend on the terminal model and the contracted deployment.
Mobile attendance may check whether a device is within an authorised area or connected to an approved network. Attendance does not need to track a worker continuously to perform that check. The customer decides which checks are enabled.
Biometric data and precise location require particular care. Before enabling them, the customer must have a specific lawful purpose, consider a less intrusive method, document its legal basis and complete any required data-protection impact assessment or consultation.
Availability in Attendance does not mean a function is lawful in every workplace.
Two further functions need particular care. A "Need help" answer in a safety check may reveal health or safety information. Intercom images may show a person's face. Customers must limit access to these data to those who need them and must tell people about them.
8. Safety check (emergency broadcast)
If a separate Safety check answer service is supplied, a manager may request answers for a site or zone. The customer decides the questions, any use of location and the records kept:
- who was on site, or in the zone, at the time of the check, based on clock-in records and similar presence data;
- each person's answer, "Safe" or "Need help", and the time of the answer;
- whether a check was a real emergency or a drill, and the results of the drill.
A "Need help" answer can reveal information about a person's health or safety. The customer should treat these answers as sensitive. Access is limited to the managers whom the customer chooses. Staff should not use the answer button as a replacement for calling the emergency services.
Attendance sends the request as a push notification through Google Firebase Cloud Messaging or the Apple Push Notification service. On a locked screen, the alert shows a general line only. It does not show names, the type of emergency or any answers.
How long we keep it. If a separate safety-answer service is supplied, the customer sets how long individual answers, drill summaries and any incident hold are kept. Ask the customer for its period, or write to support@lemorange.com.
The customer is the controller. It must tell its staff about the safety check, decide who may see the answers, and decide if a record should be kept for longer after a real incident.
9. Tablet kiosk and reception calls
If a tablet kiosk is supplied, it may let staff or visitors clock in, sign in or call reception. The customer sets the fields, how a shared session is cleared and how long data is kept. Possible data include:
- NFC or RFID card numbers;
- terminal PINs, which are stored in a form the terminal can check and are visible only to administrators who manage people;
- staff profile photos, which the tablet shows after a card or PIN is used, so that people can see that the right person is signed in;
- kiosk event logs, such as sign-ins, errors and connection status;
- a live video and audio call to reception.
Reception calls. A call may use live audio or video and a relay. For the current media path, recording, relay and retention details of your installation, write to support@lemorange.com. Call metadata and still images may be held separately.
The customer decides if a camera, microphone and photos are shown at its kiosk. The customer must put up a notice at the kiosk where a camera is used.
How long we keep it. Kiosk events, shared-device data, staff photos and card numbers are kept for the period the customer sets, and the customer sets how a shared device is cleared.
10. Door access, intercom and payroll
Door access. When connected, Attendance may record door, device, acting user, time, action, result and reason. The customer sets the permissions and how long hardware and gateway logs are kept; ask the customer, or write to support@lemorange.com, for the current period.
Intercom. An intercom may hold a visitor still image and call metadata. Still images are kept for 30 days by default and the customer can set any period from 1 to 365 days; the call-log period is separate and set by the customer. For live media, recording, gateway and relay details, write to support@lemorange.com. Access follows the customer’s scoped call-log permissions. The staff an intercom call rings can also see its still image while it rings, the person who answers can see it during the call, and a colleague a call is transferred to can see it if the workspace allows that (on by default).
Payroll. If the customer uses payroll, Attendance may hold pay terms, tax and social-insurance details, deductions, identity and bank details, payslips and exports. Access must be restricted to authorised roles. The customer sets how long payroll records are kept and must keep them for any period the law requires.
11. Team Moments (photo sharing)
Team Moments lets employees share photos with colleagues in the phone app. It is off by default for every workplace. The customer's administrator turns it on, and chooses whether posts are shown to the whole workspace or to one site only, whether managers approve posts first, and whether a quiet push notification is sent for a new post.
When it is on, Attendance holds:
- the photos (up to 4 per post) and the caption (up to 280 characters);
- who posted, and when;
- reactions (one of six emoji per person per post) and comments (up to 500 characters), with who wrote them and when;
- reports made against a post, and the actions managers take. These are kept in an audit history.
Photos are made smaller on the phone. The server removes the EXIF data, including GPS location, before the photo is stored. Photos are kept in the customer's own storage area. Only members of that workspace or site can see them. They are never public. Clock-in photos and intercom images cannot be posted.
People in photos. A photo can show other people. When an employee posts a photo with other people in it, the app asks them to tick a box to confirm that those people agree. This tick is a record that the employee gave their word. It does not replace the customer's own duty to have a lawful basis. A person who appears in a photo can ask the customer to remove it.
Who can remove posts. The author can delete their own posts and comments. Managers in scope can hide or delete any post or comment. Anyone can report a post, and anyone can block another person so that their posts and comments no longer show to them. The app shows a short "Be kind" rule before posting: be respectful, post only what you are happy for colleagues to see, and do not post anything that is hateful, unlawful or private.
How long we keep it. 180 days by default. The customer can change this. After that, posts are removed automatically. Comments and reactions are deleted with the post. When an employee leaves the workplace, their posts are hidden at once, and are erased on request, within one month.
The customer is the controller. It should decide if Team Moments suits its workplace, tell staff how it is used, and set its own rules for what may be posted. Posting is not required. Staff can mute notifications for it.
12. Cookies and browser storage
Attendance.cy stores your Google Analytics choice in browser storage and in a strictly necessary first-party preference cookie named attendance_cookie_consent_v2. The cookie lasts for up to 12 months, exists only to remember that choice and does not track you.
Google Analytics runs only after you select “Allow analytics”. Google may then set the first-party cookies _ga, to distinguish browsers, and _ga_<container-id>, to maintain session state. Attendance.cy limits both to 12 months and disables Google signals and ad-personalisation signals.
If you disable Analytics later, Attendance.cy sends a denied consent signal and removes the Google Analytics cookies it can access. We do not use advertising or remarketing cookies.
When an authorised user signs in, Attendance uses the session and security information needed for authentication. The browser may also store practical preferences such as the last view or navigation state. Those preferences remain on that device until cleared.
The Attendance mobile app and the kiosk do not use advertising identifiers or advertising cookies.
The analytics preference also remains in local browser storage until changed or cleared; it has no matching automatic cookie expiry. The consent cookie is attendance_cookie_consent_v2 and the local storage key is shown below. External maps and other SDKs may use their own storage under their own terms. Withdrawing consent does not undo earlier processing.
lem.consent.analytics.v2
13. Why we use data and the legal basis
When Lemorange Ltd is controller, it uses data to answer enquiries, prepare a requested quotation or demonstration, provide the contracted service, administer accounts and billing, deliver support, secure its systems, prevent misuse and meet legal obligations.
The legal basis depends on the context. It may be steps requested before entering a contract, performance of a contract, a legal obligation, your consent or Lemorange Ltd’s legitimate interests in operating, supporting and protecting its business and services.
Google Analytics is based on consent. You can withdraw that consent at any time through the controls at the end of this page without affecting the website’s operation.
When processing is based on legitimate interests, we consider the purpose, necessity and impact on individuals. You may object on grounds relating to your particular situation.
When Lemorange Ltd acts as processor, the customer decides the purposes. The customer's purposes are normally: to record and calculate working time, to schedule staff, to pay staff, to control access to its premises, to know who is on site, to protect staff in an emergency, and to welcome and track visitors. The legal basis is the customer's to decide. For safety check, it is often the customer's legal duty to protect its staff, or its legitimate interest. For payroll, it is the employment contract and legal duties. For visitors, it is often the customer's legitimate interest in site security.
14. Which information is required
Required fields are marked on the contact form. Without basic contact information and enough detail about the enquiry, we may be unable to reply or prepare a relevant quotation. A telephone number and Google Analytics are optional.
Inside Attendance, the customer decides which information is needed for the selected functions. If a required identifier, schedule, attendance event or permission is missing, a function or calculation may not complete correctly. The customer is responsible for checking completeness and accuracy.
15. What the customer must do
- Give workers clear information before collection begins.
- Use only the data and attendance methods genuinely needed for the stated purpose.
- Identify and document the legal basis, retention period and people with access.
- Keep employee, site, terminal and integration information accurate.
- Handle worker requests and ask Lemorange Ltd for the assistance provided by the data-processing agreement.
- Complete any required data-protection impact assessment, consultation or approval before using biometrics, location, monitoring or another intrusive method.
- Give Lemorange Ltd lawful, clear and documented instructions and have the right to send data to every connected system.
- Tell visitors who will see their data, how long it is kept, and how to ask for deletion. Link them to the visitor notice.
- Tell staff before using Team Moments, Safety check, kiosk cameras, door access, intercom images or payroll. Limit who can see "Need help" answers and intercom images.
- Put up a notice at any kiosk or door where a camera is used.
- Set retention periods that fit the purpose. Do not keep visitor records longer than needed.
Before monitoring, the employer should give staff a notice naming its full legal identity and privacy contact, each method and purpose, required or optional data, legal basis and any special-category condition, less intrusive alternatives, recipients, access scope, retention, device copies, rights and complaint route. It should explain how missed punches are corrected and how a person can report a private-mode or safety-alert problem. Receipt of a notice is not blanket consent. The notice must reflect the actual deployment and be available in a language staff understand.
16. Who may have access
Access inside Lemorange Ltd is restricted to authorised people who need the data for service delivery, security, billing or technical support.
Lemorange Ltd uses sub-processors for hosting, email, messages, push notifications, call relay, payments and network services. The current list, with what each one does and where, is at attendance.cy/privacy#sub-processors. We update that list before we add or replace a sub-processor, and customers can object as set out in the Data Processing Terms.
Data may be sent to HR, payroll, access-control or another system only when the customer activates or requests that integration. It may also be disclosed to professional advisers, insurers, authorities or courts where required by law or needed for a legal claim.
If Lemorange Ltd is reorganised, merged, acquired or transfers a business, relevant information may be disclosed to advisers and the successor under confidentiality duties and applicable law.
Lemorange Ltd does not sell personal data and does not use customer workforce or visitor data for advertising.
Backups are kept at Hetzner in the EU, on our servers and in an off-site Hetzner Storage Box, with restricted access. Encryption of backups is planned. Older backup copies held at Microsoft Azure in the EU are being deleted. Provider roles are listed in section 28 of this notice.
17. Transfers outside the European Economic Area
If data must be transferred outside the European Economic Area, Lemorange Ltd uses a mechanism recognised by data-protection law, such as an adequacy decision or standard contractual clauses, and considers whether additional safeguards are required.
The hosting location, deployment model and relevant providers may be described more specifically in the customer agreement and data-processing agreement.
Provider and support access outside the EEA must be identified for the actual deployment. Before any restricted transfer, Lemorange Ltd identifies the entity, country, role and onward access and puts the required transfer terms and safeguards in place. The current list is at https://attendance.cy/privacy#sub-processors.
18. Security and personal-data breaches
Lemorange Ltd applies technical and organisational measures appropriate to the service and risk. They include access controls, separation between customer workspaces, encryption of production communications, audit history, controls against malicious or repeated requests and managed support access.
No online system is completely secure. Customers must protect their administrator accounts, networks, servers, terminals, mobile devices and integrations and notify Lemorange Ltd promptly if they suspect a compromise.
When Lemorange Ltd becomes aware of a personal-data breach affecting customer data, it informs the customer without undue delay and provides available information in stages. A full investigation does not delay the first notice. Incident contact: support@lemorange.com or 80012900.
An initial notification may be supplemented as the investigation progresses. Notification does not by itself amount to an admission of fault or liability.
For the functions in this notice, the measures also include: terminal PINs visible only to administrators who manage people; app invitation codes stored hashed; encryption in transit for the app, the kiosk and calls; access to safety check answers, intercom images and payroll data limited by role; and visitor pass tokens that cannot be guessed.
The security measures that apply are listed in Annex B of the Data Processing Terms. Report a suspected incident to support@lemorange.com or 80012900 without sending passwords or unnecessary sensitive records.
19. How long we keep data
There is no single period for every category. We consider the purpose, the duration of the relationship, customer instructions, security and support needs, legal limitation periods and the possibility of a legal claim.
Website enquiries are kept for as long as needed to answer, continue a genuine business discussion and address misuse. Contract, billing and support records are kept for the periods required by the relationship, accounting rules and law.
Workforce data follows the settings and documented instructions of the relevant customer. The product defaults are these.
- Visitor register and pass records: kept for the period set by the host organisation; intercom stills are kept for 30 days by default (1 to 365 days).
- Safety answers and drill records: kept for the period set by the customer.
- Kiosk events and shared-device copies: kept for the period set by the customer.
- Door and gateway logs: kept for the period set by the customer.
- Intercom snapshots and photos: 30 days by default. The customer can set any period from 1 to 365 days; the cleanup deletes a snapshot once it is older than the period set for that workspace.
- Team Moments posts: 180 days. Configurable.
- Payroll records: kept for the period set by the customer, which must be at least what the law requires.
On termination, data is returned or deleted as agreed. Limited backup copies may remain protected until overwritten in the normal backup cycle.
Lemorange Ltd may keep specific information longer when required by law, court or administrative proceedings, or to establish, exercise or defend a legal claim. Access is restricted to that purpose.
20. Your rights
Depending on the circumstances, you may request access, correction, erasure, restriction or portability. You may also object to processing based on legitimate interests and withdraw consent for future processing.
These rights are not absolute. For example, information may need to be retained for a legal obligation, active dispute or compelling lawful reason. We will explain if a request cannot be met in full.
To protect the data, we may request information needed to confirm identity or authority. We respond without undue delay and normally within one month. A complex request or multiple requests may permit the extension provided by the General Data Protection Regulation.
Visitors can export their data and ask for erasure through the customer's managers, or write to support@lemorange.com, and we pass the request on. The customer may have to keep some information in a form that does not identify you, such as the entry log without names. The customer can ask Lemorange to hold a record for a real incident under investigation, and must then tell you.
You may also object at any time to direct marketing, including related profiling. Where required, the controller tells recipients about correction, erasure or restriction. A necessary extension of up to two further months must be explained within the first month. If a request is refused, the reasons and complaint route must be given within the applicable period. Identity checks must be proportionate. Rights concerning solely automated significant decisions include applicable human review and a chance to challenge the decision.
When the controller receives information about you indirectly, it must give the notice required by applicable law within the relevant period and cannot wait for you to make a request. The timing and exceptions depend on the flow and on the applicable law.
21. If your data is in your employer’s workspace
In the Attendance.cy mobile app, open Settings and choose Your data rights to submit and track an access, correction, erasure, restriction, portability or objection request. The request goes to the employer or organisation that controls the relevant workspace and is responsible for assessing it.
Lemorange Ltd does not delete or change workforce data on a worker’s direct instruction without involving the responsible customer, unless the law requires otherwise. It will pass on the request and assist the customer as required by the data-processing agreement.
For information controlled directly by Lemorange Ltd, such as an enquiry you submitted on attendance.cy, email support@lemorange.com.
If you are a visitor, ask the customer that invited you, or email support@lemorange.com. We will pass the request on to the customer.
22. Attendance calculations and recommendations
Attendance may calculate hours, flag records that need review and suggest available workers for shift cover. These functions assist the customer’s authorised managers.
Lemorange Ltd does not use those outputs to make employment decisions about an individual. The customer must review the data, correct possible errors and decide whether and how to act.
23. Questions and complaints
For a question, request or complaint about information controlled by Lemorange Ltd, email support@lemorange.com or call 80012900. We will review the matter and provide our response.
You may also complain to the Office of the Commissioner for Personal Data Protection in Cyprus or the data-protection authority where you live or work.
Office of the Commissioner for Personal Data Protection: https://www.dataprotection.gov.cy/
24. Changes to this notice
We update this notice when the service, processing, a significant provider or legal requirements change. The date at the top shows the latest revision.
If a change is material, we will provide additional notice where required. A customer agreement or data-processing agreement may specify how a customer is notified.
Before a new purpose or method starts, the customer must complete its staff notice, identify the actual legal basis and any special-category condition, and assess high-risk monitoring. Acknowledging a notice does not supply consent. The service is for workplaces; where a minor is lawfully employed, the employer must assess age-appropriate safeguards. Lemorange Ltd's contact details are at the start of this notice; for anything further, write to support@lemorange.com.
25. Fleet tracking and fuel
If Fleet is enabled, the customer may process vehicle and tracker identifiers, position, time, speed, trips, stops, mileage, alerts and driver links. Access follows vehicle permissions and site or department scope. Opening a position or trail may create a separate access log. The customer must set and explain work and private-use rules; the software alone does not limit every tracker to working hours.
For records marked private by the tracker, the receiver removes location, speed, heading and cell-location information before storage, or drops the record under the configured policy. Limited time, mileage and driver information may remain. Private mode needs device configuration and testing; it does not erase a route already stored as a business trip. For copies held on the device or in the SIM network, write to support@lemorange.com.
Fuel records may include the driver, vehicle, station and coordinates, date and time, litres, price, VAT, payment type, last four card digits, odometer, notes, receipt image and review decision. When receipt reading is configured, the full image goes to Anthropic and may contain incidental personal details. People must check the extracted figures. The customer must set a retention schedule for routes, fuel and receipts.
26. Photos, messages and System tools
Where enabled, a phone may capture a selfie or work photo for an attendance attempt. A terminal may take a punch photo held by its gateway. Scoped manager workflows can retrieve punch photos. The selfie flow does not perform face matching. Separate terminal enrolment may use face images, templates, fingerprints or card numbers; for storage and deletion on a given device and gateway, write to support@lemorange.com.
Work messages can hold text, files, sender, recipients, times, edits, reactions and read state. Retraction can remove active content while metadata or copies received by others remain. Push providers may receive routing data and notification previews. A preview may appear on a device screen.
When configured, Anthropic receives schedule images or PDFs for transcription, fuel receipt images for reading, and selected sales-mail details for lead classification. A schedule file itself may name workers. If a conversational assistant is offered, this notice will be updated to describe its data flow before it is used. System output needs human review, especially for pay, VAT, employment and safety decisions. We make no promise about provider training or zero retention.
When configured, employee or demo invitations through WhatsApp may send a name, phone number and invitation link through a gateway to Meta. Transactional email sends recipient details, content and attachments through the configured relay. For the current gateway, mail provider, countries and provider logs, see https://attendance.cy/privacy#sub-processors or write to support@lemorange.com.
27. Providers and remaining details
Providers we use or may use include Hetzner for hosting; Cloudflare for edge services; Hetzner Storage Box for off-site backups in the EU; Microsoft Azure (EU) for older backup copies that are being deleted; Anthropic for configured model tasks; Zoho Mail and Books; Stripe; Google Firebase and Apple for push delivery; Meta/WhatsApp and a gateway; a configured email relay described as SMTP2GO; possible 1NCE tracker connectivity; Google Analytics; and configured map, geocoding and weather services. Not every provider is used for every customer, and some act as independent controllers. The current list, with each provider's role and country, is at https://attendance.cy/privacy#sub-processors.
A provider brand, EU endpoint or EU hosting does not establish every processing country. Restricted transfers need the applicable mechanism and assessment. Customers may choose independent recipients such as accountants and integrations. The approved sub-processor register must distinguish these roles.
Retention differs by record. By default, linked phone punch photos are kept for 90 days, intercom stills for 30 days (the customer can set 1 to 365 days) and position-view logs for 730 days. Payroll records, and route, door, message, fuel, visitor and safety records, are kept for the period the customer sets; write to support@lemorange.com for the current period.
Other cleanup rules make unused phone-photo uploads eligible after 15 minutes, schedule source files after 24 hours, leave certificates after a configurable 24-month default, certificate access logs after three years, and notification-centre entries after a 60-day default. Eligibility is not instant erasure: the relevant cleanup process must run. Underlying messages, exports, recipients and backups may follow separate schedules.
28. Sub-processors
This is the provider and access register for Lemorange Attendance. A listed provider is not necessarily used for every customer. The customer agreement and the Data Processing Terms identify the recipients, contracts and safeguards that apply before customer data is disclosed.
| Provider or access | What it does | Data it may handle | Location | Transfer basis |
|---|---|---|---|---|
| Hetzner | Hosting of servers and databases, and off-site backups (Storage Box, EU) | All data stored in Attendance | Ask support@lemorange.com | Put in place before any transfer outside the EEA |
| Microsoft Azure | Older backup copies, being deleted; no new copies since 14 November 2026 | Data stored in Attendance, in backup copies | EU | Put in place before any transfer outside the EEA |
| Configured email relay (SMTP2GO) | Sends email: visitor invites, notices, reports | Recipient name and email, email content | Ask support@lemorange.com | Put in place before any transfer outside the EEA |
| Meta/WhatsApp and gateway operator | Sends WhatsApp messages: host arrival alerts and other messages the customer turns on | Recipient phone number, message text | Ask support@lemorange.com | Put in place before any transfer outside the EEA |
| Google Firebase | Delivers push notifications to Android devices | Device push token, notification content | Ask support@lemorange.com | Put in place before any transfer outside the EEA |
| Apple push service | Delivers push notifications to iPhones and iPads | Device push token, notification content | Ask support@lemorange.com | Put in place before any transfer outside the EEA |
| Call relay or gateway operator | Possible relay for live calls | Call media in transit, connection details | Ask support@lemorange.com | Put in place before any transfer outside the EEA |
| Stripe | Billing and card payments for the customer's subscription | Customer billing contact, payment details (held by Stripe) | Ask support@lemorange.com | Put in place before any transfer outside the EEA |
| Cloudflare | DNS and content delivery network | Web traffic metadata (IP addresses), traffic to attendance.cy | Ask support@lemorange.com | Put in place before any transfer outside the EEA |
The advance notice and objection process in the Data Processing Terms applies: 30 days' notice. Before an addition or replacement, we identify the entity, service, countries, data and safeguards and resolve a timely objection before disclosure.
To ask a question, write to support@lemorange.com.
Google Analytics
Google Analytics settings
Choose whether Google Analytics may run in this browser. Attendance.cy works without it.