Privacy policy
Version 1.0 · Last updated 29 September 2026
What we collect, why we are allowed to collect it, how long we keep it, and how to get it back or have it deleted.
- Who we are, and what this covers
- The law we work under
- What we collect
- What we do not do
- Why we are allowed to process it
- Deposits are public and permanent
- Cookies
- How long we keep it
- Who processes it for us
- Requests from authorities
- Keeping it safe
- Your rights
- Children
- Changes to this policy
- Contact and complaints
01Who we are, and what this covers
The Jugaad Archive (“the Archive”, “we”, “us”) is an open access archive for research, theses, papers, essays and literary work produced in Pakistan. Contact the archive at hello@purplepixl.org.
This policy explains what personal data we collect when you browse the Archive, create an account, or deposit a work; why we collect it; how long we keep it; who else processes it; and what you can ask us to do about it.
It applies to this website only. It does not apply to any other site we link to, including the repositories, journals and libraries we point readers towards.
02The law we work under
Pakistan does not yet have a comprehensive data protection statute in force. The Personal Data Protection Bill has been through several drafts and has not been enacted. We do not treat that as permission to be careless, and we are not waiting for it.
We align our practices with:
- the National Cyber Security Policy 2021, which requires the confidentiality, integrity and availability of personal data to be safeguarded;
- the data protection guidelines issued by the National Cyber Emergency Response Team (PKCERT) for organisations handling personally identifiable information — including classifying data by sensitivity, encrypting it, enforcing multi-factor authentication, retaining personal data only as long as the law requires, and disposing of what is no longer needed;
- the Prevention of Electronic Crimes Act, 2016 (PECA), including the requirement in section 32 to retain traffic data for at least one year and the safeguards in section 38; and
- the Electronic Transactions Ordinance, 2002 (LI of 2002) on the handling and originality of electronic records.
We extend the same set of rights to every user, wherever you are. If you are in the European Union, the United Kingdom, or another jurisdiction with its own data protection law, and that law gives you rights beyond the ones listed in section 12, we will honour them too.
03What we collect
| What | When | Why |
|---|---|---|
| Name, email address, and an optional profile image | When you create an account | To identify you, sign you in, and contact you about your deposits |
| A hashed password | When you register with an email and password | To authenticate you. We never store your password in a form we can read |
| Account identifiers and access, refresh and identity tokens | If you sign in with a third-party provider | To keep you signed in and to perform the actions you ask for |
| IP address, browser user agent, and session times | Automatically, on sign-in | Session security and fraud prevention, and because PECA s. 32 requires us to retain traffic data |
| The works you deposit, their metadata, and anything personal you put inside them | When you deposit | To archive, preserve and publish them — this is the service |
| Affiliation and verification information | If you submit that you are affiliated with a university | To confirm an affiliation and keep the record accountable. Optional |
| Your correspondence with us | When you email us | To answer you and to keep a record of decisions we make |
| Error reports and diagnostic data | When something breaks | To find and fix faults |
We do not ask for, and do not want, sensitive personal data — identity or passport document numbers, financial details, medical information, biometric data, or data about your religion, ethnicity or political views. Please do not put that information in a deposit or in an email to us.
04What we do not do
- We do not sell your personal data, and we never will.
- We do not run advertising, and we do not embed advertising or social-media trackers.
- We do not run analytics that profile you across other sites. The Archive currently has no analytics product installed at all.
- We do not place deposits behind a paywall, and we do not sell access to them.
- We do not use your data to train machine learning models, or license it to anyone who would.
05Why we are allowed to process it
Under the Contract Act, 1872 and the Electronic Transactions Ordinance, 2002, our agreement with you is a contract. We process most of your data to perform it — creating your account, authenticating you, archiving and publishing what you deposit, and answering you when you write.
Beyond that, we rely on:
- Legal obligation — retaining traffic data for at least one year, and responding to lawful orders and directions under PECA, 2016.
- Legitimate interest — keeping the Archive secure, preventing abuse and spam, debugging faults, and keeping a record of editorial and takedown decisions. We balance this against your interests, and you may object at any time.
- Consent — for anything optional and specific, such as publishing a profile image or verifying an affiliation. You can withdraw consent at any time; it will not affect anything done before you withdrew it.
06Deposits are public and permanent
Read this before you deposit. It is the single most important thing on this page.
A deposit is published. Anyone can read it, cite it, and — depending on the licence you chose — reuse it, including outside Pakistan, for as long as the Archive exists.
Anything inside a deposit is therefore public: your name and affiliation in the metadata, acknowledgements, the ethics section of a thesis that names participants, a literary work with a real address in it, an email address, a photograph of an identifiable person. Depositing does not remove it from the record, and the licence you granted us is irrevocable.
We will remove or restrict a deposit under the process in the Terms and Conditions where there is a rights, privacy or safety ground to do so, and we encourage you to ask. But removal leaves a public note that the record was withdrawn, and it does not reach copies other people have already downloaded, cached, or cited.
If you need to include identifiable or personal information about someone else, get their consent first.
07Cookies
We use one class of cookie: the ones needed to keep the site working and to keep you signed in. We do not set advertising or analytics cookies, so there is nothing here for you to opt in or out of, and no consent banner is shown.
| Cookie | Purpose | Set by | Lifetime |
|---|---|---|---|
| Session cookie | Keeps you signed in and protects your session from hijacking | The Jugaad Archive | 7 days of inactivity; refreshed while you use the site |
| Bot-management cookie | Distinguishes people from automated traffic and protects against abuse | Cloudflare | 30 minutes |
If we ever add anything that is not strictly necessary — analytics, embedded media, an external font, anything that tracks you — we will ask for your consent first, and this policy will be updated before it goes live.
You can clear or block cookies in your browser. Blocking the session cookie will stop you signing in, but you can still read the Archive.
08How long we keep it
We keep personal data only for as long as we need it or as long as the law requires, and then we delete it. The periods below are the ones we actually apply.
| What | Kept for | Then |
|---|---|---|
| Account details — name, email, profile image | While your account is open, plus 90 days | Deleted |
| Session and traffic data — IP address, user agent, session times | 12 months | Purged. PECA s. 32 requires a minimum of one year |
| Password verification and reset tokens | 24 hours after they expire | Purged |
| Third-party sign-in tokens | While the account is linked | Deleted when you unlink it or delete your account |
| Deposits and their metadata | Indefinitely | Retained. This is what an archive is for |
| Withdrawn or retracted records | Indefinitely | Metadata, persistent identifier and a withdrawal note; files removed |
| Emails you send us | 3 years | Deleted |
| Error reports and diagnostics | 90 days | Deleted automatically |
| Backups | 35 days, rolling | Overwritten |
We may keep data longer where we are legally required to — for example where a dispute, a complaint, or a court order is live, or where a limitation period under the Limitation Act, 1908 has not yet run. Where that happens, we keep only what is necessary and stop using it for anything else.
09Who processes it for us
We are an open access archive. We do not run our own servers, and we rely on a short list of infrastructure providers. They process personal data on our instructions and for our purposes only.
| Provider | What it does | What it sees |
|---|---|---|
| Cloudflare | Hosts and serves the site, and shields it from attack | Requests, IP addresses, and content served |
| Neon | Hosts the database | Account records, deposits and metadata |
| Sentry | Collects error reports so we can fix faults | Technical diagnostics attached to an error; set not to include your personal data by default |
| Resend | Delivers transactional email | Your email address and the contents of the message we send you |
Cross-border transfers. These providers operate infrastructure outside Pakistan, so your data will be stored and processed outside Pakistan. We choose providers that offer contractual data protection commitments and encryption in transit. We will keep this list current, and we will not add a processor that materially changes how your data is handled without updating this policy.
Other than the above, we share personal data only:
- where you have asked us to;
- where we are legally required to, as set out in section 10; or
- with a successor organisation, as described in section 12 of the Terms and Conditions, and only on the terms set out there.
10Requests from authorities
We will only hand over user data to an investigation agency or an authority where we are legally obliged to: on a court order, on a warrant, or on a lawful direction, as contemplated by PECA, 2016.
We publish a transparency note whenever we can lawfully do so, and we will tell you if your data is requested unless we are barred from telling you. Where we are served with a confidentiality notice, we may be legally required to keep the existence of an investigation from you for up to 14 days, and for longer if a court authorises an extension.
We will challenge a request that is overbroad or unlawful, and we will only disclose what the request actually compels.
11Keeping it safe
Our measures follow the PKCERT data protection guidance and the National Cyber Security Policy 2021. In practice:
- encryption in transit for everything the site serves;
- passwords stored only as salted hashes, and never logged or readable by us;
- strict access control, so that only the people who need access to a system have it, with multi-factor authentication for administrative accounts;
- dependencies and systems kept patched and monitored;
- data classified by sensitivity, and treated according to its classification; and
- backups, with the retention period stated in section 08.
No system is perfectly secure, and we will not pretend otherwise. If a breach occurs that is likely to affect you, we will tell you and the relevant authority without undue delay, tell you what we know, and tell you what we are doing about it.
12Your rights
You can ask us to do all of the following, and we will not charge you for it. Write to hello@purplepixl.org, and tell us which right you are exercising. We answer within 30 days. We may ask you to confirm who you are, but only to the extent necessary.
- Access — tell you what personal data we hold about you, and give you a copy.
- Correction — fix data that is inaccurate or incomplete.
- Deletion — delete your account and the personal data that goes with it, subject to what follows.
- Restriction — pause our use of your data while a question about it is resolved.
- Portability — give you your data in a structured, commonly used, machine-readable format.
- Objection — object to processing we justify by legitimate interest.
- Withdraw consent — for anything you consented to, at any time.
The one important limit. Deposits are the exception. Once a work has been published in the Archive, and someone may already have cited it, we cannot simply erase it, because the licence in section 06 of the Terms and Conditions is irrevocable. Instead you can ask for the Record to be withdrawn: the files come down, and the metadata, identifier and a withdrawal note stay. Section 11 of the Terms and Conditions sets out how that works. Your account and the personal data attached to it are deleted separately and in full.
You can also complain to us — see section 15 — and, once the Personal Data Protection Bill is in force and a regulator exists, to that regulator.
13Children
The Archive is not directed at children under 13, and we do not knowingly hold accounts for them. If you believe a child under 13 has given us personal data, write to hello@purplepixl.org and we will delete it.
If you are between 13 and 18, you may hold an account and deposit work only with the consent of a parent or guardian, who should read section 06 with you.
14Changes to this policy
We may update this policy. For a material change we will post a notice on the site at least 30 days before it takes effect, and email account holders.
Every version is dated, and we keep the previous versions available on request, so you can see what changed and when.
15Contact and complaints
For anything on this page — a rights request, a question, a deletion request, or a complaint about how we have handled your data — write to hello@purplepixl.org with “Privacy” in the subject line.
We acknowledge within 5 working days and answer within 30 days. If you are not satisfied with our answer, tell us, and we will escalate it to a director. Once Pakistan has a data protection regulator in force, you will also be able to complain to it, and we will publish how.
For copyright, privacy or safety problems with a specific deposit, use the removal process in section 11 of the Terms and Conditions — it gets to the right place faster.
