Information you provide
If you contact LootKit, you may provide contact messages that include your message, page URL, correction notes, source suggestion, or contact address. This information is used to review and respond to the request.
Privacy
Privacy Policy
LootKit's privacy policy explains the basic data practices for an unofficial Roblox tools website.
Site analytics
LootKit may use privacy-conscious analytics or standard web analytics to understand aggregate traffic, popular pages, internal navigation, and technical issues. Analytics are used to improve the site, prioritize updates, and diagnose broken pages, not to sell personal profiles.
Third-party services
Hosting, analytics, search indexing, or browser services may process limited technical information such as IP address, device type, referrer, and page URL according to their own policies.
Data retention
LootKit keeps contact messages and correction context only as long as needed to review the request, maintain update history, protect the site, or respond to a policy issue. Aggregate analytics may be retained longer because they do not need to identify an individual visitor.
Children and accounts
LootKit does not ask visitors to create a Roblox account, share passwords, submit account credentials, or provide payment details. Do not send private Roblox account information through a correction or contact message.
Requests
For privacy questions or a removal request, contact LootKit with enough detail to identify the relevant message or record. Requests are reviewed against site security, legal, operational, and correction-history needs.
Example privacy request
A useful privacy request says which contact message or correction report you sent, the approximate date, and what should be removed or corrected. Do not send extra private account information to prove the request unless it is necessary for identifying the message.
Data boundary
LootKit's normal pages are public reference pages. The site does not need Roblox credentials, payment details, private inventory screenshots, or account recovery information to provide value lists, calculators, outfit prompts, or correction workflows.
What LootKit does not collect
LootKit does not ask for passwords, payment card details, Roblox login tokens, private messages, account recovery codes, or marketplace transaction records. If a third-party service processes technical data, that processing is controlled by that service's policy.
Example analytics use
Analytics may show that players often move from a Grow a Garden value list to a calculator or that a hub page receives visits but few tool clicks. LootKit uses that aggregate signal to improve navigation and page clarity, not to identify a specific player.
Analytics boundary
Analytics is used as a site-improvement signal. For example, LootKit may review whether visitors reach the Grow a Garden calculator after opening a value list, whether a stock reference page creates confusion, or whether a privacy page receives repeated visits after contact messages. That review should stay at the page, path, device, referrer, and aggregate behavior level. It should not become a profile of one player, one Roblox account, one private inventory, or one trade history.
Player feedback boundary
Player feedback is most useful when it describes a public page problem: a value row looks outdated, a mutation multiplier needs review, a calculator assumption is unclear, or a stock reference note needs a better label. LootKit does not need private chat logs, account screenshots, friend lists, location details, or full inventory history to review that feedback. If a screenshot is shared, crop it to the item or visible game context and remove unrelated personal information before sending.
Contact form boundary
A contact form or email message should include the smallest useful correction package: page URL, item or tool name, what seems wrong, source context, and whether the issue is time-sensitive. Do not include passwords, account recovery codes, payment information, private Discord messages, or a request to recover a Roblox account. LootKit can use a contact message to fix a page, clarify a data boundary, or reply to a site question, but it is not an account support channel.
Correction-message handling
A correction message may be kept with page notes long enough to understand why a row changed. If the message includes personal details that are not needed for the correction, LootKit can review whether those details should be removed from operational notes.
Visitor checklist
Use LootKit without sharing private account data. A page URL, item name, update date, and source note are usually enough for a correction. If a message asks for a password, payment method, token, or account recovery code, it is outside LootKit's normal workflow and should not be sent.
Data minimization
Send the smallest amount of information that can identify the page issue. For example, a correction usually needs the page URL, item name, and source context, not your Roblox username, inventory history, private chat, or device details.
Examples of safe messages
A safe message might say: the Grow a Garden mutation page lists a multiplier that seems inconsistent with the latest update, or the privacy page should explain how correction messages are handled. A risky message says: here is my full account, private inventory, password, payment record, or recovery code. LootKit can act on the first kind of message because it points to a public page issue. The second kind creates privacy and account-safety risk without helping the site improve.
What happens after a privacy request
When LootKit receives a privacy request, the practical review starts by identifying the message, correction note, or operational record involved. Then the site checks whether the information is still needed for a response, security review, legal reason, or page-correction history. If the detail is unnecessary for those purposes, the response can focus on removal, redaction, or minimizing future retention. The request does not require sharing new private Roblox account information.