Tower Rush India privacy and enquiry processing

What data an enquiry contains

The editorial form provides for a name, email, subject and message. You may also add a link to the page your question concerns: this field is optional. The link identifies specific content, while the subject and text explain the enquiry. The recipient is the editorial mailbox on the project's own domain.

The editorial question form and the data request form serve different purposes. The first is for communication about the guide's content; the second concerns the processing of information relating to you. Similar fields do not turn an article enquiry into a marketing request or mean that a reader account is created.

Separate consent is provided for processing an enquiry. A marketing subscription is not automatically included when a form is submitted. The website's minimal service set has no newsletter, subscription provider or advertising database; an email supplied to contact the editorial team should therefore not be treated as registration for promotional emails.

Information you should not send

Passwords and payment documents are not collected through the editorial form. Do not attach them to prove that you read an article, registered with a casino or placed a bet. A question about the guide's content can be described without access to your gaming account or information that would allow someone to log into it.

KYC documents go to the operator verifying its customer. The editorial team does not replace that channel or use the website's age notice as documentary identification. The same distinction applies to readers in India: contacting an article's author and verifying a payment instrument's owner are different procedures with different recipients.

How long enquiries and technical records are retained

An enquiry's working record and email copy are retained for 90 calendar days after the enquiry is closed. The period is tied specifically to closure, not to each time an editorial employee opens the email. Rereading does not start a new ninety-day period or by itself change the event from which retention is counted.

Service delivery and error logs have a separate period of 14 days from the event. These are different records with a different purpose: they concern website operation, not gaming cashier content. Payment content is not recorded in these logs, and the editorial team does not receive events from your operator bets through them.

Backups follow a 30-day rotation. The period starts when the copy is created. Deleting an enquiry from the working database and removing its backup may therefore happen at different times: these are two separate processes, not two names for the same deletion operation.

Deleting the working record and the backup

After the period expires, the working record is deleted unless a separate obligation requires its retention. A backup's existence does not mean the enquiry must remain available in the working database. The last copy containing it leaves through its own thirty-day cycle; immediate disappearance of every copy at the moment of working-record deletion is not assumed.

Restoring a backup must not return expired enquiries to the working database either. Otherwise, a technical restoration would effectively create a new retention period for a message already deleted. The enquiry retention rule continues to apply after restoration: backups are not a way to extend it repeatedly.

These periods cannot be added into one period for all information. Fourteen days relate to a log event, ninety to enquiry closure, and thirty to backup creation. Records may have different starting points, so one category's calendar does not automatically determine another's.

If your question concerns retention, identify the enquiry and record category involved. Distinguishing an email, working record and backup helps define the request without submitting payment documents. Sending such a question should not be understood as confirmation that deletion has already occurred in every system.

Language preference and available services

A setting in the browser's local storage is provided for language selection. It concerns the guide's presentation and is not a gaming profile.

Third-party analytics, advertising cookies and advertising pixels are not enabled on the website. The technical language preference is separate from analytics and advertising: its presence does not mean those categories are connected. The website also does not receive betting events for advertising tracking or maintain a newsletter subscriber database.

The website displays an AI assistant preview. It returns a fixed availability message without generating answers or creating an assistant conversation history. The website does not send requests to an AI provider on behalf of this feature. External model conversation-retention settings do not apply here: text you send to the editorial team through a form is treated as an editorial enquiry.

User comments are disabled; no moderation log for them is created. Reader registration is not used either. These features must be distinguished from operator websites: a casino's personal account, chat or comments do not mean an equivalent feature and database exist at Tower Rush India.

How to ask about your data

For a question about editorial enquiry processing, use the contact page or editorial email. State the subject so that it concerns our website's data. Send a casino financial complaint separately: the editorial contact does not control access to funds in a gaming account.

1. State that you are enquiring about data provided to Tower Rush India.
2. Describe the relevant message or content; add a link to the guide page if needed.
3. Do not share a gaming account password or attach payment documents instead of explaining the question.
4. If the enquiry concerns KYC, a bet or a withdrawal, use the relevant operator's channel rather than the editorial form.

Where this policy's scope ends

The policy describes Tower Rush India's data and does not replace the terms of Galaxsys, a casino or a payment service. Moving to another participant changes the subject of the interaction: the developer is responsible for its product, the operator for its own account and cashier, and the editorial team for the guide and enquiries about it.

Read more about the project's role on the about the editorial team page, and about the content's purpose in the terms of use. The affiliate disclosure and methodology explain other aspects of the guide's work while maintaining this division of responsibility.