Privacy Policy

Privacy overview

Roblox GUI Maker is currently designed as a browser-based, no-login editor. This roblox gui maker privacy policy explains the information the current site may use and the information it intentionally does not require. The main privacy principle is simple: the editor should let creators experiment with templates and generated UI code without asking for an account before the core workflow is useful.

The current editor may store your most recent draft in your browser's local storage. Local storage is saved on your device by your browser. It helps the editor restore recent work after a refresh, but it is not the same as a cloud account. If you clear browser storage, use a private window, or switch devices, that local draft may be unavailable.

Information currently handled

The editor can handle the interface data you create inside the browser, including object names, text labels, colors, sizes, positions, and template choices. This data is used to render the preview and generate Luau UI instance code. The current editor does not require you to upload a Roblox project, connect a Roblox account, or send generated GUI data to a server for AI generation.

The site also uses the browser clipboard when you press copy actions for generated Luau. Clipboard access is handled by the browser and may require permission depending on your environment. If the browser blocks copying, the page should let you select code manually rather than silently sending data elsewhere.

Accounts, payments, and contact forms

The current public editor does not require accounts, subscriptions, or payment checkout. If those features are added in a future version, this policy should be updated before launch to explain what account data, payment provider data, support data, retention periods, and user choices apply.

The visible contact page currently states that live contact submission is not active from that page. If a support inbox or contact form becomes active, the privacy policy should be updated first. A live form should explain what fields are collected, where messages are sent, how long they are kept, and how users can request follow-up or deletion where applicable.

Analytics and logs

Roblox GUI Maker uses Google Analytics 4 to understand whether public pages and the editor workflow are working. Analytics events can include page views, the page path, button or call-to-action identifiers, editor open events, bundled template slugs, editor element types, device preview choices, and the source surface for Luau copy actions. The analytics code is designed to avoid sending raw generated Luau, Roblox credentials, Roblox account data, payment information, email addresses, passwords, tokens, freeform user text, or private project files.

Google Analytics may process technical information such as browser, device, approximate location derived from network data, referral source, page URL, and event timing according to Google's own terms and settings. The site owner should keep Google Analytics retention and sharing settings aligned with this policy before enabling any new event category. Visitors can reduce analytics collection by using browser privacy controls, blocking scripts, or Google's available Analytics opt-out browser add-on where supported.

Like most web applications, the hosting platform may process technical request data such as IP address, user agent, request path, timestamp, and error information. That information is typically used to deliver the site, detect abuse, troubleshoot failures, and understand whether pages are working. The site should not use technical logs to imply personal Roblox account knowledge.

Children and Roblox accounts

Roblox GUI Maker is an independent creator tool. It does not ask for Roblox passwords, Roblox cookies, Roblox account tokens, or Roblox private account information. Users should never paste Roblox credentials into this site. The site cannot recover Roblox accounts, change Roblox purchases, moderate Roblox experiences, or provide official Roblox support.

Creators using this site are responsible for following the rules that apply to their own Roblox experiences, including platform policies and any privacy requirements for their game. This site helps prototype interface code; it does not replace the creator's responsibility to handle player data safely inside their own project.

Data control and practical choices

Because the current draft workflow is browser-local, the most direct control is in the browser. You can clear local site data if you want to remove stored editor drafts or theme preferences. You can also avoid saving work in the browser by using a private browsing session, though that may reduce convenience. Analytics controls also live mostly in the browser: privacy extensions, script blockers, browser tracking-prevention settings, and supported Google opt-out tools can limit or block Google Analytics requests.

This policy should stay aligned with the actual product. If Roblox GUI Maker later adds accounts, cloud saves, AI generation, file uploads, newsletter signup, payments, live support, a new analytics provider, or analytics events that collect new categories of data, the privacy page must be updated before those features collect user data.

Future update triggers

This privacy policy should be updated before any feature collects new data. Important triggers include accounts, contact form submission, newsletter signup, payments, cloud saves, AI generation, file uploads, shared project links, error monitoring, support inbox routing, a new analytics provider, or a broader analytics payload. Each trigger should name the provider, the purpose, the retention approach, and the practical user choice where one exists.

The policy should not claim that data is never processed if hosting logs, browser storage, or optional integrations exist. It should stay plain and specific. Users do not need vague privacy language; they need to know what the current editor does, what it does not do, and what will change before a future feature becomes active.

Navigation and review

This page should stay connected to the rest of the site without becoming a sales page. Visitors should be able to return to the editor, browse templates, read support notes, or review the disclaimer depending on the question that brought them here. Internal links should clarify the next step, not distract from the page duty.

Review this page after any product change that affects user expectations. If a feature is added, removed, delayed, or renamed, the utility copy should be updated at the same time as the product page. Keeping these pages current protects users from stale promises and keeps the site's SEO signals aligned with the real product.