MCONTACT

What would you like to tell us?

What helped, what got in the way, or what you expected instead. One specific experience is a good place to start.

Email is the primary support channel and may be sent at any time. Telephone support is available only on Korean business days from 10:00 to 17:00 KST. The initial-response target is within two Korean business days and is not a guaranteed resolution time.

Email support@mindstruo.com · Privacy privacy@mindstruo.com · Phone +82 10-3981-5924

PREPARE YOUR MESSAGE

Tell us what happened.

Prepare your message here, then send it from your email app.

Recipientsupport@mindstruo.com

Your message is not sent until you send it from your email app. Reloading clears the form.

Read the full support policy

Email is the primary support channel and may be sent at any time. Telephone support is available only on Korean business days from 10:00 to 17:00 KST. The initial-response target is within two Korean business days and is not a guaranteed resolution time.

Support channels

Primary support channel
support@mindstruo.com · email may be sent at any time
Product and installation
support@mindstruo.com
Billing, subscription, and refunds
support@mindstruo.com
Privacy rights
privacy@mindstruo.com
Security reports
support@mindstruo.com with [SECURITY] in the subject
Telephone support
+82 10-3981-5924 · Korean business days, 10:00–17:00 KST
Telephone closed
Weekends and Korean public holidays

Supported matters

  • Installation, first launch, and updates from an official installer
  • Reproducible product defects on a published supported operating system
  • Google account connection and device or entitlement status
  • Paddle customer-portal access, cancellation, duplicate charges, and refund requests
  • Cloud-account deletion and privacy-rights requests

Outside support scope

  • Legal, tax, medical, or investment decisions based on user files, or professional validation of AI output
  • Unsupported operating systems, modified apps, unofficial installers, and third-party plugins
  • Account recovery or outage resolution inside Google, Paddle, OpenAI, Codex, or Cloudflare
  • Recovery of material without authorization, access-control bypass, or disclosure of another person's account or billing data

Useful information for a request

Do not send passwords, API keys, full card numbers, CVCs, national identifiers, or source documents that are unnecessary to resolve the issue. Redact sensitive material before sending it.

  • MindStruo version and operating-system version
  • The screen, action, and actual result
  • A redacted screenshot or diagnostic record
  • For billing, the order email and Paddle transaction ID

Priority and records

Security vulnerabilities, duplicate charges, account-access failures, and possible data damage are reviewed before general how-to questions.

General support records are kept for one year after closure. Consumer complaint and dispute records are kept for three years as required by applicable law. If an unnecessary password, API key, full payment-card number, or similar secret is found in a request, safe removal is prioritized.

프로젝트 이어가기

Archived September 9, 2026 · Actual app with example data

WHY I BUILT MINDSTRUO

I wanted to build a small app. I ended up building a way to keep going.

In early 2026, ChatGPT and Gemini made me curious about what I could build. I was impressed, but longer, more complicated work still felt difficult. After hearing about vibe coding on YouTube, I wanted to try making a calendar app or a small game.

I barely knew where to start. I pasted AI-generated code into development tools and brought the errors back to the chat. Getting something to run took time. Getting it to run didn't mean it worked well.

I later experimented with more autonomous coding setups, including OpenHands. A different problem became clearer: I kept explaining past decisions, failed approaches, and unfinished work. I started exploring how that context could carry into the next task.

For a while, the coding models in my setup still felt like the larger bottleneck, and I stepped back. Codex was the turning point for me. I found it easier to finish real tasks, so I returned to those earlier experiments and developed them around a Codex workflow.

I didn't want starting the next conversation to mean rebuilding the whole project.

That work became MindStruo. Using it made the connection between decisions, evidence, reviewed results, and next steps increasingly clear. There is still a lot I want to improve and build on this foundation.

Now I want to know whether it helps people who work differently from me. That's why I want to hear about the useful moments, the frustrating ones, and the experience that didn't match what you expected.

MAKE MINDSTRUO MORE USEFUL

사용 경험을 들려주세요.

One concrete experience is enough.

Your message is not stored on a server or sent automatically. Review it in your email app before sending. Do not include passwords, API keys, or sensitive source content.