Trensli
Sign in Get a Private Walkthrough

Security

Your operating knowledge, held carefully.

How Trensli protects the procedures, training and restaurant information your group depends on.

Effective September 8, 2026 · Trensli Inc.

Encrypted

In transit and at rest

Scoped access

By role and location

Approval-controlled

Only named approvers publish

Version history

Plus recurring backups

Security Privacy Terms

Our approach

Your operating information belongs to your company. Trensli’s job is to keep it current, controlled and available to the people who should have it.

This page describes the practices in place today. It is a plain description of how the product works, not a certification claim.

Customer ownership

Your content remains your company’s content.

That covers your recipes, procedures, policies, training and role guides, and the restaurant-specific material Trensli builds from your operation.

If your relationship with Trensli ends, you can take your approved operating material with you in a usable export.

How Trensli staff work in your account

Human review doesn’t change who owns the standard. Trensli does not independently decide how your restaurants should operate.

Trensli may

  • Prepare and organize approved material
  • Review managed changes before they’re published
  • Provide the managed service you engaged us for

Your authorized leaders

  • Decide how your restaurants operate
  • Approve every operating standard
  • Own the content, before and after launch

Access and permissions

Every person in Trensli sees content scoped to their role and their location. A line cook at one restaurant does not see another location’s manager guidance, and a shift-level account cannot change an approved standard.

Role scoping — Content is filtered by the role assigned to each account.

Location scoping — Access is limited to the restaurants a person actually works.

Approval rights — Only named approvers can publish a change to an operating standard.

Trensli staff — Our team accesses your workspace only to perform the managed work you have engaged us for.

Data in transit and at rest

In transitEncrypted between your team and Trensli using TLS.
At restStored data is encrypted by our infrastructure provider.
CredentialsHashed, never stored in readable form and never logged.

Change history

Trensli keeps prior versions of operating content rather than overwriting them.

Every approved change retains

Previous versionNew versionApproverDate

A restaurant needs to know what was in force on a given date, and an accidental or unauthorized change can be identified and reversed.

Availability and backups

BackupsRecurring, by our infrastructure provider.
EncryptionBackups are encrypted.
RetentionKept on a rolling window.
IncidentsWe tell you what happened, what it affected and what we changed.

Reporting something

If you believe you have found a vulnerability, or you see content in Trensli that a person should not have access to, write to security@trensli.com. Please include enough detail for us to reproduce it. We will acknowledge within one business day.

Questions about this page?

Write to legal@trensli.com and we’ll come back to you.