your data,
your controls.

The short version

local Mac data such as iMessage is read on your machine after you grant macOS permissions. Cloud systems store account metadata, billing and entitlement state, encrypted OAuth tokens for hosted integrations, hosted integration records when enabled, product telemetry, and selected context only when a hosted AI or cloud automation feature needs it.

we do not sell your data, share it with advertisers, or train a shared AI model on your messages. Local LLM generation sends prompt content to local Ollama; BYOK cloud generation sends selected context to the provider you configure.

What we collect

Account data

• your email, name, workspace identifiers, member roles, and sign-in state
• OAuth tokens you grant for connected services, encrypted at rest
• billing details, plan state, invoices, and payments handled with Stripe

Product and automation data

• sources connected, features used, app version, and settings
• automation choices such as selected people, channels, limits, templates, and status
• hosted integration records from Slack, Gmail, Calendar, Stripe, or lead sources when enabled
• selected context needed for hosted AI, cloud automation, follow-up, reply handling, or booking
• AI provider, model, operation, token counts, aggregate counts, and product telemetry
• error logs, designed to avoid message bodies where possible

Support data

• messages you send to [email protected] or through support channels
• screenshots, exports, logs, or recordings you voluntarily attach to a request

Local Mac data

• iMessage / chat.db. the Mac app reads iMessage locally when you grant the required macOS permission, including supported direct and group chats. the raw chat.db file is not uploaded as a source file.
• local index. dripos can keep a local index on your Mac so searches and context work without making our cloud the primary copy of your local conversations.
• AI provider paths. hosted dripos AI sends selected context through our backend, BYOK sends selected context to the cloud provider you configure, and local LLM generation sends selected context to local Ollama. BYOK and local LLM usage may still report provider, model, operation, and token counts for entitlement and billing.

How we use data

• operate the Mac app, backend, billing, and connected account flows
• send first messages, follow up, handle one-to-one and group replies, and book meetings when automation is enabled
• generate messages, summaries, signals, and call context from the sources you choose
• show plan, credit, and usage state inside the app
• debug, secure, and improve the product
• respond to support, privacy, legal, and security requests

How we store data

cloud metadata that reaches our backend is stored on managed cloud infrastructure. Transport is protected with TLS 1.2 or higher. Managed databases and cloud storage use encryption at rest. Sensitive tokens and secrets are additionally protected with application-level encryption where configured.

account data is retained for the life of your workspace plus a limited deletion window unless a longer period is required by law, tax, security, or legitimate business needs. Product telemetry may be retained in aggregate form after raw records expire.

Third-party processors

• Stripe for payment processing, checkout, invoicing, and billing records.
• DigitalOcean for compute and database hosting.
• Cloudflare for CDN, DNS, security, and performance.
• Sentry for error monitoring and reliability.
• AI providers for hosted dripos AI or customer-managed Anthropic/OpenAI keys depending on your plan and settings. Local Ollama runs on your machine and is not a cloud AI processor for prompt content.
• Connected tools such as LinkedIn, Google, Slack, Stripe, calendar providers, and meeting tools when you authorize them.

Your choices

• choose which sources to connect
• choose the people, channels, limits, templates, and rules before automation runs
• choose hosted dripos AI, BYOK cloud providers, or local LLM where your plan allows it
• pause automation at any time
• revoke connected account access through dripos settings or the provider
• remove local app data and the local database from your Mac

Your rights (GDPR + CCPA)

if you are in the EU, UK, or California, you may have the right to access, correct, export, or delete personal data. You can also object to processing or restrict it. Submit a request to [email protected] and we will respond within 30 days where required by law.

Children

dripos is built for businesses. it is not intended for anyone under 16 and we do not knowingly collect data from minors.

Changes to this policy

we may update this policy from time to time. for material changes we will notify workspace admins or users through the app, email, or another reasonable channel. the "last updated" date at the top of this page reflects the current version.

Contact

questions, requests, or concerns: [email protected]. for general support, write to [email protected].