Isolation between organizations
Every organization works in a separate space. Filtering is enforced in code and again at row level in the database, so even a faulty query does not cross the line.
CVs, pay, security clearance and contracts. The data that moves through LinkMatch is among the most sensitive an organization holds, and the system was built accordingly: isolation between organizations, action-level permissions, and a record of every sensitive action.
Every organization works in a separate space. Filtering is enforced in code and again at row level in the database, so even a faulty query does not cross the line.
230+ permissions and 30+ roles. Access is checked by the action being requested, not by the name of the role.
Passwords are stored with Argon2id. Two-factor sign-in, sign-in with a Microsoft or Google account, and rate limiting on sign-in attempts.
Sensitive actions, sign-ins and administrative actions are recorded in separate logs: who, what and when.
Secrets for external connections are encrypted with AES-256-GCM. Traffic is encrypted, and files are kept in dedicated storage.
Every API call passes schema validation. An uploaded file is checked by its content, not only by its extension.
Before text is sent to a language model, identifying details are removed from it.
CVs and documents are read as data, not as instructions.
Noa sees and does nothing the user is not personally allowed to see or do.
Each organization has a usage quota and a daily spend cap, so there are no surprises.
The SaaS edition runs in the AWS Tel Aviv region, in an account dedicated to the product. Files and database backups are kept in separate storage in the same account.
For organizations whose data does not leave the building: exactly the same system, installed in your environment and under your control.
Card details never pass through the system. Payment happens on the payment provider’s hosted page.
Six clearance levels, separate roles for the clearance coordinator and the security officer, and an alert before expiry.
Recorded consent before sharing, a profile without identifying details in the shared pool, and export or deletion at any time.
Detailed security documents, including architecture and procedures, are shared as part of a procurement process and under a confidentiality agreement.