Legal
Terms of use
These terms explain how ClientCadence may be used, what users are responsible for, and how AI drafts, integrations, subscriptions, and account deletion work.
Last updated May 2026
On this page
Overview
ClientCadence is intended for lawful business communication and productivity. By using the service, you agree to use it responsibly, keep your account secure, and review generated content before using or sending it.
If you use ClientCadence for a workspace or client project, you are responsible for making sure you have the right to submit that content and use the resulting drafts.
Last updated: May 20, 2026.
Eligibility
ClientCadence is intended for users who are at least 18 years old and able to enter into these terms. If you use ClientCadence for a company, agency, client, or other organization, you confirm that you have authority to use the service on that organization's behalf.
What the service provides
ClientCadence provides tools for drafting client updates, email replies, weekly summaries, risk reports, suggested next updates, project memory, saved History, workspace organization, insights, sharing, billing, optional Gmail and Slack workflows, and optional GitHub activity context and explicit command replies.
Agency workspaces may include team roles, shared usage visibility, activity review, invites, and workspace collaboration features. The service is designed to help organize and draft communication, not to promise that every output is correct or complete.
Your responsibilities
- You are responsible for notes, prompts, drafts, files, client details, and other content you submit.
- You must review AI-generated output before sending, sharing, or relying on it.
- You are responsible for confirming facts, dates, prices, deadlines, deliverables, promises, and client-specific obligations.
- You must have the right to use submitted content and comply with contracts, confidentiality duties, provider terms, and applicable laws.
- You are responsible for having permission to connect repositories and process GitHub activity through ClientCadence.
- You should avoid entering passwords, API keys, payment credentials, regulated information, or confidential third-party data unless authorized and necessary.
- You must keep account, workspace, and integration access secure.
No professional or fiduciary relationship
ClientCadence is a software tool for drafting and organizing business communication. It does not create a professional, fiduciary, advisor, agency, attorney-client, accountant-client, medical, financial, tax, security, or compliance relationship.
You remain responsible for your client relationships, business decisions, communication strategy, legal obligations, confidentiality duties, and the final decision to send, share, or rely on any draft. Users are responsible for any commitments, deadlines, pricing, deliverables, or representations they choose to send to clients, whether or not the wording began as a ClientCadence draft.
AI-generated output
AI can make mistakes. Outputs are suggestions or drafts and may be inaccurate, incomplete, outdated, or unsuitable for a specific client situation.
ClientCadence may provide draft language, risk labels, cadence signals, summaries, suggested follow-ups, and insights. These outputs may not reflect legal, business, contractual, compliance, or client-specific requirements.
Cadence signals, blocker detection, quiet-client indicators, summaries, risk labels, and suggested next actions are automated estimates and may be inaccurate or incomplete.
ClientCadence is not legal, financial, medical, tax, security, or compliance advice. You remain responsible for reviewing and deciding whether to use any output.
AI-assisted features may behave differently over time as models, prompts, providers, limits, and safety checks change. Do not rely on generated output as the only source of truth for client commitments, pricing, deadlines, legal obligations, or confidential decisions.
AI generation providers may process prompts, generated output, and related context according to their own operational, safety, reliability, abuse-prevention, and retention practices.
Workspace owners and members
Workspace owners and admins are responsible for inviting appropriate members, assigning roles, reviewing workspace activity, managing billing, and removing access when someone should no longer use the workspace.
Members may see workspace projects, saved History, generated drafts, usage activity, shared records, and integration activity depending on their role. Do not add people to a workspace unless they are allowed to see the workspace information available to that role.
Workspace-owned records, History, projects, audit activity, and shared records may remain associated with the workspace even if individual members leave or are removed.
History controls and retention
Workspace settings may let you turn saved History on or off for newly generated drafts. Individual draft controls may also let you choose whether a specific draft is saved.
Turning History off prevents generated drafts from being saved to your workspace History. Temporary processing, security logs, billing records, abuse-prevention logs, operational records, provider records, backups, and anonymous aggregate analytics may still exist where needed.
Deleting a History item removes the saved item from visible workspace History. It does not undo messages already sent through Gmail or Slack, copied content, shared content, billing records, provider records, or records retained for legal, security, abuse-prevention, or operational reasons.
Acceptable use
You may not use ClientCadence to:
- Abuse, overload, scrape, reverse engineer, or attack the service.
- Bypass usage limits, payment requirements, access controls, or security protections.
- Generate spam, phishing, malware, credential theft, fraud, deceptive claims, or impersonation.
- Harass others, violate rights, or publish unlawful or harmful content.
- Submit or process content you do not have the right to use.
- Violate laws, regulations, contracts, confidentiality obligations, workplace rules, or platform policies.
- Use automated systems to create abusive traffic, repeated requests, or artificial usage.
Sensitive content
ClientCadence is not designed to store or process highly sensitive personal, medical, financial, legal, tax, security, government, or regulated information.
You should not submit passwords, private keys, API keys, payment card details, bank details, government ID numbers, protected health information, regulated personal data, or confidential third-party data unless you have determined that the use is appropriate and authorized.
ClientCadence may block obvious secrets, credential patterns, payment card numbers, government ID patterns, bank details, or private keys where possible, but automated checks may not catch every sensitive case.
Context file uploads
Context file uploads are provided to assist draft generation and should not be used as a primary storage system, backup system, legal archive, document management system, or regulated records platform.
Users are responsible for ensuring they have the right to upload or process any file content they provide to ClientCadence. You should not upload prohibited, sensitive, regulated, confidential, or third-party content unless you are authorized to do so and have determined that ClientCadence is appropriate for that content.
ClientCadence extracts readable text from supported files to assist drafts. It does not verify the legality, accuracy, completeness, or professional suitability of uploaded file content, and file context should not be treated as legal, financial, medical, tax, security, or compliance advice.
GitHub activity import and commands
GitHub activity import is provided to help users summarize selected repository activity into client-ready updates. Users are responsible for ensuring they have permission to connect repositories and process GitHub activity through ClientCadence.
ClientCadence may post a GitHub issue or pull request conversation comment only when a user writes an explicit `/clientcadence` or `/cc` command. Passive GitHub events do not create automatic comments. ClientCadence does not create issues, edit or delete comments, create commits, create releases, merge pull requests, or modify repository settings.
ClientCadence may summarize pull requests, issues, commits, tags, releases, labels, timestamps, links, and related repository metadata. Release and completion signals are based on available GitHub activity and should not be treated as a guarantee that work is shipped, complete, approved, or ready for a client.
You remain responsible for reviewing generated updates before sending or sharing them, especially when a draft refers to completed work, released work, blockers, client approvals, or next steps.
Subscriptions and billing
Paid plans are processed through Stripe. Prices, plan limits, usage limits, and features may change over time. If a subscription is canceled, downgraded, unpaid, disputed, or expires, access to paid features may be limited or removed.
You can manage billing through the billing tools provided in the app. Stripe may apply its own terms, payment rules, taxes, and billing policies.
Export and backup responsibility
ClientCadence is not intended to be your only recordkeeping system. You are responsible for exporting, copying, or backing up any drafts, client notes, project records, billing records, or communication records that you need outside the service.
Account deletion, workspace changes, plan changes, provider outages, or service changes may affect access to stored records.
Account deletion
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 confirmation, ClientCadence removes your local account, workspace, projects, saved generation History, integrations, and active access. You are responsible for saving any records you need before confirming deletion.
If you own a workspace with other members, ownership may need to be transferred before account deletion can continue. Workspace-owned History and project records remain with the workspace when a member is removed.
If you have an active paid subscription, confirmed account deletion cancels subscription access immediately. Minimal legal, billing, tax, security, abuse-prevention, deletion-audit, backup, operational, and anonymous aggregate records may remain where needed to operate and protect the service. Stripe may retain invoices and payment records according to its own policies.
Third-party services and integrations
ClientCadence may rely on third-party providers for authentication, hosting, storage, AI generation, billing, email delivery, analytics, error monitoring, security, support, and optional Slack, Gmail, or GitHub integrations. These providers have their own terms, policies, security practices, and availability.
Gmail, Slack, and GitHub integrations use OAuth, GitHub App, or other authorized provider flows where applicable. These flows allow you to approve limited access without sharing provider passwords with ClientCadence.
You are responsible for using integrations only with accounts, workspaces, channels, recipients, and content that you have the right to use. Integrations may change, become unavailable, require reauthorization, or be affected by provider outages or policy changes.
Features that rely on third-party providers, including AI generation, Gmail, Slack, hosting, authentication, billing, email delivery, or analytics services, may become temporarily unavailable, rate limited, delayed, modified, or discontinued outside ClientCadence's control.
ClientCadence does not guarantee delivery, receipt, inbox placement, message visibility, or successful transmission through third-party providers such as Gmail or Slack.
Disconnecting an integration removes saved ClientCadence connection access and may attempt provider-side revocation where supported. You may also revoke access directly from Google, Slack, GitHub, or other provider settings.
No warranty and availability limits
ClientCadence is provided on an as-available basis. Features, plans, limits, integrations, providers, or workflows may change over time. Downtime, maintenance, errors, or third-party service issues may occur.
We work to keep ClientCadence useful and reliable, but we do not promise uninterrupted access, error-free output, guaranteed delivery, or that every draft, insight, integration, or workflow will meet your specific business needs.
We may update these terms as the product changes. Continued use after changes means you accept the updated terms.
Governing law
Unless a written agreement says otherwise, these terms are governed by the laws of California, United States, without regard to conflict of law rules. Courts located in California will have jurisdiction for disputes that cannot be resolved informally, except where applicable law requires another forum.
Limitation of liability
ClientCadence is a drafting and productivity tool. It is not designed to replace your professional review, client judgment, legal review, financial review, tax review, medical review, security review, or compliance process.
To the extent allowed by law, ClientCadence is not liable for indirect business losses, lost profits, client disputes, missed deadlines, inaccurate or incomplete AI outputs, third-party provider failures, or decisions made by relying solely on generated drafts without review.
Contact
For terms, support, deletion, billing, abuse reports, copyright concerns, legal notices, or account questions, contact support@clientcadence.io.
Related guides
Start with the workspace
Use ClientCadence in the project workflow where drafts, History, integrations, and review controls belong.
Get started