Privacy policy

ClientCadence helps freelancers, consultants, agencies, and service teams turn rough project notes into client-ready drafts, organize those drafts in workspace History, and optionally send approved messages through Gmail or Slack.

You control what notes you submit and which integrations you connect. Integrations are optional, and drafts should be reviewed before they are sent or shared.

Last updated: May 28, 2026.

ClientCadence collects information needed to operate the product, protect accounts, provide workspace features, and support optional integrations.

• Account data, such as email address, authentication status, profile name, and login method.
• Workspace and role data, such as workspace name, plan, team role, invitations, and member activity.
• Project data, such as project name, optional client name, cadence, client preferences, communication style, and last update timestamp.
• Draft and History data, including notes you submit, generated drafts, saved outputs, source labels, timestamps, and project associations.
• Usage and analytics data, such as generation counts, feature activity, sign-in steps, billing steps, page views, and plan-limit activity.
• Integration metadata, such as Gmail, Slack, or GitHub connection status, provider account references, Slack command text, Slack channel choices, Gmail recipients, subjects, message bodies you choose to send, selected GitHub repositories, and imported GitHub activity metadata.
• Billing data, such as subscription status, plan, customer reference, and billing events handled through Stripe.
• Technical and security data, such as IP address, browser details, request logs, errors, abuse-prevention records, and security events.
• Support communications, feedback, or account questions you choose to send.

ClientCadence is not intended to collect sensitive regulated information. Avoid submitting passwords, API keys, payment credentials, government IDs, health records, bank details, highly confidential client records, or other regulated information unless you have decided it is appropriate for your use case.

• To provide the service, including drafting updates, saving History, organizing project memory, and showing workspace state.
• To generate drafts, summaries, insights, and suggested next actions from the notes and context you choose to provide.
• To maintain projects, cadence signals, history filters, pinned records, share activity, and integration send activity.
• To operate optional Gmail, Slack, and GitHub workflows, including sending approved Gmail messages, responding to supported Slack commands, listing channels when needed, and importing selected GitHub activity for draft context.
• To manage accounts, workspace roles, usage limits, subscriptions, billing, deletion requests, and support requests.
• To prevent abuse, fraud, spam, automated misuse, repeated expensive requests, and security incidents.
• To improve reliability, troubleshoot errors, understand onboarding and feature usage, and maintain product quality.

We do not intentionally send prompt text, generated drafts, Gmail message bodies, or Slack message text to analytics events.

We may use aggregated or anonymized usage information to understand product performance, reliability, feature adoption, and abuse patterns. Aggregated or anonymized information is not intended to identify a specific customer, workspace, client, or draft.

Workspace settings can turn saved History on or off for newly generated drafts, and individual draft controls can override that default before generation. Turning History off prevents generated drafts from being saved to your workspace History.

Temporary processing, security logs, billing records, abuse-prevention logs, analytics events, provider records, and operational records may still exist where needed. Disabling History may also reduce saved context for future workflow memory, cadence signals, and insights.

Users are responsible for exporting or saving records they need outside ClientCadence before deleting accounts, archiving projects, or changing workspace access.

Pro and Agency users may optionally upload small PDF, TXT, or Markdown files as context for draft generation. Unless otherwise stated in the product, ClientCadence extracts readable text from supported files to provide the requested generation and does not store the original uploaded file as a workspace attachment by default.

Saved History may record that a context file was used, along with limited metadata such as sanitized filename, file type, file size, extracted character count, and extraction status. ClientCadence does not save the original file or full extracted text to workspace History by default.

Text-based PDFs are supported. Scanned PDFs and OCR are not supported unless expressly stated. Do not upload passwords, API keys, payment details, regulated records, or highly sensitive client data.

ClientCadence uses service providers to run core product features. These may include hosting, storage, authentication, AI generation, billing, transactional email, analytics, error monitoring, security, and optional OAuth integration providers.

Providers may process data only as needed to provide their services to ClientCadence or to operate an integration you choose to connect.

ClientCadence uses reasonable administrative, technical, and operational safeguards intended to help protect accounts and workspace information. However, no internet service, storage provider, integration, or transmission method can be guaranteed completely secure.

ClientCadence and its service providers may process and store information in the United States and other countries where providers operate. Privacy and data protection rules may differ from the rules in your location.

