Contact
CubeScroll is maintained by one person, and every message goes to one inbox:
There is no contact form and no ticket queue on purpose — a form would need storage, and this site is built to hold nothing about you. Email is the whole support channel, and it is read.
Reporting a bug
Bug reports are genuinely welcome. The ones that get fixed fastest say:
- What you forged — roughly what the image was (a photo, a logo, a transparent PNG) and its approximate dimensions. You do not need to send the image itself.
- The settings — grid rows, cube faces (full image or flat), and any theme or palette flags. If you used the command line, the exact command is ideal.
- Where you saw it — browser and operating system, desktop or phone. Rendering problems are very often GPU-specific, so this matters more than it looks like it should.
- What you expected instead.
Other reasons to write
- Documentation that is wrong or unclear. This counts as a bug. If something in the documentation, the guides or the FAQ sent you down the wrong path, saying so is the fastest way to get it corrected.
- Feature requests. Useful ones describe the page you were trying to build and what stopped you, rather than naming a setting to add — the underlying problem is usually the more interesting half.
- Licensing. The short answer is on the FAQ: the project is MIT-licensed and the code it generates is yours, commercial use included, with no attribution required. Write if your situation is not covered there.
- Privacy. Requests and questions about data go to the same address; what the site does and does not collect is set out on the privacy page.
What this project is not
It is an independent tool, not a company, and it is not affiliated with three.js, Google, or any of the services linked from this site. There is no paid support tier and no service-level agreement — replies come as fast as one person can manage, which is usually quick but is never a guarantee. More about who builds it and why is on the about page.