Privacy
Last updated 28 October 2026
What stays on your device
Your platform picks and your recent names are kept in your browser’s local storage. They never leave it. Clearing site data removes them.
What a check sends
A check sends the name you typed and the platforms you picked to beat.rip. The beat.rip server then asks each platform itself, using that platform’s own public API or its own profile address, and nothing else: no aggregators and no lookup services. Domain checks ask each registry’s RDAP service, found through IANA’s public directory. If beat.rip cannot reach a platform, your browser may ask a few platforms directly; those requests go from your browser to the platform.
What the server keeps
Answers are cached for seconds to minutes, keyed by platform and name, so a repeat check does not ask the platform again; the cache holds the answer, not who asked.
To enforce rate limits, short-lived counters are held in server memory per network address (per /64 block for IPv6) and forgotten when the server instance is recycled. For bulk jobs, a record is kept under a one-way identifier derived from that address: the day, how many platform requests were made, and the running job. It holds no address and no names, and it is deleted automatically after the day ends.
Beat.rip does not keep logs: Worker logging is turned off, and the code writes none, so neither the names you check nor your address are recorded by us. Cloudflare, which runs the service, processes requests at its edge under its own privacy policy. There are no analytics and no advertising. Accounts are optional; everything above works without one.
If you sign in
Signing in is optional and goes through Sykbot, made by the same studio, with Discord, Google or GitHub at Sykbot. Beat.rip never sees your password and never receives your email address. From Sykbot it receives your Sykbot account id (your Discord id, or a Sykbot id if you signed up with Google or GitHub), your display name, your Discord username and avatar if your account has Discord, and whether you have Sykbot Premium and until when.
That profile is kept only in an encrypted, HttpOnly cookie in your browser for 30 days, not on our servers. If your account has a Discord avatar, the Beat.rip server fetches the picture from Discord and passes it to your browser, so Discord does not see your address; the picture is not stored by us. To stop a sign-in link being used twice, the server keeps that link’s random one-time id until the link expires, at most ten minutes later.
Saved lists
If you save a list, the server stores it under your account id: the list’s name, its names, the platforms you saved with it, and when it was created and last changed. An account holds up to 50 lists of up to 500 names. Nothing else about you is stored with them. You can export every list as a file from the Saved lists panel at any time.
If you made a Sykbot account with Google or GitHub and later connected Discord, Sykbot folds the two together and tells Beat.rip at your next sign-in. Beat.rip then moves the older account’s saved lists into your account and deletes them from the older one, ending any Beat.rip session still signed in as it. Lists past the 50-list limit are kept, read-only, until you make room.
Deleting your data
Delete my data, in the account menu, deletes every saved list at once and signs you out on every device. To end those other sessions, the server then keeps one thing, the time you pressed it, for 30 days (the longest a session lasts), and then deletes that too. Sign out removes the cookie from the browser you are using. Neither touches your Sykbot account, which you manage at Sykbot.
Contact
Beat.rip is made by Sick & Nexra Studio.