SECURITY

Practical security for an evolving product.

ToolDucky uses authenticated workspaces, HTTPS, scoped integrations, and clear processing boundaries while the product continues to mature.

Transport security

Public ToolDucky services are served over HTTPS. Security controls are used to reduce exposure of internal services and protect traffic in transit.

Accounts and workspace access

ToolDucky Chat uses authenticated user accounts and workspace roles. Businesses are responsible for controlling who is authorized to access their workspace and connected business assets.

Connected platform data

External platform connections are used to provide the requested service. Access is scoped to authorized connections and is handled according to the product's current integration design and third-party platform requirements.

File processing

ToolDucky utilities may use local browser processing or isolated temporary server processing depending on the tool. Processing behavior is described in the Privacy page and where relevant in the tool itself.

What we do not claim

Unless explicitly stated otherwise, ToolDucky is not presented as independently certified under SOC 2, ISO 27001, HIPAA, PCI DSS, or another formal compliance framework.

Report a security issue

If you believe you found a security issue, contact [email protected] with enough detail for us to reproduce and investigate it. Do not include passwords, API keys, or other secrets in plain email.