MEGURO Docs
Documentation

Task-oriented technical guidance for practice, evidence, automation, and verification.

Reference and troubleshooting

Contact support

Escalate an unresolved Documentation problem with enough customer-safe context to investigate it.

Scope and proof boundaries

Support context should identify the visible customer-facing failure without exposing secrets, private payloads, customer data, or internal implementation details.

Contact support

Email hello@meguro.io after completing the relevant troubleshooting step. There is no need to send a private diagnostic bundle.

What to include

  • Your account email.
  • The route where the problem appears.
  • The visible store, run, or receipt ID when available.
  • The timestamp and timezone.
  • The exact visible error text.
  • Whether the issue persists after reload.

What never to send

Never send access tokens, API keys, credentials, authorization headers, private request payloads, secrets, or customer PII/data. Remove those values before sending any screenshot or copied text.