What we collect
Public forms may collect listing details, sources and private submitter contact information. Administrator applications collect identity, experience, requested service area and consent records. Basic security logs may include an IP-derived request identifier, time and action. Privacy-friendly analytics record aggregate daily visits and coarse country, region and city information supplied by Cloudflare; raw IP addresses and individual visitor profiles are not stored for analytics.
What becomes public
Approved place, institution, shrine and event information may be public. Submitter contact information is not public. A personal contact may appear only when explicit publication permission and its date are recorded; institutional contact details are treated separately.
Administrator applications
Administrator applications are private and visible to the Super Admin. Applying does not create access. The application includes contact details, an official state and district code, local connection and the applicant’s reason for applying. Phone verification is completed manually.
Photos and posters
Event posters are re-encoded in the browser and stripped again on the server before storage to remove common camera and location metadata. Submitters must have permission to share uploaded media. A Super Admin decides whether a poster is appropriate to publish.
Retention and requests
Records may be retained for safety, correction history, rate limiting and accountability. Request-rate identifiers are created with a protected one-way key rather than storing the raw address in the rate-limit table. You may request correction, removal or access through the Report a Concern page. A report creates a review request; report volume alone does not automatically remove published information.
Contact
Email privacy questions to globalshias@gmail.com.