Privacy Policy

Time and Attendance is published by Red Lotus Tecnologia da Informação Ltda. (CNPJ 49.623.066/0001-27), R. Padre Adelino, 570, sala 804, Quarta Parada, São Paulo, SP, 03303-000, Brazil ("Red Lotus", "we"). For the processing described here, Red Lotus acts under Brazil's General Data Protection Law (LGPD, Law No. 13,709/2018).

Time and Attendance ("the app") is a Freshservice app that reads the file a time clock exports, finds the days on which an employee's punches do not fit their work schedule, and asks each employee to explain or correct those days through a Freshservice ticket. This policy explains what data the app handles and where it goes.

1. Summary

• The app works only with your own Freshservice account: everything it reads comes from it or from the file your HR agent uploads, and everything it creates is written back to it.
• The clock file is read in the agent's browser and is never uploaded, stored or sent anywhere. No punch and no attendance record is kept.
• Nothing is sent to Red Lotus or to any other third party. The app has no servers and no database of its own; what it keeps lives in the Freshworks app data store of your account.
• The app sets no cookies and uses no analytics or error-reporting services.

2. What the app reads

When an HR agent runs the app, it reads:

• the clock file the agent chooses, in the browser: the worker ids it contains (CPF, PIS or employee number) and the time of each punch
• from your Freshservice account, through the Freshworks platform and with the API key the admin enters: the requesters (and, if the key allows, the agents) with their name, email, language, reporting manager and the user fields employee id (the CPF, PIS or employee number the clock uses) and work schedule; the group ids entered at install, to check them
• the signed-in agent's id, name, email and language, to check that they belong to the HR group and to show the app in their language

This is used in the agent's browser to match workers to employees and compare their punches with the work schedules. The file and the punches are discarded when the run ends or the page closes.

3. What the app writes

Only when an HR agent asks for it, after reviewing the findings, the app writes to your Freshservice account:

• one ticket per employee, with the employee as requester, assigned to the group and workspace chosen at install
• one reply on that ticket with the days and findings, in the employee's language, with the employee's reporting manager in CC

Freshservice emails the ticket and the reply to the employee and the manager, as it does for any ticket.

4. What the app keeps

In the Freshworks app data store of your account, the app keeps:

• HR's definitions: work schedules, holiday calendars, CSV file formats, rules, ticket text and the names of the user fields
• a memory, for 12 months, of which employee (by Freshservice user id) had which day raised or dismissed, so a later run does not raise it again
• the run in progress, until it completes: the employees' names, emails, manager emails, and the selected days with their punch times and findings, so an interrupted run can resume
• the run history: date, period, file names, the HR agent's name and email, and how many tickets were raised

The clock file itself and the punches of days with nothing to adjust are never stored.

5. Installation settings

The admin enters a Freshservice domain, an agent's API key, the HR group id, the workspace and group for the tickets, and a language. Freshworks stores them; the API key is a secure parameter, encrypted by Freshworks and used only on Freshworks' servers. It never reaches agents' browsers, and Red Lotus never sees it. The app only calls your own Freshservice account's API.

6. Cookies and third parties

The app sets no cookies, uses no analytics, does no tracking, and loads no script or font from any third party.

7. Retention and deletion

The definitions, the memory of raised days, the run in progress and the history are kept in the Freshworks app data store of your account for as long as the app is installed; the memory of raised days is pruned after 12 months. Uninstalling the app makes Freshworks delete that data store. Tickets and replies it created are your account's tickets: uninstalling leaves them in place, and they can be edited or deleted like any others.

8. Data transfers

The clock file stays in the agent's browser. What the app keeps stays in the Freshworks platform, in the data centre region of your account. Red Lotus does not receive or transfer any of it. Where Freshworks hosts your account is set by your Freshworks agreement.

9. Your rights

Under the LGPD (Art. 18) and similar laws you may ask to confirm, access, correct or delete personal data. Red Lotus receives no data from the app, and everything the app keeps or writes is held in your Freshworks account, so the account owner controls it; we will help with any request. For other data in your Freshservice account, see Freshworks' privacy policy. Uninstalling the app stops all processing immediately.

10. Changes

We will post changes here and update the effective date. Material changes will be noted in the app's Marketplace listing.

11. Contact

Red Lotus Tecnologia da Informação Ltda., info@redlotus.com.br, or the contact form (subject "Privacy" or "LGPD").