Security, in plain language.
Teryli supports behavioral-health operations. Before a customer uses it with real organizational data, the exact workspace scope, access model, and data-handling requirements are reviewed in writing.
Start with the boundary. Then verify the controls.
Public preview
Synthetic data only
Product previews use synthetic sample data. No customer record is needed to evaluate the interface.
Public site
No PHI in forms or email
Do not submit protected health information, client details, or resident details through this marketing site, booking page, or email.
Organization access
Scope before activation
Teryli confirms the customer organization, purchaser authority, authorized users, and agreed workspace scope before activation.
Buyer review
Controls are evidence questions
Encryption, access, session, isolation, retention, and incident-response requirements should be reviewed against current technical evidence and the customer agreement.
We’d rather walk through your questions than gesture at badges.
Teryli is an operational coordination layer, not an EHR and not a clinical decision-maker. The customer remains responsible for defining what information belongs in the workspace and who is authorized to see it.
The public demo uses synthetic, non-real data. This marketing site is not a place to send PHI, client details, or resident details.
This page does not make a blanket HIPAA, compliance, certification, or BAA claim. Bring those requirements to a workflow review, or email [email protected], so they can be answered against the current product and agreement.
Filled · in scope · Ruled through · out of scope
Teryli · Security · teryli.com/security
Put the requirements in the agreement.
Before real organizational data is introduced, confirm the data scope, permitted users, authentication and session expectations, retention and deletion terms, support path, incident responsibilities, and whether a BAA or other written term is required.
- Data scopeConfirm in writing
- Permitted usersConfirm in writing
- Authentication and session expectationsConfirm in writing
- Retention and deletionConfirm in writing
- Support pathConfirm in writing
- Incident responsibilitiesConfirm in writing
- BAA or other written termConfirm in writing
- Go-live dateConfirm in writing
Directory records are operational research aids. A source or last-checked date is not an endorsement, availability guarantee, licensure conclusion, accreditation conclusion, or clinical recommendation. Confirm current facts directly with the program.
Found something? Tell us directly.
If you believe you’ve found a security issue involving Teryli, email [email protected] with the details. We take reports seriously and will respond promptly. The same contact is published at /.well-known/security.txt.
Your requirements. A clear conversation.
Review your access, data-handling, and agreement requirements with Christopher. We will identify what needs evidence or written confirmation before live use.