Nothing hidden

Privacy, plainly

What RoLARP uses and where it goes

Effective October 9, 2026 · Extension version 1.3.3

Your customization stays in your browser
No passwords. No authentication-cookie access. No RoLARP backend.

What the extension does

RoLARP is operated by the RoLARP project. It changes how supported Roblox pages look in your browser for personal previews and larping. It doesn't modify real account information or grant Robux, inventory, verification or Premium. It isn't intended for impersonation or misleading others.

What stays on your device

RoLARP uses Chrome's local extension storage to save names and Robux display amounts you enter, badge choices, whether customization is enabled and public profile data retrieved by Copy User.

Copied data can include a public user ID, names, bio, social counts, public badge status, avatar image URLs and worn-item details. RoLARP doesn't send these saved settings to its operator and doesn't use Chrome sync storage.

When it connects to Roblox

Custom mode doesn't make extension API requests. When you choose Copy User, the extension sends the username you entered to Roblox to resolve the public profile. It then uses public user and item IDs to request profile details, thumbnails, worn items, social counts and available item prices.

These requests go directly to users.roblox.com, thumbnails.roblox.com, avatar.roblox.com, friends.roblox.com, catalog.roblox.com and economy.roblox.com. Images load from Roblox's rbxcdn.com CDN. The extension's public API requests omit credentials.

Roblox and its CDN receive normal connection information such as your IP address and the requested resource. Their handling of those requests is governed by Roblox's privacy policy. Roblox's own page requests still operate normally, including authenticated requests initiated by Roblox itself.

What it doesn't collect

The extension doesn't read authentication cookies, passwords or session tokens. It doesn't collect browsing history, private messages, payment information or real account balances for reporting. There are no analytics SDKs, advertising trackers or hidden telemetry in the extension.

The extension doesn't send data to rolarp.xyz or api.rolarp.xyz and doesn't depend on this website. We don't receive, sell or share your extension customization data.

Why it needs permissions

Storage saves your customization locally. Access to the listed Roblox API hosts supports the public Copy User lookup. Content scripts run on www.roblox.com to change displayed text and images and locally substitute selected public display responses.

Those scripts can read public page context to recognize your own profile. They don't rewrite outgoing Roblox account-update requests. The extension has no cookies permission and downloads no executable code.

Retention and your controls

Saved customization stays on your device until you replace it, press Clear or uninstall the extension. Pausing stops customization but keeps the saved settings. Clear removes the saved customization; refresh Roblox to restore its normal display.

There is no RoLARP account or operator-side copy of extension settings to delete. Ordinary browser caching and Roblox's own data retention are separate from RoLARP's local storage.

This website

This site serves static pages and images. It has no analytics, tracking pixels, accounts, forms, advertising or browser-storage features. It doesn't communicate with the extension.

Your browser sends normal web request information, including an IP address and requested URL, to the hosting server to load the site. The supplied server configuration doesn't enable HTTP access logging. Hosting infrastructure may still retain operational or security logs; this policy does not claim that visiting a website is anonymous.

Updates and questions

If data handling changes, this page and its effective date will be updated. This policy describes the current clean release, not legacy versions.

The Chrome Web Store listing isn't live yet. Its support channel will be linked here when available. A direct operator contact must be added before public launch.