Policy document

Privacy policy

This policy explains what information Paper Khoj receives, why it is needed, and how it is protected when you use the archive or send material for review.

Published by
Paper Khoj
Last updated
11 September 2026
Status
Current

01Information we receive

You can browse the public archive without creating an account. Information is received only when you choose to contribute material, report a problem, or use a private editorial account.

A contribution or report may include programme and course details, an exam year, notes, uploaded files or shared links, the page being discussed, and an optional email address.

02How information is used

Submission details are used to identify, verify, organise, and review academic material. An optional email address is used only when an editor needs clarification about that submission or report.

Paper Khoj does not sell personal information or use contribution details for advertising or marketing email.

03Contributed files and links

Uploaded material is staged privately for editorial review. It is not published automatically. Editors check source context, rights, page order, and readability before deciding whether any material can enter the public archive.

Shared links may be opened by an editor solely to access and verify the material you submitted.

04Editorial accounts

Editorial access is protected with secure, encrypted token authentication. Editorial permissions are stored in protected application metadata and cannot be elevated or modified through the public interface.

05Analytics and cookies

Paper Khoj does not sell personal information or run intrusive behavioural profiling. Any future non-intrusive sponsorships or banners introduced to keep the archive free for students will not compromise your contribution records. Authentication cookies may be used for authorised editors to maintain a secure private session.

06Questions and requests

To ask about information connected to a contribution or report, use the Report a problem page and include enough context for the relevant record to be located.