Security Statement

Controls include encrypted network transport, protected password hashing, secure session cookies, role-based access, separation of staff and customer sessions, permission checks for sensitive actions, audit records, rate and input controls, isolated custom content and restricted integration permissions.

We use managed infrastructure, least-privilege access, deployment review, backups appropriate to the service and monitoring of operational errors. Recovery objectives depend on incident scope; no architecture can guarantee zero downtime or zero data loss.

Use a unique password, protect the email account tied to LENK, review staff permissions, disconnect unused integrations, remove former team members and verify unexpected support requests. Do not share session links, reset links, credentials or integration secrets.

Authorized senior support may open a time-limited, audited support session to an account when needed to investigate or fix a customer issue. Access is role-restricted, linked to an actor and target, and can be ended. Staff should never ask for a customer password.

Send a clear report to security@link.bi with the affected URL, reproduction steps, impact and safe evidence. Do not access other people’s data, degrade the service, use social engineering, demand payment before disclosure or publish details before we have had a reasonable opportunity to respond.

We investigate credible security events, contain impact, preserve relevant records, restore safely and notify affected parties or authorities when legally required. Notification timing and detail depend on confirmed facts and legal obligations.