https://docs.sirius.menu/rayfield https://www.rayfield.gg/ https://developer.sirius.menu/

Analytics and privacy

When a Rayfield window opens, Rayfield sends one event to Sirius's analytics service. It contains:

• a pseudonymous user ID: a SHA-256 hash of your Roblox user ID, which our server re-keys with a key that changes every month, so you can't be followed from one month to the next
• the game (place and universe ID), your executor's name and version, platform (PC, mobile or console) and locale
• about the script: its name, the Rayfield build and theme, whether it uses a key system, configuration saving or a Discord invite, and the developer's Sirius script ID if they set one
• if you are later kicked or banned from that game, the Roblox error code and whether it was a kick or a ban. Never the message itself.

Cloudflare tells us the country the request came from. Your IP address is not stored, and nothing you type, say or click is ever sent.

Turning it off

Open the Rayfield Settings tab in any Rayfield window and switch off Usage Analytics (pseudonymous). The choice is saved in Rayfield/settings.rfld and applies to every Rayfield script. While it is off, Rayfield doesn't download its analytics module at all, and nothing is sent. Turning it off mid-session also stops anything already queued, such as kick reporting.

For script developers

Set this before loading Rayfield to turn analytics off for everyone who runs your script:

getgenv().DISABLE_RAYFIELD_REQUESTS = true

It forces the setting off, stops the analytics module being fetched, and skips Rayfield's occasional uptime ping. Rayfield still downloads its icon set and prompt module from GitHub.

Remote modules are loaded from a pinned commit (RAYFIELD_COMMIT and SIRIUS_COMMIT at the top of source.lua), not from a branch.

Privacy policy: https://sirius.menu/privacy