Introduction
PixelScale Studio is an independent, free tool run by one developer. We built it this way because the images you scale are often work in progress that you would rather not hand to a stranger's server. That principle shapes everything below: your images are processed inside your own browser and are never transmitted to us.
1. Client-Side Processing Architecture
The pixel art scaler runs entirely inside your web browser using the built-in HTML5 Canvas API. When you drop a file onto the page, the scaling happens on your own device. Your image is never uploaded to us, never written to any server we control, and never seen by us. It does not pass through a backend, and we have no copy of it.
2. Cookies, Analytics, and Third-Party Requests
We set no cookies of our own. We do not run Google Analytics, Facebook Pixel, or any similar analytics or advertising tracker, and the scaler does not write anything to your device's local storage. There are no accounts to create and nothing to sign in to.
We would rather be straight with you about the rest, though. Like almost every website, this one loads some files from other companies' servers, and those companies necessarily see your IP address in the process. They operate under their own privacy policies and may set their own cookies.
Third parties that receive a request from your browser:
- fonts.googleapis.com / fonts.gstatic.com — Google Fonts, which serves the typefaces
- cdnjs.cloudflare.com — serves the Font Awesome icon stylesheet
None of these see your images. Your image data is never included in any of these requests, because it never leaves your browser in the first place.
This site is hosted on GitHub Pages, so the hosting provider also processes technical request data such as your IP address to serve you the page. If we ever add advertising of our own, we will update this policy and ask for your consent before setting any non-essential cookie.
3. Who Is Responsible for This Site
PixelScale Studio is an independent project run by a single developer, Kitsorix. There is no company behind it and no external funding. For the purposes of data protection law, that individual is the data controller for the limited information described on this page.
You can reach us through our GitHub profile or the About page. Because we are one person, a message may take a little longer to answer than it would from a support team, but every message is read by the same developer who runs the site.
4. Your Data Protection Rights
If you are in the EEA or the UK, you have the right to ask us for access to any personal data we hold about you, to have it corrected or erased, to restrict or object to how it is used, and to complain to your country's data protection authority. Contact us and we will respond.
In practice there is very little to hand over. We do not operate accounts, we do not sell data, we do not run analytics, and we never receive your images. The only personal information we ever hold is what you choose to send us when you contact us, and we keep that only for as long as it takes to deal with your matter.
Third-party providers listed above are separate controllers or processors for the data they handle on their own behalf. Requests concerning their data should go to them, though we are happy to point you the right way.
5. Changes to This Policy
If this policy changes, the date at the top of the page will change with it. If we make a material change — for instance if we introduce advertising — we will update this page before the change takes effect, and describe exactly what is different. Continuing to use the site after a change means you accept the updated policy.
Questions about this policy?
If you have any questions or concerns about our privacy practices, please reach out through our About page or visit our GitHub repository. For rules about using the tool, see our Terms of Use; for copyright matters, see our Copyright Policy.