Skip to content

Security & data

What Lyntcast stores, how it is protected, and the controls you have. For the full overview see the Security page.

What Lyntcast stores

  • Account data: name, email, a scrypt hash of your password, workspace membership and role.
  • CMS credentials: encrypted with AES-256-GCM before they are written to the database.
  • Changes: each proposal, its diff, findings, decision and the snapshot taken before it was applied. This includes the content of the fields involved.
  • Audit log: who did what and when, hash-chained.
  • Agent keys and OAuth tokens: stored only as SHA-256 hashes; the key itself is shown once.

Lyntcast does not copy your whole site. It reads documents through the CMS API when an agent or reviewer needs them.

When content is sent to an AI model

Only for ai_policy rules. The proposed change (not the whole page) is sent to a model through the Vercel AI Gateway. If you have no AI policy rules, no content is sent to any AI model by Lyntcast. AI agents you connect see what they read through Lyntcast’s tools; that is between you and your agent provider.

What the WordPress plugin reports

The plugin sends Lyntcast events about changes on your site: content changes (with who made them and how), security alerts (injected code, new administrators, price drops) and, from version 0.3.0, reinfection alerts. Reinfection alerts carry the file path, setting name or scheduled-task name involved and a short reason (for example “script loaded from evil.example.net”), not file contents. Each event is authenticated with the site's own secret and checked before it is stored. The plugin only reports: neither it nor Lyntcast deletes files or switches plugins off. See Reinfection alerts.

Who is alerted

Security alerts go to the workspace's Slack channel (if set up) and by email to owners and admins who haven't turned workspace emails off in their account settings. They stay open under Sites until someone marks them checked, or the site marks them as expected.

Your controls

  • Revoke an agent or connected app: its key or tokens stop working immediately.
  • Emergency stop: pause every agent in the workspace.
  • Remove a site: its stored credentials are deleted. Also revoke the token in the CMS.
  • Export the audit log at any time (admins).
  • Roles: owner, admin, reviewer, viewer.

Self-hosting

Lyntcast can run on your own infrastructure (Docker Compose or any Node 22 host with Postgres). You then hold the encryption key (GATEHOUSE_ENCRYPTION_KEY) and all data.

More detail: Security overview, Privacy policy, Subprocessors.