Security at Telani AI

Privacy in the daily workflow.

Access controls, workspace locking, and encryption for selected patient information. Understand what protects your team’s work.

See the protections
Conceptual illustration of a coordinator securing a patient folder in a cabinet

01 / Protect workspace access

Step away.
Keep the workspace locked.

Cover the workspace when you leave your screen. A PIN or password is required to resume the session.

  1. Lock the workspace
  2. Verify access with a PIN or password
  3. Return to the session
More about security controls

Automatic walkthrough with sample credentials. No real sign-in or patient data.

02 / Protect selected stored information

Readable for the work.
Encrypted in storage.

Message text and selected patient fields—including names and dates of birth—use AES-256 encryption at rest. Authorized application services decrypt these values when needed.

Loading interface preview…
Understand the encryption scope

03 / Manage access and activity

Controls around everyday work.

A second step at sign-in

When enabled, email-based multi-factor authentication adds verification to account sign-in.

Explore security controls

Access that follows responsibility

Roles and permissions govern access to organization workflows. Review team membership and roles as responsibilities change.

Explore access controls

Choose the conversation audience

Patient rooms distinguish internal Care Team messages from Patient & Family communication. Check the audience before sending.

Explore messaging

A record of supported actions

Application audit events record supported activity for administrative review. Confirm the event coverage your organization needs.

Explore activity logs

04 / Your organization’s requirements

Software controls are part of the picture.

HIPAA’s Security Rule addresses administrative, physical, and technical safeguards. Your organization’s policies, configuration, and agreements matter alongside the software you use.

Discuss security documentation, Business Associate Agreement requirements, and your intended use with our team before sharing patient information.

HHS: Security Rule overview ↗HHS: Business Associate Contracts ↗

These resources explain the regulatory context. They are not certifications or endorsements of Telani.

A closer look

Security questions, answered.

Is this end-to-end encryption?

No. The implementation uses server-side encryption at rest for message text and selected patient fields. Authorized application services decrypt those values when needed.

Does the encryption example cover every field and file?

No. The illustration shows selected patient fields and message text. It does not represent encryption coverage for every database field, attachment, or file.

Does screen locking sign me out?

Screen locking covers the workspace and requires a PIN or password to resume the session. Signing out is a separate action.

Can we review our security and BAA requirements?

Yes. Contact our team to discuss the documentation, agreements, and intended use your organization needs before sharing patient information. This page does not confirm that a BAA has been executed for your organization.

Let’s review what your team needs.

Bring your security questions and intended workflow to a conversation with us.