By using ClientCadence, connecting integrations, or inviting workspace members, you understand that information may be processed by providers in different locations as needed to operate the service.

When you generate a draft or insight, relevant notes, settings, and project context may be sent to third-party AI providers to produce the requested output. ClientCadence may use different AI generation providers over time for drafts, summaries, insights, workflow suggestions, safety, reliability, or abuse-prevention needs. Outputs are suggestions and may be inaccurate, incomplete, or unsuitable for a specific client situation.

You remain responsible for reviewing generated content before sending or using it. Check facts, names, dates, deadlines, prices, promises, deliverables, legal or compliance obligations, and client-specific details.

AI providers may temporarily process prompts, generated output, and related context to provide the requested generation, safety, reliability, and abuse-prevention functions according to their own policies and ClientCadence's provider configuration.

Provider training, retention, safety, and abuse-prevention practices may vary by provider and may change over time. ClientCadence makes no provider-wide retention commitment unless a specific provider agreement or configuration supports that commitment.

You choose what notes to submit. Avoid sensitive or regulated information in prompts and project memory unless you have determined that ClientCadence is appropriate for that content.

ClientCadence may block obvious secrets or high-risk patterns before generation, but automated checks may not catch every sensitive detail.

ClientCadence is a productivity tool for ordinary business communication. It is not designed to store or process medical records, legal records, financial records, tax documents, regulated healthcare data, government secrets, highly sensitive credentials, or regulated compliance archives.

Users should avoid submitting secrets, passwords, API keys, payment credentials, government IDs, bank details, health records, or regulated information unless absolutely necessary and authorized.

If your work requires special confidentiality, retention, privacy, or security obligations, you are responsible for deciding whether ClientCadence is appropriate before submitting that content.

Gmail and Slack integrations use OAuth or authorized app flows where applicable. OAuth lets users authorize limited access without sharing their Google or Slack password with ClientCadence.

Gmail sending is user-controlled. ClientCadence uses a connected Gmail account to send messages you approve from the product. The current Gmail workflow is designed for sending approved drafts, not inbox reading, mailbox scanning, or broad mailbox access.

Slack actions happen within authorized workspaces, channels, commands, mentions, and app messages. Supported Slack requests may create saved History records and may be associated with a project when the message includes a matching project or client name.

Workspace owners or admins may have visibility into connected-service activity depending on the feature, role, and workspace settings.

You can disconnect Gmail or Slack from ClientCadence settings. You may also revoke access from Google or Slack account and workspace settings where those providers support it.

If you connect GitHub, ClientCadence may process selected GitHub project activity to help generate client-ready updates. GitHub is an activity context workflow in ClientCadence, not a client sending channel or repository management tool.

GitHub data may include GitHub account or organization names, selected repository names, repository metadata, pull request titles, status, labels, authors, timestamps, and links, issue titles, status, labels, authors, timestamps, and links, commit messages and timestamps, tags, release metadata, webhook delivery metadata, passive project signals, explicit `/clientcadence` command text, imported activity summaries, and generated update metadata saved in History when you choose to save a draft.

ClientCadence uses GitHub activity to import project context, summarize progress, help identify completed or released work, prepare draft client updates, update passive project signals, reply to explicit `/clientcadence` or `/cc` commands in GitHub comments, and save compact source metadata in workspace History when a generated draft is saved.

ClientCadence does not automatically comment on GitHub pull requests, issues, releases, or pushes. It posts a GitHub issue or pull request conversation comment only when a user writes an explicit `/clientcadence` or `/cc` command. It does not create issues, modify repositories, create commits, create releases, edit or delete GitHub comments, or fetch or store source code files, raw diffs, or patches.

Users choose which repositories to install or select. You can disconnect GitHub from ClientCadence settings. Disconnecting GitHub stops new GitHub imports, but existing saved History may keep compact GitHub metadata unless deleted through normal deletion controls.

GitHub is a third-party service. GitHub's own terms, privacy policy, account controls, and security practices apply to your GitHub account and GitHub-hosted data.

If you connect Gmail or use Google sign-in, ClientCadence may receive limited Google user data needed for the feature you choose to use. This may include your Google account email address and profile information for sign-in, Gmail connection status, token expiry metadata, provider account references where available, and the recipient, subject, and message body for Gmail messages you review and choose to send through ClientCadence.

