How BrowseRP operates
Hub summaries updated 6 October 2026. Read the full Terms of service and Privacy policy for the current policies and their update dates. Payments remain unavailable. Optional Google visit counts need a separate browser choice before loading; Microsoft Clarity session recording is unavailable. Profile picture uploads and staff advert artwork uploads are available, with file checks and access controls.
Terms summary
This section summarises the full Terms of service, last updated 22 September 2026.
BrowseRP is a directory and moderation platform for roleplay communities. We do not own, operate or endorse listed servers unless a listing says so explicitly. Server owners are responsible for their communities, rules, staff, content and compliance.
- You must be authorised to list a server and keep information accurate.
- Do not impersonate a community, manipulate votes, evade moderation or submit unsafe links.
- We may review, request changes, suspend or remove content to protect users and the service.
- Availability is not guaranteed; planned and emergency maintenance may occur.
Privacy summary
This section summarises the full Privacy policy, last updated 29 September 2026. Read the full policy for details of optional recommendations, listing statistics, analytics and moderation.
BrowseRP processes the minimum information needed for accounts, listings, moderation and security. If you register with email, you provide your first name, last name and email address; Supabase Auth handles your password and email confirmation. Google supplies a provider identifier, name, email address and profile image when you choose Google sign-in. Discord supplies a provider identifier, username, email address and avatar when you choose Discord sign-in; BrowseRP requests your Discord community list only when a server-ownership check needs it. We use this information to create and secure your account, show your chosen identity, connect accounts at your request, communicate about account or moderation actions and verify server claims.
BrowseRP does not request access to Gmail, Google Drive, Google Calendar, Discord messages or unrelated provider data. Provider access and refresh tokens are used only for the requested sign-in or ownership-check flow and are never copied into operational logs. Account, listing and moderation records are stored with Supabase. BrowseRP runs on Vercel, with Cloudflare helping protect the domain and website traffic. We share data with these service providers only as needed to operate and protect BrowseRP; we do not sell account information or use it for cross-site advertising.
For abuse prevention we use a random first-party device token, coarse browser/operating-system/device labels, a masked network range and keyed hashes. The full network address is separately encrypted. Staff see the masked range by default. The Owner, Management and Head Admin may approve access to protected network evidence and make an audited view themselves. Other authorised staff need an approved, time-limited request for a single view. Every view is audited. Our own account-restriction controls use this random device identifier instead of hardware or canvas fingerprinting.
Cloudflare separately helps protect BrowseRP against bots and attacks. Its essential security checks may process IP addresses, request and browser characteristics, and browser signals, and may set a cf_clearance security cookie. These checks are separate from BrowseRP’s account device identifier. See Cloudflare’s privacy policy and security cookie information. BrowseRP does not use these checks for advertising or cross-site marketing profiles.
After 45 days without recorded activity, an account may receive an in-app reminder. After 60 days, it may appear in a staff review list. Inactivity alone does not delete your account, remove your server ownership or close an appeal. Any requested account deletion requires a separate review of the data that must be removed or retained; security evidence may be pseudonymised or retained where needed for abuse prevention, legal obligations or appeals.
Deletion is not an automatic purge. Review must address reports involving other people, moderation and security evidence, staff duty records, any financial evidence, server ownership and uploaded files. Request status alone does not confirm removal of records, sign-in identities or files. Backups have separate retention and recovery handling; immediate removal from every retained backup is not promised. You may request access, correction or deletion subject to security, legal-hold and fraud-prevention exceptions.
Community standards
Listings, comments, adverts, profiles and blogs must be lawful, accurate and respectful. BrowseRP prohibits credential theft, malicious downloads, doxxing, threats, hate, sexual exploitation, targeted harassment, impersonation, ban evasion, vote manipulation and coordinated false reporting.
We are aware that disputes between roleplay communities can spill into TikTok and other social platforms. BrowseRP does not tolerate using this directory to continue “beef”, organise harassment or retaliate against another server. Evidence-based safety reports are welcome; drama campaigns are not and can lead to permanent restriction.
Safety guidelines
- Never share passwords, authentication codes, session tokens or private identity documents with a server listing.
- Check that Discord and Cfx links use their normal official domains.
- Report impersonation, unsafe downloads, harassment and misleading claims from the server page.
- Do not assume an owner-verified badge is a guarantee of a community’s conduct.
- Use the public appeal reference if you believe a BrowseRP restriction is wrong.
Refund policy
BrowseRP Coins and paid advertising are not currently for sale. Before payments open, checkout will show the exact digital service, price, delivery timing and applicable cancellation/refund terms. The production payment system must support failed fulfilment, expiry, full and partial refunds, disputes and ledger reversals before it can be enabled. This section will be replaced with the reviewed final policy before the first sale.
Advertising policy
Adverts are clearly labelled and placed in fixed top or side carousels. Campaigns must be relevant to roleplay communities and may not contain misleading claims, unsafe downloads, credentials, harassment or impersonation. Payment never bypasses content review, and adverts do not silently alter organic directory ranking.
Operator and contact
For management enquiries, partnerships or an issue you need to escalate, email [email protected]. You can also use this address if you cannot access your account to ask for help.
BrowseRP is an independent roleplay server directory operated in the United Kingdom. Profile and visibility settings are available in your signed-in account. Restriction appeals are available at the public appeal page. Send and follow a request for a copy, correction or deletion from Your data on your profile. Staff review each request; submitting one does not immediately export, change or delete your data.
Optional listing statistics
Listing statistics stay off until you separately allow them in the Listing statistics controls on a server listing. This browser-only choice is independent of recommendations. When allowed, BrowseRP sends only the listing reference and whether you viewed it or clicked a community or join control. We store daily totals per listing and activity type, without visitor, account or device identifiers or individual event records. Owners can view the last 7 or 30 days for their own listings. These counts cover opted-in activity; they are not unique visitors, player counts or confirmed joins.
You can turn future recording off in the same controls on any listing. Global Privacy Control and Do Not Track signals keep recording off. Turning it off stops future collection; existing combined totals cannot be identified as yours or removed individually. No recommendation history is sent. Normal hosting and security processing still applies, including the separate short-lived network rate limit used to prevent abuse.