This page describes everything rbxoffsets records when you visit this site, why it is recorded, how long it stays, and who else is ever in a position to see it. It is written to be read rather than to be skimmed past, and it describes this deployment specifically.

The short version: there are no accounts, no sign-up, no payment, no contact form and no advertising on this site. Nothing here asks you for your name, your email address or anything else about you, and there is no mechanism by which you could supply one even if you wanted to. The only information that exists about your visit is the information a web server unavoidably handles in order to answer a request, plus a single audience measurement that does not run at all until you say it may.

What is recorded

Request logs

Like every web server, this one processes the information your browser sends in order to answer: the address you asked for, your IP address, the browser and operating system your browser identifies itself as, the page that linked you here if any, and the moment the request arrived. This is handled by the server and by the hosting provider that operates the machine. It is used for exactly three things — delivering the page, diagnosing faults, and identifying abuse such as a single source making enough requests to affect other people. It is never used to build a profile of an individual, and it is never combined with the analytics described below.

Audience measurement

This site uses Google Analytics 4 to count visits and to see which pages are being read. It does not run until you consent. Google Consent Mode is installed before the measurement library loads, with every storage category set to denied, so the library starts already forbidden to write anything to your browser. If you decline, or simply never answer, nothing is stored and no measurement is sent. If you accept, Google Analytics sets the identifiers described on the cookie policy page and records which pages you visited, roughly where in the world you are (derived from your IP address, which is truncated before storage), and what kind of device and browser you used.

What it is used for is deciding what to work on. Whether anybody reads the Android offsets pages is a question this project cannot answer any other way, and the answer changes what gets built next. It is not used to identify you, it is not linked to anything else, and the data is not sold, shared with advertisers, or used to target advertising — advertising storage and personalisation are both permanently denied on this site regardless of what you consent to.

Your consent choice

Your answer to the cookie notice is kept in your browser’s local storage, not in a cookie. It never leaves your device and is never transmitted to this server. Clearing your browser’s site data for this domain erases it and the notice appears again.

What is not recorded

• No accounts, profiles, passwords or authentication of any kind for ordinary visitors.
• No advertising networks, no ad tracking, no retargeting, no data brokers.
• No cross-site tracking, no fingerprinting, no session recording, no heat mapping.
• No sale or rental of any information about you, to anyone, for any purpose.
• No newsletter, no marketing email, no notifications — there is nowhere to give an address, so there is nothing to send anything to.
• Nothing about what you do with the files or offsets after you download them. Once a response leaves this server, this site has no visibility into it whatsoever.

Who else is involved

Four third parties are in the path of a normal visit, and no others.

The Google Fonts request is worth being explicit about, because it is the one thing on this site that contacts a third party before you have consented to anything. It is treated as essential rather than optional: it fetches a typeface and nothing else, it is behind a complete fallback so the site renders fully without it, and it carries no identifier of any kind. If you would rather it did not happen at all, a content blocker that blocks fonts.googleapis.com leaves this site entirely functional — the pages simply render in your system font.

Downloads are answered with a redirect to Cloudflare R2 rather than served through this machine, which means the download itself is a request to Cloudflare and appears in their logs rather than ours. This is done so that a large file is delivered by infrastructure built for it; the side effect is that this site does not know whether a download you started ever finished.

Legal basis, if you are in the UK or EU

• Legitimate interest for request logs — a server cannot answer a request without processing it, and cannot be kept secure without being able to see abuse.
• Consent for audience measurement. Freely given, specific, and as easy to withdraw as it was to give: the footer link reopens the notice on any page, and declining costs you nothing — every page and every file remains fully available.

Retention

Request logs are kept only as long as they are useful for fault diagnosis and abuse handling, and are rotated out in the ordinary course. Analytics data is retained under Google’s own retention settings for this property, which are set to the shortest period the platform offers. Your consent choice stays in your browser until you clear it.

International transfers

Google and Cloudflare are global providers and process data outside the country you are reading this from, under the transfer mechanisms those companies publish. If that is not acceptable to you, declining analytics removes Google from the path entirely, and the pages and the API remain fully usable.

Your rights

Depending on where you live you may have the right to access what is held about you, to have it corrected or erased, to object to or restrict its processing, to receive it in a portable form, and to complain to your data protection authority. In practice there is very little to exercise these against here — this site holds no identifier that could be used to find "your" data, because it never collects one. What you can do immediately and without asking anyone:

• Withdraw analytics consent from the footer link on any page, which stops measurement at once.
• Clear this site’s data in your browser, which erases your stored consent choice and any analytics identifiers.
• Write to the contact route published on this project’s public repository with any request or question about this policy.

Children

This site publishes technical material — memory offsets, build identifiers and client package metadata — and is intended for developers. It is not directed at children, it carries no content aimed at children, and it collects no personal information from anybody of any age. We are conscious that the software this site tracks has a young audience, so to be explicit: there is no account system, nothing here asks a visitor for personal details, and no information is knowingly collected from a child under 13. If you believe a child has somehow provided personal information through this site, write to the contact route published on this project’s public repository and it will be deleted.

Changes

This policy changes when the site does. Because the site is open source, every change to this page is recorded in its public revision history, which is a more precise account than a date at the top of a page would be. A change that materially affects what is collected will also reset the cookie notice, so you will be asked again rather than quietly carried over.

Contact

Questions about this policy, or about anything on this site: the contact route published on this project’s public repository.