Scope of this privacy information
This page explains the website interactions described in the Banig.net access pages and guides. It covers browsing information, access links, local interface features and the contact channels published on the website. It does not replace the privacy information of a service you visit after following an external link.
A gaming account, app store, messaging service and hosting provider may each process information for different purposes. Read the notice of the service receiving your information before submitting personal details there. Similar branding or a linked destination does not establish that the same party controls every record.
Information involved when loading a page
Opening a website requires your browser to communicate with the systems delivering it. Request information can include an IP address, requested address, browser information and connection details. Hosting, security or content-delivery services may process this information to deliver pages, maintain availability and investigate technical problems.
The information recorded and the period for which it is kept depend on the services and settings used to operate the website. This page does not state a fixed retention period for systems whose configuration is not specified. Do not assume that closing the browser removes request records held by a hosting or security service.
Gaming credentials and account forms
The access guides do not contain a gaming registration, password-entry or payment form. Their buttons direct visitors to configured destinations or relevant information pages. Do not send gaming passwords or one-time verification codes through a general website enquiry.
If you enter account information after leaving Banig.net, the destination service receives that submission under its own process. Check the address before entering details. Banig.net cannot inspect or delete account records held by another provider merely because a link to that provider appears here.
Access links and redirects
Configured external entries may use a local /go/ address before opening the selected destination. The link identifies an allowed destination option; it is not intended for entering account credentials. The redirect feature itself does not create a website record of your gaming password or account balance.
A redirect request may still appear in infrastructure logs like other website requests. Your browser and the destination may also exchange normal connection or referral information according to their behaviour and settings. Avoid sharing temporary URLs containing private values, and read the destination’s privacy notice before continuing.
Browser storage and interface controls
The menu, FAQ, picture tabs and tutorial dialog operate within the current page. Their supplied interface code does not save gaming passwords or use local storage to retain your account information. Selecting a device tab changes which instructions are visible.
WordPress features, signed-in administration sessions and additional services can have separate cookie or browser-storage behaviour. Browser settings can affect those functions. Do not assume that a statement about the tutorial controls describes every feature of a hosting service, plugin or external destination.
Images, fonts and page resources
The page layouts provide local image positions and use device-available fonts. Loading a local image sends a request to the systems delivering this website. An image filename or visual identity does not establish which account provider operates an external service.
If externally hosted resources or embedded services are added to the website, their delivery can involve additional providers. Their data practices must be considered separately. Following a link and loading an embedded resource are different interactions; a service may receive a request when an embedded resource loads even without a visitor selecting a link.
Analytics and additional services
The supplied page code does not add an analytics tag, advertising pixel or externally embedded social feed. This describes those page features, rather than a claim that no other system can process browsing information.
Hosting features, security services and installed plugins can change the deployed website’s behaviour. Any additional data collection should be explained according to the service actually used. A browser extension or separate application on your device may also process information independently of the website.
Email and contact-channel enquiries
Selecting an email link normally opens your chosen email application. Sending the message involves that email service and the recipient’s systems. Selecting a Telegram, WhatsApp or Facebook entry opens the configured destination, where that service’s own privacy practices apply.
Include only the information needed to explain your enquiry. A relevant page address, approximate time and error may be enough to begin. Do not send passwords, verification codes, complete payment credentials or identity documents through a general message. Confirm the recipient and the purpose of the channel before sending sensitive information.
Public groups and visible messages
A social destination may be a public page, group, announcement channel or direct conversation. Review its format before writing. Information shared in a group or public comment can be visible to people who are not responsible for resolving your enquiry.
Do not publish private account screenshots to obtain a faster response. Remove personal information and unrelated notifications from images. If a provider needs a document, ask for its specified secure submission method rather than assuming that a public messaging space is appropriate.
Support records and information minimisation
An enquiry may include a message, contact address, relevant references and any attachments you choose to send. The receiving party may need that information to understand the issue and reply. Send a concise description rather than a complete account history or device backup.
Keep case references privately and avoid sending the same sensitive information to several unverified contacts. If someone requests additional information, ask why it is needed and how it should be submitted. The existence of a support conversation does not establish authority to collect passwords or one-time codes.
Identity documents and payment information
Do not submit identity documents or payment credentials to this website’s general information channels to resolve an external account matter. Identity checks and transaction reviews belong to the provider responsible for the relevant account and must follow its verified process.
Check the destination and requested purpose before submitting a document. Provide only what the secure process requires. Banig.net cannot approve another provider’s verification, inspect its payment records or remove information from its systems. Contact that provider about documents or transaction data supplied to it.
Storage periods and deletion questions
Different systems may retain information for different purposes and periods. Website request records, correspondence and external account records are not necessarily stored together or controlled by the same party. No universal deletion time is promised on this page.
If you want to ask about information, identify the interaction and the service that received it. Do not send additional documents merely to begin an enquiry. Use the published contact process and ask which details are needed to identify the relevant record and verify the request securely.
Information requests and available controls
Questions about access to information, correction, removal or other privacy concerns should be directed to the party responsible for that information. Available procedures depend on the service and the requirements that apply to it. Read the relevant provider’s notice for its contact and verification process.
Use browser controls for local history, cookies and saved credentials when appropriate. Removing local browser data does not necessarily remove information already received by a website, email recipient or account provider. Likewise, uninstalling an app does not automatically close the account held by its service.
Account and device protection
Keep passwords unique and verification codes private. Use a trusted device when handling sensitive account information, and sign out of shared devices. A familiar logo, contact image or message thread does not by itself establish that a recipient is authorised.
No claim of absolute security is made here. Be careful with remote-access requests, unfamiliar installers and unexpected account approvals. If information appears to have been exposed, contact the responsible provider through a verified channel and follow its account-protection process.
Age requirements and younger visitors
Gaming-related access information is intended for adults who meet the relevant service and applicable requirements. Do not use another person’s identity to register or allow children to use an adult account. Keep passwords and payment methods away from younger people.
If you believe information involving a child has been sent to a service, contact the party that received it using its published process. Avoid placing further identifying details in public messages. An external account provider must address information held in its own records.
Changes to website features
New contact methods, embedded resources, forms or other services can change the information involved in using the website. Privacy information should describe the features actually provided. Check this page and the relevant service’s notice when a new interaction asks for additional information.
Do not assume that an older screenshot or saved copy explains every future feature. Before submitting information, read the current request, identify the recipient and understand its stated purpose. Ask for clarification when the process is unclear.
How to raise a privacy enquiry
Use the Contact page for published website enquiry details. State the page or interaction involved, the approximate date and the nature of your question. Include enough context to identify the issue while avoiding unnecessary personal information.
For information submitted to an external account provider, messaging service, app store or email service, use that service’s privacy process. Banig.net cannot act on records it does not control. If ownership of the information is unclear, begin by asking which party is responsible rather than sending sensitive documents to several contacts.