Privacy & control
Your work.
Your permission.
You choose what Camus can capture and whether summaries can leave your Mac. Local capture and cloud processing are separate choices.
Read the privacy policy
Where your data goes
Local journal.
Separate cloud consent.
On your Mac
Your raw journal stays local.
Your work journal stays encrypted on your Mac. Detected secrets are filtered locally.
The published policy specifies a 14-day retention period for the encrypted local journal. Other data has its own retention rules in the privacy policy.
With your consent
Redacted summaries can leave.
After separate cloud consent, redacted summaries can go to Camus’s servers. Some processing happens there.
Enabling Mac capture does not grant cloud consent. Detected secrets are removed before a summary is sent.
Capture boundaries
Camus knows
when to look away.
Recognized sensitive contexts are blocked.
Recognized password managers, banking, health, HR, payroll, and private windows are blocked from capture.
Some contexts stay metadata-only.
Email, messaging, terminals, and calls are metadata-only contexts, without message bodies or transcripts.
Recognition has limits. Review drafts for confidential details before you publish or share them.
The controls
Pause. Inspect.
Have the final say.
Pause capture and sending.
You can pause capture and summary sending at any time.
Inspect what happens.
You can inspect attempted sends and their outcomes.
Review before publishing.
You review, publish, and send. Camus prepares the content for your judgment.
The practical questions
Clear boundaries.
Does my raw journal leave my Mac?
Your raw journal stays encrypted on your Mac. Redacted summaries can leave after separate cloud consent, and some processing happens on Camus’s servers.
Is everything deleted after 14 days?
The 14-day period applies to the encrypted local journal. Other data has separate retention rules. The privacy policy explains those rules.
Does Camus read my private LinkedIn messages?
No. Camus does not read private LinkedIn messages or send messages on your behalf. You review, publish, and send.
What is planned for team privacy?
The V2 plan keeps personal journals, chats, and voice examples private, including from admins. Shared knowledge, drafts, and prospects have explicit permissions. Internal access does not automatically permit public reuse.
This is the team product direction, beyond the current individual beta. Read the V2 plan.
Read the policies.
Ask us directly.
This page is a guide to the published policies.
Privacy policy Terms
A question about your data? Talk to Nathan