Trust center
A plain-language description of the Signalisys pilot data boundary. Effective September 10, 2026.
This notice describes the pilot product. A design-partner agreement or order form may add customer-specific commitments and identifies the contracting provider.
Account and workspace information, including your display name, role, organization settings, and audit activity.
New messages and related metadata from Discord channels an authorized workspace administrator explicitly selects. The pilot does not import historical server conversations.
Signal proposals, source excerpts, reviewer decisions, action records, and pilot observations created through the product.
To identify possible decisions, commitments, issues, requests, and changes for human review; create approved action records; protect tenant boundaries; troubleshoot the service; and evaluate the pilot.
Signalisys is not designed for generalized member profiling, sentiment surveillance, targeted advertising, or autonomous outreach.
Workspace administrators choose the monitored channels and a raw source-message retention period. The scheduled retention process deletes raw messages after that period. Reviewed excerpts, decisions, actions, and audit records may remain longer so organizations can preserve accountability.
Owners and administrators can export workspace data and request workspace deletion. Participant access, correction, or deletion requests should be sent to the organization operating the relevant Discord server first, because it determines the pilot scope and reviewer access.
The pilot relies on Discord for source conversations, Supabase for application data and authentication, and the application hosting provider selected for deployment. These providers process data under their own terms and security programs.
Access is organization-scoped and role-based. Evidence is required before approval, and review activity remains auditable. No external CRM or general-purpose AI model receives conversation content in the native-only pilot.
An organization using Signalisys in a community that includes minors must obtain any notices, permissions, or consent its policies and applicable law require. It should monitor the narrowest practical channels and avoid collecting sensitive personal information.
Contact your workspace owner or the organization that operates the relevant Discord server. Workspace owners should use the privacy contact named in their pilot agreement. See the Participant Notice for a shorter community-facing explanation.