Security and privacy summary

Each institution runs its own RankLyst instance with its own database. Your applicant data never sits in the same table as another institution's.

Every applicant record and letter is stored in an encrypted database, not just protected in transit.

Institutions can sign in with their own institutional login (single sign-on). Passwords, where used, are salted and hashed (PBKDF2, 390,000 iterations), and accounts lock after repeated failed logins.

Admins manage uploads, accounts and deletions. Reviewers can view files and comment; they can't change accounts or delete records.

Every upload, role change and deletion is logged. When a record is deleted, the history of who, when and why survives; the applicant's own data does not.

You set a retention window. RankLyst lists the records past it; an admin reviews the list and confirms before anything is permanently removed. Nothing is deleted automatically.

Document text is sent to Anthropic's Claude API to extract the evidence. We'll walk you through what that means for your data agreements before you upload anything real.

Race, ethnicity, disability status, citizenship or visa status and other protected characteristics are excluded at the schema level: never extracted into a field, flag or score. An applicant's own personal statement is kept in full, as your committee already reads it.

Every extracted fact and flag links back to the sentence in the source document, so a reviewer can check it.