Step 1
Understand what happens after the # character
A shareable wheel can encode supported entries and settings in the URL fragment—the portion after #. Browsers do not send that fragment in the normal HTTP request, so the site server and ordinary request logs do not receive it. The receiving page reads the fragment locally to reconstruct the shared view.
That transport property is useful but does not make the link encrypted or confidential. Anyone with the complete URL can inspect, forward, screenshot, or decode its contents. Browser extensions, password managers, clipboard tools, messaging previews, workplace monitoring, and screen recordings may also observe what the user handles locally.
Step 2
Review what the link includes and deliberately leaves out
Before sharing, inspect the generated preview or documented payload. A collaboration link may include wheel names, labels, weights, modes, colors, or other supported configuration. To reduce exposure and keep links manageable, history, scores, local file references, unrelated workspaces, and some large state should remain outside the share format.
Do not assume that an omitted history makes the remaining labels harmless. A class roster, candidate list, medical choice, access code, or unannounced product name can be sensitive on its own. Use the full workspace export for controlled backup, not as a substitute URL when the share payload is too large.
Check before continuing
- Open the share preview and read every visible label.
- Confirm weights and modes are intended for the recipient.
- Remove unrelated wheels and private context.
- Use an export, not a larger public link, for a protected backup.
Step 3
Replace personal or confidential labels before creating the link
Use initials, seat numbers, public handles, or event ticket aliases when the recipient does not need full identities. Keep the protected mapping in the authoritative registration or attendance system rather than adding emails and phone numbers to a wheel. Avoid labels that reveal health, discipline, performance, immigration, or other sensitive context.
Minimization should happen in a copy. Editing the only authoritative workspace to make it public can destroy information needed for the private workflow, while sharing the original can disclose more than intended. Name the sanitized copy clearly so the operator does not later update the wrong list.
Step 4
Handle receipt before analytics and external navigation
The receiving page should parse the supported fragment locally, validate size and schema, then remove it from the visible address before analytics or unrelated code can observe a long-lived copy. It should reject malformed or oversized payloads without sending the raw data to an error collector. The resulting wheel remains local to that browser unless the user explicitly shares or exports it again.
Recipients should verify the sender, active count, visible entries, weights, and mode before using the wheel. A valid fragment proves only that the payload can be decoded; it does not authenticate the sender or establish that the list is current.
Run it in this order
- Open the link only in the intended browser profile.
- Confirm the fragment disappears after a successful local import.
- Review the reconstructed list and rules against the sender's message.
- Delete the local copy when the handoff is no longer needed.
Step 5
Choose a delivery channel and retention period deliberately
A copied URL may enter clipboard history, synchronized devices, chat retention, email archives, support tickets, meeting recordings, and link-scanning systems. Use an approved restricted channel for non-public labels, address it to the intended recipients, and avoid posting the same link in a public document for convenience.
There is no remote revoke button for data already copied into a fragment. Deleting a message does not erase screenshots, browser history, or forwarded copies. If access must be revoked, treat the old payload as disclosed, create a new sanitized wheel or new identifiers, and communicate which version is authoritative.
Step 6
Use sharing for handoff and workspace export for recovery
Share links are intentionally bounded; a practical limit may allow only a few wheels, a restricted number of entries per wheel, and a maximum fragment length. These limits protect browser performance and discourage treating URLs as databases. Large rosters, image data, long-term history, and complete workspace recovery belong in a controlled export workflow.
A workspace JSON file can contain substantially more state and deserves stronger storage protection. Validate imports before replacing local data, keep backups out of public download folders, and delete superseded copies. Choose the transfer format by purpose: a minimized collaborative handoff or a protected operational backup.
Use the right surface
Tools mentioned in this guide
Common questions
Questions about sharing and privacy
Does the server receive data after # in a share link?
The browser does not include the fragment in its normal HTTP request. The page reads it locally, but the complete link remains visible to recipients and software that handles the clipboard, browser, chat, or screen.
Is a fragment-based share link encrypted?
No. Encoding is not encryption. Anyone with the complete link can inspect or decode the supported wheel data, so remove sensitive labels before sharing.
What is omitted from a share link?
The bounded collaboration format should omit state such as selection history and scores and may enforce wheel, entry, and total-length limits. Review the preview because the supported configuration that remains can still be sensitive.
Can I revoke a wheel link after sending it?
Not reliably. You can delete your message, but you cannot erase copied or forwarded fragments. Create a replacement with sanitized data or new identifiers and mark the old version invalid.
When should I use a workspace export instead?
Use a protected JSON export when you need complete recovery, larger state, history, or scores. Store it like a sensitive file and validate it before an import replaces local data.