Website policy

Privacy Policy

This policy explains what this independent platform receives, how the reporting service is controlled, and the limits that still apply.

Information received

The website may receive information that you voluntarily provide through its reporting route. This can include your message, country, optional name, optional mobile number and optional email address. File uploads and attachments are disabled at the form and server.

Anonymous reporting and identity data

Name, mobile number and email address are optional. When supplied, contact details are stored in a separate table linked to the report reference. This is technical separation, not independent organisational separation, and it does not prevent an authorised platform administrator from accessing linked records.

No online service can promise absolute anonymity. Hosting and network providers may process technical request information independently of this website. Do not use the form for an emergency; contact the appropriate emergency service or law-enforcement authority directly.

Storage, encryption and delivery

The form uses HTTPS POST and the website enforces HSTS. Reports are stored in Cloudflare D1. Cloudflare documents that D1 encrypts stored database objects using AES-256 GCM and protects transfers between Workers and D1 with TLS. This is provider-backed technical evidence, not an independent audit of Cloudflare by the website operator.

A successful submission is stored with a reference and status for manual review. It is not automatically emailed, published or forwarded to an authority. Submission does not guarantee investigation, referral or a particular outcome.

Access and operating ownership

The application exposes no public route for reading report or contact records. At the latest operational verification, the Sites project had one owner and no additional editors. Nitish Jindal is the website operator and the contact for reporting-data questions at nj@nitishjindal.com. Hosting-provider administrative access remains governed by the provider's own controls.

Rate limiting and operational logging

The reporting endpoint limits repeated submissions using a short-lived pseudonymous hash derived from network and browser request data. The current application limit is five accepted attempts per 15-minute window. Rate-limit records are purged after one day.

Cloudflare Worker invocation logs are active. The application also writes a minimal event record containing the report reference, event type and time; it does not deliberately copy report text or optional contact details into application log messages. Provider-generated request logs may contain technical request information under the provider's logging controls.

Retention and deletion

New reports and linked contact details are assigned a 180-day retention end. The application deletes expired report records, linked contact details and related event records during a subsequent reporting-service maintenance cycle. This does not guarantee deletion at the exact second the period expires. Provider recovery copies may remain for the applicable backup-recovery window.

To request earlier deletion, email nj@nitishjindal.com with the report reference and enough information to assess the request. A record may need to be retained where required by law or necessary for a responsible safety or legal process.

How information may be used

Information may be used to review a report, seek clarification where contact details were supplied, protect the website from abuse, or prepare a responsible referral to an appropriate authority. Reports are not automatically forwarded.

External services and questions

The homepage may load market information supplied by TradingView and link to X, Ground News and other external services. Those organisations apply their own privacy practices. For a privacy question, correction or deletion request, email nj@nitishjindal.com.

Effective: 2 August 2026 · Revised: 2 August 2026