Privacy and Cookie Choices at Tower Rush France

If you’re reading from France, you can browse the Tower Rush game guide in English or switch to the French edition. This policy covers your visit to the editorial site and your correspondence with the team. If you open a game or service on another website, check that site’s policy for the information it asks you to provide. The terms of use describe the scope of this site.

Information you send to the editorial team

The contact form is for your name, email address and message. The editorial team receives those fields. Your name identifies who wrote to us, your email gives us an address to reply to, and your message tells us what you need. Email is the main contact channel, including for questions about the data you sent in an earlier message.

Keep the details in your message relevant to the request. For an editorial question about a particular page, include its address so the team can see the context. If your question concerns your personal data, describe the information you’re asking about, such as the details you entered in a contact form. The page address can help explain a question about the site, while an earlier email subject is more useful for identifying a previous exchange.

Language cookies and analytics consent

The site uses necessary cookies to remember your choice of English or French and uses separate analytics cookies only after you consent to analytics. You can keep your chosen language and leave analytics off. Sending a message to the editorial team does not give consent for analytics. The team can reply to your request regardless of your analytics choice.

How Matomo handles analytics data

The site uses a self-hosted Matomo installation for consent-based measurement. Matomo shortens the IP address before recording the analytics data. The metrics used in the aggregate count are de-identified. That count is a measure of use of the site. It serves a different purpose from the editorial correspondence that the team uses to answer a specific reader.

OVHcloud provides the hosting in Gravelines, France. That is the location of the self-hosted analytics setup. When you read “aggregate analytics” in the retention table, it refers to the de-identified measurement data from that setup.

The site has no editorial accounts. There is no comment section, so use the editorial contact channel if you want to send a question about an article. The site has no newsletter. The site uses no advertising pixels. It also has no AI chat and collects no AI chat history.

How long records are kept

Retention ranges from 21 days for technical log entries to 105 days for email copies of correspondence. Check both columns for the type of record you’re asking about. A single visit followed by a message to the team can involve records that start ageing at different times.

Contact requests and email copies

The working record of a contact request and the email copy start their retention periods at the same point. Use the date the request was closed when reading the two periods in the table. The date you first wrote to the team may be earlier, especially if the exchange took several messages to resolve.

Because the email copy has the longer retention period, it can still exist after the working record of the request has expired. If you ask about an older exchange, specify whether you mean the original request or the email correspondence. This lets the team identify the part of the exchange your question concerns.

Technical logs and aggregate analytics

Technical log entries and aggregate analytics events each age from the time of the event. The retention period for one event therefore does not depend on when you last opened the site or whether you have an open contact request. The two categories use different periods in the table.

Deletion from working records and backups

Working records are deleted when their retention period expires. A backup is a snapshot made at a particular time. If an older snapshot includes a copy of a record that has since been removed from the working records, deleting the working record does not automatically change that snapshot. The backup expires on its own schedule.

Take a backup made while a request is still open. The backup’s retention period has already begun even though the request’s clock starts only when the case closes. A later backup can have a different expiry date even if it contains a copy of the same record. Closing the request or deleting the working copy does not reset either backup’s clock.

When you ask about deletion, the status of the working record and the expiry of any snapshot that still contains a copy are separate questions. The backup period is measured from creation even when the working record is no longer held.

Where to send a request about your data

1. Open the editorial contact page or email [email protected]. You can write in French or English.
2. Use a subject such as “Personal data request” to distinguish it from an editorial enquiry.
3. State what information your request concerns and what you want the team to look into. If you are asking for deletion, say so in the message.