Solar System SimulatorAccuracy & sources

Legal

Privacy

Local simulations and page statistics.

This policy covers solarsystemsimulator.com. It was last updated on October 21, 2026.

The simulator

The simulators run entirely in your browser. Changing a date, visiting a body or editing a scene runs on your device without uploading the scene. When you save a picture, it is made on your device and goes straight to your downloads.

The Sky inspector also calculates on your device. Latitude, longitude and time inputs are not uploaded or included in analytics. Export positions creates a local file containing the entered coordinates and moment; sharing that file shares those details. Location is not added to the simulator's share links.

The planets visible tonight and meteor shower tonight planners also calculate on your device. To open on a nearby city they read your device's time zone setting, on your device. The place you choose, any coordinates you type and the date are not uploaded or included in analytics. Searching for a city loads one list of places from this site, the same for everyone; what you type stays on your device. The planners keep the place you chose in this site's local storage, shared between the two, so they open there next time; your browser's site-data controls remove it. The seasons simulator reads that remembered place, or your time zone's main city, the same way, to open its latitude; the latitude you set there is not stored or sent.

The asteroid impact simulator also calculates on your device. To open aimed at a nearby city it reads that remembered place, or your time zone's main city, the same way. The place you aim at, whether you pick it on the globe, search for a city or type coordinates, is not uploaded, not included in analytics and not stored: the planners' remembered place is left as it was. Its Share link holds the place, the asteroid and the moment after the # in the address, which browsers do not send to a website; whoever opens the link sees that place. The globe's map arrives as square picture tiles from this site as you move and zoom. Each request names one tile, at its finest a square of the map 5.6 degrees on a side (about 600 km from north to south), so the server that sends it, Cloudflare's, can tell which broad region is on screen, though not the point you chose.

The solar system and eclipse simulators load the same map tiles once you zoom in on Earth past the opening view, so the server can likewise tell which broad region of Earth is on screen. The tile requests carry nothing else about the view.

Gravity scene files are also made and opened locally. The browser keeps one autosaved gravity scene in this site's local storage, including its bodies, velocities, time and view settings. Scenes → Clear autosave removes it and pauses autosaving for the visit. Your browser's site-data controls can also remove it. The site's local storage also keeps the list of gravity challenges you have finished, so they stay marked on a later visit. That list holds nothing else and is not sent anywhere. A downloaded scene file remains wherever you saved it; sharing that file gives its contents to the recipient.

Share links contain the selected body or black hole scene, moment, camera and display settings. Opening a shared link sends its address to Cloudflare to load the page. Google Analytics removes those scene parameters and fragments from its page-view address; only the limited campaign tags described below are retained.

Gravity scene links hold the whole scene after the # in the address: bodies, any names you gave them, speeds, time and view settings. A black hole scene you have built or changed travels the same way: its black holes and stars, their settings, speeds and the view. Browsers do not send that part of an address to any server, so Cloudflare, our page counts and Google Analytics never receive it. Anyone you send the link to can read the scene. Opening a gravity link does not replace an autosaved scene you have not yet resumed or dismissed; black hole scenes are not saved on your device.

What the site records

These anonymous Cloudflare counts are separate from Google Analytics, described below. We do not use advertising identifiers.

When a page is requested, our server records a count with: the page address, the domain of the website that linked to it (if your browser shares one), a broad source category taken from that domain or the link's campaign source tag (a named search engine or AI assistant, this site, another site or none), the country (worked out by our hosting provider from your connection; the IP address itself is not stored in these counts), whether the device is a phone, tablet or computer, and whether the request looks automated.

