Privacy Policy
Effective July 18, 2026. Applies to securecoms.ai and the SecureComs service operated by MotiveFlow LLC.
The short version
SecureComs is built so that we cannot read your message content or your files. Encryption and decryption happen on your devices. Our servers store and route ciphertext. Help chats with the in-app assistant are the exception; they are described below.
We do collect the minimum we need to run accounts, billing, and the service itself, and this policy describes that plainly.
What we cannot see
Message content, attachments, and encrypted file content are end-to-end encrypted with keys held on your devices and your Agent Connectors. The server never holds decryption keys and cannot read this data, even under compromise or compulsion.
If you lose all of your devices and your recovery material, we cannot recover your encrypted content for you. That is a design guarantee, not a support limitation.
What we do collect
Account data: your email address and authentication identifiers, processed through Clerk, our sign-in provider.
Billing data: subscription status and invoices, processed by Stripe. Your card details go to Stripe directly and never touch our servers.
Service metadata: workspace, channel, and membership records, device and agent identity records, message timing and sizes, and tamper-evident audit entries. We can see who is in a conversation and when it is active, but not what is said.
For each agent, SecureComs servers keep the latest summary of how the agent handled your most recent message in your private chat with it: when that summary last changed, which built-in tools it offered, how many connected-app tools it offered, which tools your own settings turned off, whether a voice helper or another member the agent did not recognize was in that chat, and, if tools were off, the reason (for example, that the agent could not confirm a message came from you). The summary never includes your messages, what the agent did with its tools, or data from your connected apps. Only you can see it.
Agents send their software version numbers to SecureComs so we can tell you when an update is available. No message content is sent.
Help chats: what you type to the Help assistant and its answers. Help chats are not end-to-end encrypted. They are stored by SecureComs and sent to Anthropic, together with the account details the assistant looks up, to generate answers. SecureComs keeps them for 90 days after the last message, or, if a chat becomes a support ticket, for two years after the ticket is opened. Anthropic deletes what it receives within 30 days, except content it flags for a usage-policy violation, which it may keep for up to two years. Messages you send to our support team, whether directly or after the assistant hands you over, are never sent to Anthropic. You can delete your Help history in the Help panel. Deleting it removes the messages SecureComs holds; it does not remove Anthropic's copy or the short summary on a support ticket, which is kept until the ticket is deleted.
Contact form submissions: the name, email, company, and message you send us, delivered to our sales inbox by Resend and used to respond to you.
What we don't do
We do not sell your data. We do not run advertising. The marketing site sets no tracking cookies.
Service providers
We use a small set of subprocessors to run the service: Clerk (authentication), Stripe (payments), DigitalOcean (application hosting, database, and encrypted object storage), Vercel (marketing site hosting), Resend (transactional email), Cloudflare (DNS), Anthropic (the AI model behind the in-app Help assistant; it receives what you type to the assistant and the account details the assistant looks up for you, such as your plan, usage and device names), LiveKit infrastructure for voice features, and, for calls with an AI agent only, Deepgram (speech to text) and Cartesia (text to speech). Each receives only what its role requires; none can read your encrypted content.
Google user data
This section applies when you connect a Google account to a SecureComs agent.
- your Google Calendar events; and
- the Google Docs, Sheets and Drive files that you pick. You pick files in Google's own file picker, which your agent opens in your browser. Your agent cannot open other files in your Drive, apart from files that SecureComs creates. Files you pick are available to each of your SecureComs agents that you connect to the same Google account.
Your agent cannot read your Gmail. Your agent does not change, send or delete anything in your Google account.
When you ask your agent a question, your agent sends the Google data that it needs for the answer to the AI model provider that you chose for that agent. That provider handles the data under your agreement with that provider. Your agent can also keep notes from a conversation in its memory on the same computer or server. You can delete that memory at any time.
SecureComs servers can see which Google services you connected to each agent, the status of each connection (for example "connected", "needs sign-in" or an error type) and when it was reported, and, for each request, whether your agent read from or changed a Google service. SecureComs servers never see your Google sign-in token, your Google data, your Google account address (unless you type it into a connection name), what your agent searched for, or which files you picked.
Retention and deletion
Audit records are retained according to your plan tier. Encrypted content persists until you delete it or your workspace is deleted. When your subscription ends, your workspace drops to the Free tier and your data stays encrypted and yours.
You can request deletion of your account and associated data by contacting us. We will honor applicable data-protection rights, including access and deletion requests under laws such as GDPR and CCPA.
Changes and contact
If we change this policy, we will update this page and its effective date. Material changes will be announced to account holders.
Questions or requests: use the contact form on this site.