How Orbit Sharing Works
A share is an explicit publication of a setup. It is separate from your editable local data, and the recipient does not receive your local result history.
Remote wheels are snapshots
When you publish a Wheel, Roulette or Coin setup, Orbit sends a separate snapshot and its active images through its sharing functions. The remote data is kept in site-wide stores so publishing a new application deployment does not intentionally replace the snapshot store. Your original editable wheel remains local.
A published snapshot does not keep following later edits. If you rename entries or change weights locally, the existing link still represents what you published earlier. Create a new snapshot when you want to share a changed setup. Local history and unrelated wheels are not included, and images unrelated to the active snapshot are not uploaded.
Anyone with the link can view it. A long unguessable identifier helps avoid casual discovery, but it is not an account permission system. Do not publish confidential names, private photographs or information that should be limited to a verified recipient. A link can be forwarded, saved or included in a screenshot.
Read-only means the original stays separate
A shared view can run the tool for that viewing session without editing the creator's snapshot. Its results do not appear in the creator's local history. Wheel and Roulette may show initial motion until the first spin of that viewing, while reduced motion disables it. Shared pages are excluded from the sitemap and carry noindex instructions; that does not make their content private.
Make a copy creates an editable setup in the recipient's local browser. It does not transfer ownership of the remote snapshot or give permission to manage the creator's other links. The copy can be changed independently. This is useful for a group that wants to start from the same options without overwriting the original.
The browser's Back and Forward controls navigate between local tool pages as usual. A shared URL stays a shared URL during read-only viewing. After copying, the recipient moves to an editable local experience. No local wheel ID or name needs to appear in its public base route.
Small utilities share configuration in the link
Number Picker, Dice Roller and Yes / No use a different format: their small validated configurations are encoded directly in a /view/ link. No server snapshot is created for those links. Number ranges, dice settings or answer labels are included; previous result history is not. The link is not encrypted, so custom labels should not contain confidential text.
Opening one of these links locks the displayed setup while allowing fresh local results for that viewing session. Make a copy saves the settings to the recipient's corresponding local tool. It does not import the sender's history. A reload begins a new shared viewing session, and the creator cannot remotely delete a configuration that someone has already saved in a URL.
Team Generator does not publish a setup link in this version. Its TXT, CSV and JSON exports provide an explicit way to distribute completed groups. Those files may contain participant names or images, so decide who should receive them. A full backup contains even more local data and should not be used as a casual public share.
Connection, deletion and sensible limits
Creating or deleting a remote snapshot needs internet. Opening a remote snapshot for the first time needs a connection too; offline caching does not guarantee that every remote link is already available. Local utility-config links need no server fetch once the application shell is cached, though opening them on a new device still requires loading the site first.
Remote share creation enforces size and rate limits. If your setup is too large, reduce the images or entry count rather than repeatedly submitting it. Existing local data remains separate when publication fails. Do not assume a share is a permanent archive; keep a downloadable backup for work you need to retain.
If you remove a managed remote share, the hosted snapshot may become unavailable, but previously downloaded copies, screenshots and forwarded data cannot be recalled. Use sharing only when that limit is acceptable. Before copying a link, review the exact active setup, its labels and images, and choose a local display instead if the group does not need a published snapshot.