Trust and security
Current status: Laborbot.si provides a public preview and a planning workspace. It does not execute customer work, connect third-party tools, send messages, book appointments, move money or charge a subscription.
Implemented controls
- Workspace records are scoped by organization membership, with owner, administrator and member permissions.
- State-changing workspace requests require a same-origin JSON request and enforce bounded per-user, per-route limits.
- Workspace controls, diagnostics and exports create tenant-scoped administrative audit records.
- Approved business rules, worker permissions and plan reviews are versioned. Approval does not enable external execution.
- Source and generated bundles are scanned for credential patterns, and application runtime code is checked for direct logging.
- Early-access and contact forms limit payload size, use a hidden anti-spam field and enforce request limits. Private removal codes are stored only as hashes.
Data and deletion
Early-access signups and contact requests can be removed with the private code issued at submission. Signed-in workspace owners can export workspace data and complete the workspace-deletion flow. These actions do not delete a ChatGPT identity or data held by a future external provider. Review the privacy notice for the verified data, provider and retention boundaries.
Review the preview use rules and draft terms and the current provider and processing disclosure and the current integration availability matrix before relying on any provider example.
Claims boundary
Workflow descriptions explain planned or currently bounded behavior. Laborbot.si does not claim guaranteed performance, revenue growth, cost savings, recovered revenue, production readiness or incremental customer impact. Any future outcome claim requires retained provider evidence, a defined comparison method and customer permission.
Open launch gates
Provider connections, live worker execution, independent hosted recovery evidence, production backup retention verification, login-provider throttling verification, billing, legal business identity and customer validation remain open. No certification, uptime promise, security-compliance claim or support SLA is made.
Report a concern
Use the stored contact-request form and choose Security, Data or privacy, or Accessibility. Do not submit credentials or sensitive customer data. The preview does not promise an immediate response.
Last reviewed October 24, 2026.