InstInt Security Overview
Review how InstInt protects company knowledge, verifies user identity, and limits access to authorized staff.
Security controls at a glance
Compare common review questions with InstInt’s built-in controls and strongest available policy settings.
| Security checkpoint | InstInt capability |
|---|---|
| Database encryption at restHow is stored database content protected? | AES-256 storage encryptionProduction databases use AES-256 at the storage layer. Managed database backups use AES-256 where enabled. |
| Encryption in transitHow are connections protected? | HTTPS/TLSTLS protects browser connections and connections from the application to the managed database service. |
| Multi-factor authentication (MFA)Can we require a second factor? | Authenticator-app MFA (TOTP)Organizations can require authenticator codes for administrators or across administrator and staff accounts. Staff sign-in policies can add work email and a password to branch and employee codes. |
| Tenant boundaries and role-based access (RBAC)Can we apply least-privilege access? | Server-side authorization by organizationAdministrative privileges are role-based. Staff knowledge access can be limited by location, role, content category, and assigned security level. |
| Credential protectionHow are passwords stored? | Salted PBKDF2-HMAC-SHA256InstInt-managed passwords are hashed with a unique salt. Email signup requires verification. |
| Session securityCan we limit how long staff stay signed in? | Configurable staff session lifetimesProduction session cookies use Secure, HttpOnly, and SameSite=Lax attributes. |
| Brute-force protectionWhat happens after repeated failed sign-ins? | Sign-in throttling and temporary lockoutsOrganizations can configure failed-attempt limits and lockout durations. |
| Administrative audit loggingWhich security activity is recorded? | Administrator sign-in and activity recordsInstInt records successful and failed administrator sign-ins and selected administrative actions. |
Security concerns
Answers about employee access, disputed responses, and how InstInt protects company data.
Staff access and answer history
Can we lock an employee’s account if we suspect misuse or their employment ends?
Yes. In Roles & Access, an authorized administrator can open the employee’s record, turn off User account is active, and select Save User. The employee can no longer sign in or use an existing staff session to make new requests. Deactivation keeps the employee record in place while you review the situation or complete offboarding.
Can staff change the procedures InstInt uses to answer questions?
Changes to the knowledge base require administrative permissions. Staff access to approved knowledge can be limited by location, role, and category. If an employee also has an administrator account, review their administrative access separately.
What if an employee says InstInt gave them the wrong answer?
An authorized reviewer can open History to see the recorded question, the answer InstInt returned, and when it was sent. This gives you something concrete to compare with the approved procedure. Unsaved records are kept for 90 days. Use Save on a relevant record to keep it beyond that window.
Data protection and incident response
Can we require administrators to use MFA?
Yes. An organization can require administrator sign-ins to use authenticator-app codes under its multi-factor authentication policy.
How is our data kept separate from other companies’ data?
InstInt checks company membership and permissions on the server before returning company data. Within an organization, staff knowledge access can be further restricted by location, role, category, and security level.
How is our data encrypted?
Production database storage uses AES-256 encryption at rest. HTTPS/TLS protects browser traffic, and TLS protects connections from the application to its managed database service.
What logs can help us investigate suspicious activity?
InstInt records successful and failed administrator sign-ins and selected administrative actions, including staff account updates. Authorized reviewers can also use History to review recorded staff questions and responses.
What should we do if we suspect a security incident, and how would we be notified?
Deactivate affected staff accounts when appropriate, save relevant History records, and report a suspected platform incident to InstInt through your support channel. Confirm your security contact, escalation process, and notification timing with InstInt as part of your security review.
What can be restored from backups, and when was recovery last tested?
Managed database backups use AES-256 encryption where enabled. Ask InstInt to confirm which data and files are covered, how long backups are retained, the latest restore-test evidence, and the applicable recovery targets.
What uploaded content is sent to AI providers?
Relevant document content may be sent to an AI provider to process an upload. Relevant question and knowledge content may also be sent to generate a response. See the privacy notice for how InstInt handles this information. Ask InstInt for the applicable provider terms if your review requires details about retention or model training.
Is a SOC 2 Type II report or independent penetration-test summary available?
Contact InstInt to confirm current availability. If either is required for your review, ask for the scope and date of the report or test.
Review InstInt for your organization
Discuss your authentication, access, and data-handling requirements with us before you roll out InstInt.
InstInt is intended for approved operational knowledge and staff procedures. Keep protected health information, credentials, and confidential personnel records out of the platform. Use your organization’s approved clinical systems for patient information and clinical decisions.

