Security
Verification worker separation
The verification API checks the request and queues a job. Gates run in a separate worker process with an allowlisted environment, and the job folder is removed when the job ends.
That separation is not a security boundary in production: the worker runs as the same user as the server and can read and write the data volume.
Authentication and ownership
Sessions use signed tokens, API keys are scoped, cookie requests need a CSRF token and OAuth sign-in checks its state. Relay sessions are checked against the caller.
Request and resource limits
The API limits request size and rate, and the relay caps what it keeps per session. A rate-limit answer is never a passing verification.
Sign-in, sign-up, password changes and OAuth sign-in are rate limited per address and per account. A refused try answers 429 with a Retry-After header.
Check records and sensitive data
Audit events carry session and trace ids. The logger redacts fields whose names mark credentials and shortens long strings; a secret inside ordinary text or code can still be kept. See Privacy for each data flow.
Account deletion
Settings > Account deletion deletes the signed-in account. It needs a recent sign-in and the typed word DELETE, and it only ever deletes the session’s own account.
It removes the account’s sessions, dashboard and check records, remote commands, webhooks, profile name and API keys. An org you own goes with it when no one else is a member; an org with other members must be handed over or closed first. In someone else’s org, only your membership and your own records go.
A record of the deletion stays, with the email replaced by a keyed hash, so the old keys and sessions stay refused. Your Google, GitHub or Microsoft account, or your password sign-in with the Asqav authentication service, stays open. Backups still hold the account, and a restore replays every later deletion first. See retention and deletion.
Your local workspace
Asondy runs with your local permissions, and what a hook can block depends on the coding tool. Keep operating-system permissions, repository protection and review in place.
Untrusted repositories
Opening an unfamiliar repository can run its agent configuration: session hooks, skill scripts, MCP server commands and environment blocks. At session start Asondy scans that configuration for code-execution and exfiltration shapes and warns with the file, line and risk. The warning arrives alongside the repository’s own start-up hooks, so it cannot stop them.
The scan reads text and runs no code, and a clean scan does not make a repository safe. The checkout Asondy was installed from is trusted and stays silent.
Report a vulnerability
Email [email protected] to report a security vulnerability in asondy.com, api.asondy.com, the dashboard, the cloud relay or the Asondy software. Include the affected address or feature, the steps to reproduce it and what an attacker could do with it. Leave out live credentials and any personal data the report does not need. The same contact is listed in security.txt.
You will get a reply by email. Please allow time for a fix before you publish details; the disclosure date is agreed with you.
When you test, follow these rules:
- Use only accounts, sessions and data that are yours or that you have permission to use.
- If you reach data that belongs to someone else, stop, do not keep or share it, and say so in your report.
- Do not run denial-of-service or load tests, send spam, or use social engineering or physical access.
- Do not change or delete data that is not yours, and remove what you created for the test when you finish.
- Keep the details confidential until the issue is fixed or a disclosure date is agreed.
Out of scope: issues in services Asondy relies on, such as Cloudflare, Hetzner, the Google, GitHub and Microsoft sign-in or the Asqav authentication service, which go to their owners; and scanner output without a demonstrated security impact, such as a missing header on its own.
Research that follows these rules in good faith is welcome. Asondy treats it as authorized and will not take legal action against you or report you to law enforcement for it. Asondy does not run a paid bug bounty program.
Secrets boundary
Claude Code on macOS and Linux: the credential gate denies a Read, Grep, Edit or shell call aimed at a credential store listed in scripts/lib/cred-stores.js.
Not built yet: an operating-system sandbox for shell commands, and a key route service for keys an agent presents.
Not stopped: misuse inside a key's rights, the harness's own login, a signed-in browser, an agent with password-less sudo, native Windows without WSL2.
Other harnesses get no read claim. The proof is the credential gate's test suite on recorded Claude Code hook events; no live harness version or sandbox version is recorded yet.
If an agent escapes a sandbox, rotate the keys that machine held.
Assurance and scope
Asondy does not claim SOC 2 certification, full gate coverage or software free of vulnerabilities.
To try the gates, install Asondy or create a free account.
References
- OWASP Top 10 for LLM Applications, OWASP GenAI Security Project
- AI Risk Management Framework, NIST
- Gitleaks secret scanner, Gitleaks