Community features are for respectful, non-diagnostic self-reporting and shared intentions. Spam, harassment, manipulation of aggregates and attempts to present community sentiment as scientific measurement are outside the intended use.
What a community check-in contains
A check-in is classified as COMMUNITY_SELF_REPORT. Optional energy, mood, sleep quality, calm, tension and creativity scores use a 1-5 scale, with optional dream and meditation categories. Country code is optional and only country-level. The form does not accept free text, precise location, IP address, user agent or account identity, and an individual submission is not made public.
When aggregates and Community Pulse are published
A public aggregate is available from the first eligible submission and a category from its first response. Supported windows are 1 h, 24 h and 7 days at global or self-reported country scope. Community Pulse is an authored index, not a physical quantity: six fields have equal weights and tension is inverted before normalization. Small samples are preliminary, and with additional check-ins the result becomes the mean of the current sample.
Abuse, duplicates and interpretation boundaries
The structural filter rejects records with an invalid schema, missing consent, invalid range, unsupported locale, duplicate submission_id or a timestamp outside the requested window. Submission infrastructure also requires an external rate limit. Spam, automated manipulation of aggregate results, harassment and presenting the aggregate as a diagnosis or geophysical measurement are outside the intended use.
4. Authenticity of anonymous check-ins
Community check-ins are voluntary self-reports. Mass fabricated scores, impersonating several participants and scripts intended to distort aggregates are prohibited. A score is subjective, so even a valid record is not an independent scientific measurement or certification of anyone's health. Submissions should describe the participant's own experience rather than unverified claims about another person. The system can reject entries violating schema checks, limits, required acknowledgements or duplicate prevention. Acceptance does not guarantee that a submission will be shown individually. GeoLira provides appropriate aggregates under the module's methodology rather than publishing each person's history.
5. Small sample sizes and limitations
An aggregate available after the first eligible submission is not a representative sample of a country, society or any demographic group. One answer can strongly affect the mean when participation is low. Visitors should inspect the response count and timeframe instead of interpreting a chart as a population survey or clinical assessment. Community views may cover 1-hour, 24-hour and 7-day windows at global or self-reported country scope. These do not establish verified residency or random sampling. The Service must not claim that a group mood pattern was caused by a space-weather measurement.
6. Harassment, discrimination and fraud
Threats, targeted harassment, unlawful discriminatory attacks, disclosure of private details, impersonation of moderators and scams seeking money or passwords are prohibited. Intention features, place suggestions and error reports must not be used to expose home addresses or material harmful to children. Lawful criticism of scientific data or spiritual interpretations is permitted and should not be removed merely because it is negative. Immediate danger should be referred to competent authorities. Reporting a concern to moderators does not replace emergency intervention or law enforcement.
7. Rights in submitted material
People uploading photos, place descriptions, comments or other materials must hold the required rights and permissions. Copying another person's photograph without authority, removing attribution or unlawfully publishing identifiable people are prohibited. A submission does not automatically transfer all intellectual-property rights to GeoLira. Technical handling can require storage, review, display or limited distribution according to the particular feature and licence. Disputed material may be restricted while a substantiated rights complaint is considered. Statutory rights and applicable challenge procedures remain available.
8. Reporting an alleged violation
An illegal-content notice should identify the material, explain why it is alleged to be unlawful and provide relevant context. Passwords, unnecessary sensitive information and unsafe files should not be supplied through ordinary reporting channels. Receiving a notice does not automatically establish a violation. Where DSA requirements apply to the particular hosting function, appropriate notice processing and statements of reasons must be provided. Decisions should reflect proportionality and context, including lawful criticism. A reporter does not automatically acquire the author's private information.
9. Proportionate moderation
GeoLira can apply proportionate restrictions to a submission or relevant function where spam, harassment, harmful content or manipulation is identified. The response should reflect the nature and seriousness of the issue. Incorrect data does not always justify blocking an Account, and negative opinions do not automatically breach the law. Affected users should be able to provide explanations where the law or applicable process requires it. Urgent protective measures should not continue unnecessarily after a matter has been resolved. Statutory judicial and DSA protections remain available where applicable.
10. Privacy, retention and voluntariness
Voluntary community check-ins are not public profiles of identified people. Forms should minimise information and display appropriate aggregates under the documented methodology. Such records have limited retention. Participating does not grant permission to use private journals for advertising. Users should avoid precise addresses, information about children and third-party medical histories. Where any record is linkable to a person, applicable data-protection duties remain relevant. Clearing browser cookies is not equivalent to erasing server records.