Content Policy — Krepusko
1. What may be submitted
Krepusko permits only one of four fixed observation categories: saw the crescent with the unaided eye, saw it with optical aid, looked and did not see it, or could not see the horizon. Optional details are limited to fixed viewing-duration and sky-clarity choices. No other user content is accepted.
2. What is never permitted
- Child sexual abuse or exploitation, CSAM, grooming, solicitation, sextortion, or child endangerment.
- Threats, harassment, stalking, coercion, discrimination, or attempts to identify an observer.
- Automated, duplicated, coordinated, manipulated, or deliberately inaccurate submissions.
- Attempts to bypass geographic weight caps, time checks, cryptographic identity controls, reporting, blocking, or moderation.
3. Privacy by structure
Observations have no public author, name, profile, message, photograph, comment, follower relationship or precise location. The app displays regional aggregates, never a feed of people. A 5 km cell has fixed model influence regardless of the number of devices reporting from it.
4. Reporting, hiding and review
Use “Report this regional summary” on the Evening screen to choose a fixed safety, coordinated-misuse, or data-integrity reason. Use “Hide this region” to block it immediately on your device. A cell is auto-hidden after the flag threshold while the developer reviews it. Reports made in bad faith may be rate-limited.
5. Enforcement
We may hide or delete observations, remove them from fitted evidence, limit a reinstall-specific key, preserve necessary safety evidence, and notify authorities where legally required. The physical Danjon limit is absolute and cannot be changed by the number of reports.
6. Withdrawal and retention
The submitting device can withdraw its shared observation in no more than two taps, even while offline. Shared observations and safety flags are deleted after 25 lunar months at the latest. Fixed fitted observer parameters are internal derived state, never displayed or returned by the API, and are regularly recomputed rather than archived.
7. Contact
For moderation or safety concerns, contact Saifullah Ahad at [email protected]. For child-safety matters, read the separate Child Safety Standards.