ClientCadence uses Google user data only to provide and improve user-facing ClientCadence features that are visible in the product, such as signing in, connecting Gmail, preparing reviewed drafts for sending, sending approved Gmail messages, showing connection status, troubleshooting delivery issues, preventing abuse, and maintaining account security.

ClientCadence does not use Gmail access to read, scan, import, or analyze your inbox. ClientCadence does not request broad Gmail mailbox access. Gmail sending is used only when you choose to send a reviewed message from your connected account.

ClientCadence does not sell Google user data, use Google user data for advertising, transfer Google user data to advertising platforms, data brokers, or information resellers, or use Google user data to determine credit-worthiness or for lending purposes.

ClientCadence does not use Google user data to train generalized AI models. If AI features are used to help draft or edit content, the content is used only to provide the requested ClientCadence feature and is handled according to this policy and our service provider terms.

ClientCadence may share Google user data with service providers only as needed to operate ClientCadence, protect the service, comply with law, or provide user-facing features you request, under appropriate confidentiality and security obligations.

ClientCadence's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

You can disconnect Gmail from ClientCadence in Settings. Disconnecting Gmail stops future Gmail sending from ClientCadence and removes active access where supported. You may also revoke ClientCadence access from your Google Account security settings. Account deletion removes or deactivates ClientCadence account data as described in the data retention and account deletion section of this policy.

If ClientCadence materially changes how it accesses, uses, stores, or shares Google user data, we will update this policy and request any additional user consent required before using Google user data in a new way.

You control where drafts are copied, shared, sent, or posted. ClientCadence does not choose recipients or publish content for you. Review drafts before sending them outside ClientCadence.

Workspace History may record share, copy, Gmail send, and Slack send activity so owners, admins, or members with access can understand how drafts were used.

Workspace content is shared according to workspace roles and product features. Owners, admins, and other authorized members may be able to view projects, saved History, generated drafts, usage activity, integration activity, audit records, and account activity for that workspace.

Workspace owners are responsible for inviting the right people, assigning appropriate roles, removing access when needed, and making sure workspace members are allowed to see the information available to them.

Workspace-owned records, History, projects, audit activity, and shared records may remain associated with the workspace even if individual members leave or are removed.

Workspace activity records help owners and admins understand important account and workspace actions. Examples may include integrations being connected or disconnected, invitations, role changes, ownership changes, billing plan changes, project activity, and other account events.

These records are intended for oversight and troubleshooting. They are not a compliance archive, legal record system, or complete message-review system.

Billing and payment processing are handled by Stripe. ClientCadence does not store full payment card numbers. Stripe may collect and retain billing information according to its own policies and legal obligations.

Third-party providers have their own terms, privacy policies, and security practices. Their policies may apply when they process data for hosting, authentication, billing, AI generation, email delivery, analytics, support, security, or integrations.

Google, Slack, and GitHub policies may apply when you connect those services. Stripe policies may apply to billing. AI-provider policies may apply to draft generation and insights.

Account, workspace, project, History, usage, integration, and activity records may be retained while your account is active and as needed to provide the service.

You can request account deletion from settings. ClientCadence sends a confirmation email before deleting account data. Deletion links expire 60 minutes after they are sent.

After confirmed deletion, ClientCadence removes your local account, workspace, projects, saved generation History, integrations, and active app access. Stored Gmail and Slack connection access is removed, and ClientCadence attempts to revoke provider access where supported.

Some records may remain temporarily or as required for legal, billing, tax, subscription, security, abuse-prevention, deletion-audit, backup, or operational reasons. Anonymous aggregate usage data may also remain. Stripe may retain invoices and payment records according to its own policies.

Deleting a saved History item removes it from visible workspace History, but it does not undo emails, Slack messages, copies, exports, provider records, temporary processing, logs, backups, or operational records that may exist where needed.

ClientCadence does not keep identifiable project notes or generation History after confirmed account deletion for future AI training. If a future training or benchmarking feature is introduced, it should be offered as a separate opt-in choice.

For privacy, support, deletion, abuse reports, copyright concerns, legal notices, or account questions, contact support@clientcadence.io.