Privacy

Short version: your files never leave your browser, this site sets no cookies, keeps no account, and runs no analytics. The rest of this page is the detail behind that sentence.

Your files

When you drop a world, an item or a texture on this site, the browser reads it into memory on your own machine. It is checked there and rendered there. It is never sent to this server, or to any other host.

This is not a policy that could be changed quietly — there is no upload address to send a file to. The server only ever hands out the site's own pages, scripts, stylesheets, fonts and preset data. It has no route that accepts a file.

To let the renderer resolve a world's own relative paths — its textures, its Inline children, its sounds — the World and Item checkers hold your files in a Service Worker running inside your browser, and serve them back to the page from there. That worker keeps everything in memory. It writes nothing to disk, and it makes no network request of its own. Load another world and the previous one is released; close the tab and all of it is gone.

Cookies

None. This site sets no cookie of any kind, and the server sends no Set-Cookie header. There is nothing to consent to and no banner to dismiss, because there is no optional tracking here to turn off.

Browser storage

Two, and only two, of the places a site can keep data in your browser are used here. Both are needed to make the tools work, and neither records anything about you.

• Local storage — one entry, written by the renderer once it has drawn a scene: X_ITE.X3DBrowser(1).BrowserOptions.Rubberband, set to false. It remembers one viewer setting — the elastic line X_ITE draws while you turn a model, which this site switches off. That is the whole of it: no identifier, no record of what you loaded, and nothing that is sent anywhere. Clearing your site data removes it, and it is written again next time a scene is drawn.
• Session storage — not used.
• IndexedDB — not used.
• Cache Storage — not used. The Service Worker stores nothing offline; it is a router for files already in memory, not a cache.
• Service Worker memory — used on the World and Item checkers, and essential. It holds the files you dropped for as long as you are working on them, so that the renderer can find them. It is how the checker functions at all, not a way of recording anything about you. You can remove it at any time from your browser's site-data settings.

Neither of these is advertising, and neither is tracking. There is no optional storage here to switch off, which is why this site has no cookie banner: a banner that offers no choice is a nuisance, not a consent.

Analytics and third parties

No analytics. The Checker does not run analytics or send analytics requests from its application code. There is no analytics product, no tracking pixel and no third-party script in anything this site serves. Every script, stylesheet, font and data file is served from this site's own address.

That claim is about the application, and it is worded that way on purpose. This site is served through Cloudflare, and a CDN in that position is able to inject its own measurement script (Cloudflare calls it Browser Insights) into a page without the application knowing. Saying flatly that "no beacon exists" would be a promise about somebody else's infrastructure that we cannot keep. What we can tell you is what happens if one ever appears: the Content-Security-Policy below allows scripts from this origin only, so an injected beacon is blocked before it runs and it sends nothing.

The site's Content-Security-Policy allows the page to fetch from this origin only, so a third-party call cannot be introduced by accident. The renderer has two optional paths to outside hosts of its own — an image proxy and a Markdown library for its built-in menu — and that policy blocks both. Neither is used here.

Your browser will contact another host only when you click a link that goes to one, such as the Cybertown Mall, Cybertown Revival, or the credited colour and material sources on the Material page. This site sends a no-referrer policy, so those sites are not told which page you came from.

Accounts

There are none. This site asks for no name, no email address and no password, has no sign-in, and takes no payment.

Server logs

The application itself keeps no record of visits: it writes no access log and no request database. Like any site, it is reached through hosting infrastructure that may keep its own short-term operational logs of network requests, which typically include an IP address and the address requested. Those logs are not created or read by this application, and this page does not state a retention period for them, because setting one is not something this site's own code does.