Effective date: 25 August 2024

1. Introduction

This policy describes what information we collect when you use Bacularis.com services: the Bacularis.com Website, the Users.Bacularis.com User Panel, Packages.Bacularis.app and Packages.Bacularis.com Package Repositories. It also has information about how we store, use, transfer and delete that information. We inform about it not just to comply with the privacy law. We would like you to trust us.

2. Data controller

In compliance with EU General Data Protection Regulation (GDPR) we provide you information about the processing of your personal data in our services.

Baculus Marcin Haba is the data controller who is responsible for the processing of Users’ personal information in the Bacularis.com services.

Contact parameters: Baculus Marcin Haba with the Tax Identification Number PL6452306864 and office at Strzelców Bytomskich 45B/22, zip code 41-902, Bytom, Poland.

3. Collected user data

What information do we collect?

3.1 Account information

We ask users to provide the following account information:

• E-mail address. It is used to identify your user account in the User Panel. This e-mail address is a login used in to sign in in the User Panel.
• Password. It is to use the User Panel as registered user and to give users access to the User Panel.

3.2 Billing information

We ask about the following billing information:

• Company name, company address and tax identification number. We use it to process your purchase transactions in the User Panel. Using it we are able to issue an invoice.

3.3 Contact information

We also ask users to provide the contact information such as:

• Contact person name. They are first and last name. We use this name to contact the User Panel users. If the User Panel user uses the support service, this e-mail is also used in the internal ticketing system.
• Contact person e-mail. We use this e-mail address to contact the User Panel users. This e-mail address is also the main form of contacting with the users that use the support service. This address can be the same as login e-mail or it can be different.

3.4 Search data

• Search queries typed in the search field in the Website. We use this information to understand what users are most likely to search for.

4. Collected logs

We saves logs from server applications used by Bacularis.com services.

4.1 Access logs

The access log contains the following information about every request sent to the Bacularis.com services:

• Visitor IP address
• Request date and time (ex: 02/Jul/2024:08:01:50 +0200)
• Request HTTP method (ex: GET, POST...etc.)
• Requested path (ex: /services/packages)
• Request HTTP error code (ex: 200, 404...etc.)
• Request size in bytes
• Refferer address - previous address that led to the visit
• User agent information that did the request (ex: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36)

We use the web server access log in the Website:

• for identifying potential dangerous behaviours, requests and attacks on Bacularis.com services
• for identifying people who behave in the manner described in the previous point
• for statistical purposes. The access logs are processed by the Awstats tool to display in friendly form the Bacularis.com web service visit statistics.

We use the web server access log in the User Panel:

• for identifying potential dangerous behaviours, requests and attacks on Bacularis.com services
• for identifying people who behave in the manner described in the previous point
• for statistical purposes. The access logs are processed by the Awstats tool to display in friendly form the Bacularis.com web service visit statistics.

We use the web server access log in the Package Repositories:

• for statistical purposes. The access logs are processed by the Awstats tool to display in friendly form the Bacularis.com Service visit statistics.
• to get information about the packages popularity.

4.2 User Panel log

In the User Panel log are written the following data:

• Request date and time (ex: 2024-07-16 04:41:32)
• Visitor IP address
• Visitor login e-mail address
• Log level (ex. Warning or Error)
• Log type (ex. Security, Application, External ...etc.)
• Log body message

All these User Panel log data are needed to keep the panel application healthy, to diagnose any unexpected application working and to protect against dangerous user behaviours.

5. Passwords

• The User Panel account access password is not stored anywhere. We store the User Panel password hash prepared with additional cryptographic salt.
• We do not send typed password to the system logs and do not remember them in any other way.

6. Support data

For realizing the support service the Support Team may ask you about sending data such as:

• system logs
• Bacularis debug logs
• system command outputs
• Bacularis web interface screenshots

We use this data to realize the Support Service for users. All this data is stored in the Support Team mailbox, from where it is imported and processed by the osTicket ticketing system.