Privacy Policy & Data Handling

The Qadamuni (Qadmoni) Restoration ("we", "us", or "our") uses a minimal-data approach, but some information is collected when you use specific features. Depending on how you interact with the site, this may include optional geolocation data for calendar calculations, basic analytics and article-view events, local browser storage for site preferences, and contact information you voluntarily submit through the Qahal dispatch form.

Qahal form submissions may include your name, email address, dispatch reason, message content, and anti-spam verification data. Article view counting records the article path and aggregate count; it is not designed as a member profile or behavioral dossier.

We use optional location data strictly to calculate local sunrise and sunset times so the calendar and chronology tools can reflect your local celestial cycle. We use analytics and article-view data to understand which pages are being used, to verify whether articles are being reached, and to make practical decisions about site maintenance and publishing.

We use Qahal form submissions to receive dispatches, review incoming questions, and, when appropriate, reply to the email address provided. Anti-spam verification is used solely to prevent abuse of the contact gate.

We do not store, harvest, or transmit your location data to our servers.

All location processing happens client-side (within your own browser). Your coordinates are temporarily passed to a public API at sunrise-sunset.org solely so celestial timestamps can be returned. Qadamuni (Qadmoni) does not maintain its own database of visitor coordinates.

The site currently loads Google Analytics to measure general site usage and page traffic. Google may process technical request data and identifiers according to its own service policies when that script runs in your browser.

Qadamuni (Qadmoni) also maintains a simple per-article view counter. That counter records the article path and an aggregate total in our D1 database. To reduce duplicate increments from repeated reloads in the same browser session, the site uses session storage on your device.

We also use local browser storage to remember site preferences such as theme selection and privacy-banner state. These local values are used for functionality and convenience rather than account profiling.

When you submit a dispatch through /qahal, the form sends your name, email, dispatch reason, message, and honeypot field to our /api/dispatch endpoint. If Cloudflare Turnstile is enabled, the form also sends a security-verification token so spam and abusive submissions can be screened.

Dispatches are then relayed through Brevo for email delivery to the configured Qadmoni inbox and for confirmation messages back to the sender. We use this information to review and respond to the dispatch, not to build a marketing mailing list or sell personal data.

We do not sell your data. We do, however, rely on third-party services that process limited categories of data to make the site function: sunrise-sunset.org for solar timestamps, Google Analytics for usage analytics, Cloudflare Turnstile for form abuse prevention, and Brevo for dispatch email delivery.

Aggregate article-view counts may remain in our D1 database as operational records. Dispatch emails and related message content may remain in the receiving inbox and transactional email systems for as long as reasonably necessary to review, respond, archive correspondence, or troubleshoot delivery and abuse issues.

Under the Philippine Data Privacy Act of 2012 and the General Data Protection Regulation (GDPR), you have the right to be informed about how your data is used and, where applicable, to request access, correction, objection, or deletion. Because some information is processed through third-party infrastructure, cross-border processing may occur depending on those providers and your location.

You may revoke browser location access through your device or browser settings at any time. If you have submitted a dispatch and want follow-up about that submission, use the Qahal contact route and reference the email address and message context involved.