HR documents that reach one person, and nobody else.
Offer letters, salary revisions, payslips, tax forms and investigation reports are personal by definition. FileLink sends each one to a single recipient, who must enter a one-time passcode sent to their email, and gives candidates and employees a secure way to send documents back, so personal data stops piling up in inboxes.
HR runs on personal data, and email spreads it
Keeping personal data only as long as needed, and only with the people who need it, is a basic data-protection principle. Email makes both hard.
An HR team sends and receives more personal data than almost any other function. Most of it travels as email attachments: an offer letter with a salary figure, a payslip, a Form 16, a warning letter. Coming the other way: PAN and Aadhaar copies, bank details, educational certificates and medical records from candidates and employees.
Wrong-recipient risk. One autocomplete mistake sends someone's salary or disciplinary record to a colleague.
Data that never leaves. Every attachment stays in the sender's and receiver's mailboxes for years, long after it's needed.
Collection by email. Asking candidates to email their ID documents puts sensitive data in shared HR inboxes with no expiry and no audit trail.
Across the employee lifecycle
Hiring
What you send: offer and appointment letters. Collect: ID documents, certificates, previous payslips, bank details.
With FileLink: send the offer as a view-only link with a one-time passcode (OTP) sent to the candidate's email, and an expiry that matches the offer's validity. Give the candidate a Secure Receiving link to upload their documents directly to you.
Pay and benefits
What you send: payslips, salary revision letters, tax forms such as Form 16.
With FileLink: send each employee their own link. Allow downloads for documents they need to keep, such as tax forms, and keep everything else view-only.
Performance and investigations
What you send: performance improvement plans, warning letters, investigation reports, documents for an internal committee.
With FileLink: restrict each document to the named people, require an NDA or confidentiality acknowledgement, watermark every page, and see exactly who accessed it and when.
Exit
What you send: relieving letters, full-and-final settlement statements, experience letters.
With FileLink: send documents to the employee's personal email with OTP, and set links to expire once the exit is complete.
What HR teams use most
- One-time passcode (OTP).. Only the named employee or candidate can open the document.
- Secure Receiving.. A link for candidates and employees to upload documents straight to HR, with no account and no email attachment.
- View-only by default.. Downloads and printing stay off unless you allow them.
- Dynamic watermarks.. The viewer's email and IP on every page.
- Expiry.. Links close automatically when the offer lapses or the process ends.
- Activity log.. A record of every open, with timestamp, IP and device.
- Access restrictions.. Limit a link to named people or your company's email domain.
- Outlook add-in.. Send letters from Outlook as protected links.
FileLink vs email for HR documents
| FileLink | ||
|---|---|---|
| Sent to the wrong person | Readable immediately | Passcode goes to the intended email only |
| How long it's kept | Indefinitely in mailboxes | Expires when you choose |
| Collecting ID documents | Attachments in a shared inbox | Upload link, stored encrypted |
| Who saw it | Unknown | Logged with timestamp |
| Where it's stored | Every mailbox involved | Encrypted |
Illustrative example
This example is illustrative, not a customer case study.
An HR team hiring 40 people in a quarter sends each offer letter as a FileLink that expires after seven days, with OTP on. Each candidate also gets a Secure Receiving link for their documents. At the end of the quarter, no ID documents sit in the shared HR mailbox, every offer link has closed on its own, and the activity log shows when each candidate opened their offer.
Security, in short
Files are encrypted in transit (TLS) and at rest (AES-256-GCM, a unique key per file), stored on infrastructure certified to ISO 27001 and SOC 2, and never read, summarised or used to train AI.