Tanglewake · Security

Security, with clear limits

This page separates application safeguards reviewed in source and synthetic tests from controls that cannot be verified from this repository. Code-level controls describe app behavior; they do not guarantee the settings or operation of a live deployment.

Application behavior

Verified in the app

These controls are checked in the application code and local tests using fabricated records.

  • Workflow access is scoped to a customer workspace

    Customer workflow APIs check the signed-in account against the workflow owner or an explicit workspace access grant. Unrelated accounts receive a not-found response for those records; admin-only APIs check the server-side admin role and deny non-admin users.

  • Event credentials are one-time secrets

    Workflow event credentials are randomly generated, stored as SHA-256 hashes, and can be rotated or revoked. The raw credential is returned only by the issue or rotation response. Sensitive access and remediation changes record the actor, action, time, and outcome without storing the credential.

  • Public intake has application-level limits

    Contact and bearer event requests have byte caps, field validation limits, and per-source request throttles. The application rejects malformed, oversized, or excessive requests before creating the associated records or sending notifications.

  • Workflow exports use server-derived access

    Workflow run exports check the caller’s workspace access on the server before reading run history. A workflow ID supplied by the caller does not grant access; available export sources are also authorized server-side.

This summary is limited to application code and the checks described above. It does not establish that customer information is categorically secure or verify external hosting, database, or operational controls.