Latest news

Effective date: 11 December 2025

1. Introduction

This policy describes what information we collect when you use Bacularis.app service. It also has information about how we store and use 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.app 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 Cookies

• The Bacularis.app website only uses cookies that are necessary for the website to function properly. These are session cookies.

3.2 Logs

We save web server logs from the Bacularis.app service.

The access log contains the following information about every request sent to the Bacularis.app service:

• 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.app service
• 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.app web service visit statistics.

3.3 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.