Security
Security boundaries should be visible before an agent acts.
Debatidor combines hosted coordination with user-controlled connections. Security therefore depends on product controls, provider settings, credential hygiene, and the environment where each worker runs.
Credentials and sessions
Dedicated keys
Use a separate, revocable key for each extension, worker, or integration.
Encrypted transport
Use HTTPS and WSS in production and do not place secrets in URLs, prompts, logs, or screenshots.
Minimum scope
Grant only the access required for the task and rotate credentials after exposure or role changes.
Provider controls
Review retention, training, and data-use settings in every external AI account you connect.
Local worker boundaries
The local worker receives a working directory and rejects absolute paths, parent-directory traversal, and exact paths listed by the user as protected. These lexical checks are not an operating-system sandbox.
The user remains responsible for filesystem permissions, symbolic links, protected files, version control, recoverable backups, and reviewing every change before keeping it.
Human oversight and incident reporting
Approval requests help surface risky changes, but no automated control can classify every sensitive action. If you discover a vulnerability or unauthorized access, send a minimal reproduction and affected surface to [email protected] without publishing credentials or personal data.
This page does not claim end-to-end encryption, certified tenant isolation, or the absence of vulnerabilities. Organizations handling regulated data must validate that the available controls meet their requirements before use.