1. What We Host
PixelScale Studio is a static website. It does not host, store, or display any user-generated content. All image processing is performed 100% client-side in your browser, and images never leave your device. The only content on this Site is the Site's own pages, documentation, and the tool itself.
2. What We Protect, and What We Don't
Not everything on this site is protected the same way, and we would rather be precise about it than claim more than we actually hold. Here is the honest breakdown.
The tool's source code — open, MIT licensed. The scaling tool is published under the MIT License. You may read it, run it, modify it, and redistribute it, including commercially, as long as you keep the licence text. See the LICENSE file. This is the one part of the site you are unambiguously free to build on.
The name, design, and layout — all rights reserved. The PixelScale Studio name, logo, page design, and visual identity are ours and are not covered by the MIT Licence. You may not copy them onto another site or use them in a way that suggests we endorse yours.
The written guides — free to reuse, no exclusivity promised. Our guides are published free of charge and you are welcome to quote, translate, summarise, or republish them, ideally with a link back to the original. Some were drafted with AI assistance. Because material produced entirely by a machine may not attract copyright protection in the EU, the UK, or the US, we cannot honestly promise you exclusive rights in that text, and we will not claim any against you for reusing it. What we do ask is that you do not present the guides as entirely your own, and that you do not present our explanations as professional legal or financial advice.
Your images — yours. We claim no rights over the images you load into the tool or the files it produces. Those never touch our servers. What rights you have in them depends entirely on where the images came from, and it is your responsibility to know.
This Site does not knowingly display copyrighted material belonging to third parties. Where tools, games, consoles, or software are mentioned by name, they belong to their respective owners and are referenced for identification only — see our Legal Disclaimer.
3. Reporting Copyright Infringement (DMCA)
If you believe in good faith that material on this Site infringes your copyright, you may submit a takedown notice. Because the Site hosts no user content, infringement claims are limited to the Site's own pages.
Your notice must be submitted to us and include the following, as required by the DMCA:
- Identification of the copyrighted work claimed to be infringed.
- Identification of the material claimed to be infringing and where it is located (URL).
- Your contact information (name, email address, and mailing address).
- A statement that you have a good-faith belief that the use is not authorized by the copyright owner, its agent, or the law.
- A statement, under penalty of perjury, that the information in your notice is accurate and that you are the owner or authorized to act on the owner's behalf.
- Your physical or electronic signature.
Submit your notice through our GitHub profile. Please read what you are agreeing to before you submit — the statements carry legal weight, and submitting a notice you do not genuinely believe in can expose you to liability.
4. Our Response
We take copyright notices seriously. Valid notices are reviewed promptly, and infringing material is removed as quickly as possible. Because this is a hobby project run by a single developer, removal may occasionally take a little longer than on commercial platforms - we appreciate your patience.
5. Counter-Notification
If you believe material was removed by mistake, you may submit a counter-notification through the same form, including: identification of the removed material and its previous location, your contact information, and a statement of good-faith belief that the removal was mistaken.
Read this before you send one
A counter-notification contains a declaration made under penalty of perjury. Knowingly sending a false one can expose you to liability, so please only send one if you genuinely hold the rights you are asserting.
By the same token, we do not automatically file counter-notices on our own behalf. Portions of this site were drafted with AI assistance, and material generated by a machine may attract no copyright protection at all in the EU, the UK, or the US. We will not swear to ownership of rights we do not hold. Where we have removed something in error, we will say so and put it back.
6. Good-Faith Notices and Trademark Concerns
We ask that every complaint arrive in good faith. A notice is a legal document, not a support ticket, and a misrepresentation can expose you to liability under the DMCA.
The same process also handles trademark concerns. If you own a brand that is described inaccurately on this site, or you would rather a reference to your product were removed, tell us through our GitHub profile and we will look at it. We would much rather correct a genuine inaccuracy than have a lawyer letter about one.
If you are unsure whether your situation qualifies as infringement, please consult a lawyer before filing. We would rather receive one accurate notice than five speculative ones.
For other legal questions, see our Terms of Use and Disclaimer.