What becomes public when you share Toolchest sessions with Community?
Check which completed sessions are shared, what edits and deletions change, and why turning sharing off may wait for a connection.
The Share sessions with Community switch in Tink’s Toolchest is a choice about your completed session history. It is off by default. You can explore Community without publishing your own results, and you can keep using on-device session history privately.
Before enabling it, review the sessions already on this device. The current sharing control covers existing completed sessions as well as future ones. It is not a “share only the next game” control.
Check the label in your installed version
This guide describes the control labeled Share sessions with Community, included in version 2.4.0. Earlier versions used Share new sessions publicly and retained previously shared snapshots after local edits or deletions. Check your installed version and the label before relying on the behavior described here.
In the current sharing panel, enabling the switch opens a name dialog and asks you to confirm sharing. Your completed sessions can appear with your chosen username or Anonymous. A blank display name does not make individual sessions unlinkable: the public profile can still associate your results with each other.
The shared record includes the game, strategy, session timing, recorded profit or loss and play count where available. Review any manually entered or practice sessions before making that history public. An active session is separate from a completed one; the service publishes completed records.
What a correction changes
With current Community sharing enabled, changing a completed local session updates its corresponding shared result after synchronization. Deleting a local session removes its public copy. These are changes to the record, not a way to change what happened at the table.
For a hypothetical example, you discover that a completed session was entered as a $40 gain when your notes show a $40 loss. Correct the local record, then allow the app to synchronize and inspect the corresponding Community result. Compare the date, game and strategy so you do not check a similarly named session from another day. Do not delete a session merely to test the sharing behavior; keep records you still need.
The observed-results guide explains another recordkeeping distinction: entering a result you watched does not mean you placed a wager. Public totals are only as meaningful as the records behind them.
Turning sharing off while offline
Turning the switch off requests that your sessions, profile results and leaderboard contributions be hidden. It keeps your local sessions. When the request cannot reach the service, the panel can display Going private when you’re back online. Treat that message as a pending change, not confirmation that the public result has already disappeared.
Reconnect and let the app complete the request. Check the panel again and inspect your public result if you need to confirm its visibility. If the message remains pending, note your app version and the exact status when contacting support. Reinstalling or clearing app data is not a useful first step; it can remove local history and profile credentials.
Turning sharing off is also different from requesting deletion of retained service records. The privacy policy explains the deletion process and support contact. Do not send payment-card details or account passwords with a request.
Check again before sharing resumes
If you edit or delete records while sharing is paused, review those changes before turning it back on. The current app applies the local changes when sharing resumes. Wait for Sharing your completed sessions… to finish before treating the visible Community list as settled.
A short checklist is enough: correct device history, intended display name, deliberate sharing choice and completed synchronization. Community results are personal records, not predictions or evidence that a casino strategy guarantees a profit. Keep your play limits independent of a leaderboard.
Tink’s Toolchest brings session tracking and casino tools together; sharing remains optional.
Sources and verification
Product steps were checked against the version 2.4.0 sharing panel and synchronization implementation. No real sessions were published or deleted to prepare this guide.