1. Information we collect
WorldLoop only asks for the information needed to run the builder, connect Roblox Studio and improve reliability during the Open Beta.
- Roblox sign-in data: Roblox user ID, username or display name, avatar URL and login state.
- Generation data: prompts, selected options, seeds, style choices, generated CAD part definitions, preview metadata and recent build history.
- Studio bridge data: Local Helper status, plugin install status, active Studio connection and asset delivery state.
- Technical data: browser storage, basic request logs, error logs, analytics events, IP address, user agent and timestamps created by hosting, analytics and security systems.
- Presence data: anonymous browser session status, current WorldLoop page, last activity time and signed-in Roblox account only when a user is authenticated.
- Open Cloud asset data: when permanent asset baking is enabled, WorldLoop may store generated Roblox asset IDs and cache keys to avoid duplicate uploads.
2. How we use information
- Authenticate your Roblox account and show the correct user session.
- Generate, preview and send requested assets to Roblox Studio.
- Remember local preferences such as language, theme, recent builds and presets.
- Debug failures in the Local Helper, OAuth flow, preview renderer or asset pipeline.
- Show private admin-only live activity diagnostics during the Open Beta.
- Protect the service from abuse, broken requests and unauthorized origins.
We do not sell personal information.
3. Roblox OAuth and Studio connection
WorldLoop uses Roblox OAuth/Open Cloud to let users sign in without sharing Roblox passwords with WorldLoop. Roblox handles the authorization screen, and users choose whether to authorize the app.
The Local Helper runs on the user's own machine and allows the browser app to communicate with Roblox Studio. It is used for local delivery into Studio and should only be installed from the official WorldLoop flow.
4. AI, hosting and service providers
WorldLoop may use third-party infrastructure and APIs to operate the product:
- Roblox: OAuth, Open Cloud, account information, Studio and asset workflows.
- Vercel: hosting, serverless functions, deployment logs and request handling.
- Google Analytics: aggregate usage analytics, funnel events and page interaction measurement.
- OpenAI API: AI-assisted generation, parsing or expansion when enabled by the pipeline.
- Render or preview infrastructure: optional visual preview services when configured.
These providers process data under their own terms and privacy policies.
5. Browser storage and history
WorldLoop stores some data in your browser, including language, theme, account display state, recent generated builds and preset metadata. Some full build definitions can be stored locally in IndexedDB to make the history faster without reloading everything from the server.
You can clear this data by signing out, clearing browser storage, or using browser privacy controls.
6. Retention
Local browser history remains on your device until you clear it. Server logs and provider logs may be retained for security, debugging and platform operation. During Open Beta, generated asset records may be kept long enough to diagnose bugs and improve stability.
7. Your choices
- Sign out of WorldLoop to remove the local Roblox session from the browser.
- Revoke Roblox OAuth access from your Roblox account settings or Creator Dashboard where available.
- Clear browser localStorage and IndexedDB to remove local preferences and history.
- Request removal of beta account data through the official support channel used to access WorldLoop.
8. Age and Roblox requirements
WorldLoop is intended for Roblox creators who are allowed to use Roblox Studio and authorize Roblox OAuth apps. Roblox may require users to be 13+ to authorize OAuth apps.
9. References
These are the main external policies and platform documents WorldLoop should remain aligned with.