​

privacy

last updated: 2026-05-25 dripos is local-first. Customer history is stored and searched on your Mac.

​

stays on your Mac

These stay local during normal use:

• synced message and meeting history
• Inbox and timeline data
• reply drafts and review status
• generated Account Signals
• local source tokens and LinkedIn bridge session metadata
• AI provider keys you save in Settings

iMessage history is read from Apple’s local Messages database after you grant Full Disk Access. LinkedIn profile pictures are not fetched aggressively. dripos prefers names, initials, source handles, profile URLs when already available, and local contact metadata.

​

reaches dripos services

dripos services may receive:

• your signed-in account and workspace
• integration connection status
• connection setup steps for sources like Google, Slack, Stripe, and Fathom
• Stripe connection metadata when Stripe is connected
• email-open signals used for local timeline updates

Normal Inbox, group timeline, draft, and Copilot views do not upload your local message history to dripos services.

​

reaches AI providers

If you use Anthropic or OpenAI, dripos sends the context needed for that AI request to the selected provider. If you use Ollama, the AI request stays on your Mac.

​

permissions

iMessage requires Full Disk Access to read local Messages history. Sending texts also requires macOS Automation permission for Messages. You can revoke permissions any time in System Settings > Privacy & Security.

​

sign out

Signing out removes the saved app session. It does not delete local history already synced on your Mac.

​

disconnect sources

Disconnect a source from Integrations to stop new sync for that source. Local history already synced on your Mac may remain until local app data is removed.