Scope of this notice
This notice concerns visiting in7z.com and contacting the website. It does not cover information you submit to an external game operator. The site does not provide a player registration form or collect deposits. Questions about a separate account should go to the provider responsible for that account.
Page requests and technical information
Serving a page requires requests for HTML, images and styles. The serving systems can receive the request address, IP address, time and browser information supplied with it. Hosting or security infrastructure may retain logs for its operation. A static page does not mean that there are no technical records.
Email you choose to send
Correspondence can include your email address, message and attachments, plus metadata handled by the email service. A page URL and a short description are usually enough for a website correction. Do not include unrelated account statements, passwords or identity documents. Keep the same thread when adding a clarification.
Cookies and browser features
The public pages delivered by this design do not implement player accounts, visitor voting or an analytics script. These pages do not set a visitor-rating cookie. Grav administration, server security and external services can have their own session or cookie behaviour. Inspect browser site-data controls for entries actually stored on your device.
External access routes
Access buttons use a share route before continuing to a separately managed destination. Requests can convey technical information to the route and the destination. This notice does not describe that separate service as anonymous or free from logging. Read its privacy information before entering personal details.
Providers and data location
Hosting, security and email systems can involve more than one infrastructure provider. No unverified server country, universal storage period or claim that all information stays in India is made here. For a specific concern, identify the website interaction so its relevant systems can be considered.
Retention and deletion enquiries
Different records may have different purposes and retention needs. Clearing browser history does not delete a previously sent email or another operator’s records. If asking about correspondence, provide the approximate date and subject without repeating sensitive attachments. No fixed deletion deadline is promised without knowing the record and applicable requirements.
Corrections and privacy requests
Contact [email protected] about information you provided to this website. State the request narrowly enough to locate the relevant correspondence. Additional verification, if needed, should be proportionate to the request. External account, payment and identity records must be addressed to their own provider, not this directory.
Security and adult readership
No website or email service can guarantee protection against every incident. Avoid sending passwords, one-time codes and banking PINs. The site is intended for adults and does not ask for children’s information. If sensitive material was sent accidentally, refer to the earlier message instead of resending it.
Changes and related information
This notice describes the current public website, not every feature a future version might introduce. A new form, account function or analytics service would require a review of the notice. The disclaimer explains editorial limits; the terms explain use of these pages and external links.
Reading pages and following links
There are two different interactions to consider. Reading an IN7 guide requests content from this website. Selecting an external access button also makes a request to a redirect route and then to another website. The destination can receive information associated with that visit, including details the browser sends automatically. Its own forms, tracking tools and account records are not controlled by this page. Check the address bar before entering information so you know which service receives it.
What to include in a privacy enquiry
Identify the page or email conversation concerned, the approximate date and the information you want reviewed. A request such as asking about a particular message is easier to locate than a request covering an unidentified account. Do not send a full identity document as an opening step. If further information is needed to establish which correspondence is yours, keep it limited to that purpose. Do not send another person’s account details without their permission.
Screenshots can contain more than the error
Before attaching an image, look at the notification bar, account name, phone number and payment fields as well as the error itself. Crop or obscure details that are not needed to explain the website problem. A payment receipt can contain reference numbers and other information intended for the payment provider, not a public content directory. If you are reporting a broken link, the page URL and the button label will usually be more useful than a complete financial screenshot.
Browser storage and shared devices
Your browser may keep cached copies of images and pages or remember browsing history independently of whether this website offers an account. A shared device can therefore reveal a visit to someone who uses the same browser later. Review the browser’s own history, download and site-data controls if that matters to you. Removing a local file or history entry affects that device; it should not be understood as a request to remove information held by a hosting provider or an external service.
Requests that belong to another operator
An IN7 player profile, identity check, wallet entry or app permission can belong to the linked operator rather than in7z.com. Send enquiries about those records through the contact channel shown by that operator. Do not email an account password here as proof that the profile belongs to you. When a concern is instead about wording on this website or a link we publish, identify that page so the two issues are not confused.
Privacy notice review
This notice was reviewed on 8 October 2026 for the public information pages described here. It does not establish the configuration of every external destination reached through a link. If a new public form, embedded service or account feature is introduced, its data flow needs to be assessed and the relevant explanation updated. You can refer to the notice and page address in a question; retaining a copy of the version you read can help explain what you are asking about.