Explicit start
Meeting listening begins only after you start a session. Cold start never resumes listening or captures a screen.
Privacy and consent
Control starts before capture.
Juely is built for meetings where capture and outside assistance are allowed. It does not bypass system permissions, hide operating-system indicators, or record repeatedly in the background.
Bounded context
Conversation context retains at most two minutes or 8,000 characters and labels only microphone or system sources.
No screenshot archive
Temporary screenshots are deleted after success, failure, cancellation, and orderly shutdown.
No hidden capture loop
Screenshots require an explicit action. Conversation assistance never takes screenshots automatically.
Screen sharing
No false promise of invisibility.
Sharing a specific application window gives the strongest separation. Content protection adds another layer, but some macOS screen-sharing tools may ignore it during full-display sharing.
Juely never bypasses screen-recording permission prompts, capture indicators, monitoring, or operating-system privacy controls.
Codex and network
Know where context goes.
The active one-device installation or paired servant needs an installed, authenticated Codex CLI. Juely gives Codex the chosen local context using restrictive execution settings.
In paired mode, selected context crosses an authenticated but currently unencrypted WebSocket connection. Use only a trusted private network.
Plain answers
Privacy FAQ
Does Juely store screenshots?
Not by default. Temporary screenshots are cleaned up after each request and during orderly shutdown.
Does Juely identify speakers?
No. Transcript segments use microphone and system source labels only.
Is paired traffic encrypted?
Not currently. Pairing authenticates the peer, but screenshot and transcript contents use unencrypted WebSockets on the trusted LAN.
Coming soon
Stay in the conversation.
Join for product notes and private preview invitations.
Join waitlist