Signal Desk
Sign inJoin beta

Security and tenancy

Private research needs clear boundaries.

Signal Desk is designed around a personal workspace, restricted service roles, protected credentials, and visible background processing state.

TENANCY

Workspace-scoped access

Authenticated requests derive workspace context from an opaque server-side session. Browser payloads do not choose a workspace.

CREDENTIALS

Protected provider configuration

OpenRouter and Telegram-related credentials are not returned in clear text after configuration and are excluded from normal application logs.

OPERATIONS

Recoverable worker flows

Collection, generation, indexing, analysis, and delivery use bounded claims, leases, retries, and recovery controls.

Tenant isolation

Customer-owned data carries workspace identity. Protected tables use row-level security, while background workers claim limited work before setting the relevant workspace context.

Secrets and files

Sessions are opaque, hashed, time-limited, revocable, HTTP-only, Secure, and SameSite=Lax. Credential encryption and workspace-prefixed attachment storage are used to reduce unnecessary exposure.

Operational visibility

The product reports collection, generation, delivery, and worker health. Digest and indexing views expose processing state and recovery controls rather than hiding failure behind a completed-looking summary.

Security questions

For security, privacy, or data-processing questions, contact us before sharing sensitive operational information by email.

Private beta

Start with a private workspace and a deliberate source boundary.

Join beta