Security

Every task runs in an ephemeral, isolated cloud sandbox (E2B). Sandboxes are scoped to a single session, auto-close after a period of inactivity, and never share state between users. Nothing you run reaches another user's machine.

• Encryption in transit (TLS) and at rest.
• Row-level security so you can only ever access your own sessions, memory, and tokens.
• Integration tokens are stored encrypted and used only to fulfil your requests.
• Google integrations request the narrowest scope that does the job (e.g. drive.file — access only to files Fulminare itself creates — rather than full account-wide access).

Every plan carries hard, server-enforced limits — concurrent sandboxes, runs per day, a weekly token budget, and overnight-run allowances (see Terms for exact numbers). These are checked before a run starts, not after, so one account can't exhaust shared infrastructure or run up an unbounded bill. Sub-agent fan-out is similarly capped per run.

The agent surfaces every tool call as it happens, and you can stop a run at any moment. Overnight runs flag irreversible decisions rather than guessing.

Found a vulnerability? We appreciate coordinated disclosure. Email fulminare@walnutlabs.in and we'll respond promptly. Please don't access data that isn't yours while testing.