God’s Eye logoGOD’S EYESECURITY FORCEHere to help
YOUR INFORMATION

Privacy notice

God’s Eye Security Force uses this form to receive and respond to enquiries and to protect the service against misuse. Contact: contact@godseyesecurity.in.

What is collected

Your full name, age, email, Indian mobile number, selected reason and description are required. Please provide only information needed for your enquiry. Email and mobile formats are checked; ownership is not verified.

For service protection, rejected requests that match suspicious code, injection, command, encoded-payload, automated-sequence or request-tampering rules create a security-event record. That record contains the observed source IP and connection peer IP, event category/rule, affected field, input length, timestamps, occurrence count and one-way correlation digests. The blocked input itself is not copied into the security-event table.

When the contact page loads, even if you do not submit, a visitor record is created with your public IP, connection peer IP, server time and user agent. The browser then sends basic platform, language, timezone and screen dimensions where available. A random visit reference and keyed session reference associate updates with that visit. A daily keyed network reference groups the observed public IP for that UTC day; it is not a router ID or a verified identity. On submission, the enquiry is linked to the visit. Browser-reported information includes platform, language and timezone. This information can be inaccurate and is not proof of identity.

Required location

This form requests your device location when the page opens. Your browser decides whether permission is already granted or a prompt is needed. Saved permission may be reused on later visits in the same browser; temporary grants, private browsing, cleared permissions or browser policy may cause another prompt. The privacy checkbox is a separate mandatory acknowledgement before submitting. Your browser controls access and may ask you to allow location. If permission is already granted, it may provide location without another prompt. A reported location is required to submit this form. We do not bypass browser or operating-system permissions.

Unticking the checkbox prevents submission; it does not revoke browser location permission. Revoke permission in browser settings to stop future location access. If your browser provides location after permission is granted, coordinates, reported accuracy and device capture time are saved to the visitor log even without submission. Denial, timeout or unavailability is recorded as a status without coordinates. Unticking the enquiry acknowledgement does not erase an already recorded visit or location. We do not continuously track location or save unfinished names, ages, email addresses, phone numbers or descriptions. We do not infer age or collect marketing subscriptions from visits. Contact us to request deletion of a visit record. The server necessarily receives a connection IP when loading the page; hosting access logs may record visits.

Cookies and device details

An essential session cookie protects the form and administrator login. Basic browser information is sent to the visit log when the page loads. No raw session cookie or browser cookie is stored in the visitor record. The required acknowledgement includes agreement to a first-party recognition cookie. Accepting the acknowledgement can create a random signed cookie before submission; a successful submission also ensures it is stored for up to 48 hours, without extending its expiry on each visit. It recognises only this browser profile. A keyed hash is stored as the browser record ID; the raw cookie is not stored in enquiry records. A valid returned cookie is marked as returning; deleted, blocked, expired or invalid cookies cannot identify a returning browser. This is not authentication, a hardware ID or location permission. A valid recognition cookie from earlier consent is also used for later visitor logs. Without one, only the current session reference is available; no persistent recognition cookie is created until acknowledgement. Unticking the checkbox clears the current visit recognition and requests cookie deletion; if the request fails, delete the site cookie in browser settings. Earlier records keep their recorded identifiers without automatic expiry. To stop recognition, delete the site cookie in your browser. A later accepted submission may create a new cookie. Historical submissions retain their original recorded consent without automatic expiry. We do not collect other websites’ cookies, MAC addresses or private device IPs.

Access and retention

Visitor logs and enquiries are accessible through authorised database access and the protected administrator interface. Original enquiry and visitor payloads are encrypted. Ordinary visitor IPs, location and user agent are readable through the protected admin view, not plaintext visitor database columns. Visit references, keyed correlation identifiers, consent/status, linked enquiry reference and timestamps are stored as indexed database metadata. No readable visitor copy is created. During enabled testing, a readable copy is also stored for inspection through phpMyAdmin; database exports and backups can include that copy.

Security-event records are stored separately for abuse investigation and include the observed source and connection peer IP addresses as security metadata. They do not store the raw blocked payload. Visitor logs, enquiries, readable enquiry testing copies, application audit records and security-event records are retained without an automatic expiry date, including older records still present in the database. They remain available to authorised administrators until deliberately deleted by an authorised operator. Scheduled cleanup removes only expired rate-limit counters. Browser recognition cookies still expire after up to 48 hours, and security sessions still time out; these do not delete saved records.

Hosting access logs and backups are managed separately by the hosting provider and may be retained longer. Deleting a live record does not automatically erase historical backups. Contact us for retention, access, correction or deletion requests.

Your choices

You can revoke location permission in browser settings and delete site cookies. If you decline location or your device cannot provide it, this form cannot be submitted. You can email contact@godseyesecurity.in instead. To discuss an enquiry or a privacy request, email contact@godseyesecurity.in and quote your enquiry reference where available.

Notice version: 2026-09-24-v9

← Return to contact form