Inquiries & Feedback

Let's shape the next puzzle together.

Whether you are a publisher exploring collaboration, a beta tester sharing touch control feedback, or a player reporting a bug, our development team is ready to listen.

Abstract numbered game tiles overlapping in a connected sequence

Direct Contact

We do not use automated help desks. Every email is read by our core game development team.

Testing Applications

Want to be part of our next closed beta? Select "Beta Testing" in the inquiry type below and include your preferred platform (iOS/Android/Web) in the message.

Send a Message

What happens next?

We respect your time. Here is our straightforward process for handling inbound communications so you know exactly what to expect after clicking send.

1

Message Review

Your email bypasses automated filters and lands directly in our studio's shared inbox, monitored daily by our lead developers.

2

Proper Routing

Feedback goes to our game designers, technical issues to our engineers, and partnership requests directly to studio management.

3

Direct Response

We aim to reply to all actionable inquiries within 48 business hours. No generic auto-replies—just real answers from real humans.

Partnership Inquiries

Are you a publisher, investor, or media representative? We are always open to discussing strategic partnerships that align with our vision for minimal, high-quality puzzle games.

  • Publishing Opportunities
  • Press & Media Kits
  • Cross-Promotion

Direct Business Line

For urgent business matters, please select "Publisher / Business Partnership" in the contact form or email us directly.

Email Business Team

How to Provide Great Feedback

When submitting bug reports or gameplay feedback, providing specific details helps our team resolve issues faster and improve the game for everyone.

1. Be Specific

Describe exactly what happened and what you expected to happen.

2. Include Device Info

Mention your phone model and OS version if reporting a technical issue.

3. Steps to Reproduce

List the exact steps you took before encountering the bug.