Your information

Privacywith Purpose.

1. Who operates this website

This website uses the name Kalash Conglomerate. This notice covers information submitted through its inquiry form and the technical information used to protect that form.

2. Information you provide

The form marks required fields with an asterisk. The current application collects:

Name & email
Required to identify the sender and provide a contact route for the inquiry.
Inquiry details
Inquiry type, interested business vertical (including “Not Sure”), subject and message are required to understand the request.
Organization & phone
Optional details to provide context and another contact route.
Consent evidence
The required consent selection, exact consent wording and UTC consent time are saved with a successful inquiry.
Internal records
The database assigns an inquiry identifier, creation time and status. The contact confirmation does not display the internal identifier.

Please provide only what is needed for your inquiry. Avoid passwords, account credentials, financial details, identity documents or sensitive personal information. There is no attachment-upload field. Share another person’s information only when you are entitled to do so.

3. How inquiries are used

The inquiry form collects information for understanding, handling and responding to your inquiry, and for keeping the form secure. The required checkbox does not request marketing permission or permission to distribute your inquiry to every listed business.

Successful inquiries are saved in the database. SMTP notifications and automatic email acknowledgements are not active in this submission flow. A website confirmation means the inquiry was stored; it does not establish that a person has read it or that an email has been delivered.

4. Security information & sessions

The server receives a connection IP address. The form uses that address to create a secret-keyed IP hash for abuse prevention. A saved inquiry contains this hash, and a separate rate-limit ledger contains the linked inquiry ID, hash, scope and UTC timestamp. These two tables do not store the raw connection IP address. A keyed hash is a pseudonymous identifier, not a guarantee of anonymity.

The limiter counts successfully saved inquiries from a connection within a rolling hour. The application default is ten; the private configuration can change the limit. This window is not a deletion schedule. Requests rejected before saving do not add inquiry or ledger records.

The contact form uses a session cookie for its security token, one-time result messages and replay protection. After errors, bounded non-message field values may be held in the server session so the form can be corrected. The error-session copy excludes the message body; an accepted message is stored in the database.

The production cookie is configured as kalash_contact, with path /, Secure, HttpOnly and SameSite=Lax settings. It has no persistent cookie lifetime. Closing a browser does not guarantee immediate removal of server-side session records; browser restoration may also preserve a session.

The code uses field validation, an anti-bot hidden field, CSRF and replay checks, prepared database statements and a transaction for the inquiry and its ledger entry. These controls do not promise complete security.

Hosting, CDN, firewall and access logs may separately contain raw IP addresses, URLs and request details. The IP hash stored by the form does not prevent these services from receiving connection information.

5. Who may access information

The form stores inquiries in the website database. Selecting a business vertical identifies the subject area of an inquiry; the form does not automatically forward it to a business or send it by email.

The page templates request fonts from Google Fonts. Loading those resources connects a visitor’s browser to an external provider, which can receive technical connection information. Links to business websites take visitors to separately operated sites.

6. Information retention

Inquiry details, consent records and linked security records are stored in the website database. The form does not automatically delete these records after a fixed period.

Inquiries & consent
Contact details, message content, consent wording and consent time are stored together in the inquiry record.
IP hashes & ledger
Security records are stored separately and linked to the inquiry. The rolling one-hour rate-limit window does not automatically erase them.
Server sessions
A browser-session cookie and its associated server-side records can have different lifetimes. Closing the browser does not itself delete the stored inquiry.
Logs & backups
Infrastructure logs and backups can have separate storage lifecycles. Removing a record from the live database does not itself erase backup copies.

7. Consent & privacy requests

You may choose not to submit an inquiry and may leave optional fields blank. When submissions are available, the form requires an affirmative, initially unchecked consent selection:

No marketing consent is requested. The database records the consent text and time with each inquiry.

For privacy questions or requests about access, correction, deletion or withdrawal of consent, contact contact@kalashconglomerate.com. Provide only the information needed to explain your request. The form has no self-service lookup, correction or deletion facility.

Handling a request may require proportionate verification. Withdrawing consent may prevent further consent-based handling of an inquiry.

8. Audience & other websites

This notice is scoped to website inquiries. A listed vertical or a link does not authorize onward sharing with all businesses. Other websites and services may explain their own handling in separate notices.

9. Contact & policy updates

Kalash Conglomerate
Privacy contact:

contact@kalashconglomerate.com

Refer to this page for information about the website inquiry form. You can use the contact address above if you have a question about this notice or the information you have submitted.