What happens to what you paste or attach here — in plain language.
A verification request is processed in memory for the duration of that
request only. There is no database and no account system. When you attach
a document, it is written to a temporary file so it can be scanned, and
that file is deleted immediately after the check completes — in a
finally block, so it is removed even if the check fails
partway through.
"312 chars of
message text", not the message itself. The full text of what you
paste is never sent to PRISM.None of these receive your name unless it appears in the company name or sender address you typed, which are necessary inputs to the checks themselves.
The optional "your email" field is used once, locally, to confirm a signed attestation was issued for you — by comparing a one-way hash, never the address itself. It is combined with the issuing domain before hashing, so the same address hashed for two different employers does not produce a matching value either. Leave it blank and that one check is simply skipped; nothing else on the page requires it.
Like any web service, requests are logged with a timestamp, path, status code, timing, and the calling IP address — for reliability and abuse prevention (see Terms). Logs never include the content of your message, company name, attached document, or attestation token.
An institutional deployment (for example, an international student office embedding this tool for its own students) may agree to additional terms covering usage volume and support — those are handled directly, not through this page, and do not change the handling described above unless stated in writing.
This is verification tooling built for job seekers, offered free. If you have a question about this policy, raise it through the project's repository.
Last updated alongside this deployment's current version.