Privacy Policy
Last updated June 10, 2026
BloxTools ("we", "us") provides developer tools for Roblox — bug and feedback reports, and error monitoring. This policy explains what we collect and why. It covers two kinds of people: account holders (the developers who use the dashboard) and players whose reports and errors are sent to us through a developer's game.
Data we collect
Account data (developers). When you create an account we collect your name, email address, and an authentication credential. Authentication and password storage are handled by our auth provider (Supabase); we never store your raw password.
Data submitted through the SDK (players). When a developer installs BloxTools in their experience, our SDK sends us the contents of bug reports and automatically captured client errors. Depending on how the developer configures it, this can include: the report category and message, the reporting player's Roblox user ID, username and display name, the place ID and version, device/platform, basic performance metrics, recent client log lines, and error messages with stack traces.
Usage data. Standard server logs (IP address, timestamps, request metadata) used to operate and secure the service.
How we use data
- To provide the dashboard: ingesting, de-duplicating, and displaying reports and errors.
- To send the alerts a developer configures (for example, a Discord webhook).
- To secure the service, prevent abuse, and debug problems.
- To communicate with account holders about their account.
We do not sell personal data, and we do not use it to advertise.
Roblox players and children's data
Roblox is used by many people under the age of 13. We take this seriously. With respect to data captured from players:
- The developer who installs BloxTools decides what data to send and is the controller of that player data. BloxTools acts as a processor, handling it on the developer's behalf.
- Developers are responsible for complying with the Roblox Terms of Use, COPPA, the GDPR (including provisions for children), and any other laws that apply to them — including obtaining any consent required before sending player data to BloxTools.
- We ask developers not to send more player data than they need, and not to send special categories of data. BloxTools does not knowingly use player data to build advertising profiles of children.
- If you believe a child's data has been sent to us and should be removed, contact us (below) or the developer of the experience, and we will work to delete it.
Sharing and subprocessors
We share data only with vendors that help us run the service, under contracts that require them to protect it. These currently include our database/auth provider (Supabase) and our hosting provider. If a developer enables a Discord webhook, alert summaries are sent to the Discord channel they configure. We may disclose data if required by law.
Retention
Report and error data is retained according to the developer's plan (for example, the free plan retains data for a limited window). When an account is deleted, its games and all associated reports, errors, and issues are permanently deleted. Account holders can delete their account at any time from Settings.
Security
Data is encrypted in transit. Passwords are hashed by our auth provider. Access to production data is restricted. No system is perfectly secure, but we work to protect data using industry-standard measures.
Your rights
Depending on where you live, you may have rights to access, correct, export, or delete your personal data. Account holders can edit their profile and delete their account directly. For other requests, or requests about player data, contact us and we will respond as required by applicable law.
Changes and contact
We may update this policy; we'll revise the date above when we do. Questions or requests: privacy@bughub.io.
