1. Who is responsible for data processing?

Service operator: LiraX. A legal entity or individual entrepreneur that provides a specific service and acts as the controller of personal data: Tetracom ltd.

Contact for privacy issues: office@lirax.ua. Other ways to contact us are listed on liraX contact page.

If your organization uses LiraCRM to work with its customers, it can independently determine the purposes and scope of processing of data entered into the CRM. In this case, LiraX processes the relevant data within the scope of the service provision and the contract, depending on the distribution of roles between the parties.

2. What data can be processed?

System user data: work login, name, contact email address, role, access rights, and information provided by the organization administrator.

Google login details: a unique Google account identifier (sub), an email address, a verification token (email_verified), and, if Google provides them and they are required for sign-in features, first name, last name, and profile picture. Technical fields of the ID token, including iss, aud, iat, and exp, are also temporarily processed to authenticate the sign-in.

Technical data: IP address, date and time of access, browser data, technical login logs and security events - to the extent necessary for the operation and protection of the service.

Data that organizations place in CRM: customer contact information, content of requests, tasks, history of communications and calls, as well as recordings or transcriptions of conversations, if the relevant capabilities are enabled and used legally.

3. Login with Google

Function "Sign in with Google" used solely to verify the user's identity and match their Google account with an authorized LiraCRM account.

• LiraCRM does not receive password from a Google account.
• Basic login uses only standard authentication data (openid, email, profile), not access to Gmail emails, Google Drive files, or Google contacts.
• The ID token received from Google is verified by the server, including the cryptographic signature, expiration date, and purpose of the token.
• The sub ID can be stored to securely link the Google account to the LiraCRM account; the email address is used to map to the account defined by the administrator.
• The very fact of successfully logging into Google does not automatically grant access to LiraCRM: access is determined by the rules and user rights in the system.

Google information is used only for authentication and related account security purposes. It is not sold or used for personalized advertising.

4. What is the data used for?

The data is processed for the purpose of providing access to LiraCRM, verifying identity during login, managing accounts and rights, ensuring stable operation of the service, preventing unauthorized access, and performing CRM functions used by the relevant organization. For customer data entered by the organization into the CRM, the specific purposes of processing are determined by this organization and the relevant contracts.

The legal grounds for processing are determined depending on the circumstances and requirements of applicable law: performance of a contract, legitimate interest, duly obtained consent or other basis provided for by law.

5. Storage and protection

Account data and Google Account linking are retained for as long as necessary to access the service and fulfill relevant contractual or legal obligations. Security logs and CRM data are retained according to the rules and terms applicable to the specific service or organization. After the specified terms, the data is deleted or depersonalized, unless further storage is required by law.

Before publication, the operator must clarify the actual storage periods. account data, logs, and CRM data and, if necessary, include them in this section.

Appropriate technical and organizational measures are used to protect data, including secure HTTPS connections, verification of login tokens, and role-based access restrictions. No information system can guarantee absolute security.

6. To whom can data be transferred?

Access to data may be provided to authorized persons of the relevant organization, hosting and technical service providers to the extent necessary for the operation of the service, as well as to state authorities in cases provided for by law. If a specific configuration involves processing outside of Ukraine, it is carried out in compliance with applicable requirements for the transfer of personal data.

LiraCRM does not sell Google Account data to third parties. Access to other Google services is not requested for the Google sign-in feature.

7. Cookies and sessions

Technically necessary cookies or other session identifiers may be used to log you in and maintain an authorized session. They are used for authentication and security, not to access Google Account content. If the site additionally uses analytical or advertising tools, information about them and the necessary consent settings must be provided separately.

8. User rights

Within the limits of applicable law, you may request access to your personal data, its clarification, correction, erasure or restriction of processing, as well as withdraw consent if the processing is based on it. Questions about data entered into the CRM by your organization may require contacting that organization directly.

For inquiries regarding LiraCRM, please write to office@lirax.ua. You can also manage third-party app connections in your Google Account settings. Revoking access to Google does not necessarily mean that your account or CRM data will be automatically deleted.

9. Policy changes

The policy may change due to updates to LiraCRM features, data processing practices, or legal requirements. The current version is posted on this page, and the update date is indicated at the beginning of the document.

10. Contacts

LiraX — LiraCRM
E-mail: office@lirax.ua
Website: https://lirax.ua
Contacts: https://lirax.ua/uk/contacts/