Security and control

Supervised actions, tenant isolation and explicit permissions.

Trakoli is designed so automation remains bounded by merchant rules, confidence thresholds and exception handling.

Review the product Explore Mini Trakoli

Core safeguards

Security is a product behavior, not only an infrastructure claim.

Tenant isolation

Merchant data is separated by tenant and access policy.

Action governance

Sensitive actions require rules, confidence and, when configured, human approval.

Operational traceability

Important decisions and status changes remain visible for review.

Security

Security and control

Credible security depends on isolation, permissions and supervision—not absolute promises.

Last updated: July 17, 2026.

Store isolation

Operational data and access are separated by store and governed by applicable permissions.

Roles and access

Team members should only see the functions and information required for their role.

Secure transport

Connections to the service use encryption in transit where supported by the protocol.

Governed actions

Assisted and automated actions remain bounded by plan capabilities, configured rules, thresholds and approvals.

Operational traceability

Important status changes and sensitive decisions are designed to remain reviewable.

Continuity and backups

Infrastructure providers support availability, backups and recovery; no online service can guarantee uninterrupted operation.

Technology providers

Some features rely on external hosting, communications and intelligence providers. Only the context needed for the requested service should be transmitted.

Shared responsibility

Merchants must protect credentials, manage team access and review sensitive actions.

Incident reporting

Report unusual activity or security concerns to Trakoli support promptly.

These principles describe general operation. Exact obligations may vary by plan, market, connected providers and applicable law.