Security

Last updated July 22, 2026

Walle is built by Winsen Labs around one structural decision: the most sensitive data involved, your credentials for other services, is kept out of our systems entirely. Everything else follows from treating what we do hold with proportionate care.

Credential isolation

OAuth grants and API keys for your connected tools are stored exclusively in our integration partner Composio's credential vault; Composio maintains SOC 2 compliance for that infrastructure. Winsen Labs holds opaque references only. A compromise of our database would not expose a single third-party credential.

Encryption

• All traffic is encrypted in transit (TLS 1.2+).
• Data is encrypted at rest by our database and storage providers.
• Slack bot tokens receive an additional layer of application-level encryption (AES-256-GCM) before they are written to our database.
• Sign-in codes are stored only as salted SHA-256 hashes, never in plaintext.

Sign-in

Walle is passwordless. Sign-in uses single-use, 30-minute, 6-digit codes delivered by email, with a hard limit of five attempts per code. Every sign-in email carries a one-click "report this sign-in attempt" link: reporting instantly invalidates the code, records a security incident, and alerts our team.

The agent cannot act alone

• Approval envelope: outward-facing actions (sending email, posting messages, creating calendar events, modifying issues) require your explicit approval in the conversation before they execute.
• Draft first: Walle's default for outbound email is a draft in your own drafts folder, not a send.
• Per-user execution: every tool call runs as the requesting user with that user's connections. In shared channels, other members' messages are context, never authorization.
• Audit trail: tool executions are recorded, per user, with timestamps.

Artifacts

Artifacts are private by default with owner-controlled sharing (private with an email-verified viewer list, or link with optional expiry), server-side access checks, and an access log. Rendered artifacts are served with a strict Content-Security-Policy that blocks all external network access from artifact content.

Honest posture

Winsen Labs is an early-stage company. We have not yet completed our own SOC 2 audit; our architecture leans on audited infrastructure providers (see the subprocessor list in our Privacy Policy) precisely so that the highest-stakes surfaces are handled by teams whose full-time job that is. As we grow, our compliance posture will grow with us, and this page will say exactly where things stand.

Reporting a vulnerability

Found something? We want to know: hello@winsen.ai. We respond quickly, we do not pursue good-faith researchers, and we credit reporters who wish to be credited.