Safety, Permissions, and Privacy
Understand what NexusRBX AI may inspect, how review gates work, what not to paste into prompts, and where to find privacy terms.
Guide
This page explains how users should think about safety, permissions, privacy, and generated code review. ## Beta Safety Notice
NexusRBX AI is currently in beta. Generated code should be reviewed and tested before it is used in a live Roblox game.
The plugin can speed up development, but it does not replace developer judgment.
What NexusRBX AI Needs Access To
| Area | Details |
|---|---|
| Roblox Studio plugin access | The plugin can inspect targeted Studio hierarchy and scripts for the current task, and can apply reviewed changes through supported commands. |
| NexusRBX account | A NexusRBX account is required for authenticated AI workspace features and Studio pairing. |
| Script content | Script content can be sent to NexusRBX services when needed to generate, review, debug, or edit code. |
| Prompts | Prompts may be processed and retained according to the Privacy Policy and account settings. |
| Project data | Only task-relevant project context should be shared; retention is governed by the Privacy Policy. |
| Billing | Billing details are shown in the NexusRBX account or checkout flow when billing is available. |
User Review Before Changes
NexusRBX AI should clearly show when the user needs to approve generated code before it is inserted or applied.
Before approving code, users should check:
- What script will be created or changed.
- Where the script will go.
- Whether the script type is correct.
- Whether object names match the project.
- Whether the code affects important systems.
What Is Not Automatically Changed
- The plugin should not publish your experience or silently rewrite unrelated scripts.
- Insertion should happen through explicit review or confirmation in the supported workflow.
- Existing scripts should be edited only when the action targets that script and the user reviews or confirms the change.
- Destructive changes should be confirmed, blocked, or snapshotted depending on the supported command.
Privacy And Data Handling
- Privacy Policy: /legal/privacy
- Terms of Service: /legal/terms
- Support requests: /contact
- Data retention: See the Privacy Policy for prompt, script, and project data retention.
- Account deletion: Use /contact for account deletion or data requests.
Do not paste secrets, private API keys, Roblox account credentials, billing details, or personal information into prompts.
Report Suspicious Behavior Or Bugs
If the plugin inserts unexpected code, shows a suspicious permission request, or behaves differently from the documentation:
- 01
Stop using the affected workflow
Stop using the affected workflow.
- 02
Save a copy of the script or error message
Save a copy of the script or error message.
- 03
Take a screenshot or short video if possible
Take a screenshot or short video if possible.
- 04
Report the issue through /contact
Open the support form, choose Security / privacy or Roblox Studio / technical, and include the saved evidence.
Send the page title and link to support so the report reaches the right context.