GeoLira contact and support details
Project, team and operator
The GeoLira project and brand are owned by the creative team GeoLira Team. BOMEGA SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ operates and maintains the service and acts as personal data controller. Contact: [email protected].
What you can report
GeoLira contact covers four main areas: data or source discrepancies, service defects, accessibility feedback, and account or privacy matters. A useful data-quality report includes the affected view, approximate observation time, visible source_id or provider name, and a description of the discrepancy. This allows the report to be traced to a specific record instead of only to a screenshot.
Contact and operator information
You can contact the service operator about privacy, accessibility, data quality and account support at [email protected]. Please include only the information needed to handle your request.
What to include and what not to send
A technical report is easier to reproduce when it includes the route, approximate time, browser and device, steps that trigger the problem and a screenshot without sensitive information. Do not send passwords, login codes, API tokens, private keys or the full contents of a private journal. Privacy matters should use the dedicated privacy contact when one is present in the confirmed operator profile.
5. Reporting scientific-data problems
Questions about geomagnetic activity, Schumann resonance, space weather, the Moon or Earth maps can be sent through GeoLira's contact channel. Useful details include the page, visible source identifier, observation time and a description of why the display appears wrong. A screenshot may help, but it does not replace the record reference and relevant context. A public chart correction should not require sending an entire Account profile or private journal. Safety-critical decisions must also rely on original official sources. A report permits investigation but cannot guarantee immediate changes at an independent provider.
6. Account and private-feature enquiries
Questions about login, journals, dream notes, data exports, correlations or notifications are easier to investigate when the affected feature and approximate time are included. Support may need proportionate information to verify Account authority but should not request the password in routine correspondence. Unnecessary health or relationship details should not accompany a technical report. Where the device or browser could contribute, the product name and version can help. Active session tokens, authentication codes and API keys must not be shared. A suspected compromise should also prompt protection of the associated email and authentication settings.
7. Privacy requests and personal-data rights
Requests for access, correction, erasure, restriction or objection can be submitted through the official privacy channel. A useful request identifies the action sought and allows appropriate verification of the authorised person. Full journal notes are not needed merely to ask about retention or copies of information. Individual rights are handled under GDPR conditions and statutory timeframes. Proportionate clarification may be requested where justified. Competent supervisory complaints and judicial protections remain available. Routine support cannot replace public authorities in an emergency.
8. Illegal content and security concerns
A notice about unlawful material, harassment, copyright infringement or a harmful link should identify the precise item and reasons for concern. Users should not submit executable malicious code or unnecessary personal data about others. Filing a report does not automatically prove a violation. Support may restrict particular material, request clarification or take another proportionate measure. Where DSA duties apply to a feature, the relevant notice and statement-of-reasons requirements must be observed. Immediate threats to people or property require competent emergency authorities.
9. Licensing, media and collaboration
Questions about chart reuse, quotation, widgets or editorial collaboration should describe the proposed use and the exact material. Access to GeoLira does not grant an unlimited commercial licence for every scientific resource obtained from external providers. The relevant source conditions and credits must be assessed. GeoLira Team owns the project and brand, while individual data suppliers retain rights in their own materials. A technical reply does not automatically grant a trademark, third-party graphic or restricted-data licence. Specific materials can be identified for a clearer rights enquiry.
10. Contact response and channel limitations
Email is available for enquiries and reports about the Service. Response handling depends on the issue, available information and relevant statutory duties. Ordinary support must not be presented as a round-the-clock medical hotline, official warning authority or guaranteed immediate intervention. Critical matters require the appropriate external emergency or specialist channel. Members can retain the submission date, message contents and a suitable reply address. Passwords, complete medical records and unnecessary private data about others must not be sent. Consumer and personal-data rights remain in force independently of the timing of a routine support reply.
Service operator
- Legal name
- BOMEGA SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ
- Jurisdiction
- PL
- Contact
- [email protected]
- Privacy contact
- [email protected]
- Address
- ul. Długa 2B
56-416 Twardogóra
Polska - Registration ID
- KRS 0000841054, NIP 9112034523
- Contact URL
- https://geolira.com/contact