Security Practices
We built SarkariPixel to keep exam uploads private. This page explains the safeguards in place today.
1. On-device architecture
Image and PDF work happens locally via HTML5 Canvas, WebAssembly, and pdf-lib. No uploads reach our servers, which eliminates centralized storage risks.
2. Secure browsing
The web app is served over HTTPS with HSTS enabled on SarkariPixel.in. Always check the lock icon before uploading sensitive documents.
3. Dependency audits
We pin and monitor third-party libraries (sharp, pdf-lib, pdf.js). Automated alerts notify us of CVEs, and we patch within 72 hours of critical disclosures.
4. Local storage discipline
Only lightweight UI preferences are stored in localStorage. We never save images, PDFs, or personal data in the browser cache.
5. Responsible disclosure
If you discover a vulnerability, email security@sarkaripixel.in. Provide details so we can reproduce the issue. We acknowledge every report.
6. Incident response
Should an incident occur, we will patch, publish a postmortem on this page, and email affected users (if contact info was provided) with remediation steps.
7. Roadmap
- Signed desktop builds for offline-first workflows.
- Optional encrypted preset sync using passphrase-protected storage.
- Security.txt file on the root domain for easier researcher contact.