/ta/ and /hi/), not a saved preference. The only data that exists
anywhere else is the ordinary web-server log kept by whoever hosts these files. The single way a
photo leaves your device is if you tap Share and pick an app to send it to.
1. How your images are handled
When you choose a photo or signature, the file is read by your browser and drawn onto an HTML canvas. Resizing, cropping, background clean-up, compression and the name-and-date stamp all run as JavaScript on your own device. The finished file is handed back to you as a download generated locally.
At no point is the image transmitted. There is no upload endpoint, because there is no server that would receive one. If you disconnect from the internet after the page has loaded, every part of the tool still works.
2. This is enforced, not just promised
Any site can claim it does not upload your files. This one ships a
Content
Security Policy with a connect-src allow-list.
That directive names the only destinations this page may contact:
connect-src https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com
Everything else is refused by your browser — every other domain, and any upload endpoint we might add. The restriction is applied by the browser, not by us, so it holds even if our code were changed or compromised. You can confirm it: open developer tools, look at the response headers for this page, and read the policy.
We should be straight about what changed. This header used to read connect-src 'none',
which meant the page could reach nothing at all. Adding analytics required loosening it, and that is a
real reduction in what we can prove to you. What it still guarantees is that your image data
has nowhere to go: it is never sent to Google Analytics, which receives page addresses and
visit counts, not file contents.
If we remove analytics, the header goes back to 'none' — and a changed header is
visible to anyone who looks.
3. The Share button is the one exception
On phones, the result screen offers a Share button alongside Download. Tapping it opens your operating system's own share sheet and hands the finished file to whichever app you then pick — WhatsApp, Gmail, Files, and so on.
That is a deliberate act of sending your photo somewhere, so it is worth being precise: the file still never passes through us or through this page's network connection. The handover happens between your browser and your operating system. But once you choose a destination, your image is in that app's hands and subject to its privacy policy, not ours.
Nothing is shared unless you tap the button and then choose a target. If your browser does not support the feature, the button is simply not shown.
The HEIC converter uses a self-hosted decoder and a local browser worker. Images stay on your device. Background correction and print-sheet generation also run locally. Worker execution is permitted by the security policy; it does not permit photograph uploads.
4. What we do not collect
- No name, email address, phone number or postal address.
- No images, signatures or documents.
- No account, because there is nothing to sign in to.
- No payment details, because nothing is for sale.
- No advertising identifiers, remarketing, or cross-site profiles. Analytics, if you allow it, is described in the next section.
5. Analytics
We use Google Analytics 4 to count visits and see which exam pages are opened. It runs only if you press Allow on the bar that appears on your first visit.
Until you choose, nothing is loaded and no cookie is set. If you press No thanks, nothing is loaded, the choice is remembered, and you are not asked again. There is no "consent by scrolling" and no pre-ticked box.
If you do allow it, Google receives the page addresses you open on this site, approximate location derived from your IP address, and general device and browser information. IP anonymisation is on. Google Signals and advertising personalisation are explicitly disabled, so this is used for traffic measurement and not for advertising, remarketing or cross-site profiling.
Your photographs and signatures are never part of this. They are not uploaded, not measured, and not transmitted to Google or anyone else. Analytics sees which page you were on, not what you did with your file.
Why we turned it on: with 128 exam presets and almost none verified against their notifications, we need to know which pages people actually open so the verification work goes where it matters. You can change your choice at any time.
6. Cookies and browser storage
We set no cookies of our own. Google Analytics sets two, and only if you allow it — see the cookie policy.
We use localStorage for two things, neither of which is written unless you take the
action that causes it. The language is not one of them: Tamil and Hindi are separate pages
(/ta/ and /hi/), and the switcher is a link to that page.
rx-signatures— signatures you drew on the signature pad and chose to keep, so you do not have to redraw one for every exam. Written only if you press Save for later.rx-consent— whether you allowed or declined analytics, so you are not asked on every page. Written only when you press one of those two buttons.
If you allow analytics, Google Analytics also sets its own cookies (_ga and
_ga_<id>). Those are sent to Google with later page views. Decline, and they
are never written. The cookie policy lists them.
The two localStorage entries stay in your browser on that one device. They are
not attached to network requests, another website cannot read them, and we cannot see them.
Saved signatures can be deleted individually from the pad. Clearing your browsing data removes
those entries and, if you allowed analytics, the Google cookies as well. On a shared computer,
delete saved signatures before you leave — or do not save them at all. Full detail is on the
cookie policy page.
7. Server logs
These pages are static files served by Firebase Hosting, a Google service. Like every web server, it records ordinary request logs — typically your IP address, the time, the page requested, and your browser's user agent string. This is a routine part of serving a website and applies to the HTML, CSS and image files themselves. It has nothing to do with your photo, which is never part of any request.
We do not combine these logs with anything else, and we do not attempt to identify anyone from them. The retention period is set by the hosting provider under their own privacy policy.
8. Links to other websites
Each exam page links to the recruitment authority that publishes the rule — SSC, UPSC, IBPS and so on — so you can check the specification against the source. Following one takes you to a site we do not control and whose privacy practices are its own. We receive nothing when you click, and we have no commercial relationship with any of them.
9. Children
The tool is aimed at candidates applying for examinations and is not directed at young children. We do not ask anyone for a name, and we hold no accounts and no files. If analytics is allowed, Google processes the visit data described above — that can include a child's visit if a child uses the site — and we do not keep a separate copy of it.
10. Your rights
Data-protection law gives you rights to access, correct and erase personal data held about you. We hold no account, no stored files and no profile. If you allowed analytics, the visit data described above is held by Google under its own policy, and you can withdraw consent on this site at any time. If you believe we hold something about you, write to us and we will look and tell you honestly what we find.
11. Changes
If this policy changes materially, the date at the top of the page changes with it. There is no mailing list to notify, so the date is the honest signal to watch.
12. Contact
Questions about any of this go to hello@pixfit.in, or see the contact page.