Your work memory belongs on your Mac.

Qubit does not keep a cloud database of your work memory. The work memory Qubit builds for you stays on your Mac.

That means your captured work context is not a shared company workspace, not a manager dashboard, and not a server-side profile of how you work.

Qubit uses macOS permissions to help with dictation, meeting notes, and questions about your work context.

It can read on-screen text through macOS Accessibility. It does not need pictures of your screen to build work memory.

macOS may also ask for Screen Recording permission. For Qubit, that permission is used so the app can hear system audio during meetings. It is not used to save screenshots of your work.

Your Qubit work memory lives locally on your Mac in an encrypted store. The key lives in your macOS Keychain.

Encryption protects the local database if someone gets access to the file. Qubit itself still needs to decrypt the information it uses while it is working for you.

Some processing uses service providers. Audio may be sent to speech-to-text services for transcription. When you ask Qubit a question, a small relevant slice of context may be sent to a language model so it can answer.

This is different from storing your work memory in the cloud. Qubit is designed so the durable memory stays on your Mac, while limited processing happens only for the job you asked it to do.

Qubit does not join meetings as a participant. There is no Qubit attendee in the room.

You remain responsible for using meeting capture lawfully and respectfully, including getting consent where your situation requires it.

Qubit is meant to be controlled by the person using the Mac. Meeting capture can be controlled by platform where the app supports it, and the product is designed around clear permission moments rather than hidden capture.

Qubit is not built as an employer monitoring product. There is no team dashboard that lets a manager read your work through Qubit.

Qubit is early software. It is improving quickly, and these pages will change as the product changes.

The rule we want to keep is simple: when a privacy or data-handling detail changes, the public explanation should change with it.