Privacy policy

Account information

When you choose Google sign-in, Google supplies your provider identifier, name, email address and profile image. When you choose Discord sign-in, Discord supplies your provider identifier, username, email address and avatar; 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.

Information you send us

We store the details, links and images you send with listing submissions, ownership claims, reports, appeals and advertising enquiries so we can review them and respond. Approved public listing and profile information can be seen by visitors. Claim evidence, reports, data requests and advertising enquiries are handled through the relevant account and authorised staff tools; they are not published as directory content. Advertising replies stay on BrowseRP with the account that sent the enquiry.

Content checks and appeals

We check comments, proposed display names and profile pictures before publication. We keep the submission, decision, reason and any appeal so the rules can be applied and a decision reviewed. Pending or blocked submissions and appeal statements are available to the submitting account and authorised reviewers, not published to visitors. Your previously approved name or picture stays in use while a replacement is reviewed.

Clear abuse or spam can be blocked with a reason. Uncertain results and unavailable or failed checks go to staff review. When automatic checks are enabled, BrowseRP sends submitted comments, proposed display names and profile pictures to OpenAI for safety classification. This includes names and pictures imported when you sign in. The checks receive the submitted text or picture without adding your account details or browsing history; submitted content may itself contain personal information. If automatic checks are disabled or cannot finish, new submissions wait privately for staff review. With automatic checks enabled, clearly acceptable comments and names can be published without waiting for staff. Profile pictures need staff approval before publication, even when an automatic check finds no concern. Applications remain manually reviewed.

You can ask for a free staff review of a blocked submission through your signed-in account. We do not charge for an appeal or put a public warning label on your profile because of a content decision. Content checks are separate from optional recommendations. Private review does not make previously published copies or older public image links private. Review records and uploaded files must be considered separately when handling a data-removal request; a decision or replacement does not itself confirm their deletion.

Storage and service providers

Account, listing and moderation records are stored with Supabase. BrowseRP runs on Vercel, with Cloudflare helping protect the domain and website traffic. Google and Discord process the information involved when you choose their sign-in services. 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.

Security information

For abuse prevention we use a random first-party device token, coarse browser, operating-system and 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.

Retention and your choices

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. A 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 that these records, sign-in identities or files have been removed. 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. You can change your profile and its visibility from your signed-in account. Restriction appeals are available on our 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 discovery recommendations

If you enable personalised recommendations, BrowseRP stores up to 80 server-view records for up to 30 days in this browser’s local storage. Each record contains a BrowseRP listing reference, game, region and viewing time. Older records expire and are removed when you next use BrowseRP. We use these records on your device to prioritise regions you enjoy; only a normal region/game directory query is sent to our server, not your viewing history. We do not read your browser history or track activity on other websites.

This is off by default and is not used for targeted advertising. Turn it off and clear its history from Cookie preferences in the footer, the recommendation section or your profile preferences. Guests choose for this browser, including anyone sharing it. When signed in, your account stores the recommendation choice, its version and when it changed, so active devices can check it. Viewing history is never synchronised. A rejection on this browser keeps recommendations off until you explicitly accept here; a saved acceptance from another device cannot override it. Recommendations pause while we check the account or preference, when those checks fail and while the page is inactive. Other devices check when active; offline devices cannot receive a changed choice immediately. Account changes clear the optional history on this browser. Essential sign-in and security storage and your theme choice are separate from this optional setting. The separate Recently viewed list is a local shortcut to the last eight BrowseRP listings you opened.

Your comparison shortlist

When you add servers to Compare, this browser remembers up to three public listing addresses and names until you remove them or clear the comparison. This is a device-only convenience, shared by anyone using this browser, and is not linked to your account. A comparison link contains only those public listing addresses. Saved favourites are separate and belong to your signed-in account.