Who is responsible for your information
Ariful Hosain is the responsible publisher and the person responsible for personal data. Send questions about your information to [email protected]. Editorial correspondence reaches Ariful in his editorial role; technical logs go to the site administrator.
This policy covers the publisher's website and contact routes. The site does not operate a casino, accept bets or provide a cashier. Casino registration happens with the external operator. Sending a message here does not create a gaming account or give the editor access to your casino balance.
What the contact form and technical logs contain
The contact form collects your name or pseudonym, email address and message text for the editorial team to handle your enquiry, with separate purposes for a factual correction and a personal-data request and only the information needed for the relevant message.
Messages, consent and the recipient
Because a message submitted through the form is directed to the editorial mailbox and stored there as a separate email copy, a question about its storage or deletion needs to distinguish the original form record from the correspondence held in that mailbox.
Before submitting a form, give the separate consent for processing your enquiry. This consent does not include a marketing subscription. There is no newsletter subscription attached to a message. You can read the site's content without giving consent to submit an enquiry.
Use a pseudonym if you prefer. Give an email address at which you can receive a reply. Keep the message focused on the correction or data question. The form does not require your casino credentials or financial details, and sending them does not help the publisher resolve a gambling-account issue.
For an ordinary correction to an article, use the editorial contact page; for a question about information already held in your correspondence, use the privacy address above and identify the relevant message.
Technical records and hosting
Technical logs contain the IP address, browser user-agent and event time, and are received by the administrator rather than used as advertising profiles. A user-agent describes the browser or software making the request; it is different from the name or pseudonym you type into a contact form.
The website uses static hosting in the EU, with enquiry data kept separately from the static site. Full casino payment details are not passed to the editorial website. The location of the static hosting does not mean that a visitor in Bangladesh has opened a casino account in the EU.
Cookies, tracking and visitor features
Only necessary technical cookies for the contact form and session settings are enabled. Analytics and marketing cookies are disabled. No third-party analytics provider is connected. Advertising pixels are also disabled, and advertising data is not sent to advertising networks.
The site's visitor features are limited to the stated contact functions:
- No reader accounts: the editorial website does not collect a reader-account password or financial details.
- No public comments or player ratings: your message is not a submission to a public discussion feed.
- No newsletter: an enquiry email address is not added to a mailing subscription.
- No visitor AI chat: reader questions are not automatically transferred to an AI model, and there is no site-side AI conversation history or storage with an AI provider for this feature.
Private technical logs remain separate from visitor profiling, and a refusal to provide form consent does not prevent you from reading the site's articles.
How long records remain and what deletion changes
Retention runs from the event assigned to each record, so the same enquiry can have different expiry dates in the form system and the editorial mailbox. The table gives the starting points for form records, mailbox copies, technical logs and rotating backups.
| Record | Retention period | When the period starts |
|---|---|---|
| Contact-form record | 180 days | Final closure of the enquiry |
| Email copy in the editorial mailbox | 180 days | Sending the reply |
| Technical log | 30 days | The logged event |
| Rotating backup | 35 days | Creation of the backup |
An enquiry's closing date and the date of a reply are separate events. If a reply is sent while the matter is still open, the mailbox copy's retention clock starts with that reply, while the form record's clock starts when the enquiry is finally closed. The periods are not added together into one continuous storage term.
Deleting the working record
A substantiated deletion request leads to deletion of the working record within 7 days. Necessary information recording that the request was carried out is retained separately for 30 days. That limited completion record is distinct from keeping the original enquiry active.
Describe which correspondence you want removed. Identify the email address used and the subject or approximate time of the message. If your request concerns both the form record and the mailbox copy, say so explicitly. You do not need to send casino login details to explain the scope of the request.
What happens to backup copies
A deleted record disappears from rotating backups no later than 35 days, and it must not be restored to the working database when a backup is used for recovery. Deletion from the live system therefore has a different timeline from expiry of a previously created backup.
How to send a privacy request
Send your personal-data request to [email protected], addressed to Ariful Hosain. Use the steps below to make the relevant correspondence clear without sharing unrelated personal information.
- Identify the enquiry using the email address you supplied and a short description of the message.
- Explain what you want to ask or have deleted, including any separate email copy relevant to your request.
- Include only the details needed to locate and understand that correspondence.
- Check your message before sending and remove passwords, payment credentials and unrelated account information.
The deletion period above concerns a substantiated request to remove a working record; it is not a promised response time for every kind of question sent to the publisher.
External services and the limits of this policy
Casino operators and the provider of an external game service handle their own services separately from this publisher. Check their privacy terms when using those services, including a provider's game displayed within a page. The rules for this site's editorial forms do not describe every record an external service may create.
A casino-account deletion request belongs with the operator holding that account. The editor cannot close it or erase its payment history. Likewise, the privacy mailbox is not an operator's support channel. Use the terms of use for the publisher's wider service boundaries, or return to the Tower Rush Bangladesh home page.