Home / Privacy Policy
Privacy Policy
Last updated: August 2026 · Applies to the UploadEze Chrome Extension and uploadeze.com
Summary
What we collect
What we collect depends on how you use UploadEze. Here is every category, with nothing left out:
Using the free tools, no account
- We collect no personal data. No name, no email, no account identifier of any kind.
- We do not use cookies, analytics, or advertising trackers of any kind.
- Files you compress, resize, crop, convert or edit in the browser tools are never uploaded anywhere.
If you create an account
- Email address — required, used to sign you in and for account emails.
- Name — optional, shown in the dashboard.
- Password — stored only as an irreversible cryptographic hash; we cannot read your actual password.
- Google account ID, name, email and profile photo — only if you sign in with "Continue with Google" instead of a password.
- Usage records — which tool you used, the input/output file size in KB, and when — never the file itself — used to enforce the monthly free limit and show your usage dashboard.
If you upgrade to Pro
- Billing details — your card, UPI or netbanking details are entered directly into Razorpay's payment form; we never see or store them.
- Subscription & invoice records — plan, billing interval, renewal date, Razorpay order/payment/subscription IDs, invoice amount and (if provided) your GSTIN — kept for billing history and tax compliance.
If you use server-side tools (PDF compress, background removal)
- Your file is sent over an encrypted connection, processed in memory, and the result returned. It is never written to disk, logged, or kept — see How the extension works.
Community Knowledge Base (anonymous, no account needed)
- When a portal rejects your upload and reveals its real size/format limit, we may contribute that limit anonymously so other users benefit — see the extension's changelog for the full feature.
- What is sent: the portal's domain (hostname only, e.g.
ssc.nic.in— never the full page URL), a normalised field label (e.g. "passport photo"), the detected size/format limit, and the extension version. - Your IP address and browser user-agent string are combined and passed through a one-way cryptographic hash purely to rate-limit abuse and avoid double-counting the same visitor — the hash cannot be reversed to reveal your IP, and neither your IP nor user-agent is ever stored in readable form.
- This contribution never includes a file, a name, an email, or a full URL. You can opt out at any time in the extension's settings.
If you contact support
- Your name, email address, and the message you send us, so we can reply.
We never do this
- We do not sell your data to anyone, for any reason.
- We do not use your data for advertising, or share it with advertisers.
- We do not read, log, or transmit the files you process in the browser-only tools.
- We do not track which websites you visit, beyond the anonymous Knowledge Base contribution described above (which you can turn off).
How the extension works
When you activate UploadEze on a page, the extension reads the file upload fields on that page to detect their size and format requirements. This information is used only to pre-fill editor settings — it is never stored or transmitted, except for the specific, opt-out anonymous Knowledge Base contribution described above.
Image work — compression, resizing, cropping, and format conversion — is performed locally using your browser's built-in Canvas API, so those files never leave your device. Two features need more processing power than a browser can provide: PDF compression and background removal. For these, the file is sent over an encrypted connection to our own server, processed in memory, and the result returned immediately — the file is never written to disk, logged, or retained.
Permissions & why
Chrome requires us to declare every permission we use. Here is exactly why each one is needed:
activeTabTo read the upload field requirements on the page you are currently viewing, so the editor can pre-fill the correct size and format limits.
scriptingTo inject the processed file back into the upload field after you finish editing, so you do not have to re-select it manually.
storageTo save your editor preferences (such as default compression level) locally on your device. Nothing is synced to a server.
offscreenTo run file processing in an isolated background document so the editor stays responsive while compressing large files.
tabsTo identify and communicate with the browser tab that contains the form you are working on.
<all_urls>File upload forms appear on thousands of different websites. This permission lets the extension work on any domain without requiring a fixed list.
Third-party services
We use a small number of service providers to run UploadEze. We share only what each one needs to do its job — never more, and never for their own marketing use.
Razorpay
Shared: Card, UPI and netbanking details for Pro subscriptions.
Why: Payment processing. Razorpay handles your card/bank details directly — we never see or store full card numbers. We store only the resulting order ID, payment ID, subscription ID, plan, amount and GST details needed for your invoice.
Google Sign-In
Shared: Your Google account ID, name, email and profile photo — only if you choose "Continue with Google".
Why: To create and log you into your UploadEze account without a separate password. If you sign up with email instead, Google is never contacted.
Resend
Shared: Your email address and the content of transactional emails.
Why: To deliver account emails: email verification, password reset, tax invoices, and replies to support tickets. Resend does not use this data for its own marketing.
Our hosting provider
Shared: Your account, usage and billing records, stored in our database.
Why: To run the website, the account system, and the server-side tools (PDF compression, background removal). Standard infrastructure — not an advertising or analytics company.
We do not use any advertising network, and we do not integrate any analytics or tracking pixel service.
Data retention & deletion
- Files processed in your browser stay on your device — we never receive them.
- Files sent to our server for PDF compression or background removal are held in memory only for the few seconds it takes to process them, then discarded — never written to disk or backed up.
- Account, usage and billing records are kept for as long as your account is active, and afterwards only as long as needed for tax and accounting law (invoices), fraud prevention, or dispute resolution.
- Community Knowledge Base contributions are aggregated and anonymous by design; they are not linked to an account and are not deleted individually, since they were never tied to your identity.
- To delete your account and personal data, email creationskiro@gmail.com from your account's email address. We will delete your account data within 30 days, except records we are legally required to retain (such as paid invoices).
Children's privacy
UploadEze does not knowingly collect any information from children under the age of 13. If you believe a child has created an account, contact us and we will delete it.
Changes to this policy
If our data practices change, we will update this page with a new date and update the extension listing accordingly. Continued use of the extension after changes are posted constitutes acceptance of the revised policy.
Contact
Questions about this privacy policy, or a data deletion request? Write to us at creationskiro@gmail.com. We will respond within 48 hours.
This privacy policy applies to the UploadEze Chrome Extension and the uploadeze.com website.