Privacy
Updated
Stereofold is published by Jacob Vogan. This page covers the Stereofold 0.1.21 plugin and project website.
The plugin runs a molecular viewer and MCP server on your computer. It requires no Stereofold account and includes no publisher-operated telemetry or advertising service. Your agent host, requested source sites, optional providers, and website host have their own data policies.
Data used by the plugin
Stereofold processes the structures, local files, URLs, lessons, annotations, and commands you choose. It uses session identifiers, pairing credentials, browser information, rendering status, and device input to control a scene. Optional voice features process recordings, transcripts, and reply text.
Your selected agent host receives conversations and tool inputs and results, which can include file paths, annotations, transcripts, and diagnostics. Coordinates pasted into chat follow that host's policies. Direct file loading reads coordinates through the local server.
Network destinations
- Public PDB and AlphaFold requests contact RCSB or EMBL-EBI. The destination receives the requested identifier and your network IP address. A supplied URL contacts its destination; uncached lesson stages contact their declared source.
- The local inspector serves your scene to a browser or host panel. Private Wi-Fi sharing sends coordinates and edits to authorized paired viewers over HTTPS. Use a network you trust.
- Meta Web Launch receives the viewer link, which can contain a one-time pairing code. An explicitly requested Cloudflare relay carries coordinates and scene traffic. Protect complete viewer links: a valid link can grant access to that share.
- Optional screenshots, exports, and recordings can contain the scene or surrounding visible information. Review them before sharing.
Voice routes
Controller push-to-talk uses the supplied on-device Apple recognizer or local Whisper. Recognized text can reach your desktop agent. With its separately configured OAuth helper, headset Talk sends audio to OpenAI Realtime for transcription.
OAuth narration sends reply text to its configured external helper and provider. The macOS system-speech route renders replies locally. Agent-host dictation follows the host's policies.
Storage and retention
Your computer stores configuration, certificates, remembered-device records, and optional bridge state. Remembered records contain a browser label, identifiers, timestamps, and a key digest; the headset browser stores its device key. Credentials have a 30-day validity limit and can expire earlier under the idle setting. Expiry limits access; stored copies can remain.
Public coordinates and lesson stages can remain in local caches. The public-source cache excludes pasted coordinates, local-file contents, and arbitrary URL sources. Saved exports, recordings, and other files remain until you delete them.
Push-to-talk attempts to remove temporary audio after processing and cleanup; an interruption can leave files. Optional transcript logging and shell-command or bridge delivery follow your configuration.
OAuth reply-audio cache entries expire after seven days. When new audio is cached, the cache attempts to remove expired entries and keep at most 64 entries. Hosts, helpers, operating systems, backups, and external providers can retain their own records.
Your controls
Use typed requests to avoid microphone capture. Choose local transcription and system speech for local voice routes, and private Wi-Fi for sharing without a public relay. Ask your agent to stop sharing, revoke a viewer, or forget a remembered headset. Clear companion-site browser data to remove its device key.
Delete caches, saved files, optional transcript logs, and bridge files you no longer need. Closing a share does not erase those files or other services' records.
Website and contact
The static GitHub Pages website includes a bundled public-structure demo and no project-added advertising or analytics tracker. Your browser can cache its files. GitHub logs visitors' IP addresses for security, as described in its Pages documentation and Privacy Statement.
Use GitHub Issues for privacy questions you can discuss publicly. Keep private data, recordings, and credentials out of public posts. An updated date identifies changes to this page.