Privacy Policy

• Account information: name, email address, account identifiers, profile image when provided, access role, preferences, and authentication/session information.
• Workspace information: client and business-contact details, project plans, tasks, comments, activity records, documents and attachments, recording links and transcripts, and other information users enter or upload.
• Optional feature information: prompts, files, conversation history, generated content, lead and outreach records, and integration settings used by enabled features. The credential vault can store credentials supplied by authorized administrators.
• Technical information: authentication events and service logs needed to operate, troubleshoot, and protect the application. Authentication cookies maintain sign-in sessions; local preferences support the interface.

If you choose Google sign-in, Google and our authentication provider, Clerk, authenticate you and provide basic identity information, including your Google account identifier, name, email address and verification status, and profile image when available. We use this information to identify your invited account, maintain your session, and associate your activity with your workspace profile.

The Google sign-in connection requests only OpenID, email, and basic profile permissions. It does not request permission to read Gmail, Google Drive files, Google Calendar events, or Google contacts. Disconnecting Google authorization does not automatically remove information already stored in BrightDesk OS; contact support@brightdesk.ai about account or data removal.

Information supports account access, client and project work, task assignment, collaboration, document storage, requested AI features, enabled integrations, support, troubleshooting, and protection against misuse. Workspace activity can be visible to other authorized users according to the application’s access controls.

When users invoke AI features, relevant prompts, attachments, conversation context, and workspace information may be sent to the configured AI services to generate responses. Users should include only information they are authorized to share for that purpose.

BrightDesk OS uses Clerk for authentication, Convex for backend processing and storage, and Vercel for application hosting. Configured AI features use Vercel AI Gateway and its model providers; the current implementation calls OpenAI models. Providers process information needed to deliver their respective services.

Enabled integrations may send relevant information to additional services. For example, Slack notifications can include task or activity details, and outreach features can share lead and sequence information with Instantly. Integration use depends on the feature and workspace configuration. Information may also be disclosed when required by law or necessary to investigate misuse or protect the service and its users.

Contact support@brightdesk.ai to request access to, correction of, or removal of your account information, or to raise a concern about workspace information. Workspace records may relate to shared business work; removing an account does not necessarily remove the project history associated with that account. Some application deletions mark records as deleted instead of immediately erasing the underlying data.

You can manage Google access through your Google Account’s third-party connections settings. You can also change available notification preferences in BrightDesk OS. Account access remains subject to invitation and workspace administration.

The application uses authenticated access and role checks. The credential-vault implementation encrypts stored credential values separately using server-side keys. These controls do not make any system risk-free; contact support@brightdesk.ai if you suspect an account or data-security issue.

When this notice changes, the published version will show its effective date. Material changes to data use should be communicated before the new use begins where required.