We also collect anonymous reliability counts: whether the page script started, broad error categories, and measurements of loading speed, responsiveness and layout movement. For the slowest response on a page, they also note how its delay divided between waiting, running and redrawing, whether it followed a tap, click or key press, and the broad kind of control involved (such as a button, link or the simulator view). In browsers that report it, they also note whose script ran longest during that response (this site's, a browser extension's or another site's), how it was started, and how the time divided between scripts, page layout and drawing, never the script's address or name. For page loading, they also note how the wait divided between connecting, the server's reply and fetching and drawing the largest image or text, whether that was text or an image, when the largest layout movement happened, and whether the page was opened fresh, reloaded, returned to or loaded in advance. They contain no error messages, typed text or visitor identifiers.

Anonymous simulator counts record the first complete scene draw and use of view, share, scene save/open/resume, undo/edit, adding a first body to a gravity scene or a first object to a black hole scene, experiment, comparison and focus controls, and starting, first trying (its first change to the scene) or finishing a gravity challenge (which of the six). They include only the simulator category; for its first draw, elapsed loading time and when its start-up code began, its 3D view was built and its opening pictures were ready; and once per page, the typical time the device took to draw the scene when it opened, how often it waited for the previous picture to finish, the graphics detail Auto then chose (on touch screens, also how many steps it raised the detail from its opening), the typical drawing time at that detail and whether it switched to its lighter picture for slow devices; if it switches later in the visit, also the typical drawing time that caused it, the detail at that moment, how long the page had been open, and how quickly it draws after the switch, based on a small frame sample. If the device's graphics stop during a visit, they also note that once, whether the graphics came back, and how long the page had been open. They never include scene settings, file names or contents, dates, custom body names or visitor identifiers, and are not sent to Google Analytics; only the fixed tool_used event described below reaches it. A download count means it was requested, not that a file was successfully saved. The planet name generator makes its names in your browser and sends none of them anywhere; it counts only its first use on a page and the style chosen (with a meaning, catalog style or made up). Its gravity simulator link carries the names after the #, which browsers do not send to any server. The asteroid impact simulator also calculates in your browser and sends none of its inputs; it counts only its first use on a page and whether a famous impact was chosen. The planets visible tonight planner counts only its first use on a page and whether it was a change of place, night or time, looking around its sky or playing its time-lapse, never which place, night, time or direction. The meteor shower tonight planner counts only its first use on a page and whether it was a change of place, night or time, a jump to a shower's peak night, looking around its sky or playing its time-lapse, never which place, night, time, direction or shower.

These counts are kept in Cloudflare Workers Analytics Engine for about three months and are used to see which simulators are used and to find problems.

Hosting diagnostics

Cloudflare keeps sampled request and error logs for up to seven days to help diagnose server failures. These hosting logs can include requested page paths (query strings are removed) and ordinary request metadata. They are separate from the anonymous tool counts described above; application inputs are not added to them.

Google Analytics

We use Google Analytics 4 to understand page visits and whether a visit used a tool: the first edit, first added body, experiment or comparison in a simulator, or the first use of the planet name generator, the asteroid impact simulator or the planets visible tonight or meteor shower tonight planner, on a page sends it one fixed tool_used event with the page path, never what you entered or the result. It may set first-party _ga cookies to recognize repeat visits. Google receives the page path, page title, limited campaign tags, the referrer's origin, and ordinary browser and connection information, including your IP address and the approximate location our hosting provider works out from it (country, region, city and approximate coordinates). Our server passes that location on because these requests reach Google through this website. Automatic enhanced measurement and advertising features are disabled. We do not send tool inputs, file names, sequences, calculations or simulated scene settings to Google Analytics. Event-level data is retained for 14 months; aggregate reports may remain available longer. See Google's Privacy Policy.

Google Analytics does not load for visitors in the EEA, UK, Switzerland or Quebec, when location is unknown, or when the browser sends Global Privacy Control. Automated and synthetic test traffic is excluded. You can remove analytics cookies through your browser's site-data controls.

Hosting

The site runs on Cloudflare, which processes every request (including your IP address) to deliver the site and protect it from abuse, as described in Cloudflare's privacy policy at cloudflare.com/privacypolicy.

Children

The simulations are available without an account. The site does not ask students for names, email addresses or school details. Google Analytics may use cookie identifiers as described above; it does not receive the scene or simulation inputs.

Email and changes

If you email us, your address and message are used only to reply. If what the site records changes (for example, if advertising or a paid option is added), this page will be updated before that change goes live.

Contact: hello@solarsystemsimulator.com.