Last updated: 13 October 2026. This policy applies to Redz Hub Script at redzhubscript.co.
What this policy covers
Redz Hub Script provides information about Redz Hub, a catalogue of selected scripts, feature descriptions and guides. This policy explains data used when you read the site, copy script text, request a .lua file, choose settings or contact us. The site does not ask for your Roblox password. Reading a guide or following an external link does not give us access to your Roblox account.
Games, source repositories, executors and other websites have their own privacy documents. Their practices apply when you visit or use them. A link on this site does not mean that we control those services, endorse every change they make, or transfer a Roblox password to them.
Data used to deliver the site
Hosting and delivery systems may process the IP address attached to a request, the requested URL, time, response status, browser information and other technical headers. These details support page delivery, security, diagnosis of errors and protection against abuse. An IP address may be processed even if optional analytics are disabled. Technical identifiers are not necessarily anonymous merely because they do not contain a name.
Depending on connected functions, analytics can describe pages viewed, interactions such as catalogue actions, browser and device characteristics, an approximate region and cookie identifiers. This is not a statement that every listed category is collected on every visit. The configuration and your choice determine which optional functions can operate. We do not require precise location information to read the catalogue.
Messages and voluntary information
If you email best.rbx.scripts@gmail.com, the message and the return address you supply are used to understand the issue and respond. You may include a page address, the name of a script, or a description of an error. Please leave out passwords, private account tokens, payment details and information about other people that is unnecessary for the request. The mail service also processes delivery information under its own terms.
Messages, email addresses, passwords and other identifying values supplied by visitors are not sent to the site’s analytics integrations. Information needed to investigate a report should stay in the correspondence, rather than in analytics event labels or page parameters.
Why data is used and who may receive it
Data is used to operate and secure the site, diagnose faults, understand readership when analytics are connected, support advertising when advertising services are connected, and answer requests. Possible recipients include hosting and content delivery providers, a mail provider, and providers of configured analytics or advertising services. Their involvement depends on the service actually used, not on every example in this policy.
Possible analytics tools include Google Analytics and Yandex Metrica. Read Google’s information about Analytics data and Yandex’s information about identifying data. Providers set restrictions on identifying information; special features can have separate rules. Our integrations do not transmit visitor messages or account credentials.
Optional functions and your choice
Configured optional analytics, advertising and external embedded functions are permitted before you make a choice. No saved decision at this stage is presented as your affirmative consent. Allow keeps optional functions permitted. Necessary Only stops subsequent optional loading, events and accessible optional storage on this site. Basic reading, search, Copy Script, .lua downloading, and your chosen colour theme remain available; language is selected through the page URL.
Open Cookie settings from the footer whenever you want to change the decision. The decision is saved for 180 days from the actual button press. A later refusal applies to future optional activity; it does not automatically recall information already sent. Questions about earlier data can be sent to the contact below. See the Cookie Policy for storage details.
Retention, international processing and protection
Retention depends on the purpose and the settings of the service concerned. Technical logs, correspondence and optional analytics do not all share the 180-day preference period. We retain correspondence as needed to handle the matter and relevant follow-up. Provider records may be governed by provider retention settings. We do not promise automatic deletion from every third-party system.
Hosting, email and configured providers may process information in countries other than yours. The applicable arrangements depend on the provider; this policy does not assert a particular server country or an unverified contract. Reasonable measures include restricting administrative access, maintaining the software and protecting requests. No online system can guarantee absolute security.
Requests, children and policy changes
You can request information about data associated with your interaction, correction or deletion by emailing best.rbx.scripts@gmail.com. Explain the request and provide only the details needed to locate it. We may need proportionate information to check that the request concerns you. Rights, exceptions and available remedies depend on applicable law; this policy does not remove rights that law gives you.
A parent or guardian can contact the same address about a child’s data. Do not send a child’s password or identity documents without a specific need being explained. We review the circumstances of a report rather than treating an age label as a substitute for age-related requirements. Material changes to this policy receive a new revision date. A policy update does not silently reverse a saved refusal.