Privacy policy
Shared Pointers connects people in a Discord voice channel so they can display named pointers during a screen share.
The companion does not send screen pixels, video, audio, remote clicks or keyboard input. Discord handles your actual screen share. Pointer coordinates are sent while you actively point.
Who operates this app
This Shared Pointers test service is operated by Daniel Aherne. For support, privacy questions or a request to access or delete information, contact @daniel2459 on Discord. Include your Discord user ID if you know it; never send a password, bot token or other secret.
Information used to provide the service
- Discord identity: signing in requests Discord’s
identifypermission. The coordinator retains your Discord user ID and display name. It does not request your email address, contacts or chat messages, and never receives your Discord password. - Voice and stream metadata: in servers where the bot is installed, it receives voice-state metadata, including server, channel and user IDs and whether someone is streaming. This can include people who have not installed the companion. The app uses the relevant metadata in memory to match companions in the same voice channel.
- Companion status: the coordinator uses your enabled/paused status, selected display’s aspect ratio and blocked participant IDs to route pointers and enforce your choices.
- Active pointers: while you point, the companion sends the selected presenter’s ID and normalized cursor coordinates. It does not upload a history of your mouse movements outside pointing mode.
- Sessions: the server stores your ID, name, a hash of an app sign-in token and its expiry so it can authenticate future connections.
What other participants can see
Companion users in the same voice channel receive relevant participant IDs, display names and available streams. The presenter receives the active pointer’s name, colour and position. Other Discord viewers can see the rendered pointers through the shared display when Discord captures the overlay.
Storage and retention
The coordinator keeps current voice metadata and pointer positions in memory; it does not write a pointer history to disk. Active pointers expire after about 0.9 seconds without an update and are removed when participation conditions fail, including pause, blocking, leaving or stopping a stream.
App session access expires after 30 days. Expired session records are removed when a new session is issued; this is not a guarantee that every stored record is deleted exactly after 30 days. A successful sign-out deletes the current session record. You can contact the operator to request removal of other records associated with your Discord ID.
On your computer, the companion stores its coordinator address, selected display, enabled/startup preferences and blocked-user IDs in local settings. The Windows app-session token is encrypted with Windows DPAPI for your Windows user. The Mac alpha stores its app-session identity and token in your login Keychain; Mac preferences are stored under your user Application Support folder. Live coordinator credentials are restricted to the service operator on the server and are not included in companion downloads. The older Windows test setup stores its credentials using Windows DPAPI.
Service providers and network data
Discord provides identity, voice-state metadata and screen sharing. The hosted coordinator runs on Oracle Cloud in London, United Kingdom. Network and hosting providers can process connection information such as IP addresses. Earlier temporary test connections used Cloudflare Tunnel. Those addresses have been retired in favour of the hosted coordinator. This information page is hosted using OpenAI Sites and its hosting infrastructure. Those providers process website visits and network requests under their own policies.
The app has no advertising or analytics integration and does not sell information. Coordinator HTTP access logging is disabled in this build. This does not mean that Discord, Cloudflare or the website hosting providers keep no infrastructure logs.
See Discord’s privacy policy, Cloudflare’s privacy policy and OpenAI’s privacy policy for their practices.
Mac input permission
The Mac alpha requests Input Monitoring only when you select the shortcut permission button. It checks the pointing modifiers locally and checks the foreground Discord app and window bounds to restrict pointing to fullscreen viewing. It does not read window titles, record screen pixels, inject input or send key events. Input Monitoring can be revoked in macOS settings. The optional Mac check saves a local report containing app version, display count and check results; that report does not contain sign-in tokens or a pointer history.
Your controls
Pointers start disabled. You can enable or pause the companion, release Right Ctrl on Windows or Control + Option on Mac to stop pointing, block an individual, sign out or quit. Signing out removes the local sign-in file or Mac Keychain item and attempts to revoke the current session; it preserves your local preferences. Pausing a companion does not stop the server bot receiving Discord voice-state metadata. A server administrator can remove the bot from the server.
Contact @daniel2459 on Discord for access, correction or deletion requests, or to raise a concern about this app’s handling of information. Any privacy rights available under applicable law remain available. If this test service’s handling of information changes, this page will be updated.