Privacy Policy

No accounts: discuss.watch does not require sign-in. Forum selections, keyword alerts, bookmarks, read/unread state, theme, and density preferences are stored in your browser (localStorage) only.

Usage data: We do not use third-party analytics trackers. Standard server logs may record IP addresses and request metadata for operational purposes.

Cached forum data is used to serve the public feed. Optional email briefs (if configured by operators) are generated from public forum content. We do not sell, rent, or share personal information with third parties for marketing purposes.

We use the following third-party services that may process operational data:

• Anthropic (Claude) — generates AI summaries for digests (no personal data is sent)
• Resend — delivers operator-configured email briefs
• Railway — hosts our infrastructure (database, application server)

Forum discussion data is cached in PostgreSQL (hosted on Railway) and Redis. Sensitive credentials (API keys for delegate monitoring) are encrypted with AES-256-GCM. All connections use TLS. Reader preferences stay in browser localStorage.

Forum discussion data from public APIs is cached for up to 15 minutes and stored in our database for historical analysis. Browser-local preferences persist until you clear site data.

You can delete bookmarks, alerts, and read state at any time through the Service or by clearing your browser storage. For other inquiries, contact us at the email below.

We use browser localStorage (not cookies) to store preferences. We do not set authentication cookies.

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last updated" date.

For privacy-related inquiries, contact us at sov@sovereignsignal.com.