GeoLira Cookie and Browser Storage Policy, version 2.0, updated 5 November 2026.
1. Cookies and storage
Cookies are information stored on a device and sent to a website on subsequent visits. GeoLira also uses localStorage, sessionStorage, service workers and cache storage. These technologies operate differently. This Policy explains their functions and available user controls.
2. Operator and brand owner
The GeoLira project and brand belong to GeoLira Team. The website operator and personal data controller is BOMEGA SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ, Długa 2B, 56-416 Twardogóra, Poland, KRS 0000841054, NIP 9112034523. Contact [email protected].
3. Essential login cookies
When users sign in, WordPress may use authentication and session cookies to maintain access and secure private features. Blocking these may prevent account-related services. Cookie duration depends on WordPress configuration and login preferences.
4. localStorage
GeoLira saves view preferences and interface settings in localStorage. Unlike cookies, these values are not automatically sent with each HTTP request. They may remain until cleared by the user or website. Removing storage may reset interface preferences.
5. Submission receipts
The browser may store identifiers and deletion tokens for anonymous community submissions. The local list is limited to 90 receipts. Clearing browser storage may remove the credentials needed to delete an anonymous entry independently.
6. Software updates and offline support
Service workers and cache storage may save application resources, version indicators and recovery state to help load pages and update the application safely. These functions are not intended for advertising tracking. They can be cleared through browser website-data controls.
7. Advertising and analytics
The current GeoLira release does not contain Google Analytics, Facebook Pixel, Hotjar, Segment or similar external advertising and analytics scripts. Infrastructure suppliers may still process necessary technical connection details. If optional technologies requiring consent are later introduced, this Policy and required consent controls must be updated before activation.
8. Traffic protection
Hosting, content delivery and security providers, including Cloudflare, may use technical mechanisms to identify abnormal traffic and process connection information. Details depend on current provider settings. The Privacy Policy explains personal data processing associated with these services.
9. Consent and necessary functions
Under Article 399 of the Polish Electronic Communications Law, storing or accessing information on a device generally requires prior information and consent, unless a statutory exception applies, including transmission of a communication or a service expressly requested by the user. Optional technologies that legally require consent should not be activated before consent is obtained.
10. Managing site storage
Users can review, block or clear cookies, localStorage, sessionStorage, cached files and service workers in their browser settings. Removing authentication cookies may log a user out; deleting stored submission tokens may prevent self-service deletion. Contact [email protected] for further information.
11. Changes
This Policy is linked from the website footer. It may be updated if technology, providers or legal requirements change. Updating the text does not replace collecting consent where required. Version 1.0 of 3 November 2026.
12. Session cookies and Accounts
WordPress cookies can maintain an authenticated session, check access to private areas and help protect operations against unauthorised requests. A session identifier is not the same thing as a member's journal content. Cookie values should not contain complete private notes, even when they let the Service recognise an active authenticated session. Blocking all cookies can prevent login and protected data entry. Deleting a cookie does not erase the server-side Account, journal records or reports already made. On shared devices, members should sign out through the proper control and avoid saving credentials without suitable protection.
13. Local storage and interface preferences
GeoLira can use localStorage or sessionStorage for selected interface preferences, such as widget appearance, recently selected views or display settings. These mechanisms differ from cookies automatically sent with HTTP requests. Depending on the storage type and browser settings, values can remain on the device after the browsing session ends. Clearing site storage may remove local preferences and require configuring the interface again. It must not be treated as a server-side personal-data erasure request. Access to private entries depends on separate Account permissions. Shared-device users should be careful that a later visitor cannot see settings or information left accessible through an open session.
14. Service workers, cache and offline views
The application can use service workers and cache storage to retain interface resources, speed up loading and provide limited access to previously fetched views. Cached data may be older than the latest scientific measurement at the provider. A chart remaining visible in cache does not prove that physical conditions have stayed unchanged. Members can refresh the page, inspect measurement timestamps or clear site data when a view looks stale. Deleting cache does not automatically erase Account records on the server. Offline availability varies by actual release and device, so cached views must not be relied on as official emergency warnings.
15. Language and timezone preferences
The interface supports multiple languages and can remember language or timezone settings through Account controls and browser storage. A locale preference changes labels and presentation but does not change the actual time a measurement was taken. Changing the timezone may display a different calendar date for the same underlying event. Language storage is not marketing consent. Not every interface translation necessarily includes a separately legally reviewed version of every policy. Current Polish and English legal documents should be distinguished from the wider set of interface languages. Clearing browser storage can reset a previously selected preference.
16. Embedded widgets on external sites
Using a GeoLira widget embedded in another website can generate requests for resources from GeoLira or another identified provider. Depending on the actual implementation, ordinary technical connection information can be transmitted. The embedding website's owner should assess what additional information or consent is required for device technologies on their own site. Embedding a public chart does not authorise access to the member's private Account records. Browser security controls can affect embedded content. GeoLira does not automatically control every third-party script added by the embedding website's operator. Visitors should check the source address and avoid untrusted code impersonating an official widget.
17. Connections to data and map providers
Scientific views and maps can use resources from external services with independent infrastructure and privacy practices. Not every scientific-data request involves an advertising cookie, and not every browser integration means a private journal is transmitted externally. The actual information involved depends on whether GeoLira's own server or an independent provider handles the request. If a future integration places optional tracking identifiers on a device, legally required information and consent must be supplied before activation. Providers can change technologies and conditions, so the notice should be kept aligned with the actual configuration. Further information about personal-data transfers appears in the Privacy Notice.
18. Consent and exceptions for necessary technology
Storing or reading information on a device is governed by applicable electronic communications law, including Polish law and relevant EU requirements. Strictly necessary transmission or a function expressly requested by the user can qualify for a statutory consent exception. That exception does not automatically authorise unrelated marketing analytics, behavioural advertising profiling or unnecessary identifiers. Where technology is optional and the law requires consent, the person should receive a clear choice before it is activated and a way to withdraw consent as appropriate. General acceptance of Terms is not a substitute for a separate device-storage choice. Refusal should not unjustifiably disable independent features that do not require the optional technology.
19. Browser settings and local deletion
Most browsers let users inspect or remove cookies, local storage and site information or restrict future storage. Clearing these records can sign someone out, reset display preferences or cause resources to be downloaded again. It does not replace export or erasure of Account-linked information in GeoLira's server database. Before clearing local data, members should confirm that important records have been saved in the appropriate Account feature. People using shared computers should sign out and protect browser data. Personal-data requests belong in the appropriate privacy process rather than relying on deleting browser history.
20. Technology updates and user questions
GeoLira may change file names, expiration settings and libraries as the application evolves. This Notice should describe the actually deployed technologies; a tool mentioned in a repository is not proof that it runs for every visitor. Material changes of purpose should be assessed for information or consent obligations before deployment. Questions about cookies, local storage, cache, widgets or personal information can be sent through the official contact page. A general problem description and browser version are normally sufficient for an initial enquiry. Active session cookies, tokens, passwords and third-party information should not be submitted. The Privacy Notice explains broader processing rules and individual rights.