Privacy notice

Effective September 15, 2026. SignalDesk is offered by Barich Holdings. Questions and data requests: call 802 809 1213.

What we collect

ChatGPT sign-in supplies an account identifier and email, plus a display name when available. We store workspace memberships, tasks, evidence notes, invitation email addresses, connection metadata, source events and an audit trail. Connected sources send only the fields configured by their owners. The browser companion sends opened ChatGPT conversation titles and links, not message bodies. The Codex bridge sends local task titles and timestamps, not transcripts or files.

Use and sharing

We use this information to deliver workspaces, enforce permissions, receive source events, provide support and operate billing. Workspace members can see information in their workspace. Hosting and sign-in use OpenAI Sites and its underlying infrastructure. If paid checkout is enabled, Stripe handles payment information; SignalDesk does not store full card numbers. Providers receive information necessary to use their configured connections.

Your controls

Connectors are opt-in. Owners can revoke credentials and remove teammate access. You can pause the browser companion, stop the local bridge and export workspace data. Contact us to request account or workspace deletion. Do not submit passwords, API secrets, regulated records or information you are not authorized to share in task notes.

Retention and security

Source events older than 90 days are eligible for automatic removal as new events arrive. Other workspace data remains until removed through supported controls or a verified deletion request, subject to billing record requirements and backup recovery periods. Tokens are stored as hashes; webhook secrets are encrypted server-side. We use access controls and encrypted connections, but no online service can promise absolute security. This release does not claim HIPAA, SOC 2 or other certifications.

Cookies and local storage

Sign-in uses the hosting platform’s authentication cookies. The companion stores its token and enablement setting locally in the browser extension, not in browser sync. We do not add advertising trackers. If this notice materially changes, the updated version will appear here.