Privacy Policy

Férias CLT 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).

Férias CLT ("the app") is a Freshservice app that manages Brazilian CLT vacation: it derives each employee's acquisition and concession periods from the admission date, checks vacation request tickets against the statutory rules, posts the verdict on the ticket, opens expiry tickets for HR and exports days to payroll. This policy explains what data the app handles and where it goes.

1. Summary

• The app has no backend and no server of its own. Its pages run in your agents' browsers, its daily job runs on the Freshworks platform, and every record it keeps lives in the app's own storage inside Freshworks, in the region of your Freshworks account.
• Red Lotus receives no data from the app, operates no service it talks to, and cannot read your records. Nothing is sent to any third party.
• The app stores no CPF, no e-mail address, no salary and no money amount. It records days.
• The app sets no cookies and uses no analytics, tracking or error-reporting services.
• Under the LGPD and the GDPR you (the customer) are the controller of your employees' data. The app processes it on your behalf, inside your own Freshworks tenancy, without any of it reaching us.

2. What the app reads

Through the Freshworks platform and with the API key the admin enters, the app reads from your own Freshservice account:

• requesters and agents: name, id, e-mail, reporting manager, department, location, active flag and language, to list the employees, find the approving manager and the team, and address the notes in the employee's language
• the requester fields you map: the admission date and, optionally, the termination date, CPF, employee or badge number and work schedule, to derive the periods, close a record on termination, match the lines of a history import, print the payroll export and find the rest day
• the vacation request ticket: its service item, the dates and days asked, the abono and 13th-salary advance flags and its approval status, to check the request and record the splits
• groups, departments, locations and the service catalog, for configuration and the holiday calendar per location

3. What the app stores

The app keeps its records in the Freshworks platform's key-value storage for this app, inside your account:

• Settings: which fields and service item are mapped, the holidays you add, the thresholds.
• One record per employee with an admission date: the employee's Freshservice id and name, the admission date, each acquisition period with its entitlement, absences, the splits taken or scheduled (dates and days), the abono days, the expiry ticket id, and the history of HR corrections (which agent id, when, what changed).
• Per-month indexes: the names, dates and ticket ids of the scheduled and taken vacations of the month, for the calendar and the daily job.
• One record per vacation ticket: the verdict the app wrote (status, splits, findings).
• Requests being registered on behalf: the draft, until the ticket exists.

The CPF and the employee number are read from the requester fields only when a history import is matched or a payroll export is built, and are written only to the CSV file your HR agent downloads to their own computer. They are never stored by the app.

4. What the app writes

The app writes to your Freshservice account, in the employee's language:

• public notes on the vacation ticket: the verdict, the vacation notice and receipt on approval, the days released on a rejection or cancellation
• expiry tickets for HR, with the employee as requester and the manager in copy, and their warning notes
• the tickets HR registers on behalf of employees

All of these are in your account and follow your Freshservice retention.

5. Installation settings

The admin enters the Freshservice domain, an API key, the HR group and a few mappings. Freshworks stores them; the API key is a secure parameter, encrypted by Freshworks and used only on Freshworks' servers, inside request templates that pin your own Freshservice domain. It never reaches agents' browsers, and Red Lotus never sees it. The app calls no host other than your Freshservice domain.

6. Cookies and third parties

The app sets no cookies, uses no analytics, and does no tracking. There is no third party, no sub-processor and no international transfer introduced by the app.

The app loads Crayons, Freshworks' own component library, at a fixed version from the jsDelivr CDN. As with any web request, jsDelivr receives the agent's IP address and browser details when it serves those files. No employee or ticket data is sent to it.

7. Retention and deletion

The records stay as long as the app is installed. Uninstalling the app deletes its storage: the Freshworks platform clears an app's records on uninstall. The notes and tickets the app wrote in Freshservice are yours and stay with your tickets.

A terminated employee's record is closed, not deleted, so the proportional vacation of the last period can be exported to payroll. The app offers no per-employee deletion: the records are removed together when the app is uninstalled.

8. Your employees' rights

Under the LGPD (Art. 18) and similar laws an employee may ask you to confirm, access, correct or delete personal data. Everything the app knows about an employee is visible on the Periods tab (periods, splits, corrections and their history) and can be corrected there by the HR group. Erasure of one employee's record is done by uninstalling the app. There is nothing to request from Red Lotus, because Red Lotus holds nothing; we will help with any request.

9. Security

• Only agents in the HR group you configure can open the app's pages. Other agents see one sentence. The ticket sidebar shows the requester's periods to the agents who can already open the ticket.
• The API key is a secure installation parameter, encrypted at rest by Freshworks.
• The app logs nothing to the browser console in normal operation; the daily job logs a one-line reason for each employee or ticket it skipped, with ids only, in the Freshworks serverless log of your account.
• The app does not compute or store pay.

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, privacidade@redlotus.com.br, or the contact form (subject "Privacy" or "LGPD"). Support: info@redlotus.com.br.